From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: mreitz@redhat.com, eblake@redhat.com, den@openvz.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/5] block: Introduce qemu-img bench
Date: Tue, 7 Jun 2016 16:13:52 +0200 [thread overview]
Message-ID: <20160607141352.GM4684@noname.str.redhat.com> (raw)
In-Reply-To: <1465217162-21115-1-git-send-email-kwolf@redhat.com>
Am 06.06.2016 um 14:45 hat Kevin Wolf geschrieben:
> After merging Den's qcow2 patch to avoid duplicated flushes, I thought I would
> be nice to reproduce the problem and I remembered 'qemu-img bench', which I had
> posted before as part of more than one RFC series, but which never made it to
> master somehow. So here is a rebased and cleaned up version of it, just by
> itself, so that it hopefully can be merged finally.
>
> Of course, I failed to actually reproduce the problem on my laptop. Who knows,
> something on my system might be more intelligent about useless flushes, or
> maybe I just misunderstood what the problematic scenario looks like at the
> block level. Doesn't make the tool less useful, though, and I already did the
> rebasing.
Thanks for the review, applied to the block branch.
Kevin
prev parent reply other threads:[~2016-06-07 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 12:45 [Qemu-devel] [PATCH v2 0/5] block: Introduce qemu-img bench Kevin Wolf
2016-06-06 12:45 ` [Qemu-devel] [PATCH v2 1/5] " Kevin Wolf
2016-06-06 12:45 ` [Qemu-devel] [PATCH v2 2/5] qemu-img bench: Sequential writes Kevin Wolf
2016-06-07 13:28 ` Denis V. Lunev
2016-06-06 12:46 ` [Qemu-devel] [PATCH v2 3/5] qemu-img bench: Make start offset configurable Kevin Wolf
2016-06-06 12:46 ` [Qemu-devel] [PATCH v2 4/5] qemu-img bench: Implement -S (step size) Kevin Wolf
2016-06-06 12:46 ` [Qemu-devel] [PATCH v2 5/5] qemu-img bench: Add --flush-interval Kevin Wolf
2016-06-07 13:32 ` Denis V. Lunev
2016-06-07 13:55 ` [Qemu-devel] [PATCH v2 0/5] block: Introduce qemu-img bench Stefan Hajnoczi
2016-06-07 14:13 ` Kevin Wolf [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=20160607141352.GM4684@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).