| Message ID | 20190914212345.23861-1-dxu@dxuuu.xyz (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | io_uring: increase IORING_MAX_ENTRIES to 32K | expand |
On 9/14/19 3:23 PM, Daniel Xu wrote: > Some workloads can require far more than 4K oustanding entries. For > example memcached can have ~300K sockets over ~40 cores. Bumping the max > to 32K seems to work pretty well. Should clarify that this is for poll entries, not actual pending IO. But makes sense, thanks, applied. We've got rlimit in place for mem usage, so there's really no reason to put anything else in place before bumping this (arbitrary) limit.
diff --git a/fs/io_uring.c b/fs/io_uring.c index 3c8859d417eb..0dadbdbead0f 100644 --- a/fs/io_uring.c +++ b/fs/io_uring.c @@ -75,7 +75,7 @@ #include "internal.h" -#define IORING_MAX_ENTRIES 4096 +#define IORING_MAX_ENTRIES 32768 #define IORING_MAX_FIXED_FILES 1024 struct io_uring {
Some workloads can require far more than 4K oustanding entries. For example memcached can have ~300K sockets over ~40 cores. Bumping the max to 32K seems to work pretty well. Reported-by: Dan Melnic <dmm@fb.com> Signed-off-by: Daniel Xu <dxu@dxuuu.xyz> --- fs/io_uring.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)