From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MIpM3-0006Sd-EW for qemu-devel@nongnu.org; Mon, 22 Jun 2009 15:38:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MIpLy-0006RO-MD for qemu-devel@nongnu.org; Mon, 22 Jun 2009 15:38:58 -0400 Received: from [199.232.76.173] (port=50329 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MIpLy-0006RL-FJ for qemu-devel@nongnu.org; Mon, 22 Jun 2009 15:38:54 -0400 Received: from mx20.gnu.org ([199.232.41.8]:22009) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MIpLy-0003qv-0R for qemu-devel@nongnu.org; Mon, 22 Jun 2009 15:38:54 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MIpLw-0006ie-SM for qemu-devel@nongnu.org; Mon, 22 Jun 2009 15:38:53 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT 3086844] Instead of writing a zero page, madvise it away Date: Mon, 22 Jun 2009 20:38:00 +0100 References: <200906221549.n5MFn3Qd015389@d03av02.boulder.ibm.com> <4A3FB390.4060809@redhat.com> <4A3FB95D.3060404@us.ibm.com> In-Reply-To: <4A3FB95D.3060404@us.ibm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906222038.01469.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Anthony Liguori , Avi Kivity > >>> We have the same issue on the migration source node. I don't see a > >>> simple way to solve it, though. > >> > >> I don't follow. In this case, the issue is: > >> > >> 1) Start a guest with 1024, balloon down to 128MB. RSS size is now > >> ~128MB > >> 2) Live migrate to a different node > >> 3) RSS on different node jumps to ~1GB > > > > 3.5) RSS on source node jumps to ~1GB, since reading the page > > instantiates the pte > > Surely we can do better here... Huh, I'm surprised we have to. I was expecting linux to populate the region with CoW mappings of a single zero page, but apparently not. I guess reading a zero page without writing to it is a fairly rare case, and it's usually better to instantiate a writable page on the first access. Paul