From: Chris Mason <chris.mason@oracle.com>
To: Roland <devzero@web.de>
Cc: Lee Trager <lt73@cs.drexel.edu>, linux-btrfs@vger.kernel.org
Subject: Re: Compressed Filesystem
Date: Thu, 18 Dec 2008 10:55:35 -0500 [thread overview]
Message-ID: <1229615735.27170.146.camel@think.oraclecorp.com> (raw)
In-Reply-To: <099201c95fb6$d0633920$0301a8c0@bui.materna.com>
On Tue, 2008-12-16 at 20:45 +0100, Roland wrote:
> >I agree that adding more options will add more complexity but it seems
> > the same amount of work in kernel space will have to be done
>
> regarding lzo compression itself - it`s already there(since july 2007).
> the in-kernel lzo is equivalent to minilzo.
> (http://www.oberhumer.com/opensource/lzo/)
The compression code initially used the kernel lzo modules. Even though
the zlib api is clunky and strange, it is actually a better fit to the
multi-page compressions that need to be done by btrfs. So adding LZO
support would require some work to compress over multiple pages at a
time.
-chris
next prev parent reply other threads:[~2008-12-18 15:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 23:19 Compressed Filesystem 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-16 18:14 devzero
2008-12-15 22:14 devzero
2008-12-15 23:07 ` Lee Trager
2008-10-27 14:54 Lee Trager
2008-10-28 15:47 ` Chris Mason
2008-10-28 16:33 ` Lee Trager
2008-10-28 17:38 ` Chris Mason
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
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=1229615735.27170.146.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=devzero@web.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=lt73@cs.drexel.edu \
/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