From: Jens Axboe <axboe@kernel.dk>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] io_uring: avoid uring_lock for IORING_SETUP_SINGLE_ISSUER
Date: Tue, 2 Sep 2025 19:29:39 -0600 [thread overview]
Message-ID: <0be5cd99-9b0d-494a-8648-d767e06eb02d@kernel.dk> (raw)
In-Reply-To: <97fbbd68-cdd1-49fa-82d3-e3714ca70eeb@kernel.dk>
On 9/2/25 7:28 PM, Jens Axboe wrote:
> On 9/2/25 4:07 PM, Caleb Sander Mateos wrote:
>> As far as I can tell, setting IORING_SETUP_SINGLE_ISSUER when creating
>> an io_uring doesn't actually enable any additional optimizations (aside
>> from being a requirement for IORING_SETUP_DEFER_TASKRUN).
>
> Indeed. It was supposed to enable future optimizations, but they
> didn't quite materialize.
>
>> This series leverages IORING_SETUP_SINGLE_ISSUER's guarantee that only
>> one task submits SQEs to skip taking the uring_lock mutex in the
>> submission and task work paths.
>
> Interesting, would indeed be great to kill the lock/unlock for each
> submit and local work run. I'll take a closer look at this tomorrow.
I just noticed that you forgot to CC io-uring@vger.kernel.org on
this posting. Would you mind re-sending and doing that? LKML isn't
really useful, for anything really, the key list to CC is the
io_uring one.
--
Jens Axboe
next prev parent reply other threads:[~2025-09-03 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 22:07 Caleb Sander Mateos
2025-09-02 22:08 ` [PATCH 1/4] io_uring: don't include filetable.h in io_uring.h Caleb Sander Mateos
2025-09-02 22:08 ` [PATCH 2/4] io_uring/rsrc: respect submitter_task in io_register_clone_buffers() Caleb Sander Mateos
2025-09-02 22:08 ` [PATCH 3/4] io_uring: factor out uring_lock helpers Caleb Sander Mateos
2025-09-02 22:08 ` [PATCH 4/4] io_uring: avoid uring_lock for IORING_SETUP_SINGLE_ISSUER Caleb Sander Mateos
2025-09-03 1:28 ` [PATCH 0/4] " Jens Axboe
2025-09-03 1:29 ` Jens Axboe [this message]
2025-09-03 3:26 ` Caleb Sander Mateos
2025-09-03 3:26 Caleb Sander Mateos
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=0be5cd99-9b0d-494a-8648-d767e06eb02d@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--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
all inboxes | Powered by JetHome®