From: Caleb Sander Mateos <csander@purestorage.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring/rsrc: skip atomic refcount for uncloned buffers
Date: Wed, 2 Jul 2025 21:23:19 -0400 [thread overview]
Message-ID: <CADUfDZqC9n4jcT_BhoraFzxA77wSyJ4+KZ7jvOs=a_cvr456WA@mail.gmail.com> (raw)
In-Reply-To: <2cf2350f-286a-42cb-aa02-2eee7099fe22@kernel.dk>
On Wed, Jul 2, 2025 at 7:10 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 7/2/25 3:11 PM, Caleb Sander Mateos wrote:
> > Hi Jens,
> > Any concerns with this one? I thought it was a fairly straightforward
> > optimization in the ublk zero-copy I/O path.
>
> Nope looks fine, I just have a largish backlog from being gone for 10
> days. I'll queue it up for 6.17.
No worries, I was away for a week too. Just wanted to make sure it
hadn't fallen off the radar.
Thanks,
Caleb
next prev parent reply other threads:[~2025-07-03 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 14:34 [PATCH] io_uring/rsrc: skip atomic refcount for uncloned buffers Caleb Sander Mateos
2025-07-02 21:11 ` Caleb Sander Mateos
2025-07-02 23:10 ` Jens Axboe
2025-07-03 1:23 ` Caleb Sander Mateos [this message]
2025-07-02 23:19 ` 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='CADUfDZqC9n4jcT_BhoraFzxA77wSyJ4+KZ7jvOs=a_cvr456WA@mail.gmail.com' \
--to=csander@purestorage.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@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