From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 1/2] qemu-iotests: Speed up make check-block
Date: Tue, 25 Nov 2014 10:58:12 +0100 [thread overview]
Message-ID: <20141125095812.GC4641@noname.redhat.com> (raw)
In-Reply-To: <20141125094457.GB17930@fam-t430.nay.redhat.com>
Am 25.11.2014 um 10:44 hat Fam Zheng geschrieben:
> On Tue, 11/25 10:31, Max Reitz wrote:
> > On 2014-11-25 at 10:30, Kevin Wolf wrote:
> > >Am 25.11.2014 um 10:21 hat Max Reitz geschrieben:
> > >>On 2014-11-25 at 10:21, Kevin Wolf wrote:
> > >>>Am 25.11.2014 um 10:12 hat Max Reitz geschrieben:
> > >>>>On 2014-10-28 at 07:45, Fam Zheng wrote:
> > >>>>>Using /tmp (usually mounted as tmpfs) and cache=writeback, the quick
> > >>>>>group can be quicker.
> > >>>>>
> > >>>>>On my laptop (Lenovo T430s with Fedora 20), this reduces the time from
> > >>>>>50s to 30s.
> > >>>>>
> > >>>>>Signed-off-by: Fam Zheng <famz@redhat.com>
> > >>>>>---
> > >>>>> tests/qemu-iotests-quick.sh | 2 +-
> > >>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
> > >>>>>
> > >>>>>diff --git a/tests/qemu-iotests-quick.sh b/tests/qemu-iotests-quick.sh
> > >>>>>index 12af731..0b54dbf 100755
> > >>>>>--- a/tests/qemu-iotests-quick.sh
> > >>>>>+++ b/tests/qemu-iotests-quick.sh
> > >>>>>@@ -3,6 +3,6 @@
> > >>>>> cd tests/qemu-iotests
> > >>>>> ret=0
> > >>>>>-./check -T -qcow2 -g quick || ret=1
> > >>>>>+TEST_DIR=/tmp/qemu-iotests-quick-$$ ./check -T -qcow2 -g quick -c writeback || ret=1
> > >>>>There are (at least) two tests which don't work with -c writeback
> > >>>>(026 and 039), one of them is in the quick group (039). Why not use
> > >>>>-c writethrough? It doesn't make any difference on tmpfs anyway (we
> > >>>>can't omit it because that will break 091).
> > >>>Why use any -c? The default is the fast option writeback, and for those
> > >>>test cases that don't support writeback, something working is chosen
> > >>>instead.
> > >>Because that breaks 091.
> > >That's unfortunate. I wish tmpfs supported O_DIRECT...
>
> Indeed unfortunate!
>
> > >
> > >But let's just remove it from quick then - it doesn't really matter if
> > >it doesn't run because of the cache mode or because we didn't include it
> > >in the group.
>
> Will do it when respin.
>
> > >-c writethrough is okay as long as you really have tmpfs on your /tmp,
> > >but it really hurts when you don't (and I for one don't, standard RHEL 7
> > >installation).
> >
>
> Oh, do you have any better idea than hardcoding to /tmp then?
I think /tmp is fine. It helps those of us who do have a tmpfs there,
and it shouldn't hurt the rest at least. Just don't combine it with
writethrough, but leave out -c.
Kevin
next prev parent reply other threads:[~2014-11-25 9:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 6:45 [Qemu-devel] [PATCH 0/2] tests: Add check-block to "make check" Fam Zheng
2014-10-28 6:45 ` [Qemu-devel] [PATCH 1/2] qemu-iotests: Speed up make check-block Fam Zheng
2014-11-25 7:22 ` Markus Armbruster
2014-11-25 9:12 ` Max Reitz
2014-11-25 9:21 ` Kevin Wolf
2014-11-25 9:21 ` Max Reitz
2014-11-25 9:30 ` Kevin Wolf
2014-11-25 9:31 ` Max Reitz
2014-11-25 9:44 ` Fam Zheng
2014-11-25 9:58 ` Kevin Wolf [this message]
2014-10-28 6:45 ` [Qemu-devel] [PATCH 2/2] tests/Makefile: Add check-block to make check Fam Zheng
2014-11-25 9:17 ` Max Reitz
2014-10-28 8:28 ` [Qemu-devel] [PATCH 0/2] tests: Add check-block to "make check" Markus Armbruster
2014-11-25 7:30 ` Markus Armbruster
2014-11-25 9:06 ` Max Reitz
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=20141125095812.GC4641@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.