[PATCH 1/3 v2] nvme: make independent ns identify default
Matias Bjørling
m at bjorling.me
Mon Nov 4 05:24:25 PST 2024
>> FYI, I still disagree with this for the same reason as before.
>> Assuming we're not really going to see hard drivers I'd be fine
>> with using it by default for 2.0 (or better even 2.1) by default.
>
> I've got the rest of the required logs and identifications implemented
> in nvmet to support this. There's one more issue, though, if we do
> restrict the identify to >= 2.0 or 2.1. nvmet reports 1.3, and I suspect
> there's a bit more work than just changing the value of NVMET_DEFAULT_VS
> in order to comply with claiming that version.
>
Awesome. I'll hold off the implementation. Would you like me to take
your patches for a spin?
More information about the Linux-nvme
mailing list