From: Benjamin Marzinski <bmarzins@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
Mike Snitzer <snitzer@redhat.com>, Jens Axboe <axboe@kernel.dk>,
dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH v2 3/6] block: make queue_limits_set() optionally return old limits
Date: Tue, 18 Mar 2025 15:23:15 -0400 [thread overview]
Message-ID: <Z9nIIydd_hZhzTss@redhat.com> (raw)
In-Reply-To: <20250318065603.GA16259@lst.de>
On Tue, Mar 18, 2025 at 07:56:03AM +0100, Christoph Hellwig wrote:
> On Mon, Mar 17, 2025 at 12:45:07AM -0400, Benjamin Marzinski wrote:
> > A future device-mapper patch will make use of this new argument. No
> > functional changes intended in this patch.
>
> If you care about the old limits just use a queue_limits_start_update +
> queue_limits_commit_update{,frozen} pair.
Yep. I'll change that.
-Ben
next prev parent reply other threads:[~2025-03-18 19:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 4:45 [PATCH v2 0/6] dm: fix issues with swapping dm tables Benjamin Marzinski
2025-03-17 4:45 ` [PATCH v2 1/6] dm: don't change md if dm_table_set_restrictions() fails Benjamin Marzinski
2025-03-17 4:45 ` [PATCH v2 2/6] dm: free table mempools if not used in __bind Benjamin Marzinski
2025-03-17 4:45 ` [PATCH v2 3/6] block: make queue_limits_set() optionally return old limits Benjamin Marzinski
2025-03-18 6:56 ` Christoph Hellwig
2025-03-18 19:23 ` Benjamin Marzinski [this message]
2025-03-17 4:45 ` [PATCH v2 4/6] dm: handle failures in dm_table_set_restrictions Benjamin Marzinski
2025-03-17 4:45 ` [PATCH v2 5/6] dm: fix dm_blk_report_zones Benjamin Marzinski
2025-03-18 6:57 ` Christoph Hellwig
2025-03-18 22:10 ` Benjamin Marzinski
2025-03-19 1:40 ` Damien Le Moal
2025-03-19 16:50 ` Benjamin Marzinski
2025-03-17 4:45 ` [PATCH v2 6/6] dm: limit swapping tables for devices with zone write plugs Benjamin Marzinski
2025-03-19 19:07 ` [PATCH v2 0/6] dm: fix issues with swapping dm tables Benjamin Marzinski
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=Z9nIIydd_hZhzTss@redhat.com \
--to=bmarzins@redhat.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.