Skywing wrote:
The far majority of pages are allocated when a process wants them
or the kernel uses them for file cache.
Is that not going to be fairly guest-specific? For example, Windows has a thread that
does background zeroing of unallocated pages that aren't marked as zeroed already. I'd
imagine that touching such pages would translate to an "allocation" as far as
any hypervisor would be concerned.
Yes. Most likely the thread runs on the same node as the memory, so it
stays local.
Still, we need to keep the vcpu within the memory node somehow,
otherwise all memory becomes non-local.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
