From: John Garry <john.g.garry@oracle.com>
To: Nilay Shroff <nilay@linux.ibm.com>, Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Jens Axboe <axboe@kernel.dk>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: What should we do about the nvme atomics mess?
Date: Tue, 9 Dec 2025 08:26:01 +0000 [thread overview]
Message-ID: <d2ce6a5d-f6e4-441c-957c-fefc33f3758d@oracle.com> (raw)
In-Reply-To: <4023a0ad-ef60-4307-aca6-514ee790d6c6@linux.ibm.com>
On 08/12/2025 12:11, Nilay Shroff wrote:
>>> Do you think that you could check with the OEM for updated firmware (that reports NAWUPF)?
>> Yes, certainly — we can check with the disk vendor for updated firmware that correctly reports
>> NAWUPF. I’ve already discussed this with my manager, and he’ll arrange a call with the vendor
>> so that I can directly explain the issue and what we want from the kernel perspective.
>> I’ll follow up with you once I’ve spoken to the vendor.
>>
> Just an update...
>
> We met with the vendor team and explained the current situation regarding atomic
> writes and the NVMe Linux kernel driver. I’m happy to report that they acknowledged
> the issue and agreed to provide updated firmware that advertises atomic write support
> using NAWUPF instead of AWUPF.
>
> We shall first receive a test firmware build with this change. Once our test team
> verifies that it behaves as expected, the vendor will proceed with a formal firmware
> release. I’ll keep you posted once we receive the updated firmware.
Thanks for the update. It's good to know that this vendor will provide
the required FW update.
Cheers
prev parent reply other threads:[~2025-12-09 8:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 14:18 What should we do about the nvme atomics mess? Christoph Hellwig
2025-07-07 14:24 ` Keith Busch
2025-07-07 15:26 ` Hannes Reinecke
2025-07-07 15:56 ` Keith Busch
2025-07-07 23:35 ` Chaitanya Kulkarni
2025-07-08 9:47 ` Christoph Hellwig
2025-07-08 15:19 ` Keith Busch
2025-07-08 1:27 ` Ming Lei
2025-07-08 2:27 ` Keith Busch
2025-07-08 2:46 ` Ming Lei
2025-07-08 2:56 ` Keith Busch
2025-07-08 3:17 ` Ming Lei
2025-07-08 9:38 ` Niklas Cassel
2025-07-08 9:48 ` Christoph Hellwig
2025-07-08 10:08 ` John Garry
2025-07-09 7:51 ` Nilay Shroff
2025-07-09 21:28 ` Keith Busch
2025-07-10 5:07 ` Nilay Shroff
2025-07-10 7:17 ` Christoph Hellwig
2025-10-20 13:42 ` John Garry
2025-10-21 15:02 ` Nilay Shroff
2025-10-22 8:50 ` John Garry
2025-10-22 15:24 ` Nilay Shroff
2025-12-08 12:11 ` Nilay Shroff
2025-12-09 8:26 ` John Garry [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2ce6a5d-f6e4-441c-957c-fefc33f3758d@oracle.com \
--to=john.g.garry@oracle.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=nilay@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).