From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: Re: [GIT PULL] io_uring epoll reaping support
Date: Thu, 27 Mar 2025 08:27:24 -0600 [thread overview]
Message-ID: <75d2935a-b560-40bb-aed9-d6cfd885b6a9@kernel.dk> (raw)
In-Reply-To: <3ad3c346-1415-45bd-bcb2-2f9b46164f30@kernel.dk>
On 3/27/25 5:47 AM, Jens Axboe wrote:
> Hi Linus,
>
> This sits on top of the recently sent out zero-copy rx pull request.
>
> This adds support for reading epoll events via io_uring. While this may
> seem counter-intuitive (and/or productive), the reasoning here is that
> quite a few existing epoll event loops can easily do a partial
> conversion to a completion based model, but are still stuck with one (or
> few) event types that remain readiness based. For that case, they then
> need to add the io_uring fd to the epoll context, and continue to rely
> on epoll_wait(2) for waiting on events. This misses out on the finer
> grained waiting that io_uring can do, to reduce context switches and
> wait for multiple events in one batch reliably.
>
> With adding support for reaping epoll events via io_uring, the whole
> legacy readiness based event types can still be reaped via epoll, with
> the overall waiting in the loop be driven by io_uring.
>
> Relies on a prep patch that went in via the VFS tree already. Please
> pull!
And even with having prepared this earlier, guess a big conference dinner
was enough to still make me mess this up. The correct git location is of
course:
git://git.kernel.dk/linux.git for-6.15/io_uring-epoll-wait-20250325
which is what I get for creating the signed tag later than the actual
PR write-up.
Everything else in the original should be fine as-is, thanks!
--
Jens Axboe
next prev parent reply other threads:[~2025-03-27 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 11:47 [GIT PULL] io_uring epoll reaping support Jens Axboe
2025-03-27 14:27 ` Jens Axboe [this message]
2025-03-28 22:11 ` pr-tracker-bot
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=75d2935a-b560-40bb-aed9-d6cfd885b6a9@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox