Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759590AbZC3TOq (ORCPT ); Mon, 30 Mar 2009 15:14:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757447AbZC3TOZ (ORCPT ); Mon, 30 Mar 2009 15:14:25 -0400 Received: from gw.goop.org ([64.81.55.164]:47593 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757562AbZC3TOX (ORCPT ); Mon, 30 Mar 2009 15:14:23 -0400 Message-ID: <49D11674.9040205@goop.org> Date: Mon, 30 Mar 2009 11:59:00 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Rik van Riel CC: Dave Hansen , Martin Schwidefsky , akpm@osdl.org, nickpiggin@yahoo.com.au, frankeh@watson.ibm.com, virtualization@lists.osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, hugh@veritas.com Subject: Re: [patch 0/6] Guest page hinting version 7. References: <20090327150905.819861420@de.ibm.com> <1238195024.8286.562.camel@nimitz> <20090329161253.3faffdeb@skybase> <1238428495.8286.638.camel@nimitz> <49D11184.3060002@goop.org> <49D11287.4030307@redhat.com> In-Reply-To: <49D11287.4030307@redhat.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1142 Lines: 27 Rik van Riel wrote: > Jeremy Fitzhardinge wrote: > >> That said, people have been looking at tracking block IO to work out >> when it might be useful to try and share pages between guests under Xen. > > Tracking block IO seems like a bass-ackwards way to figure > out what the contents of a memory page are. Well, they're research projects, so nobody said that they're necessarily useful results ;). I think the rationale is that, in general, there aren't all that many sharable pages, and asize from zero-pages, the bulk of them are the result of IO. Since its much simpler to compare device+block references than doing page content matching, it is worth looking at the IO stream to work out what your candidates are. > The KVM KSM code has a simpler, yet still efficient, way of > figuring out which memory pages can be shared. How's that? Does it do page content comparison? J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/