From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET v3 0/5] Add support for batched min timeout
Date: Fri, 16 Aug 2024 14:38:11 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
After somewhat of a lengthy delay from v2, here's v3 of this patchset.
We've now validated this actually makes sense and helps for production
workloads where there's a big gap between the peak and slow hours in
terms of load. Having a min time enables the same settings to be used
for peak hours (guaranteeing minimum response time), while avoiding
excessive context switches during lulls.
For a full description, see the v2 posting:
https://lore.kernel.org/io-uring/[email protected]/
As before, there's a liburing branch with added test cases, it can be
found here:
https://git.kernel.dk/cgit/liburing/log/?h=min-wait
The patches are on top of for-6.12/io_uring, and with David Wei's
new iowait feat and enter flag added to avoid conflicts with that.
Changes since v2:
- Rebase on current 6.12 tree, which was mostly centered around Pavel's
rework of the timeout handling and ABS_TIME additions
- Since there's now one more argument for io_cqring_wait(), wrap those
output arguments in a struct ext_arg.
include/uapi/linux/io_uring.h | 3 +-
io_uring/io_uring.c | 187 +++++++++++++++++++++++++---------
io_uring/io_uring.h | 4 +
3 files changed, 147 insertions(+), 47 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-08-16 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 20:38 Jens Axboe [this message]
2024-08-16 20:38 ` [PATCH 1/5] io_uring: encapsulate extraneous wait flags into a separate struct Jens Axboe
2024-08-16 20:38 ` [PATCH 2/5] io_uring: move schedule wait logic into helper Jens Axboe
2024-08-16 20:38 ` [PATCH 3/5] io_uring: implement our own schedule timeout handling Jens Axboe
2024-08-16 20:38 ` [PATCH 4/5] io_uring: add support for batch wait timeout Jens Axboe
2024-08-16 20:38 ` [PATCH 5/5] io_uring: wire up min batch wake timeout Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox