summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2010-10-26 10:27:29 -0400
committerNick Mathewson <nickm@torproject.org>2010-10-26 10:27:29 -0400
commit2cbb1a161e843a0f50f3d42f622d58d5c58c510d (patch)
treeb9d4e61661f421c64d3c10fff152311924e34a21 /include
parent8e342e563060a5dfc4c33bd46a2a6819a5d5b2f7 (diff)
downloadlibevent-2cbb1a161e843a0f50f3d42f622d58d5c58c510d.tar.gz
Make rate-limits go up to SIZE_MAX/EV_SSIZE_MAX, not just INT32_MAX
Someday, when networks are far faster and people frequently want a burst value greater than 2GB per tick, this will seem very forsightful indeed. For now, it breaks ABI, but not source. Fixes bug 3092096.
Diffstat (limited to 'include')
-rw-r--r--include/event2/bufferevent.h7
1 files changed, 5 insertions, 2 deletions
diff --git a/include/event2/bufferevent.h b/include/event2/bufferevent.h
index 5155d251..ee84e084 100644
--- a/include/event2/bufferevent.h
+++ b/include/event2/bufferevent.h
@@ -565,6 +565,9 @@ struct ev_token_bucket_cfg;
*/
struct bufferevent_rate_limit_group;
+/** Maximum configurable rate- or burst-limit. */
+#define EV_RATE_LIMIT_MAX EV_SSIZE_MAX
+
/**
Initialize and return a new object to configure the rate-limiting behavior
of bufferevents.
@@ -582,8 +585,8 @@ struct bufferevent_rate_limit_group;
of Libevent may implement them more tightly.
*/
struct ev_token_bucket_cfg *ev_token_bucket_cfg_new(
- ev_uint32_t read_rate, ev_uint32_t read_burst,
- ev_uint32_t write_rate, ev_uint32_t write_burst,
+ size_t read_rate, size_t read_burst,
+ size_t write_rate, size_t write_burst,
const struct timeval *tick_len);
/** Free all storage held in 'cfg'.