From: Omar Sandoval <osandov@osandov.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Omar Sandoval <osandov@fb.com>,
linux-block@vger.kernel.org,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH blktests 2/2] Add a test that triggers blk_mq_update_nr_hw_queues()
Date: Thu, 24 Oct 2019 10:42:42 -0700 [thread overview]
Message-ID: <20191024174242.GB137052@vader> (raw)
In-Reply-To: <20191021225719.211651-3-bvanassche@acm.org>
On Mon, Oct 21, 2019 at 03:57:19PM -0700, Bart Van Assche wrote:
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
> tests/block/029 | 63 +++++++++++++++++++++++++++++++++++++++++++++
> tests/block/029.out | 1 +
> 2 files changed, 64 insertions(+)
> create mode 100755 tests/block/029
> create mode 100644 tests/block/029.out
>
> diff --git a/tests/block/029 b/tests/block/029
> new file mode 100755
> index 000000000000..1999168603c1
> --- /dev/null
> +++ b/tests/block/029
> @@ -0,0 +1,63 @@
> +#!/bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (C) 2019 Google Inc.
> +#
> +# Trigger blk_mq_update_nr_hw_queues().
> +
> +. tests/block/rc
> +. common/null_blk
> +
> +DESCRIPTION="trigger blk_mq_update_nr_hw_queues()"
> +QUICK=1
> +
> +requires() {
> + _have_null_blk
> +}
> +
> +# Configure one null_blk instance.
> +configure_null_blk() {
> + (
> + cd /sys/kernel/config/nullb || return $?
> + (
> + mkdir -p nullb0 &&
> + cd nullb0 &&
> + echo 0 > completion_nsec &&
> + echo 512 > blocksize &&
> + echo 16 > size &&
> + echo 1 > memory_backed &&
> + echo 1 > power
> + )
> + ) &&
> + ls -l /dev/nullb* &>>"$FULL"
What's the point of these nested subshells? Can't this just be:
configure_null_blk() {
cd /sys/kernel/config/nullb &&
mkdir -p nullb0 &&
cd nullb0 &&
echo 0 > completion_nsec &&
echo 512 > blocksize &&
echo 16 > size &&
echo 1 > memory_backed &&
echo 1 > power &&
ls -l /dev/nullb* &>>"$FULL"
}
> +}
> +
> +modify_nr_hw_queues() {
> + local deadline num_cpus
> +
> + deadline=$(($(_uptime_s) + TIMEOUT))
> + num_cpus=$(find /sys/devices/system/cpu -maxdepth 1 -name 'cpu[0-9]*' |
> + wc -l)
Please just use nproc. Or even better, can you just read the original
value of /sys/kernel/config/nullb/nullb0/submit_queues? Or does that
start at 1?
> + while [ "$(_uptime_s)" -lt "$deadline" ]; do
> + sleep .1
> + echo 1 > /sys/kernel/config/nullb/nullb0/submit_queues
> + sleep .1
> + echo "$num_cpus" > /sys/kernel/config/nullb/nullb0/submit_queues
> + done
> +}
> +
> +test() {
> + : "${TIMEOUT:=30}"
> + _init_null_blk nr_devices=0 queue_mode=2 &&
> + configure_null_blk
> + modify_nr_hw_queues &
> + fio --rw=randwrite --bs=4K --loops=$((10**6)) \
> + --iodepth=64 --group_reporting --sync=1 --direct=1 \
> + --ioengine=libaio --filename="/dev/nullb0" \
> + --runtime="${TIMEOUT}" --name=nullb0 \
> + --output="${RESULTS_DIR}/block/fio-output-029.txt" \
> + >>"$FULL"
> + wait
> + rmdir /sys/kernel/config/nullb/nullb0
> + _exit_null_blk
> + echo Passed
> +}
> diff --git a/tests/block/029.out b/tests/block/029.out
> new file mode 100644
> index 000000000000..863339fb8ced
> --- /dev/null
> +++ b/tests/block/029.out
> @@ -0,0 +1 @@
> +Passed
> --
> 2.23.0.866.gb869b98d4c-goog
>
next prev parent reply other threads:[~2019-10-24 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 22:57 [PATCH blktests 0/2] Add a test that triggers blk_mq_update_nr_hw_queues() Bart Van Assche
2019-10-21 22:57 ` [PATCH blktests 1/2] Move and rename uptime_s() Bart Van Assche
2019-10-22 17:55 ` Chaitanya Kulkarni
2019-10-24 17:27 ` Omar Sandoval
2019-10-24 17:41 ` Bart Van Assche
2019-10-24 17:44 ` Omar Sandoval
2019-10-21 22:57 ` [PATCH blktests 2/2] Add a test that triggers blk_mq_update_nr_hw_queues() Bart Van Assche
2019-10-22 17:59 ` Chaitanya Kulkarni
2019-10-24 17:42 ` Omar Sandoval [this message]
2019-10-24 17:55 ` Bart Van Assche
2019-10-24 17:58 ` 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=20191024174242.GB137052@vader \
--to=osandov@osandov.com \
--cc=bvanassche@acm.org \
--cc=jthumshirn@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