Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753728AbZF0L2z (ORCPT ); Sat, 27 Jun 2009 07:28:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754362AbZF0L2q (ORCPT ); Sat, 27 Jun 2009 07:28:46 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:40901 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753652AbZF0L2p (ORCPT ); Sat, 27 Jun 2009 07:28:45 -0400 Date: Wed, 24 Jun 2009 17:04:21 +0200 From: Pavel Machek To: Dan Magenheimer Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, npiggin@suse.de, chris.mason@oracle.com, kurt.hackel@oracle.com, dave.mccracken@oracle.com, Avi Kivity , jeremy@goop.org, Rik van Riel , alan@lxorguk.ukuu.org.uk, Rusty Russell , Martin Schwidefsky , akpm@osdl.org, Marcelo Tosatti , Balbir Singh , tmem-devel@oss.oracle.com, sunil.mushran@oracle.com, linux-mm@kvack.org, Himanshu Raj Subject: Re: [RFC] transcendent memory for Linux Message-ID: <20090624150420.GH1784@ucw.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1764 Lines: 40 Hi! This description (whole mail) needs to go into Documentation/, somewhere. > Normal memory is directly addressable by the kernel, > of a known normally-fixed size, synchronously accessible, > and persistent (though not across a reboot). ... > Transcendent memory, or "tmem" for short, provides a > well-defined API to access this unusual class of memory. > The basic operations are page-copy-based and use a flexible > object-oriented addressing mechanism. Tmem assumes Should this API be documented, somewhere? Is it in-kernel API or does userland see it? > "Preswap" IS persistent, but for various reasons may not always > be available for use, again due to factors that may not be > visible to the kernel (but, briefly, if the kernel is being > "good" and has shared its resources nicely, then it will be > able to use preswap, else it will not). Once a page is put, > a get on the page will always succeed. So when the kernel > finds itself in a situation where it needs to swap out a page, > it first attempts to use preswap. If the put works, a disk > write and (usually) a disk read are avoided. If it doesn't, > the page is written to swap as usual. Unlike precache, whether Ok, how much slower this gets in the worst case? Single hypercall to find out that preswap is unavailable? I guess that compared to disk access that's lost in the noise? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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/