Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Yao Sang <sangyao@kylinos.cn>
Cc: linux-nvme@lists.infradead.org, axboe@kernel.dk, hch@lst.de,
	sagi@grimberg.me, shinichiro.kawasaki@wdc.com
Subject: Re: [PATCH v4] nvme: refresh multipath head zoned limits from path limits
Date: Tue, 2 Jun 2026 13:31:14 +0100	[thread overview]
Message-ID: <ah7NEVWsaCYfVEcY@kbusch-mbp> (raw)
In-Reply-To: <20260528073601.4139342-1-sangyao@kylinos.cn>

On Thu, May 28, 2026 at 03:36:01PM +0800, Yao Sang wrote:
> queue_limits_stack_bdev() updates the multipath head limits from the
> path queue, but it does not propagate max_open_zones or
> max_active_zones. As a result, a zoned multipath namespace head can
> keep stale 0/0 values even after a ready path reports finite zoned
> resource limits.

Thanks, applied to nvme-7.2.


      parent reply	other threads:[~2026-06-02 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  7:36 [PATCH v4] nvme: refresh multipath head zoned limits from path limits Yao Sang
2026-05-28  8:29 ` Christoph Hellwig
2026-06-02 12:31 ` Keith Busch [this message]

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=ah7NEVWsaCYfVEcY@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=sangyao@kylinos.cn \
    --cc=shinichiro.kawasaki@wdc.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