From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC] parallelize migration_bitmap_sync()
Date: Sat, 02 Mar 2013 00:24:43 -0500 [thread overview]
Message-ID: <51318D1B.4010406@linux.vnet.ibm.com> (raw)
In-Reply-To: <51307618.6010708@redhat.com>
Juan,
Can I try this patch that Paolo mentioned?
Does it go directly from GET_LOG_DIRTY => migration_bitmap?
Or is there still an intermediate sync in your patch?
Thanks,
- Michael
On 03/01/2013 04:34 AM, Paolo Bonzini wrote:
> Il 01/03/2013 00:22, Michael R. Hines ha scritto:te
>> Hi,
>>
>> Currently migration_bitmap_sync() is very expensive: on the order of
>> 15-20 milliseconds by my count using timestamps (for a simple 2GB ram
>> virtual machine).
>> Until new EPT processor versions come out in 2014, we need software
>> support for cutting this time down much lower........by at least an
>> order of magnitude.
>>
>> Would anyone be opposed to me writing a patch that creates N threads and
>> dividing up the migration_bitmap_sync() function to have the dirty page
>> scanning run in parallel?
> Yes, that's a possibility. You can make a quick prototype using OpenMP.
>
> But Juan is working on making the dirty bitmap really a bitmap (not a
> "bytemap"). That should speed up migration_bitmap_sync by a factor of
> 64 (i.e. sizeof(long)*8).
>
> Paolo
>
prev parent reply other threads:[~2013-03-02 5:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <512FE6C3.5030409@linux.vnet.ibm.com>
2013-03-01 9:34 ` [Qemu-devel] [RFC] parallelize migration_bitmap_sync() Paolo Bonzini
2013-03-01 19:32 ` Michael R. Hines
2013-03-02 5:24 ` Michael R. Hines [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=51318D1B.4010406@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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.