From: alan.adamson@oracle.com
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH v2 blktests 2/2] nvme/059: add atomic write tests
Date: Tue, 4 Feb 2025 10:57:56 -0800 [thread overview]
Message-ID: <fd76be2c-1e27-4ecd-b67e-fa57cf52e9ab@oracle.com> (raw)
In-Reply-To: <vhdb3rsa4vgxm6nm7js75cnlxpv7d4rjxdvqpa5b63u442m3sd@b7w5w6mzjj35>
On 1/31/25 4:50 AM, Shinichiro Kawasaki wrote:
> On Jan 28, 2025 / 15:50, Alan Adamson wrote:
>> Tests basic atomic write functionality using NVMe devices
>> that support the AWUN and AWUPF Controller Atomic Parameters
>> and NAWUN and NAWUPF Namespace Atomic Parameters.
>>
>> Testing areas include:
>>
>> - Verify sysfs atomic write attributes are consistent with
>> atomic write capablities advertised by the NVMe HW.
>>
>> - Verify the atomic write paramters of statx are correct using
>> xfs_io.
>>
>> - Perform a pwritev2() (with and without RWF_ATOMIC flag) using
>> xfs_io:
>> - maximum byte size (atomic_write_unit_max_bytes)
>> - a write larger than atomic_write_unit_max_bytes
> These test contests are smallre than those in scsi/009. Is it intentional?
> No "minimum byte size" test, and no "a write smaller than
> atomic_write_unit_min_bytes" test.
SCSI supports atomic writes a bit differently than NVMe. SCSI has an
atomic granularity which translates to a minimum write size when doing
an atomic write. NVMe doesn't have this concept and always guarantees
writes of 1 block will be atomic so the additional tests aren't need for
NVMe.
Alan
prev parent reply other threads:[~2025-02-04 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 23:50 [PATCH v2 blktests 0/2] Add atomic write tests for scsi and nvme Alan Adamson
2025-01-28 23:50 ` [PATCH v2 blktests 1/2] scsi/009: add atomic write tests Alan Adamson
2025-01-31 12:44 ` Shinichiro Kawasaki
2025-01-28 23:50 ` [PATCH v2 blktests 2/2] nvme/059: " Alan Adamson
2025-01-31 12:50 ` Shinichiro Kawasaki
2025-02-04 18:57 ` 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=fd76be2c-1e27-4ecd-b67e-fa57cf52e9ab@oracle.com \
--to=alan.adamson@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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