From: Tokunori Ikegami <ikegami.t@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 2/2] nvme: initialize known effects to set ns_mgmt NCC and ns_attach NIC
Date: Wed, 29 Apr 2026 21:49:03 +0900 [thread overview]
Message-ID: <51b59525-c551-40e5-976c-4c5a7a1bc31f@gmail.com> (raw)
In-Reply-To: <afHF6FJAPbDXAniR@kbusch-mbp.client.m3-hotspots.de>
On 2026/04/29 17:48, Keith Busch wrote:
> Yes, but the namespace management commands are also optional, so it
> sounds weird to me for an implementation to choose to support the
> optional command that's more difficult to do and skip the easy log page
> that advertises support for it.
Okay understood as the changes not necessary.
> You can attach namespaces to controllers driven by a different host, so
> the AEN is the only way to trigger a rescan in such a scenario without
> admin intervention. An extra scan_work is otherwise harmless, I don't
> see a particular need to introduce a mechanism to avoid it.
Noted this also. Thank you.
prev parent reply other threads:[~2026-04-29 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 13:04 [PATCH v3 0/2] scan_work improvement Tokunori Ikegami
2026-04-25 13:04 ` [PATCH v3 1/2] nvme: delete unnecessary empty lines Tokunori Ikegami
2026-04-25 13:04 ` [PATCH v3 2/2] nvme: initialize known effects to set ns_mgmt NCC and ns_attach NIC Tokunori Ikegami
2026-04-28 6:51 ` Keith Busch
2026-04-29 6:08 ` Tokunori Ikegami
2026-04-29 8:48 ` Keith Busch
2026-04-29 12:49 ` Tokunori Ikegami [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=51b59525-c551-40e5-976c-4c5a7a1bc31f@gmail.com \
--to=ikegami.t@gmail.com \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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