From: Kanchan Joshi <joshi.k@samsung.com>
To: shinichiro.kawasaki@wdc.com
Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
mcgrof@kernel.org, Kanchan Joshi <joshi.k@samsung.com>
Subject: [PATCH blktests 1/2] common,fio: helper for version check
Date: Fri, 31 Mar 2023 09:14:13 +0530 [thread overview]
Message-ID: <20230331034414.42024-2-joshi.k@samsung.com> (raw)
In-Reply-To: <20230331034414.42024-1-joshi.k@samsung.com>
Add new helper _have_fio_ver which checks whether installed fio version
is greater than or equal to input.
Signed-off-by: Kanchan Joshi <joshi.k@samsung.com>
---
common/fio | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/common/fio b/common/fio
index bed76d5..67c5339 100644
--- a/common/fio
+++ b/common/fio
@@ -25,6 +25,20 @@ _have_fio_zbd_zonemode() {
fi
return 0
}
+# Check whether the version of the fio is greater than or equal to $1.$2.$3
+_have_fio_ver() {
+ local d=$1 e=$2 f=$3
+
+ _have_fio || return $?
+
+ IFS='.' read -r a b c < <(fio --version | cut -c 5- | sed 's/-.*//')
+ if [ $((a * 65536 + b * 256 + c)) -lt $((d * 65536 + e * 256 + f)) ];
+ then
+ SKIP_REASONS+=("fio version too old")
+ return 1
+ fi
+ return 0
+}
declare -A FIO_TERSE_FIELDS
FIO_TERSE_FIELDS=(
--
2.25.1
next prev parent reply other threads:[~2023-03-31 3:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230331034524epcas5p31c3793c0c2071846ed82ff0f1369e90d@epcas5p3.samsung.com>
2023-03-31 3:44 ` [PATCH blktests 0/2] nvme uring-passthrough test Kanchan Joshi
2023-03-31 3:44 ` Kanchan Joshi [this message]
2023-03-31 3:44 ` [PATCH blktests 2/2] nvme/047: add test for uring-passthrough Kanchan Joshi
2023-04-07 8:07 ` Shin'ichiro Kawasaki
2023-04-10 0:43 ` Shin'ichiro Kawasaki
2023-04-10 12:43 ` Kanchan Joshi
2023-04-11 1:35 ` Shin'ichiro Kawasaki
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=20230331034414.42024-2-joshi.k@samsung.com \
--to=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mcgrof@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