From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: dw@davidwei.uk
Subject: [PATCHSET v5 0/5] Add support for batched min timeout
Date: Wed, 21 Aug 2024 08:16:21 -0600 [thread overview]
Message-ID: <20240821141910.204660-1-axboe@kernel.dk> (raw)
Hi,
Here's v5 of the min-wait patchset. For a full description, see the v2
posting:
https://lore.kernel.org/io-uring/20240215161002.3044270-1-axboe@kernel.dk/
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 master with for-6.12/io_uring pulled in.
Changes since v4:
- Use READ/WRITE_ONCE consistently with iowq->hit_timeout
- Unify how io_cqring_timer_wakeup() handles ring types by always using
wake_up_process().
- Fix race in min timer wakeup with DEFER_TASKRUN
- Don't reset ctx->cq_wait_nr if timeout has been hit
include/uapi/linux/io_uring.h | 3 +-
io_uring/io_uring.c | 191 +++++++++++++++++++++++++---------
io_uring/io_uring.h | 4 +
3 files changed, 150 insertions(+), 48 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-08-21 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 14:16 Jens Axboe [this message]
2024-08-21 14:16 ` [PATCH 1/5] io_uring: encapsulate extraneous wait flags into a separate struct Jens Axboe
2024-08-21 14:16 ` [PATCH 2/5] io_uring: move schedule wait logic into helper Jens Axboe
2024-08-21 14:16 ` [PATCH 3/5] io_uring: implement our own schedule timeout handling Jens Axboe
2024-08-22 13:22 ` Pavel Begunkov
2024-08-22 15:27 ` Jens Axboe
2024-08-21 14:16 ` [PATCH 4/5] io_uring: add support for batch wait timeout Jens Axboe
2024-08-21 18:25 ` David Wei
2024-08-21 18:38 ` Jens Axboe
2024-08-21 18:54 ` David Wei
2024-08-22 13:46 ` Pavel Begunkov
2024-08-22 15:37 ` Jens Axboe
2024-08-22 16:06 ` Pavel Begunkov
2024-08-22 16:14 ` Jens Axboe
2024-08-22 16:24 ` Pavel Begunkov
2024-08-21 14:16 ` [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 \
--in-reply-to=20240821141910.204660-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=dw@davidwei.uk \
--cc=io-uring@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.