From: Jens Axboe <[email protected]>
To: [email protected], [email protected],
[email protected], Pavel Begunkov <[email protected]>
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: [PATCH for-next 0/2] Enable IOU_F_TWQ_LAZY_WAKE for passthrough
Date: Thu, 25 May 2023 08:54:33 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 15 May 2023 13:54:41 +0100, Pavel Begunkov wrote:
> Let cmds to use IOU_F_TWQ_LAZY_WAKE and enable it for nvme passthrough.
>
> The result should be same as in test to the original IOU_F_TWQ_LAZY_WAKE [1]
> patchset, but for a quick test I took fio/t/io_uring with 4 threads each
> reading their own drive and all pinned to the same CPU to make it CPU
> bound and got +10% throughput improvement.
>
> [...]
Applied, thanks!
[1/2] io_uring/cmd: add cmd lazy tw wake helper
commit: 5f3139fc46993b2d653a7aa5cdfe66a91881fd06
[2/2] nvme: optimise io_uring passthrough completion
commit: f026be0e1e881e3395c3d5418ffc8c2a2203c3f3
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-05-25 14:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 12:54 [PATCH for-next 0/2] Enable IOU_F_TWQ_LAZY_WAKE for passthrough Pavel Begunkov
2023-05-15 12:54 ` [PATCH for-next 1/2] io_uring/cmd: add cmd lazy tw wake helper Pavel Begunkov
2023-05-16 10:00 ` Kanchan Joshi
2023-05-16 18:52 ` Pavel Begunkov
2023-05-17 10:33 ` Kanchan Joshi
2023-05-17 12:00 ` Pavel Begunkov
2023-05-19 15:00 ` Pavel Begunkov
2023-05-15 12:54 ` [PATCH for-next 2/2] nvme: optimise io_uring passthrough completion Pavel Begunkov
2023-05-17 7:23 ` Christoph Hellwig
2023-05-17 12:32 ` Pavel Begunkov
2023-05-17 12:39 ` Christoph Hellwig
2023-05-17 13:30 ` Pavel Begunkov
2023-05-17 13:53 ` Christoph Hellwig
2023-05-17 20:11 ` Pavel Begunkov
2023-05-17 19:31 ` Jens Axboe
2023-05-18 2:15 ` Ming Lei
2023-05-16 11:42 ` [PATCH for-next 0/2] Enable IOU_F_TWQ_LAZY_WAKE for passthrough Anuj gupta
2023-05-16 18:38 ` Pavel Begunkov
2023-05-25 14:54 ` 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=168502647392.717124.7925068931544884226.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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