From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Orit Wasserman <owasserm@redhat.com>
Subject: Re: [Qemu-devel] [RFC][PATCH 8/9] migration: do not sent zero_pages in bulk stage
Date: Tue, 12 Mar 2013 14:26:39 -0600 [thread overview]
Message-ID: <513F8F7F.2030207@redhat.com> (raw)
In-Reply-To: <513F4FA6.6000701@dlhnet.de>
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
On 03/12/2013 09:54 AM, Peter Lieven wrote:
> if the dup_page is a zero_page do not send it at all.
> the memory at the destination reads as zero anyway.
It might help to comment that this is only true for the bulk migration
stage. If the guest is actively zeroing pages, then later stages might
encounter an all-zero page that was not all zeros in the bulk migration,
so we must transmit the page in that case.
>
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> arch_init.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch_init.c b/arch_init.c
> index 04c82e4..abd54a7 100644
> --- a/arch_init.c
> +++ b/arch_init.c
> @@ -447,9 +447,11 @@ static int ram_save_block(QEMUFile *f, bool
> last_stage)
> bytes_sent = -1;
> if (ram_bulk_stage && is_dup_page(p)) {
> acct_info.dup_pages++;
> - bytes_sent = save_block_hdr(f, block, offset, cont,
> + if (p[0]) {
Your code has it right, because of the ram_bulk_stage check guarding
this if body, but I did a double take when reading just your commit message.
> + bytes_sent = save_block_hdr(f, block, offset, cont,
> RAM_SAVE_FLAG_COMPRESS);
> - qemu_put_byte(f, *p);
> + qemu_put_byte(f, *p);
> + }
> bytes_sent += 1;
> } else if (!ram_bulk_stage && migrate_use_xbzrle()) {
> current_addr = block->offset + offset;
--
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-12 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 15:54 [Qemu-devel] [RFC][PATCH 8/9] migration: do not sent zero_pages in bulk stage Peter Lieven
2013-03-12 20:26 ` 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=513F8F7F.2030207@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@dlhnet.de \
--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;
as well as URLs for NNTP newsgroup(s).