[PATCH V2] nvme: set non-mdts limits in nvme_scan_work

[Chaitanya Kulkarni]

On 5/18/22 07:51, Christoph Hellwig wrote:
> On Wed, May 18, 2022 at 08:42:02AM -0600, Keith Busch wrote:
>> On Wed, May 18, 2022 at 10:56:02AM +0200, Christoph Hellwig wrote:
>>> This re-reads the limits everytime a namespace is added or deleted,
>>> is that really such a good idea?
>>
>> The limits are reported in logical blocks, which is dependent on the formats
>> that attached namespaces have.
> 
> Well, the Identify controller limits aren't really supposed to
> change randomly.  But ok, maybe that is a reason to frequently
> rescan due work around this broken design.  Can we add a comment
> to explain that?

sent out V3 with added comment.

-ck