From: Ming Lei <ming.lei@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Jeffle Xu <jefflexu@linux.alibaba.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [dm-devel] [PATCH V3 0/3] block/dm: support bio polling
Date: Tue, 1 Mar 2022 08:58:21 +0800 [thread overview]
Message-ID: <Yh1vrWXlaTnEcrNd@T590> (raw)
In-Reply-To: <Yhz4AGXcn0DUeSwq@redhat.com>
On Mon, Feb 28, 2022 at 11:27:44AM -0500, Mike Snitzer wrote:
> On Wed, Jun 23 2021 at 3:40P -0400,
> Ming Lei <ming.lei@redhat.com> wrote:
>
> > Hello Guys,
> >
> > Based on Christoph's bio based polling model[1], implement DM bio polling
> > with one very simple approach.
> >
> > Patch 1 adds helper of blk_queue_poll().
> >
> > Patch 2 adds .bio_poll() callback to block_device_operations, so bio
> > driver can implement its own logic for io polling.
> >
> > Patch 3 implements bio polling for device mapper.
> >
> >
> > V3:
> > - patch style change as suggested by Christoph(2/3)
> > - fix kernel panic issue caused by nested dm polling, which is found
> > & figured out by Jeffle Xu (3/3)
> > - re-organize setup polling code (3/3)
> > - remove RFC
> >
> > V2:
> > - drop patch to add new fields into bio
> > - support io polling for dm native bio splitting
> > - add comment
> >
> > Ming Lei (3):
> > block: add helper of blk_queue_poll
> > block: add ->poll_bio to block_device_operations
> > dm: support bio polling
> >
> > block/blk-core.c | 18 +++---
> > block/blk-sysfs.c | 4 +-
> > block/genhd.c | 2 +
> > drivers/md/dm-table.c | 24 +++++++
> > drivers/md/dm.c | 131 ++++++++++++++++++++++++++++++++++++++-
> > drivers/nvme/host/core.c | 2 +-
> > include/linux/blkdev.h | 2 +
> > 7 files changed, 170 insertions(+), 13 deletions(-)
> >
> > --
> > 2.31.1
> >
>
> Hey Ming,
>
> I'd like us to follow-through with adding bio-based polling support.
> Kind of strange none of us that were sent this V3 ever responded,
> sorry about that!
>
> Do you have interest in rebasing this patchset (against linux-dm.git's
> "dm-5.18" branch since there has been quite some churn)? Or are you
> OK with me doing the rebase?
Hi Mike,
Actually I have one local v5.17 rebase:
https://github.com/ming1/linux/tree/my_v5.17-dm-io-poll
Also one for-5.18/block rebase which is done just now:
https://github.com/ming1/linux/tree/my_v5.18-dm-bio-poll
In my previous test on v5.17 rebase, the IOPS improvement is a bit small,
so I didn't post it out. Recently not get time to investigate
the performance further, so please feel free to work on it.
Thanks,
Ming
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2022-03-01 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 7:40 [dm-devel] [PATCH V3 0/3] block/dm: support bio polling Ming Lei
2021-06-23 7:40 ` [dm-devel] [PATCH V3 1/3] block: add helper of blk_queue_poll Ming Lei
2021-06-23 7:40 ` [dm-devel] [PATCH V3 2/3] block: add ->poll_bio to block_device_operations Ming Lei
2021-06-23 7:40 ` [dm-devel] [PATCH V3 3/3] dm: support bio polling Ming Lei
2022-02-28 16:27 ` [dm-devel] [PATCH V3 0/3] block/dm: " Mike Snitzer
2022-03-01 0:58 ` Ming Lei [this message]
2022-03-01 21:19 ` Mike Snitzer
2022-03-02 0:45 ` Ming Lei
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=Yh1vrWXlaTnEcrNd@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=jefflexu@linux.alibaba.com \
--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;
as well as URLs for NNTP newsgroup(s).