From: Mike Snitzer <snitzer@kernel.org>
To: axboe@kernel.dk
Cc: ming.lei@redhat.com, hch@lst.de, dm-devel@redhat.com,
linux-block@vger.kernel.org
Subject: [PATCH v3 0/3] block/dm: use BIOSET_PERCPU_CACHE from bio_alloc_bioset
Date: Thu, 24 Mar 2022 16:35:23 -0400 [thread overview]
Message-ID: <20220324203526.62306-1-snitzer@kernel.org> (raw)
Hi Jens,
This v3 is a rebase of the previous v2 series ontop of the revised v2
patch that Christoph provided.
Linus hasn't pulled the for-5.18/dm-changes branch yet, so the 3rd DM
patch cannot be applied yet. But feel free to pickup the first 2
block patches for 5.19 and I'll rebase dm-5.19 on block accordingly.
Thanks,
Mike
v3: tweaked some code comments, refined patch headers and folded DM
patches so only one DM patch now.
v2: add REQ_ALLOC_CACHE and move use of bio_alloc_percpu_cache to
bio_alloc_bioset
Mike Snitzer (3):
block: allow using the per-cpu bio cache from bio_alloc_bioset
block: allow use of per-cpu bio alloc cache by block drivers
dm: conditionally enable BIOSET_PERCPU_CACHE for dm_io bioset
block/bio.c | 88 +++++++++++++++++++++++------------------------
block/blk.h | 7 ----
block/fops.c | 11 ++++--
drivers/md/dm-table.c | 11 ++++--
drivers/md/dm.c | 8 ++---
drivers/md/dm.h | 4 +--
include/linux/bio.h | 8 +++--
include/linux/blk_types.h | 3 +-
8 files changed, 73 insertions(+), 67 deletions(-)
--
2.15.0
next reply other threads:[~2022-03-24 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 20:35 Mike Snitzer [this message]
2022-03-24 20:35 ` [PATCH v3 1/3] block: allow using the per-cpu bio cache from bio_alloc_bioset Mike Snitzer
2022-03-24 20:35 ` [PATCH v3 2/3] block: allow use of per-cpu bio alloc cache by block drivers Mike Snitzer
2022-03-25 5:35 ` Christoph Hellwig
2022-03-24 20:35 ` [PATCH v3 3/3] dm: conditionally enable BIOSET_PERCPU_CACHE for dm_io bioset Mike Snitzer
2022-03-30 18:51 ` (subset) [PATCH v3 0/3] block/dm: use BIOSET_PERCPU_CACHE from bio_alloc_bioset Jens Axboe
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=20220324203526.62306-1-snitzer@kernel.org \
--to=snitzer@kernel.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--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).