From: Daniel Wagner <dwagner@suse.de>
To: linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Chaitanya Kulkarni <kch@nvidia.com>,
Shin'ichiro Kawasaki <shinichiro@fastmail.com>,
Daniel Wagner <dwagner@suse.de>
Subject: [PATCH blktests v2 3/9] common-xfs: Make size argument optional for _xfs_run_fio_verify_io
Date: Thu, 20 Apr 2023 20:31:13 +0200 [thread overview]
Message-ID: <20230420183121.4489-5-dwagner@suse.de> (raw)
In-Reply-To: <20230420183121.4489-1-dwagner@suse.de>
Make the size argument optional by reading the filesystem info. The
caller doesn't have to guess (or calculate) how big the max IO size.
The log data structure of XFS is reducing the capacity.
Signed-off-by: Daniel Wagner <dwagner@suse.de>
---
common/xfs | 6 ++++++
tests/nvme/012 | 2 +-
tests/nvme/013 | 2 +-
tests/nvme/035 | 2 +-
4 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/common/xfs b/common/xfs
index 2c5d96164ac1..ec35599e017b 100644
--- a/common/xfs
+++ b/common/xfs
@@ -27,6 +27,12 @@ _xfs_run_fio_verify_io() {
_xfs_mkfs_and_mount "${bdev}" "${mount_dir}" >> "${FULL}" 2>&1
+ if [[ -z "${sz}" ]]; then
+ local avail
+ avail="$(df --output=avail "${mount_dir}" | awk 'NR==2 {print $1}')"
+ sz="$(printf "%d" $((avail / 1024 - 1 )))m"
+ fi
+
_run_fio_verify_io --size="$sz" --directory="${mount_dir}/"
umount "${mount_dir}" >> "${FULL}" 2>&1
diff --git a/tests/nvme/012 b/tests/nvme/012
index e60082c2e751..c9d24388306d 100755
--- a/tests/nvme/012
+++ b/tests/nvme/012
@@ -44,7 +44,7 @@ test() {
cat "/sys/block/${nvmedev}n1/uuid"
cat "/sys/block/${nvmedev}n1/wwid"
- _xfs_run_fio_verify_io "/dev/${nvmedev}n1" "900m"
+ _xfs_run_fio_verify_io "/dev/${nvmedev}n1"
_nvme_disconnect_subsys "${subsys_name}"
diff --git a/tests/nvme/013 b/tests/nvme/013
index 9d60a7df4577..265b6968fd34 100755
--- a/tests/nvme/013
+++ b/tests/nvme/013
@@ -41,7 +41,7 @@ test() {
cat "/sys/block/${nvmedev}n1/uuid"
cat "/sys/block/${nvmedev}n1/wwid"
- _xfs_run_fio_verify_io "/dev/${nvmedev}n1" "900m"
+ _xfs_run_fio_verify_io "/dev/${nvmedev}n1"
_nvme_disconnect_subsys "${subsys_name}"
diff --git a/tests/nvme/035 b/tests/nvme/035
index eb1024edddbf..8b485bc8e682 100755
--- a/tests/nvme/035
+++ b/tests/nvme/035
@@ -32,7 +32,7 @@ test_device() {
port=$(_nvmet_passthru_target_setup "${subsys}")
nsdev=$(_nvmet_passthru_target_connect "${nvme_trtype}" "${subsys}")
- _xfs_run_fio_verify_io "${nsdev}" "900m"
+ _xfs_run_fio_verify_io "${nsdev}"
_nvme_disconnect_subsys "${subsys}"
_nvmet_passthru_target_cleanup "${port}" "${subsys}"
--
2.40.0
next prev parent reply other threads:[~2023-04-20 18:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 18:31 [PATCH blktests v2 0/9] nvme testsuite runtime optimization Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 1/9] nvme-rc: Auto convert test device size info Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 2/9] nvme: Do not hard code device size for dd test Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 2/4] nvme: Make test image size configurable Daniel Wagner
2023-04-20 18:31 ` Daniel Wagner [this message]
2023-04-20 18:31 ` [PATCH blktests v2 3/4] nvme-rc: Move discovery generation counter code to rc Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 4/4] nvme: Make the number iterations configurable Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 4/9] nvme: Use runtime fio background jobs Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 5/9] nvme: Make test image size configurable Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 6/9] nvme-rc: Add minimal test image size requirement Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 7/9] nvme-rc: Calculate IO size for fio jobs Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 8/9] nvme-rc: Move discovery generation counter code to rc Daniel Wagner
2023-04-20 18:31 ` [PATCH blktests v2 9/9] nvme: Make the number iterations configurable Daniel Wagner
2023-04-21 5:59 ` [PATCH blktests v2 0/9] nvme testsuite runtime optimization Daniel Wagner
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=20230420183121.4489-5-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro@fastmail.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