From: Bart Van Assche <bvanassche@acm.org>
To: Omar Sandoval <osandov@fb.com>
Cc: linux-block@vger.kernel.org,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
Daniel Wagner <dwagner@suse.de>,
Bart Van Assche <bvanassche@acm.org>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: [PATCH blktests v4 3/4] Introduce the function _configure_null_blk()
Date: Sat, 28 Mar 2020 11:22:50 -0700 [thread overview]
Message-ID: <20200328182251.19945-4-bvanassche@acm.org> (raw)
In-Reply-To: <20200328182251.19945-1-bvanassche@acm.org>
Introduce a function for creating a null_blk device instance through
configfs.
Suggested-by: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Reviewed-by: Daniel Wagner <dwagner@suse.de>
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
---
common/multipath-over-rdma | 17 +++++------------
common/null_blk | 14 ++++++++++++++
tests/block/029 | 16 ++--------------
3 files changed, 21 insertions(+), 26 deletions(-)
diff --git a/common/multipath-over-rdma b/common/multipath-over-rdma
index a56e7a8269db..e689a9633d13 100644
--- a/common/multipath-over-rdma
+++ b/common/multipath-over-rdma
@@ -620,18 +620,11 @@ run_fio() {
configure_null_blk() {
local i
- (
- cd /sys/kernel/config/nullb || return $?
- for i in nullb0 nullb1; do (
- { mkdir -p $i &&
- cd $i &&
- echo 0 > completion_nsec &&
- echo 512 > blocksize &&
- echo $((ramdisk_size>>20)) > size &&
- echo 1 > memory_backed &&
- echo 1 > power; } || exit $?
- ) done
- )
+ for i in nullb0 nullb1; do
+ _configure_null_blk $i completion_nsec=0 blocksize=512 \
+ size=$((ramdisk_size>>20)) memory_backed=1 \
+ power=1 || return $?
+ done
ls -l /dev/nullb* &>>"$FULL"
}
diff --git a/common/null_blk b/common/null_blk
index a4140e365955..6611db03a00e 100644
--- a/common/null_blk
+++ b/common/null_blk
@@ -29,6 +29,20 @@ _init_null_blk() {
return 0
}
+# Configure one null_blk instance with name $1 and parameters $2..${$#}.
+_configure_null_blk() {
+ local nullb=/sys/kernel/config/nullb/$1 param val
+
+ shift
+ mkdir "$nullb" || return $?
+ while [[ $# -gt 0 ]]; do
+ param="${1%%=*}"
+ val="${1#*=}"
+ shift
+ echo "$val" > "$nullb/$param" || return $?
+ done
+}
+
_exit_null_blk() {
_remove_null_blk_devices
udevadm settle
diff --git a/tests/block/029 b/tests/block/029
index 0d521edb0cf6..dbb582eab473 100755
--- a/tests/block/029
+++ b/tests/block/029
@@ -14,19 +14,6 @@ requires() {
_have_null_blk
}
-# Configure one null_blk instance.
-configure_null_blk() {
- local nullb0="/sys/kernel/config/nullb/nullb0"
-
- mkdir "$nullb0" &&
- echo 0 > "$nullb0/completion_nsec" &&
- echo 512 > "$nullb0/blocksize" &&
- echo 16 > "$nullb0/size" &&
- echo 1 > "$nullb0/memory_backed" &&
- echo 1 > "$nullb0/power" &&
- ls -l /dev/nullb* &>>"$FULL"
-}
-
modify_nr_hw_queues() {
local deadline num_cpus
@@ -45,7 +32,8 @@ test() {
: "${TIMEOUT:=30}"
_init_null_blk nr_devices=0 queue_mode=2 &&
- configure_null_blk
+ _configure_null_blk nullb0 completion_nsec=0 blocksize=512 \
+ size=16 memory_backed=1 power=1 &&
if { echo 1 >$sq; } 2>/dev/null; then
modify_nr_hw_queues &
fio --rw=randwrite --bs=4K --loops=$((10**6)) \
next prev parent reply other threads:[~2020-03-28 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 18:22 [PATCH blktests v4 0/4] Test the blk_mq_realloc_hw_ctxs() error path Bart Van Assche
2020-03-28 18:22 ` [PATCH blktests v4 1/4] Make _exit_null_blk remove all null_blk device instances Bart Van Assche
2020-03-28 18:22 ` [PATCH blktests v4 2/4] Use _{init,exit}_null_blk instead of open-coding these functions Bart Van Assche
2020-03-28 18:22 ` Bart Van Assche [this message]
2020-03-28 18:22 ` [PATCH blktests v4 4/4] Add a test that triggers the blk_mq_realloc_hw_ctxs() error path Bart Van Assche
2020-03-30 7:39 ` Daniel Wagner
2020-04-08 22:05 ` [PATCH blktests v4 0/4] Test " Omar Sandoval
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=20200328182251.19945-4-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=chaitanya.kulkarni@wdc.com \
--cc=dwagner@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.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).