From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv3 9/9] migration: use XBZRLE only after bulk stage
Date: Thu, 21 Mar 2013 13:31:18 -0600 [thread overview]
Message-ID: <514B6006.2010904@redhat.com> (raw)
In-Reply-To: <1363881457-14814-10-git-send-email-pl@kamp.de>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
On 03/21/2013 09:57 AM, Peter Lieven wrote:
> at the beginning of migration all pages are marked dirty and
> in the first round a bulk migration of all pages is performed.
>
> currently all these pages are copied to the page cache regardless
> if there are frequently updated or not. this doesn't make sense
s/if there/of whether they/
> since most of these pages are never transferred again.
>
> this patch changes the XBZRLE transfer to only be used after
> the bulk stage has been completed. that means a page is added
> to the page cache the second time it is transferred and XBZRLE
> can benefit from the third time of transfer.
>
> since the page cache is likely smaller than the number of pages
> its also likely that in the second round the page is missing in the
s/its/it's/
> cache due to collisions in the bulk phase.
>
> on the other hand a lot of unnecessary mallocs, memdups and frees
> are saved.
>
...
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> arch_init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Prior review still stands (touching up typos in a commit message
generally does not invalidate carrying forward a reviewed-by comment).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
prev parent reply other threads:[~2013-03-21 19:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 15:57 [Qemu-devel] [PATCHv3 0/9] buffer_is_zero / migration optimizations Peter Lieven
2013-03-21 15:57 ` [Qemu-devel] [PATCHv3 1/9] move vector definitions to qemu-common.h Peter Lieven
2013-03-21 17:29 ` Eric Blake
2013-03-21 15:57 ` [Qemu-devel] [PATCHv3 2/9] cutils: add a function to find non-zero content in a buffer Peter Lieven
2013-03-21 18:12 ` Eric Blake
2013-03-21 19:11 ` Peter Lieven
2013-03-21 15:57 ` [Qemu-devel] [PATCHv3 3/9] buffer_is_zero: use vector optimizations if possible Peter Lieven
2013-03-21 18:16 ` Eric Blake
2013-03-21 15:57 ` [Qemu-devel] [PATCHv3 4/9] bitops: use vector algorithm to optimize find_next_bit() Peter Lieven
2013-03-21 19:18 ` Eric Blake
2013-03-21 15:57 ` [Qemu-devel] [PATCHv3 5/9] migration: search for zero instead of dup pages Peter Lieven
2013-03-21 19:24 ` Eric Blake
2013-03-21 15:57 ` [Qemu-devel] [PATCHv3 6/9] migration: add an indicator for bulk state of ram migration Peter Lieven
2013-03-21 19:27 ` Eric Blake
2013-03-21 15:57 ` [Qemu-devel] [PATCHv3 7/9] migration: do not sent zero pages in bulk stage Peter Lieven
2013-03-21 19:26 ` Eric Blake
2013-03-21 19:44 ` Peter Lieven
2013-03-21 15:57 ` [Qemu-devel] [PATCHv3 8/9] migration: do not search dirty " Peter Lieven
2013-03-21 19:27 ` Eric Blake
2013-03-21 19:57 ` Peter Lieven
2013-03-21 15:57 ` [Qemu-devel] [PATCHv3 9/9] migration: use XBZRLE only after " Peter Lieven
2013-03-21 19:31 ` Eric Blake [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=514B6006.2010904@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.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).