[PATCH] nvme: stop using AWUPF

John Garry john.g.garry at oracle.com
Mon Jan 26 08:07:01 PST 2026


On 26/01/2026 15:14, Christoph Hellwig wrote:
> On Mon, Jan 26, 2026 at 01:28:42PM +0000, John Garry wrote:
>> As for the per-controller AWUPF, how this value applies to shared
>> namespaces is missing in the specification. Furthermore, the value is in
>> terms of logical blocks, which is an NS entity.
>>
>> Since AWUPF is so poorly defined, stop using it already together.
>> Hopefully this will force vendors to implement NAWUPF support always.
>>
>> Note that AWUPF not only effects atomic write support, but also the
>> physical block size reported for the device.
> 
> Can you add a dev_info to the kernel log when AWUPF is set, but
> NAWUPF is not? 

Sure

> This might really help with debugging any issue
> if people were already using the atomic write support (hopefuly
> not..), or if any other issue arises later.  Otherwise this looks
> good to me.
> 




More information about the Linux-nvme mailing list