From: Jens Axboe <[email protected]>
To: Xiaoguang Wang <[email protected]>,
[email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH v7 1/2] io_uring: avoid whole io_wq_work copy for requests completed inline
Date: Wed, 10 Jun 2020 19:19:17 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/10/20 5:41 AM, Xiaoguang Wang wrote:
> If requests can be submitted and completed inline, we don't need to
> initialize whole io_wq_work in io_init_req(), which is an expensive
> operation, add a new 'REQ_F_WORK_INITIALIZED' to determine whether
> io_wq_work is initialized and add a helper io_req_init_async(), users
> must call io_req_init_async() for the first time touching any members
> of io_wq_work.
>
> I use /dev/nullb0 to evaluate performance improvement in my physical
> machine:
> modprobe null_blk nr_devices=1 completion_nsec=0
> sudo taskset -c 60 fio -name=fiotest -filename=/dev/nullb0 -iodepth=128
> -thread -rw=read -ioengine=io_uring -direct=1 -bs=4k -size=100G -numjobs=1
> -time_based -runtime=120
>
> before this patch:
> Run status group 0 (all jobs):
> READ: bw=724MiB/s (759MB/s), 724MiB/s-724MiB/s (759MB/s-759MB/s),
> io=84.8GiB (91.1GB), run=120001-120001msec
>
> With this patch:
> Run status group 0 (all jobs):
> READ: bw=761MiB/s (798MB/s), 761MiB/s-761MiB/s (798MB/s-798MB/s),
> io=89.2GiB (95.8GB), run=120001-120001msec
>
> About 5% improvement.
Thanks for pulling this one to completion! I've applied 1-2 for 5.8.
One note on future patches only - please use a coverletter, makes
it easier to reply to the series as a whole.
--
Jens Axboe
prev parent reply other threads:[~2020-06-11 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 11:41 [PATCH v7 1/2] io_uring: avoid whole io_wq_work copy for requests completed inline Xiaoguang Wang
2020-06-10 11:41 ` [PATCH v7 2/2] io_uring: avoid unnecessary io_wq_work copy for fast poll feature Xiaoguang Wang
2020-06-11 1:19 ` 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 \
[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