From: Mike Snitzer <snitzer@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
Mikulas Patocka <mpatocka@redhat.com>, Song Liu <song@kernel.org>,
Yu Kuai <yukuai3@huawei.com>,
dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: [PATCH 3/9] dm: use queue_limits_set
Date: Fri, 23 Feb 2024 12:30:57 -0500 [thread overview]
Message-ID: <ZdjWUdwrwmPT0mX1@redhat.com> (raw)
In-Reply-To: <20240223161247.3998821-4-hch@lst.de>
On Fri, Feb 23 2024 at 11:12P -0500,
Christoph Hellwig <hch@lst.de> wrote:
> Use queue_limits_set which validates the limits and takes care of
> updating the readahead settings instead of directly assigning them to
> the queue. For that make sure all limits are actually updated before
> the assignment.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks good,
Reviewed-by: Mike Snitzer <snitzer@kernel.org>
next prev parent reply other threads:[~2024-02-23 17:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:12 atomic queue limit updates for stackable devices Christoph Hellwig
2024-02-23 16:12 ` [PATCH 1/9] block: add a queue_limits_set helper Christoph Hellwig
2024-02-23 16:12 ` [PATCH 2/9] block: add a queue_limits_stack_bdev helper Christoph Hellwig
2024-02-23 16:12 ` [PATCH 3/9] dm: use queue_limits_set Christoph Hellwig
2024-02-23 17:30 ` Mike Snitzer [this message]
2024-02-23 16:12 ` [PATCH 4/9] md: add queue limit helpers Christoph Hellwig
2024-02-23 16:12 ` [PATCH 5/9] md/raid0: use the atomic queue limit update APIs Christoph Hellwig
2024-02-23 16:12 ` [PATCH 6/9] md/raid1: " Christoph Hellwig
2024-02-23 16:12 ` [PATCH 7/9] md/raid10: " Christoph Hellwig
2024-02-23 16:12 ` [PATCH 8/9] md/raid5: " Christoph Hellwig
2024-02-23 16:12 ` [PATCH 9/9] block: remove disk_stack_limits Christoph Hellwig
2024-02-23 17:36 ` atomic queue limit updates for stackable devices Mike Snitzer
2024-02-23 17:38 ` Mike Snitzer
2024-02-27 15:10 ` Christoph Hellwig
2024-02-27 15:16 ` Mike Snitzer
2024-02-27 15:17 ` Christoph Hellwig
2024-02-27 15:36 ` Mike Snitzer
2024-02-27 21:50 ` Song Liu
2024-02-28 19:56 ` Christoph Hellwig
2024-02-29 2:02 ` Song Liu
2024-02-29 13:20 ` Christoph Hellwig
2024-02-23 17:41 ` Christoph Hellwig
2024-02-27 15:09 ` Christoph Hellwig
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=ZdjWUdwrwmPT0mX1@redhat.com \
--to=snitzer@kernel.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mpatocka@redhat.com \
--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 NNTP newsgroup(s).