From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [zcrx-next 0/2] add support for synchronous refill
Date: Wed, 20 Aug 2025 13:02:18 -0600 [thread overview]
Message-ID: <b811389e-2a4b-42b3-b9ed-3d31e5e30fd2@kernel.dk> (raw)
In-Reply-To: <c6ea1a29-3a0a-4eee-b137-a0b2929f00df@gmail.com>
On 8/20/25 12:57 PM, Pavel Begunkov wrote:
> On 8/20/25 19:20, Jens Axboe wrote:
>>
>> On Sun, 17 Aug 2025 23:44:56 +0100, Pavel Begunkov wrote:
>>> Returning buffers via a ring is efficient but can cause problems
>>> when the ring doesn't have space. Add a way to return buffers
>>> synchronously via io_uring "register" syscall, which should serve
>>> as a slow fallback path.
>>>
>>> For a full branch with all relevant dependencies see
>>> https://github.com/isilence/linux.git zcrx/for-next
>>>
>>> [...]
>>
>> Applied, thanks!
>
> Leave these and other series out please. I sent them for
> review, but it'll be easier to keep in a branch and rebase
> it if necessary. I hoped tagging with zcrx-next would be
> good enough of a sign.
Alright, but then please make it clear when you are sending
something out for merging.
--
Jens Axboe
next prev parent reply other threads:[~2025-08-20 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 22:44 [zcrx-next 0/2] add support for synchronous refill Pavel Begunkov
2025-08-17 22:44 ` [zcrx-next 1/2] io_uring/zcrx: introduce io_parse_rqe() Pavel Begunkov
2025-08-17 22:44 ` [zcrx-next 2/2] io_uring/zcrx: allow synchronous buffer return Pavel Begunkov
2025-08-20 18:20 ` [zcrx-next 0/2] add support for synchronous refill Jens Axboe
2025-08-20 18:57 ` Pavel Begunkov
2025-08-20 19:02 ` Jens Axboe [this message]
2025-08-20 19:33 ` Pavel Begunkov
2025-08-20 19:36 ` 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=b811389e-2a4b-42b3-b9ed-3d31e5e30fd2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).