From: Ming Lei <ming.lei@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: axboe@kernel.dk, hch@lst.de, dm-devel@redhat.com,
linux-block@vger.kernel.org
Subject: Re: [PATCH v4 0/2] block/dm: support bio polling
Date: Sat, 5 Mar 2022 09:43:00 +0800 [thread overview]
Message-ID: <YiLAJIOZz9UHbUKq@T590> (raw)
In-Reply-To: <20220304212623.34016-1-snitzer@redhat.com>
On Fri, Mar 04, 2022 at 04:26:21PM -0500, Mike Snitzer wrote:
> Hi,
>
> I've rebased Ming's latest [1] ontop of dm-5.18 [2] (which is based on
> for-5.18/block). End result available in dm-5.18-biopoll branch [3]
>
> These changes add bio polling support to DM. Tested with linear and
> striped DM targets.
>
> IOPS improvement was ~5% on my baremetal system with a single Intel
> Optane NVMe device (555K hipri=1 vs 525K hipri=0).
>
> Ming has seen better improvement while testing within a VM:
> dm-linear: hipri=1 vs hipri=0 15~20% iops improvement
> dm-stripe: hipri=1 vs hipri=0 ~30% iops improvement
>
> I'd like to merge these changes via the DM tree when the 5.18 merge
> window opens. The first block patch that adds ->poll_bio to
> block_device_operations will need review so that I can take it
> through the DM tree. Reason for going through the DM tree is there
> have been some fairly extensive changes queued in dm-5.18 that build
> on for-5.18/block. So I think it easiest to just add the block
> depenency via DM tree since DM is first consumer of ->poll_bio
>
> FYI, Ming does have another DM patch [4] that looks to avoid using
> hlist but I only just saw it. bio_split() _is_ involved (see
> dm_split_and_process_bio) so I'm not exactly sure where he is going
> with that change.
io_uring(polling) workloads often cares latency, so big IO request
isn't involved usually, I guess. Then bio_split() is seldom called in
dm_split_and_process_bio(), such as if 4k random IO is run on dm-linear
or dm-stripe via io_uring, bio_split() won't be run into.
Single list is enough here, and efficient than hlist, just need
a little care to delete element from the list since linux kernel doesn't
have generic single list implementation.
> But that is DM-implementation detail that we'll
> sort out.
Yeah, that patch also needs more test.
Thanks,
Ming
next prev parent reply other threads:[~2022-03-05 1:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 21:26 [PATCH v4 0/2] block/dm: support bio polling Mike Snitzer
2022-03-04 21:26 ` [PATCH v4 1/2] block: add ->poll_bio to block_device_operations Mike Snitzer
2022-03-04 21:39 ` Jens Axboe
2022-03-05 1:30 ` Mike Snitzer
2022-03-04 21:26 ` [PATCH v4 2/2] dm: support bio polling Mike Snitzer
2022-03-05 1:43 ` Ming Lei [this message]
2022-03-05 2:14 ` [PATCH v4 0/2] block/dm: " Mike Snitzer
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=YiLAJIOZz9UHbUKq@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=snitzer@redhat.com \
/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