linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <andreas.dilger@oracle.com>
To: ngupta@vflare.org
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	Minchan Kim <minchan.kim@gmail.com>,
	chris.mason@oracle.com, viro@zeniv.linux.org.uk,
	akpm@linux-foundation.org, adilger@sun.com, tytso@mit.edu,
	mfasheh@suse.com, joel.becker@oracle.com, matthew@wil.cx,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	ocfs2-devel@oss.oracle.com, linux-mm@kvack.org, jeremy@goop.org,
	JBeulich@novell.com, kurt.hackel@oracle.com, npiggin@suse.de,
	dave.mccracken@oracle.com, riel@redhat.com, avi@redhat.com,
	konrad.wilk@oracle.com
Subject: Re: [PATCH V2 0/7] Cleancache (was Transcendent Memory): overview
Date: Wed, 2 Jun 2010 22:53:44 -0600	[thread overview]
Message-ID: <3721BEE2-DF2D-452A-8F01-E690E32C6B33@oracle.com> (raw)
In-Reply-To: <4C07179F.5080106@vflare.org>

On 2010-06-02, at 20:46, Nitin Gupta wrote:
> On 06/03/2010 04:32 AM, Dan Magenheimer wrote:
>>> From: Minchan Kim [mailto:minchan.kim@gmail.com]
>>=20
>>>> I am also eagerly awaiting Nitin Gupta's cleancache backend
>>>> and implementation to do in-kernel page cache compression.
>>>=20
>>> Do Nitin say he will make backend of cleancache for
>>> page cache compression?
>>>=20
>>> It would be good feature.
>>> I have a interest, too. :)
>>=20
>> That was Nitin's plan for his GSOC project when we last discussed
>> this.  Nitin is on the cc list and can comment if this has
>> changed.
>=20
> Yes, I have just started work on in-kernel page cache compression
> backend for cleancache :)

Is there a design doc for this implementation?  I was thinking it would =
be quite clever to do compression in, say, 64kB or 128kB chunks in a =
mapping (to get decent compression) and then write these compressed =
chunks directly from the page cache to disk in btrfs and/or a revived =
compressed ext4.

That would mean that the on-disk compression algorithm needs to match =
the in-memory algorithm, which implies that the in-memory compression =
algorithm should be selectable on a per-mapping basis.

Cheers, Andreas
--
Andreas Dilger
Lustre Technical Lead
Oracle Corporation Canada Inc.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-06-03  4:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100528173510.GA12166@ca-server1.us.oracle.com>
2010-06-02  6:03 ` [PATCH V2 0/7] Cleancache (was Transcendent Memory): overview Minchan Kim
2010-06-02 15:27   ` Dan Magenheimer
2010-06-02 16:38     ` Minchan Kim
2010-06-02 23:02       ` Dan Magenheimer
2010-06-03  2:46         ` Nitin Gupta
2010-06-03  4:53           ` Andreas Dilger [this message]
2010-06-03  6:25             ` Nitin Gupta
2010-06-03 15:43               ` Dan Magenheimer
2010-06-04  9:36                 ` Nitin Gupta
2010-06-04 13:45                   ` Minchan Kim
2010-06-02 13:00 ` Jamie Lokier
2010-06-02 15:35   ` Dan Magenheimer
2010-06-02 13:24 ` Christoph Hellwig
2010-06-02 16:07   ` Dan Magenheimer
2010-05-28 17:35 Dan Magenheimer
     [not found] <20100528173510.GA12166@ca-server1.us.oracle.comAANLkTilV-4_QaNq5O0WSplDx1Oq7JvkgVrEiR1rgf1up@mail.gmail.com>

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=3721BEE2-DF2D-452A-8F01-E690E32C6B33@oracle.com \
    --to=andreas.dilger@oracle.com \
    --cc=JBeulich@novell.com \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=chris.mason@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=dave.mccracken@oracle.com \
    --cc=jeremy@goop.org \
    --cc=joel.becker@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kurt.hackel@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew@wil.cx \
    --cc=mfasheh@suse.com \
    --cc=minchan.kim@gmail.com \
    --cc=ngupta@vflare.org \
    --cc=npiggin@suse.de \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=riel@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).