All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Orit Wasserman <owasserm@redhat.com>
Cc: quintela@redhat.com,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Isaku Yamahata <yamahata@valinux.co.jp>,
	benoit.hudzia@sap.com, chegu_vinod@hp.com
Subject: Re: [Qemu-devel] Migration ToDo list
Date: Tue, 13 Nov 2012 18:16:30 +0100	[thread overview]
Message-ID: <50A2806E.20605@redhat.com> (raw)
In-Reply-To: <50A27EBF.3090402@redhat.com>

Il 13/11/2012 18:09, Orit Wasserman ha scritto:
>> > 
>>> >>   b) do scatter/gather of the pages?
> I would prefer to postpone changing the protocol and start with using iov (writev)
> for sending the pages (still sending header and than the page). Later we can 
> move to scatter/gather I'm not sure of how large the performance gain will be.
>> > 
>> > c) Remove compression of non-zero repetitive pages.
> +1
> we can look of identify the zero pages without calling is_dup_page which looks
> expensive.

Identifying ballooned zero pages is useful, because those cause the
clear_page calls in the kernel even in a guest that has been running for
a while.

But a generic solution doesn't really matter, because is_dup_page and
clear_page shouldn't really be in the profile in practice, except in
microbenchmarks.

Paolo

  reply	other threads:[~2012-11-13 17:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 16:18 [Qemu-devel] Migration ToDo list Juan Quintela
2012-11-13 16:28 ` Paolo Bonzini
2012-11-13 17:09   ` Orit Wasserman
2012-11-13 17:16     ` Paolo Bonzini [this message]
2012-11-14  2:14       ` Isaku Yamahata
2012-11-14  2:20         ` Paolo Bonzini
2012-11-14  2:31           ` Isaku Yamahata
2012-11-13 16:40 ` Orit Wasserman
2012-11-13 16:48 ` Chegu Vinod
2012-11-13 16:57   ` Orit Wasserman

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=50A2806E.20605@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=benoit.hudzia@sap.com \
    --cc=chegu_vinod@hp.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=owasserm@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=yamahata@valinux.co.jp \
    /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.