aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorJens Axboe <[email protected]>2019-10-04 12:10:03 -0600
committerJens Axboe <[email protected]>2019-10-29 10:22:46 -0600
commit33a107f0a1b8df0ad925e39d8afc97bb78e0cec1 (patch)
tree7050b2355408fcc4fa9ab8753e195335a5126c5f /tools/perf/scripts/python/bin/stackcollapse-record
parentc3a31e605620c279163c14068a60869ea3fda203 (diff)
io_uring: allow application controlled CQ ring size
We currently size the CQ ring as twice the SQ ring, to allow some flexibility in not overflowing the CQ ring. This is done because the SQE life time is different than that of the IO request itself, the SQE is consumed as soon as the kernel has seen the entry. Certain application don't need a huge SQ ring size, since they just submit IO in batches. But they may have a lot of requests pending, and hence need a big CQ ring to hold them all. By allowing the application to control the CQ ring size multiplier, we can cater to those applications more efficiently. If an application wants to define its own CQ ring size, it must set IORING_SETUP_CQSIZE in the setup flags, and fill out io_uring_params->cq_entries. The value must be a power of two. Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions