io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: Re: [zcrx-next 0/2] add support for synchronous refill
Date: Wed, 20 Aug 2025 19:57:40 +0100	[thread overview]
Message-ID: <c6ea1a29-3a0a-4eee-b137-a0b2929f00df@gmail.com> (raw)
In-Reply-To: <175571405086.442349.7150561067887044481.b4-ty@kernel.dk>

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.

-- 
Pavel Begunkov


  reply	other threads:[~2025-08-20 18:56 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 [this message]
2025-08-20 19:02     ` Jens Axboe
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=c6ea1a29-3a0a-4eee-b137-a0b2929f00df@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=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;
as well as URLs for NNTP newsgroup(s).