From: Luis Chamberlain <mcgrof@kernel.org>
To: shinichiro.kawasaki@wdc.com
Cc: linux-block@vger.kernel.org, hare@suse.de,
patches@lists.linux.dev, gost.dev@samsung.com, mcgrof@kernel.org
Subject: [PATCH blktests 2/4] common/xfs: use min io for fs blocksize
Date: Wed, 18 Dec 2024 03:21:51 -0800 [thread overview]
Message-ID: <20241218112153.3917518-3-mcgrof@kernel.org> (raw)
In-Reply-To: <20241218112153.3917518-1-mcgrof@kernel.org>
Use the min io for the target block size. Likewise we need to increase
the log size if using a bs > 4096.
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
common/xfs | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/common/xfs b/common/xfs
index 569770fecd53..9a13258789e6 100644
--- a/common/xfs
+++ b/common/xfs
@@ -13,10 +13,16 @@ _have_xfs() {
_xfs_mkfs_and_mount() {
local bdev=$1
local mount_dir=$2
+ local bs=$(_test_dev_min_io $bdev)
+ local xfs_logsize="64m"
+
+ if [[ $bs -gt 4096 ]]; then
+ xfs_logsize="128m"
+ fi
mkdir -p "${mount_dir}"
umount "${mount_dir}"
- mkfs.xfs -l size=64m -f "${bdev}" || return $?
+ mkfs.xfs -l size=$xfs_logsize -f "${bdev}" -b size=$bs || return $?
mount "${bdev}" "${mount_dir}"
}
--
2.43.0
next prev parent reply other threads:[~2024-12-18 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 11:21 [PATCH blktests 0/4] enable bs > ps device testing Luis Chamberlain
2024-12-18 11:21 ` [PATCH blktests 1/4] common: add and use min io for fio Luis Chamberlain
2024-12-23 9:37 ` Shinichiro Kawasaki
2025-01-04 4:10 ` Luis Chamberlain
2025-01-07 5:19 ` Shinichiro Kawasaki
2025-02-04 19:06 ` Luis Chamberlain
2024-12-18 11:21 ` Luis Chamberlain [this message]
2024-12-18 11:21 ` [PATCH blktests 3/4] tests: use test device min io to support bs > ps Luis Chamberlain
2024-12-18 11:21 ` [PATCH blktests 4/4] nvme/053: provide time extension alternative Luis Chamberlain
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=20241218112153.3917518-3-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=patches@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.