From: Tokunori Ikegami <ikegami.t@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2 2/2] nvme: initialize known effects to set ns_mgmt NCC and ns_attach NIC
Date: Fri, 24 Apr 2026 02:51:48 +0900 [thread overview]
Message-ID: <7af729f6-25e7-483a-9a5e-770d6c6e6805@gmail.com> (raw)
In-Reply-To: <aem0x5CsghH7HoWd@infradead.org>
On 2026/04/23 14:57, Christoph Hellwig wrote:
> Can you explain the rational a little better here? Do you have a
> device that does not have these entries? And what problems does that
> cause for you for which workload?
The change is just an idea to improvement the scan_work to make sure as
always do scan for the ns_mgmt and ns_attach commands.
Actually I do not have the device as I have only a drive these entries
as NCC for ns_mgmt and NIC for ns_attach.
(Another drive I have but does not support both ns_attach and ns_mgmt
then does not have these entries. Also third drive broken then I can not
confirm it for now.)
All drives supporting ns_mgmt and ns_attach should have the entries but
I do not think the driver side not needed to be depended on it as always
do scan.
I tried to fix the issue below with the changes at first but the issue
was caused by the test script then currently resolved already.
<https://github.com/linux-nvme/nvme-cli/issues/3251>
So no need this change for now for the issue but in future still I think
we can reduce related issue or its investigation by the change.
prev parent reply other threads:[~2026-04-23 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 14:11 [PATCH v2 0/2] scan_work improvement Tokunori Ikegami
2026-04-22 14:11 ` [PATCH v2 1/2] nvme: delete unnecessary empty lines Tokunori Ikegami
2026-04-22 14:11 ` [PATCH v2 2/2] nvme: initialize known effects to set ns_mgmt NCC and ns_attach NIC Tokunori Ikegami
2026-04-23 5:57 ` Christoph Hellwig
2026-04-23 17:51 ` 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=7af729f6-25e7-483a-9a5e-770d6c6e6805@gmail.com \
--to=ikegami.t@gmail.com \
--cc=hch@infradead.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