From: Kevin Wolf <kwolf@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] the qemu-iotests test suite is now available
Date: Mon, 14 Sep 2009 10:03:22 +0200 [thread overview]
Message-ID: <4AADF8CA.3050800@redhat.com> (raw)
In-Reply-To: <20090911184045.GD13621@lst.de>
Am 11.09.2009 20:40, schrieb Christoph Hellwig:
> On Fri, Sep 11, 2009 at 04:04:17PM +0200, Kevin Wolf wrote:
>>> Done. Below is a version of my original patch with you l2 cluster size
>>> changes incorporate. The problem is that I really uses up tons of disk
>>> space for the last test in io_test() for 64k clusters, in fact more than
>>> I can make available on the laptop I'm travelling with currently..
>>
>> What happened with this patch, Christoph? I just looked at the tests
>> again and found that we're still aligning our test requests for 4k clusters.
>
> I't been a while.. Wasn't this the one that took so long that it
> didn't complete even in a few hours?
Hm, might be. However, not testing the critical points is really bad. If
we hit any interesting case with the current tests, it's pure luck.
What we can do is to reduce the number of write requests. In theory,
just one request for each case should be enough. However, if we change
the test in this way, we would lose a test doing lots of small writes.
Maybe an additional test instead that aligns it requests according to
the cluster size?
Kevin
next prev parent reply other threads:[~2009-09-14 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 21:05 [Qemu-devel] the qemu-iotests test suite is now available Christoph Hellwig
2009-06-23 9:16 ` Kevin Wolf
2009-06-23 14:31 ` Christoph Hellwig
2009-06-23 14:36 ` Kevin Wolf
2009-06-23 16:41 ` Christoph Hellwig
2009-06-24 7:35 ` Kevin Wolf
2009-07-06 11:18 ` Kevin Wolf
2009-07-06 17:36 ` Christoph Hellwig
2009-07-07 7:30 ` Kevin Wolf
2009-09-11 14:04 ` Kevin Wolf
2009-09-11 18:40 ` Christoph Hellwig
2009-09-14 8:03 ` Kevin Wolf [this message]
2009-06-23 16:03 ` Anthony Liguori
2009-06-23 16:36 ` Christoph Hellwig
2009-06-24 9:12 ` Kevin Wolf
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=4AADF8CA.3050800@redhat.com \
--to=kwolf@redhat.com \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).