From: Yao Sang <sangyao@kylinos.cn>
To: john.g.garry@oracle.com
Cc: axboe@kernel.dk, hch@lst.de, john.garry@linux.dev,
kbusch@kernel.org, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org, sagi@grimberg.me,
sangyao@kylinos.cn
Subject: Re: [PATCH v3 0/5] block, nvme: support same-LBA multipath limit stacking
Date: Thu, 10 Sep 2026 18:08:48 +0800 [thread overview]
Message-ID: <20260910100848.1248846-1-sangyao@kylinos.cn> (raw)
In-Reply-To: <b6372900-7be4-4e6e-94ae-f816341e4c07@oracle.com>
Hi John,
Sorry for the late reply, and thanks for the review.
Initializing the head limits only once needs some care, as we still
need to refresh them after Format NVM and namespace changes.
I'm working on this and will send v4 once it's ready.
Thanks,
Yao
prev parent reply other threads:[~2026-09-10 10:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 10:10 [PATCH v3 0/5] block, nvme: support same-LBA multipath limit stacking Yao Sang
2026-08-21 10:10 ` [PATCH v3 1/5] nvme: factor namespace-head queue-limit update Yao Sang
2026-08-21 10:10 ` [PATCH v3 2/5] block: factor mapped-range topology out of blk_stack_limits Yao Sang
2026-08-21 10:10 ` [PATCH v3 3/5] block: factor path limits " Yao Sang
2026-08-21 10:10 ` [PATCH v3 4/5] block: factor atomic write hardware limit stacking Yao Sang
2026-08-21 10:10 ` [PATCH v3 5/5] block, nvme: add same-LBA multipath limit helpers Yao Sang
2026-09-07 9:44 ` John Garry
2026-08-31 8:03 ` [PATCH v3 0/5] block, nvme: support same-LBA multipath limit stacking Yao Sang
2026-09-07 9:34 ` John Garry
2026-09-10 10:08 ` Yao Sang [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=20260910100848.1248846-1-sangyao@kylinos.cn \
--to=sangyao@kylinos.cn \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=john.garry@linux.dev \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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