From: Omar Sandoval <osandov@osandov.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Omar Sandoval <osandov@fb.com>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Marco Patalano <mpatalan@redhat.com>,
"Ewan D. Milne" <emilne@redhat.com>
Subject: Re: [PATCH] block/021: test setting 'nr_requests'
Date: Mon, 11 Jun 2018 13:40:09 -0700 [thread overview]
Message-ID: <20180611204009.GA10337@vader> (raw)
In-Reply-To: <20180602050204.20786-1-ming.lei@redhat.com>
On Sat, Jun 02, 2018 at 01:02:04PM +0800, Ming Lei wrote:
> 'nr_requests' can be a bit different for 'none' scheduler,
> and especially current blk-mq can only decrease this value
> for 'none.'
>
> The patch of 'blk-mq: fix read/write 'nr_requests' in case of 'none' scheduler'
> has been sent out for fixing this issue.
Applied with a couple of fixes mentioned below.
> Cc: Marco Patalano <mpatalan@redhat.com>
> Cc: "Ewan D. Milne" <emilne@redhat.com>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
> tests/block/021 | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/block/021.out | 2 ++
> 2 files changed, 53 insertions(+)
> create mode 100755 tests/block/021
> create mode 100755 tests/block/021.out
>
> diff --git a/tests/block/021 b/tests/block/021
> new file mode 100755
> index 000000000000..b72d9bd8b41d
> --- /dev/null
> +++ b/tests/block/021
> @@ -0,0 +1,51 @@
> +#!/bin/bash
> +#
> +# Test blk-mq request allocation when hardware tags are limited. Regression
> +# test for commit e6fc46498784 ("blk-mq: avoid starving tag allocation after
> +# allocating process migrates").
This wasn't updated for this test. I fixed it.
> +# Copyright (C) 2018 Ming Lei <ming.lei@redhat.com>
> +#
> +# This program is free software: you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation, either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program. If not, see <http://www.gnu.org/licenses/>.
> +
> +DESCRIPTION="read/write nr_requests on null-blk with different scheduler"
> +QUICK=1
> +
> +requires() {
> + _have_module null_blk
> +}
> +
> +test() {
> + echo "Running ${TEST_NAME}"
> +
> + modprobe -r null_blk
> + modprobe null_blk
> +
> + local scheds
> + # shellcheck disable=SC2207
> + scheds=($(sed 's/[][]//g' /sys/block/nullb0/queue/scheduler))
> +
> + for sched in "${scheds[@]}"; do
> + echo "Testing $sched" >> "$FULL"
> + echo "$sched" > /sys/block/nullb0/queue/scheduler
> + max_nr=`cat /sys/block/nullb0/queue/nr_requests`
I changed this to the preferred $() style command substitution.
> + for nr in `seq 4 $max_nr`; do
I changed this to the preferred bash for loop syntax.
> + echo $nr > /sys/block/nullb0/queue/nr_requests
> + done
> + done
> +
> + modprobe -r null_blk
> +
> + echo "Test complete"
> +}
> diff --git a/tests/block/021.out b/tests/block/021.out
> new file mode 100755
> index 000000000000..3a397c5c8ff5
> --- /dev/null
> +++ b/tests/block/021.out
> @@ -0,0 +1,2 @@
> +Running block/021
> +Test complete
> --
> 2.9.5
>
prev parent reply other threads:[~2018-06-11 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 5:02 [PATCH] block/021: test setting 'nr_requests' Ming Lei
2018-06-11 20:40 ` 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=20180611204009.GA10337@vader \
--to=osandov@osandov.com \
--cc=axboe@kernel.dk \
--cc=emilne@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mpatalan@redhat.com \
--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).