From: Mike Snitzer <snitzer@redhat.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Damien Le Moal <damien.lemoal@opensource.wdc.com>
Subject: Re: [PATCH 0/8] dm: io accounting & polling improvement
Date: Tue, 12 Apr 2022 13:15:14 -0400 [thread overview]
Message-ID: <YlWzoj+M1ykUubH+@redhat.com> (raw)
In-Reply-To: <20220412085616.1409626-1-ming.lei@redhat.com>
On Tue, Apr 12 2022 at 4:56P -0400,
Ming Lei <ming.lei@redhat.com> wrote:
> Hello Guys,
>
> The 1st patch adds bdev based io accounting interface.
>
> The 2nd ~ 5th patches improves dm's io accounting & split, meantime
> fixes kernel panic on dm-zone.
>
> The other patches improves io polling & dm io reference handling.
>
>
> Ming Lei (8):
> block: replace disk based account with bdev's
> dm: don't pass bio to __dm_start_io_acct and dm_end_io_acct
> dm: pass 'dm_io' instance to dm_io_acct directly
> dm: switch to bdev based io accounting interface
> dm: always setup ->orig_bio in alloc_io
> dm: don't grab target io reference in dm_zone_map_bio
> dm: improve target io referencing
> dm: put all polled io into one single list
>
> block/blk-core.c | 15 +--
> drivers/block/zram/zram_drv.c | 5 +-
> drivers/md/dm-core.h | 17 ++-
> drivers/md/dm-zone.c | 10 --
> drivers/md/dm.c | 190 +++++++++++++++++++---------------
> include/linux/blkdev.h | 7 +-
> 6 files changed, 131 insertions(+), 113 deletions(-)
>
> --
> 2.31.1
>
I'll review this closely but, a couple weeks ago, I queued up quite a
lot of conflicting changes for 5.19 here:
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-5.19
next prev parent reply other threads:[~2022-04-12 17:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 8:56 [PATCH 0/8] dm: io accounting & polling improvement Ming Lei
2022-04-12 8:56 ` [PATCH 1/8] block: replace disk based account with bdev's Ming Lei
2022-04-16 5:57 ` Christoph Hellwig
2022-04-12 8:56 ` [PATCH 2/8] dm: don't pass bio to __dm_start_io_acct and dm_end_io_acct Ming Lei
2022-04-12 8:56 ` [PATCH 3/8] dm: pass 'dm_io' instance to dm_io_acct directly Ming Lei
2022-04-12 20:28 ` Mike Snitzer
2022-04-13 1:43 ` Ming Lei
2022-04-12 8:56 ` [PATCH 4/8] dm: switch to bdev based io accounting interface Ming Lei
2022-04-12 8:56 ` [PATCH 5/8] dm: always setup ->orig_bio in alloc_io Ming Lei
2022-04-12 20:52 ` Mike Snitzer
2022-04-12 22:38 ` Damien Le Moal
2022-04-12 23:00 ` Mike Snitzer
2022-04-12 23:31 ` Damien Le Moal
2022-04-13 0:00 ` Damien Le Moal
2022-04-13 1:56 ` Ming Lei
2022-04-13 6:12 ` Mike Snitzer
2022-04-13 12:26 ` Ming Lei
2022-04-13 17:58 ` Mike Snitzer
2022-04-14 0:36 ` Ming Lei
2022-04-14 2:25 ` Mike Snitzer
2022-04-14 3:57 ` Ming Lei
2022-04-14 17:45 ` Mike Snitzer
2022-04-15 0:14 ` Ming Lei
2022-04-15 21:06 ` Mike Snitzer
2022-04-17 2:22 ` Ming Lei
2022-04-12 8:56 ` [PATCH 6/8] dm: don't grab target io reference in dm_zone_map_bio Ming Lei
2022-04-12 8:56 ` [PATCH 7/8] dm: improve target io referencing Ming Lei
2022-04-12 8:56 ` [PATCH 8/8] dm: put all polled io into one single list Ming Lei
2022-04-12 17:15 ` Mike Snitzer [this message]
2022-04-16 5:58 ` [PATCH 0/8] dm: io accounting & polling improvement Christoph Hellwig
2022-04-17 1:23 ` 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=YlWzoj+M1ykUubH+@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@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).