From: Omar Sandoval <osandov@osandov.com>
To: Xiao Liang <xiliang@redhat.com>
Cc: linux-block@vger.kernel.org, osandov@fb.com
Subject: Re: [PATCH blktests] block/020: dynamically change iodepth if test aio-nr lager than aio-max-nr
Date: Thu, 4 Apr 2019 11:10:55 -0700 [thread overview]
Message-ID: <20190404181055.GB25741@vader> (raw)
In-Reply-To: <20190401033800.6032-1-xiliang@redhat.com>
On Mon, Apr 01, 2019 at 11:38:00AM +0800, Xiao Liang wrote:
> When system has large count of cpus(eg. 96), the test failed as aio-nr over
> aio-max-nr limitation.
>
> This patch continues to use 1024 as default iodepth, but change it if
> iodepth*$(nproc) > aio-max-nr.
>
> Signed-off-by: Xiao Liang <xiliang@redhat.com>
> ---
> tests/block/020 | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/tests/block/020 b/tests/block/020
> index 39dde66..f03c131 100755
> --- a/tests/block/020
> +++ b/tests/block/020
> @@ -29,10 +29,16 @@ test() {
> # shellcheck disable=SC2207
> scheds=($(sed 's/[][]//g' /sys/block/nullb0/queue/scheduler))
>
> + aio_max_nr=$(cat /proc/sys/fs/aio-max-nr)
> + max_iodepth=$(($aio_max_nr/$(nproc)))
> + iodepth=1024
> + if (( $iodepth > $max_iodepth )); then
> + iodepth=$max_iodepth
> + fi
This has a few shellcheck errors:
tests/block/020:33:17: note: $/${} is unnecessary on arithmetic variables. [SC2004]
tests/block/020:35:8: note: $/${} is unnecessary on arithmetic variables. [SC2004]
tests/block/020:35:19: note: $/${} is unnecessary on arithmetic variables. [SC2004]
Can you please address those and resend?
Thanks!
prev parent reply other threads:[~2019-04-04 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 3:38 [PATCH blktests] block/020: dynamically change iodepth if test aio-nr lager than aio-max-nr Xiao Liang
2019-04-04 18:10 ` Omar Sandoval [this message]
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=20190404181055.GB25741@vader \
--to=osandov@osandov.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
--cc=xiliang@redhat.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