From: Christoph Hellwig <hch@infradead.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>,
eguan@redhat.com, fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH 2/2] fstests: run xfs_io as multi threaded process
Date: Sun, 16 Oct 2016 00:14:58 -0700 [thread overview]
Message-ID: <20161016071458.GA17675@infradead.org> (raw)
In-Reply-To: <CAOQ4uxjumg_VO3LV7rgtHbO=yTmxUp6KdpmrCh8ASEjG6tG3XA@mail.gmail.com>
On Sat, Oct 15, 2016 at 11:59:22PM +0300, Amir Goldstein wrote:
> So far so good, but then I looked closer at its sister test
> generic/132, which is
> an even more CPU intensive test, also of many small reads and writes
> from few xfs_io runs.
> This is not a 'quick' group test.
> Here the runtime difference was significant 17sec without -M and 20sec
> with -M flag.
>
> So without looking much closer into other non quick tests, I think
> that perhaps the
> best value option is to turn on -M flag for all the quick tests.
>
> What do you think?
Sounds like a good idea, now how do we find out in the xfs_io
helper if it's a quick test?
next prev parent reply other threads:[~2016-10-16 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 20:43 [PATCH 1/2] fstests: fix call sites that used xfs_io directly Amir Goldstein
2016-10-14 20:43 ` [PATCH 2/2] fstests: run xfs_io as multi threaded process Amir Goldstein
2016-10-15 9:11 ` Christoph Hellwig
2016-10-15 15:13 ` Amir Goldstein
2016-10-15 17:04 ` Christoph Hellwig
2016-10-15 20:59 ` Amir Goldstein
2016-10-16 7:14 ` Christoph Hellwig [this message]
2016-10-16 8:51 ` Amir Goldstein
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=20161016071458.GA17675@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@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