[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3e5fe0d0-53a9-49fd-8c12-2ee94062dd0f@default>
Date: Fri, 14 Jan 2011 15:28:32 -0800 (PST)
From: Dan Magenheimer <dan.magenheimer@...cle.com>
To: "Ted Ts'o" <tytso@....edu>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Christoph Hellwig <hch@...radead.org>,
Al Viro <viro@...IV.linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: RE: clearcache (Was: Re: [git pull] vfs pile 1)
> > 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists