From: Chris Mason <chris.mason@oracle.com>
To: Lee Trager <lt73@cs.drexel.edu>
Cc: linux-btrfs@vger.kernel.org, balajirrao@gmail.com,
miguel.filipe@gmail.com
Subject: Re: Compressed Filesystem
Date: Tue, 28 Oct 2008 13:38:37 -0400 [thread overview]
Message-ID: <1225215517.6448.176.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20081028163337.GA8488@tux64-02>
On Tue, 2008-10-28 at 12:33 -0400, Lee Trager wrote:
> On Tue, Oct 28, 2008 at 11:47:27AM -0400, Chris Mason wrote:
> > On Mon, 2008-10-27 at 10:54 -0400, Lee Trager wrote:
> > > I have read on the mailing list that there has been some interest in
> > > implementing transparent compression on btrfs and I too am thinking about
> > > trying to implement it. Before I start from scratch I am wondering if
> > > anyone else has started to work on this and if so how far along have
> > > they gotten? I would be happy to work on this alone or with someone else
> > > but currently I am doing some preliminary research.
> >
> > Compression is working on my machine, I'm just running some long tests
> > before I push it out to the unstable repo. The current code uses the
> > in-kernel zlib implementation.
> >
> > -chris
> >
>
> Thats great I am eager to try it. How long will these tests take? I
> would love to look at the code. Is compression done for every file by
> default or does a user space program have to set a compression flag on
> the file?
This is a fairly large change, I plan on running it overnight.
Compression is optional and off by default (mount -o compress to enable
it). When enabled, every file is compressed.
-chris
next prev parent reply other threads:[~2008-10-28 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 14:54 Compressed Filesystem Lee Trager
2008-10-28 15:47 ` Chris Mason
2008-10-28 16:33 ` Lee Trager
2008-10-28 17:38 ` Chris Mason [this message]
2008-10-28 17:40 ` Zach Brown
2008-10-28 17:46 ` Chris Mason
[not found] ` <53696.2001:470:e828:1::2:2.1225304096.squirrel@avalon.arbitraryconstant.com>
2008-10-29 20:08 ` Chris Mason
2008-11-04 0:08 ` Chris Samuel
-- strict thread matches above, loose matches on Subject: below --
2008-12-15 22:14 devzero
2008-12-15 23:07 ` Lee Trager
2008-12-15 23:19 devzero
2008-12-16 15:20 ` Lee Trager
2008-12-16 15:26 ` Chris Mason
2008-12-16 16:25 ` Lee Trager
2008-12-16 19:45 ` Roland
2008-12-18 15:55 ` Chris Mason
2008-12-16 18:14 devzero
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=1225215517.6448.176.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=balajirrao@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lt73@cs.drexel.edu \
--cc=miguel.filipe@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.