From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Coly Li <colyli@suse.de>, Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
linux-m68k@lists.linux-m68k.org, linux-bcache@vger.kernel.org,
nvdimm@lists.linux.dev, linux-block@vger.kernel.org
Subject: pass queue_limits to blk_alloc_disk for simple drivers
Date: Thu, 15 Feb 2024 08:10:46 +0100 [thread overview]
Message-ID: <20240215071055.2201424-1-hch@lst.de> (raw)
Hi Jens,
this series converts all "simple" bio based drivers that don't have
complex internal layering or other oddities to pass the queue_limits to
blk_mq_alloc_disk. None of these drivers updates the limits at runtime.
Diffstat:
arch/m68k/emu/nfblock.c | 10 ++++---
arch/xtensa/platforms/iss/simdisk.c | 8 +++--
block/genhd.c | 11 ++++---
drivers/block/brd.c | 26 +++++++++---------
drivers/block/drbd/drbd_main.c | 6 ++--
drivers/block/n64cart.c | 12 +++++---
drivers/block/null_blk/main.c | 7 ++--
drivers/block/pktcdvd.c | 7 ++--
drivers/block/ps3vram.c | 6 ++--
drivers/block/zram/zram_drv.c | 51 +++++++++++++++++-------------------
drivers/md/bcache/super.c | 48 +++++++++++++++++----------------
drivers/md/dm.c | 4 +-
drivers/md/md.c | 7 ++--
drivers/nvdimm/btt.c | 14 +++++----
drivers/nvdimm/pmem.c | 14 +++++----
drivers/nvme/host/multipath.c | 6 ++--
drivers/s390/block/dcssblk.c | 10 ++++---
include/linux/blkdev.h | 10 ++++---
18 files changed, 143 insertions(+), 114 deletions(-)
next reply other threads:[~2024-02-15 7:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 7:10 Christoph Hellwig [this message]
2024-02-15 7:10 ` [PATCH 1/9] block: pass a queue_limits argument to blk_alloc_disk Christoph Hellwig
2024-02-15 7:10 ` [PATCH 2/9] nfblock: pass queue_limits to blk_mq_alloc_disk Christoph Hellwig
2024-02-15 7:10 ` [PATCH 3/9] brd: " Christoph Hellwig
2024-02-17 0:42 ` Chaitanya Kulkarni
2024-02-15 7:10 ` [PATCH 4/9] n64cart: " Christoph Hellwig
2024-02-17 0:43 ` Chaitanya Kulkarni
2024-02-15 7:10 ` [PATCH 5/9] zram: " Christoph Hellwig
2024-02-19 12:04 ` Sergey Senozhatsky
2024-02-15 7:10 ` [PATCH 6/9] bcache: " Christoph Hellwig
2024-02-17 0:44 ` Chaitanya Kulkarni
2024-02-15 7:10 ` [PATCH 7/9] btt: " Christoph Hellwig
2024-02-15 18:16 ` Dave Jiang
2024-02-15 7:10 ` [PATCH 8/9] pmem: " Christoph Hellwig
2024-02-15 18:15 ` Dave Jiang
2024-02-17 0:45 ` Chaitanya Kulkarni
2024-02-15 7:10 ` [PATCH 9/9] dcssblk: " Christoph Hellwig
2024-02-15 22:04 ` pass queue_limits to blk_alloc_disk for simple drivers Dan Williams
2024-02-17 0:51 ` Himanshu Madhani
2024-02-20 13:22 ` 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=20240215071055.2201424-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=geert@linux-m68k.org \
--cc=ira.weiny@intel.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=minchan@kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=senozhatsky@chromium.org \
--cc=vishal.l.verma@intel.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).