From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Jens Axboe <axboe@kernel.dk>,
xen-devel@lists.xenproject.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 3/4] xen-blkfront: don't redundantly set max_sements in blkif_recover
Date: Tue, 20 Feb 2024 13:16:05 +0100 [thread overview]
Message-ID: <ZdSYBQB-F1CwjoHN@macbook> (raw)
In-Reply-To: <20240220084935.3282351-4-hch@lst.de>
On Tue, Feb 20, 2024 at 09:49:34AM +0100, Christoph Hellwig wrote:
> blkif_set_queue_limits already sets the max_sements limits, so don't do
> it a second time. Also remove a comment about a long fixe bug in
> blk_mq_update_nr_hw_queues.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
Thanks, Roger.
next prev parent reply other threads:[~2024-02-20 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 8:49 convert xen-blkfront to atomic queue limit updates Christoph Hellwig
2024-02-20 8:49 ` [PATCH 1/4] xen-blkfront: set max_discard/secure erase limits to UINT_MAX Christoph Hellwig
2024-02-20 11:39 ` Roger Pau Monné
2024-02-20 15:50 ` Christoph Hellwig
2024-02-20 8:49 ` [PATCH 2/4] xen-blkfront: rely on the default discard granularity Christoph Hellwig
2024-02-20 11:50 ` Roger Pau Monné
2024-02-20 8:49 ` [PATCH 3/4] xen-blkfront: don't redundantly set max_sements in blkif_recover Christoph Hellwig
2024-02-20 12:16 ` Roger Pau Monné [this message]
2024-02-20 8:49 ` [PATCH 4/4] xen-blkfront: atomically update queue limits Christoph Hellwig
2024-02-20 12:35 ` Roger Pau Monné
2024-02-20 15:53 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 12:58 convert xen-blkfront to atomic queue limit updates v2 Christoph Hellwig
2024-02-21 12:58 ` [PATCH 3/4] xen-blkfront: don't redundantly set max_sements in blkif_recover 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=ZdSYBQB-F1CwjoHN@macbook \
--to=roger.pau@citrix.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jgross@suse.com \
--cc=linux-block@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).