From: Alan Adamson <alan.adamson@oracle.com>
To: linux-block@vger.kernel.org
Cc: linux-scsi@vger.kernel.org, alan.adamson@oracle.com,
linux-nvme@lists.infradead.org, shinichiro.kawasaki@wdc.com
Subject: [PATCH v2 blktests 0/2] Add atomic write tests for scsi and nvme
Date: Tue, 28 Jan 2025 15:50:32 -0800 [thread overview]
Message-ID: <20250128235034.307987-1-alan.adamson@oracle.com> (raw)
Changes in v2:
- Add additional comments in common/xfs
- Remove xfs_io and kernel version checking
- Simplify paths for sysfs attributes
- Fix failed case output (missing echo) in scsi/009
- Add local variable that sets Test # and description (test_desc) for scsi/009 and nvme/059
- Only use scsi_debug device if no scsi test device is provided.
- nvme testing done with qemu-nvme.
- scsi testing done with scsi_debug and qemu-scsi (no atomic write support). No testing on
atomic write capable scsi devices was done.
-------------------------------------------------------------------------------------------
Add tests for atomic write support.
Tests will be delivered for scsi (using scsi_debug) and nvme. NVMe can use the qemu-nvme
emulated device that supports Controller-based Atomic Parameters (QEMU 9.2).
The xfs_io utility delivered with the xfsprogs-devel package (version 6.12) is required by
these tests.
The Linux Kernel 6.11 (and greater) supports Atomic Writes and is required by these tests.
next reply other threads:[~2025-01-28 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 23:50 Alan Adamson [this message]
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
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=20250128235034.307987-1-alan.adamson@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