From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com
Subject: [PATCHSET 0/2] Allow non-atomic allocs for overflows
Date: Fri, 16 May 2025 10:08:55 -0600 [thread overview]
Message-ID: <20250516161452.395927-1-axboe@kernel.dk> (raw)
Hi,
This is heavily inspired by the series that Pavel posted here:
https://lore.kernel.org/io-uring/cover.1747209332.git.asml.silence@gmail.com/
since I do think that potentially increasing the reliability of overflow
handling is a worthy endeavour. It's just somewhat simpler as it doesn't
move anything around really, it just does the split of allocating
the overflow entry separately from adding it to the io_ring_ctx context.
Further cleanups could be done on top of this, obviously.
io_uring/io_uring.c | 79 +++++++++++++++++++++++++++++----------------
1 file changed, 52 insertions(+), 27 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-05-16 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 16:08 Jens Axboe [this message]
2025-05-16 16:08 ` [PATCH 1/2] io_uring: split alloc and add of overflow Jens Axboe
2025-05-16 16:31 ` Caleb Sander Mateos
2025-05-16 16:33 ` Jens Axboe
2025-05-16 16:43 ` Pavel Begunkov
2025-05-16 16:44 ` Jens Axboe
2025-05-16 16:58 ` Pavel Begunkov
2025-05-16 16:57 ` Jens Axboe
2025-05-16 18:27 ` Pavel Begunkov
2025-05-16 16:08 ` [PATCH 2/2] io_uring: make io_alloc_ocqe() take a struct io_cqe pointer 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=20250516161452.395927-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--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.