Linux filesystem development
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: "Ted Ts'o" <tytso@mit.edu>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@infradead.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: RE: clearcache (Was: Re: [git pull] vfs pile 1)
Date: Fri, 14 Jan 2011 13:11:02 -0800 (PST)	[thread overview]
Message-ID: <7aa3a707-4713-41ca-b9f1-327485774722@default> (raw)
In-Reply-To: <20110113220039.GF31800@thunk.org>

Hi Ted --

Thanks for taking the time to reply.

> The real problem is I don't think anyone is really paying attention to
> cleancache.

It's a bit more complicated than that.  There ARE a lot of people
interested in it, but there is a bit of a deadlock.  I've heard from
many people that would love to use Xen transcendent memory as
a great solution for memory overcommitment in the cloud, but they
get skittish when I tell them it requires kernel changes that haven't
been accepted upstream.  But key Linux maintainers don't consider
the Xen base interesting enough to allow merging of cleancache
(and frontswap), despite its simplicity and negligible impact,
without at least a second (and preferably in-kernel) user.

> Dan, something that might be useful to drive interest would be a
> demonstration of this improves performance on, say, a netbook using
> cleancache and zram, and how it is better than just using zram
> directly as a swap device.  With maybe some numbers?  That might get
> some interest from the community desktop distributions...

Indeed.  I was hoping that Nitin's work on zcache (the page cache
version of zram) would serve that purpose but GregKH declined to
merge it because it was dependent on unmerged cleancache... thus a
chicken-and-egg problem; and Nitin has apparently now moved on to
other (non-Linux-kernel) things.  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.  (I had hoped to post V1 of kztmem
by today but ran into a problem in an overnight test run.  So
stay tuned.)

Dan

P.S. The numbers look pretty good.
P.P.S. kztmem should also be easily adaptable to KVM, but I haven't
 the KVM expertise to make it happen

  reply	other threads:[~2011-01-14 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13  5:35 [git pull] vfs pile 1 Al Viro
2011-01-13  6:25 ` Stephen Rothwell
2011-01-13  8:55   ` Christoph Hellwig
     [not found]     ` <20110113214239.1b23b523.sfr@canb.auug.org.au20110113220039.GF31800@thunk.org>
2011-01-13 10:42     ` clearcache (Was: Re: [git pull] vfs pile 1) Stephen Rothwell
2011-01-13 16:08       ` Dan Magenheimer
2011-01-13 22:00       ` Ted Ts'o
2011-01-14 21:11         ` Dan Magenheimer [this message]
2011-01-14 22:35           ` Ted Ts'o
2011-01-14 23:28             ` Dan Magenheimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7aa3a707-4713-41ca-b9f1-327485774722@default \
    --to=dan.magenheimer@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=viro@ZenIV.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox