From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Orit Wasserman <owasserm@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [RFC] optimize is_dup_page for zero pages
Date: Tue, 12 Mar 2013 13:02:50 +0100 [thread overview]
Message-ID: <513F196A.5020509@redhat.com> (raw)
In-Reply-To: <51C6C0ED-112B-4421-B00A-5CD701AC193D@dlhnet.de>
Il 12/03/2013 12:51, Peter Lieven ha scritto:
>> > buffer_is_zero is used in somewhat special cases (block
>> > streaming/copy-on-read) where throughput doesn't really matter, unlike
>> > is_dup_page/find_zero_bit which are used in migration. But you can use
>> > similar code for is_dup_page and buffer_is_zero.
> ok, i will prepare a patch series for review. at the moment without touching
> is_dup_page(). you can decide later if you use buffer_Is_zero to check
> for zero pages later (maybe if the first x-bit are zero).
>
> Two comments on changing is_dup_page() to is_zero_page():
> a) Would it make sense to only check for zero pages in the first (bulk) round?
Interesting idea. Benchmark it. :)
> b) Would it make sense to not transfer zero pages at all in the first round?
Perhaps yes, but I'm not sure how to efficiently implement it. There
really isn't a well-specified first round in the RAM migration code. Of
course you could have another bitmap for known-zero pages.
But zero pages should be rare in real-world testcases, except for
ballooned pages. The OS should try to use free memory for caches.
> The memory at the target should read as zero (not allocated) anyway.
Paolo
next prev parent reply other threads:[~2013-03-12 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 10:51 [Qemu-devel] [RFC] optimize is_dup_page for zero pages Peter Lieven
2013-03-12 11:11 ` Paolo Bonzini
2013-03-12 11:20 ` Peter Lieven
2013-03-12 11:46 ` Paolo Bonzini
2013-03-12 11:51 ` Peter Lieven
2013-03-12 12:02 ` Paolo Bonzini [this message]
2013-03-12 12:15 ` Peter Lieven
2013-03-12 20:10 ` Peter Lieven
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=513F196A.5020509@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=owasserm@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.