[PATCH v2 2/2] nvme: initialize known effects to set ns_mgmt NCC and ns_attach NIC

Tokunori Ikegami ikegami.t at gmail.com
Thu Apr 23 10:51:48 PDT 2026


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.




More information about the Linux-nvme mailing list