From: Omar Sandoval <osandov@osandov.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Jens Axboe <axboe@fb.com>,
Linux Block Layer Mailinglist <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests v2] tests: use nproc to get number of CPUs for fio jobs
Date: Fri, 14 Jul 2017 10:11:10 -0700 [thread overview]
Message-ID: <20170714171110.GA13690@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <20170630090735.11709-1-jthumshirn@suse.de>
On Fri, Jun 30, 2017 at 11:07:35AM +0200, Johannes Thumshirn wrote:
> Use nproc to get number of CPUs for fio jobs and introduce
> _run_fio_rand_io helper for parallel IO which we don't really care about
> the details and just want some IO.
Thanks, Johannes, applied with a fix below.
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
> ---
> common/fio | 7 +++++++
> tests/block/005 | 4 +---
> tests/block/006 | 2 +-
> tests/block/008 | 4 +---
> tests/block/011 | 5 ++---
> 5 files changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/common/fio b/common/fio
> index 86ed4b2b7180..2b0759d19f5d 100644
> --- a/common/fio
> +++ b/common/fio
> @@ -166,6 +166,13 @@ _run_fio() {
> fio "${args[@]}" "$@"
> }
>
> +# Wrapper around _run_fio used if you need some I/O but don't really care much
> +# about the details
> +_run_fio_rand_io() {
> + _run_fio --bs=4k --rw=randread --norandommap --numjobs=$(nproc) \
> + --name=reads --direct=1
I added "$@" at the end here, it looks like that's what you intended and
it doesn't work otherwise.
> +}
> +
prev parent reply other threads:[~2017-07-14 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 9:07 [PATCH blktests v2] tests: use nproc to get number of CPUs for fio jobs Johannes Thumshirn
2017-07-14 9:26 ` Johannes Thumshirn
2017-07-14 17:11 ` 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=20170714171110.GA13690@vader.DHCP.thefacebook.com \
--to=osandov@osandov.com \
--cc=axboe@fb.com \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
/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