From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH RFC v2 5/6] KVM: moving dirty bitmaps to user space
Date: Fri, 23 Apr 2010 11:45:37 +0000 [thread overview]
Message-ID: <4BD18861.6020603@redhat.com> (raw)
In-Reply-To: <20100420200225.efca602f.yoshikawa.takuya@oss.ntt.co.jp>
On 04/23/2010 02:14 PM, Takuya Yoshikawa wrote:
>
>> Do you have performance numbers? I'm interested in both measurements of
>> KVM_SWITCH_DIRTY_LOG under various conditions and macro benchmarks (for
>> example, total guest throughput improvement under Kemari).
>>
>
> Currently, I'm just checking the performance visually.
> - on laptops, we can feel the speed directly: my favorite is installing
> ubuntu or debian by alternate installers
>
> - live migration with heavy work load
>
> Now that I've got the overall design, I want to measure the
> performance by numbers.
>
>
> About performance under Kemari: we(oss.ntt.co.jp staffs: me and
> Fernando) are
> now concentrating on improving the basic live-migration
> infrastructures and
> they(lab.ntt.co.jp staffs) are working hard for building Kemari itself.
>
> - We are also interested in using live-migration with HA software
> and this needs
> light, stable live-migration: same as Kemari!
>
General live migration improvements are also interesting, I just the
improvement would be more pronounced under Kemari. Looking forward to
seeing the results.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2010-04-23 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 10:58 [PATCH RFC v2 5/6] KVM: moving dirty bitmaps to user space Takuya Yoshikawa
2010-04-20 11:10 ` Alexander Graf
2010-04-20 11:26 ` Takuya Yoshikawa
2010-04-21 11:26 ` Avi Kivity
2010-04-22 9:07 ` Takuya Yoshikawa
2010-04-23 10:28 ` Avi Kivity
2010-04-23 11:14 ` Takuya Yoshikawa
2010-04-23 11:29 ` Yoshiaki Tamura
2010-04-23 11:45 ` Avi Kivity [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=4BD18861.6020603@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@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