From: "Ted Ts'o" <tytso@mit.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@infradead.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
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: Thu, 13 Jan 2011 17:00:39 -0500 [thread overview]
Message-ID: <20110113220039.GF31800@thunk.org> (raw)
In-Reply-To: <20110113214239.1b23b523.sfr@canb.auug.org.au>
On Thu, Jan 13, 2011 at 09:42:39PM +1100, Stephen Rothwell wrote:
>
> "I didn't really follow the discussion at Kernel Summit, but there seemed
> to be some question as to whether the cleancache stuff will be merged or
> not. It missed 2.6.37 (obviously), but my question now is do I keep in
> in linux-next in the hope that it will be merged in 2.6.38? Or is that
> not going to happen?"
The real problem is I don't think anyone is really paying attention to
cleancache.
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...
- Ted
next prev parent reply other threads:[~2011-01-13 22:01 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 [this message]
2011-01-14 21:11 ` Dan Magenheimer
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=20110113220039.GF31800@thunk.org \
--to=tytso@mit.edu \
--cc=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=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
Powered by JetHome