From: Zhang Yi <yi.zhang@huaweicloud.com>
To: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@lst.de, tytso@mit.edu, djwong@kernel.org,
john.g.garry@oracle.com, bmarzins@redhat.com,
chaitanyak@nvidia.com, shinichiro.kawasaki@wdc.com,
yi.zhang@huawei.com, yi.zhang@huaweicloud.com,
chengzhihao1@huawei.com, yukuai3@huawei.com,
yangerkun@huawei.com
Subject: [PATCH blktests 0/3] blktest: add unmap write zeroes tests
Date: Tue, 18 Mar 2025 15:28:32 +0800 [thread overview]
Message-ID: <20250318072835.3508696-1-yi.zhang@huaweicloud.com> (raw)
From: Zhang Yi <yi.zhang@huawei.com>
The Linux kernel is planning to support FALLOC_FL_WRITE_ZEROES in
fallocate(2). Add tests for the newly added BLK_FEAT_WRITE_ZEROES_UNMAP
feature flag on the block device queue limit. These tests test block
device unmap write zeroes sysfs interface
/sys/block/<disk>/queue/write_zeroes_unmap
with various SCSI/NVMe/device-mapper devices.
The /sys/block/<disk>/queue/write_zeroes_unmap interface should return
1 if the block device supports unmap write zeroes command, and it should
return 0 otherwise.
- scsi/010 test SCSI devices.
- dm/003 test device mapper stacked devices.
- nvme/060 test NVMe devices.
Thanks,
Yi.
Zhang Yi (3):
scsi/010: add unmap write zeroes tests
dm/003: add unmap write zeroes tests
nvme/060: add unmap write zeroes tests
common/rc | 16 +++++++++++
tests/dm/003 | 57 ++++++++++++++++++++++++++++++++++++++
tests/dm/003.out | 2 ++
tests/nvme/060 | 68 ++++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/060.out | 4 +++
tests/scsi/010 | 56 ++++++++++++++++++++++++++++++++++++++
tests/scsi/010.out | 2 ++
7 files changed, 205 insertions(+)
create mode 100755 tests/dm/003
create mode 100644 tests/dm/003.out
create mode 100755 tests/nvme/060
create mode 100644 tests/nvme/060.out
create mode 100755 tests/scsi/010
create mode 100644 tests/scsi/010.out
--
2.46.1
next reply other threads:[~2025-03-18 7:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 7:28 Zhang Yi [this message]
2025-03-18 7:28 ` [PATCH blktests 1/3] scsi/010: add unmap write zeroes tests Zhang Yi
2025-04-03 7:26 ` Shinichiro Kawasaki
2025-04-28 3:32 ` Zhang Yi
2025-03-18 7:28 ` [PATCH blktests 2/3] dm/003: " Zhang Yi
2025-04-03 7:43 ` Shinichiro Kawasaki
2025-04-28 4:32 ` Zhang Yi
2025-04-28 8:13 ` Shinichiro Kawasaki
2025-04-28 9:04 ` Zhang Yi
2025-04-28 9:25 ` Shinichiro Kawasaki
2025-04-28 13:55 ` Zhang Yi
2025-03-18 7:28 ` [PATCH blktests 3/3] nvme/060: " Zhang Yi
2025-04-03 7:49 ` Shinichiro Kawasaki
2025-04-03 7:55 ` [PATCH blktests 0/3] blktest: " Shinichiro Kawasaki
2025-04-28 4:34 ` Zhang Yi
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=20250318072835.3508696-1-yi.zhang@huaweicloud.com \
--to=yi.zhang@huaweicloud.com \
--cc=bmarzins@redhat.com \
--cc=chaitanyak@nvidia.com \
--cc=chengzhihao1@huawei.com \
--cc=djwong@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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).