From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH 0/3] optimise submit+iopoll mutex locking
Date: Wed, 23 Mar 2022 06:29:34 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 22 Mar 2022 14:07:55 +0000, Pavel Begunkov wrote:
> This saves one mutex lock/unlock pair per syscall when users do
> submit + getevents. Perf tells that for QD1 iopoll this patch reduces overhead
> on locking from ~4.3% to ~2.6%, iow cuts 1.3% - 1.9% of CPU time. Something
> similar I see in final throughput.
>
> It's a good win for smaller QD, especially considering that io_uring only
> takes about 20-30% of all cycles, the rest goes to syscalling, the block
> layer and below.
>
> [...]
Applied, thanks!
[1/3] io_uring: split off IOPOLL argument verifiction
(no commit info)
[2/3] io_uring: pre-calculate syscall iopolling decision
(no commit info)
[3/3] io_uring: optimise mutex locking for submit+iopoll
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-03-23 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 14:07 [PATCH 0/3] optimise submit+iopoll mutex locking Pavel Begunkov
2022-03-22 14:07 ` [PATCH 1/3] io_uring: split off IOPOLL argument verifiction Pavel Begunkov
2022-03-22 14:07 ` [PATCH 2/3] io_uring: pre-calculate syscall iopolling decision Pavel Begunkov
2022-03-22 14:07 ` [PATCH 3/3] io_uring: optimise mutex locking for submit+iopoll Pavel Begunkov
2022-03-23 12:29 ` Jens Axboe [this message]
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=164803857464.12296.859321851786945843.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
/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