From: alan.adamson@oracle.com
To: Klaus Jensen <its@irrelevant.dk>
Cc: kbusch@kernel.org, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH 0/1] hw/nvme: add atomic write support
Date: Tue, 17 Sep 2024 09:38:11 -0700 [thread overview]
Message-ID: <ebfbedb9-8c93-469a-a101-c6b82d60302e@oracle.com> (raw)
In-Reply-To: <53d53e7b-247d-4546-8425-8bfa8561f907@oracle.com>
On 9/17/24 9:21 AM, alan.adamson@oracle.com wrote:
>
> On 9/17/24 12:59 AM, Klaus Jensen wrote:
>> On Aug 20 09:11, Alan Adamson wrote:
>>> Since there is work in the Linux NVMe Driver community to add Atomic
>>> Write
>>> support, it would be desirable to be able to test it with qemu nvme
>>> emulation.
>>> This patch will focus on supporting NVMe controller atomic write
>>> parameters (AWUN and
>>> AWUPF) but can be extended to support Namespace parameters (NAWUN
>>> and NAWUPF)
>>> and Boundaries (NABSN, NABO, and NABSPF).
>> Hi Alan,
>>
>> I am trying to test this with John's atomic-writes-v6.10-v9 linux
>> branch, but that does not seem to work for me.
>>
>> Do I need anything else?
>
> Hi Klaus,
>
> What are you trying to test?
>
> You can see if it is being setup properly with:
>
> [root@localhost ~]# nvme id-ctrl /dev/nvme0 | grep awupf
> awupf : 31
> [root@localhost ~]# nvme id-ctrl /dev/nvme0 | grep awun
> awun : 63
> [root@localhost ~]#
>
> With or without John's atomic support, for this case, 32k writes will
> be atomic while 64k writes will not be. This can be validated with fio
> since corruption is observed when using 64k writes.
>
> Alan
BTW, I'm going to send out a v2 of the patch that includes your suggestions.
Alan
prev parent reply other threads:[~2024-09-17 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 16:11 [PATCH 0/1] hw/nvme: add atomic write support Alan Adamson
2024-08-20 16:11 ` [PATCH 1/1] " Alan Adamson
2024-09-12 8:42 ` Klaus Jensen
2024-09-17 7:59 ` [PATCH 0/1] " Klaus Jensen
2024-09-17 16:21 ` alan.adamson
2024-09-17 16:38 ` alan.adamson [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=ebfbedb9-8c93-469a-a101-c6b82d60302e@oracle.com \
--to=alan.adamson@oracle.com \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).