From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Subject: [PATCHSET 0/2] Split out wait and task_work handling
Date: Thu, 22 Jan 2026 09:21:50 -0700 [thread overview]
Message-ID: <20260122162424.353513-1-axboe@kernel.dk> (raw)
Hi,
io_uring.c is still pretty massive, even after a bit of cancelation
refactoring in the 6.19 work. We can reasonably split out the wait
and task_work handling into separate files as well, bringing the file
from about 103k to about 84k. Outside of that, it makes the code
easier to reason about and navigate.
No functional changes in this series.
io_uring/Makefile | 14 +-
io_uring/cancel.c | 1 +
io_uring/io_uring.c | 693 +-------------------------------------------
io_uring/io_uring.h | 79 +----
io_uring/tw.c | 355 +++++++++++++++++++++++
io_uring/tw.h | 116 ++++++++
io_uring/wait.c | 308 ++++++++++++++++++++
io_uring/wait.h | 49 ++++
8 files changed, 842 insertions(+), 773 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-01-22 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 16:21 Jens Axboe [this message]
2026-01-22 16:21 ` [PATCH 1/2] io_uring: split out task work code into tw.c Jens Axboe
2026-01-22 16:21 ` [PATCH 2/2] io_uring: split out CQ waiting code into wait.c 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=20260122162424.353513-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox