From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>, Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
dm-devel@lists.linux.dev, linux-block@vger.kernel.org
Subject: convert newly added dm-zone code to the atomic queue commit API v3
Date: Mon, 27 May 2024 14:36:17 +0200 [thread overview]
Message-ID: <20240527123634.1116952-1-hch@lst.de> (raw)
Hi all,
the new dm-zone code added by Damien in 6.10-rc directly modifies the
queue limits instead of using the commit-style API that dm has used
forever and that the block layer adopted now, and thus can only run
after all the other changes have been commited. This is quite a land
mine and can be easily fixed.
Mike said he's fine with merging this through the block tree as the
dm-zone changes came in through that.
Changes since v2:
- add a missing IS_ENABLED() to fix compilation without zoned device
support
Changes since v1:
- fix an error return
- remove a superflous queue_limits_update_cancel call
Diffstat:
dm-table.c | 15 +++++-------
dm-zone.c | 72 +++++++++++++++++++++++++++----------------------------------
dm.h | 3 +-
3 files changed, 41 insertions(+), 49 deletions(-)
next reply other threads:[~2024-05-27 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 12:36 Christoph Hellwig [this message]
2024-05-27 12:36 ` [PATCH 1/3] dm: move setting zoned_enabled to dm_table_set_restrictions Christoph Hellwig
2024-05-27 12:36 ` [PATCH 2/3] dm: remove dm_check_zoned Christoph Hellwig
2024-05-27 12:36 ` [PATCH 3/3] dm: make dm_set_zones_restrictions work on the queue limits Christoph Hellwig
2024-05-27 15:17 ` convert newly added dm-zone code to the atomic queue commit API v3 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=20240527123634.1116952-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
/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