From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>, Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>, Song Liu <song@kernel.org>,
Yu Kuai <yukuai3@huawei.com>
Cc: dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: atomic queue limit updates for stackable devices v3
Date: Wed, 28 Feb 2024 14:56:39 -0800 [thread overview]
Message-ID: <20240228225653.947152-1-hch@lst.de> (raw)
Hi all,
this series adds new helpers for the atomic queue limit update
functionality and then switches dm and md over to it. The dm switch is
pretty trivial as it was basically implementing the model by hand
already, md is a bit more work.
I've run the mdadm testsuite, and it has the same (rather large) number
of failures as the baseline, and the lvm2 test suite goes as far as
the baseline before handing in __md_stop_writes.
nvme-multipath will be handled separately as it is too tightly integrated
with the rest of nvme.
Changes since v2:
- drop drbd from this series again for now as we've not made any
review progress
- keep the NULL gendisk checks for DM-mapped MD devices, and add a few
helpers to better document and abstract them
- use mddev_suspend instead of blk_mq_freeze_queue around updating
io_opt
Changes since v1:
- a few kerneldoc fixes
- fix a line remove after testing in raid0
- also add drbd
Diffstat:
block/blk-mq.c | 14 ++-
block/blk-settings.c | 47 +++++++++----
drivers/md/dm-table.c | 27 +++----
drivers/md/md-bitmap.c | 9 --
drivers/md/md.c | 89 ++++++++++++++++++-------
drivers/md/md.h | 28 +++++++
drivers/md/raid0.c | 42 ++++++-----
drivers/md/raid1.c | 51 ++++++--------
drivers/md/raid10.c | 85 +++++++++++------------
drivers/md/raid5-ppl.c | 3
drivers/md/raid5.c | 174 +++++++++++++++++++++++--------------------------
include/linux/blkdev.h | 5 -
12 files changed, 321 insertions(+), 253 deletions(-)
next reply other threads:[~2024-02-28 22:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 22:56 Christoph Hellwig [this message]
2024-02-28 22:56 ` [PATCH 01/14] block: add a queue_limits_set helper Christoph Hellwig
2024-02-28 22:56 ` [PATCH 02/14] block: add a queue_limits_stack_bdev helper Christoph Hellwig
2024-02-28 22:56 ` [PATCH 03/14] dm: use queue_limits_set Christoph Hellwig
2024-02-28 22:56 ` [PATCH 04/14] md: add a mddev_trace_remap helper Christoph Hellwig
2024-02-28 22:56 ` [PATCH 05/14] md: add a mddev_add_trace_msg helper Christoph Hellwig
2024-02-28 22:56 ` [PATCH 06/14] md: add a mddev_is_dm helper Christoph Hellwig
2024-02-28 22:56 ` [PATCH 07/14] md: add queue limit helpers Christoph Hellwig
2024-02-28 22:56 ` [PATCH 08/14] md/raid0: use the atomic queue limit update APIs Christoph Hellwig
2024-02-28 22:56 ` [PATCH 09/14] md/raid1: " Christoph Hellwig
2024-02-28 22:56 ` [PATCH 10/14] md/raid5: " Christoph Hellwig
2024-02-28 22:56 ` [PATCH 11/14] md/raid10: " Christoph Hellwig
2024-02-28 22:56 ` [PATCH 12/14] md: don't initialize queue limits Christoph Hellwig
2024-02-28 22:56 ` [PATCH 13/14] md: remove mddev->queue Christoph Hellwig
2024-02-28 22:56 ` [PATCH 14/14] block: remove disk_stack_limits Christoph Hellwig
2024-02-29 19:40 ` atomic queue limit updates for stackable devices v3 Christoph Hellwig
2024-03-01 15:55 ` (subset) " Jens Axboe
2024-03-02 4:14 ` Song Liu
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=20240228225653.947152-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=yukuai3@huawei.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 read-only IMAP folder(s) and NNTP newsgroup(s).