public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Anopolsky <erpo41@gmail.com>
To: Balaji Rao <balajirrao@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Transparent compression for Btrfs
Date: Sun, 31 Aug 2008 20:49:57 -0600	[thread overview]
Message-ID: <1220237397.11137.17.camel@telesto> (raw)
In-Reply-To: <200809010739.29862.balajirrao@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]

On Mon, 2008-09-01 at 07:39 +0530, Balaji Rao wrote:
> Hi,
> 
> For a medium term project, I'm thinking of working on transparent compression 
> for Btrfs. Please give any hints and comments on how we would want to go 
> about this, the features we would like to have and some common pitfalls to 
> avoid.
> 
> Is looking at how it's done in Reiser4, a good idea ? Can we allow the 
> compression algorithm be configurable on a per file basis, may be using an 
> xattr ? This, for example, would allow us to make a compromise between speed 
> and compression ratio.
> 
> Any other ideas welcome.

If the algorithm is tunable on a per file basis, why not make the
compression level tunable on a per file basis? I think it's also
important to consider the tradeoff the between learning
curve/administrative overhead and the granularity of control over
compression, but I don't have any good answers.

While we're on the subject, someone on the ZFS list expressed a need to
tune redundancy on a per-file basis (or even tune redundancy at all
after the filesystem is created). Currently ZFS is very inflexible in
this regard, so it could be a way for btrfs to get ahead.

Cheers,
Eric


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-09-01  2:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01  2:09 Transparent compression for Btrfs Balaji Rao
2008-09-01  2:49 ` Eric Anopolsky [this message]
2008-09-01 13:52 ` Chris Mason

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=1220237397.11137.17.camel@telesto \
    --to=erpo41@gmail.com \
    --cc=balajirrao@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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