Re: [Qemu-devel] [RFC PATCH RDMA support v4: 03/10] more verbose documentation of the RDMA transport

["Michael S. Tsirkin" <mst@redhat.com>]

On Wed, Mar 20, 2013 at 04:20:06PM -0400, Michael R. Hines wrote:
> On 03/20/2013 03:06 PM, Michael S. Tsirkin wrote:
> 
>     No, not just ballooning. Overcommit (i.e. cgroups).
> 
>     Anytime cgroups kicks out a page (or anytime the balloon kicks in),
>     the page would become unmapped.
> 
>     OK but we still need to send that page to remote.
>     It's in swap but has guest data in there, you can't
>     just ignore it.
> 
> 
> Yes, absolutely: https://www.kernel.org/doc/Documentation/vm/pagemap.txt
> 
> The pagemap will tell you that.
> 
> In fact the pagemap ideally would *only* be used for the 1st migration round.
> 
> The rest of them would depend exclusively on the dirty bitmap as they do.
> 
> Basically, we could use the pagemap as first-time "hint" for the bulk of
> the memory that costs the most to transmit.

OK sure, this could be useful to detect pages deduplicated by KSM and only
transmit one copy. There's still the question of creating same
duplicate mappings on destination - do you just do data copy on destination?

Not sure why you talk about unmapped pages above though, it seems
not really relevant...

There's also the matter of KSM not touching pinned pages,
that's another good reason not to pin all pages on destination,
they won't be deduplicated.