From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: clearcache (Was: Re: [git pull] vfs pile 1) Date: Fri, 14 Jan 2011 15:28:32 -0800 (PST) Message-ID: <3e5fe0d0-53a9-49fd-8c12-2ee94062dd0f@default> References: <20110113053554.GQ19804@ZenIV.linux.org.uk> <20110113172557.c016ec51.sfr@canb.auug.org.au> <20110113085547.GA7414@infradead.org> <20110113214239.1b23b523.sfr@canb.auug.org.au20110113220039.GF31800@thunk.org> <7aa3a707-4713-41ca-b9f1-327485774722@default 20110114223525.GA20593@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8BIT Cc: Stephen Rothwell , Christoph Hellwig , Al Viro , Linus Torvalds , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: "Ted Ts'o" Return-path: In-Reply-To: <20110114223525.GA20593@thunk.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org > > As a result, I've spent most of my > > free time over the last three months working on kztmem, which will > > hopefully serve the purpose. > > You'll have to forgive me, but I have absolutely no idea what kztmem > is or what it does. Is it just compressed tmem, and hence, something > that is only of interest to people using Xen? If so, it's not clear > to me how it will help non-Xen people become interested in these > patches. Ah, sorry, processing too much email backlog and left out some context... Kztmem is entirely in-kernel, no virtualization required (neither Xen nor KVM). I'll cc you when I post V1 soon but, yes, it is compressed *in-kernel* tmem, a more flexible/dynamic replacement for zcache and possibly also for zram as well, architected and designed to more easily (than zcache/zram) exploit some other directions I plan to take with tmem concepts, including (but not limited to) page-addressable memory (http://marc.info/?l=linux-mm&m=127811271605009). Kztmem is coded (at least for now) as a staging driver, but uses exactly the proposed cleancache (and frontswap) patches. Hope that helps! Dan