[PATCH 1/3] nvmet: use subsys->max_nsid to report MNAN

Christoph Hellwig hch at lst.de
Sun Jun 13 23:36:29 PDT 2021


On Sun, Jun 13, 2021 at 01:02:50PM -0700, Chaitanya Kulkarni wrote:
> For Spec regarding MNAN value:-
> 
> If the controller supports Asymmetric Namespace Access Reporting, then
> this field shall be set to a non-zero value that is less than or equal
> to the NN value.
> 
> Instead of using NVMET_MAX_NAMESPACES use subsys->max_nsid to set the
> MNAN value.

I think this is a rather bad idea as it is supposed to be a relatively
static number.  I think the right fix is to stop playing games with a
dyanmic NN and always report UINT_MAX in nn.



More information about the Linux-nvme mailing list