From: Martin Mailand <martin@tuxadero.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Dongsu Park <dongsu.park@profitbricks.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: virtio-blk performance regression and qemu-kvm
Date: Wed, 29 Feb 2012 14:12:58 +0100 [thread overview]
Message-ID: <4F4E245A.9050509@tuxadero.com> (raw)
In-Reply-To: <CAJSP0QVj7AzSORw-PCtvQBwHvzkkOq28StXbV74x2u16H=1WXw@mail.gmail.com>
Hi Stefan,
you are right, the performance for the commits 0b9b128530b and
4fefc55ab04d are both good.
What is the best approach to stay in the qemu-kvm.git history?
-martin
On 29.02.2012 09:38, Stefan Hajnoczi wrote:
> I suggest testing both of the qemu-kvm.git merge commits, 0b9b128530b
> and 4fefc55ab04d. My guess is you will find they perform the same,
> i.e. the qemu.git commits which were merged did not affect performance
> in qemu-kvm.git. That would be evidence that git-bisect has not
> located the real culprit.
next prev parent reply other threads:[~2012-02-29 13:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 14:36 virtio-blk performance regression and qemu-kvm Dongsu Park
2012-02-12 23:55 ` Rusty Russell
2012-02-21 16:45 ` Dongsu Park
2012-02-21 22:16 ` Rusty Russell
2012-02-13 11:57 ` Stefan Hajnoczi
2012-02-21 15:57 ` Dongsu Park
2012-02-21 17:27 ` Stefan Hajnoczi
2012-02-22 16:48 ` Dongsu Park
2012-02-22 19:53 ` Stefan Hajnoczi
2012-02-28 16:39 ` Martin Mailand
2012-02-28 17:05 ` Stefan Hajnoczi
2012-02-28 17:15 ` Martin Mailand
2012-02-29 8:38 ` Stefan Hajnoczi
2012-02-29 13:12 ` Martin Mailand [this message]
2012-02-29 13:44 ` Stefan Hajnoczi
2012-02-29 13:52 ` Stefan Hajnoczi
2012-03-05 16:13 ` Martin Mailand
2012-03-05 16:35 ` Stefan Hajnoczi
2012-03-05 16:44 ` Martin Mailand
2012-03-06 12:59 ` Stefan Hajnoczi
2012-03-06 22:07 ` [Qemu-devel] " Reeted
2012-03-07 8:04 ` Stefan Hajnoczi
2012-03-07 14:21 ` Reeted
2012-03-07 14:33 ` Stefan Hajnoczi
2012-03-07 10:39 ` Martin Mailand
2012-03-07 11:21 ` Paolo Bonzini
2012-03-06 14:32 ` Dongsu Park
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=4F4E245A.9050509@tuxadero.com \
--to=martin@tuxadero.com \
--cc=dongsu.park@profitbricks.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox