From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail172.messagelabs.com (mail172.messagelabs.com [216.82.254.3]) by kanga.kvack.org (Postfix) with SMTP id BC85D620002 for ; Fri, 25 Dec 2009 14:18:57 -0500 (EST) Date: Fri, 25 Dec 2009 20:18:49 +0100 From: Pavel Machek Subject: Re: Tmem [PATCH 0/5] (Take 3): Transcendent memory Message-ID: <20091225191848.GB8438@elf.ucw.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org To: Dan Magenheimer Cc: Nitin Gupta , Nick Piggin , Andrew Morton , jeremy@goop.org, xen-devel@lists.xensource.com, tmem-devel@oss.oracle.com, Rusty Russell , Rik van Riel , dave.mccracken@oracle.com, sunil.mushran@oracle.com, Avi Kivity , Schwidefsky , Balbir Singh , Marcelo Tosatti , Alan Cox , chris.mason@oracle.com, linux-mm , linux-kernel List-ID: On Wed 2009-12-23 09:15:27, Dan Magenheimer wrote: > > As I mentioned, I really like the idea behind tmem. All I am proposing > > is that we should probably explore some alternatives to achive this using > > some existing infrastructure in kernel. > > Hi Nitin -- > > Sorry if I sounded overly negative... too busy around the holidays. > > I'm definitely OK with exploring alternatives. I just think that > existing kernel mechanisms are very firmly rooted in the notion > that either the kernel owns the memory/cache or an asynchronous > device owns it. Tmem falls somewhere in between and is very Well... compcache seems to be very similar to preswap: in preswap case you don't know if hypervisor will have space, in ramzswap you don't know if data are compressible. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org