public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: jim owens <jowens@hp.com>
To: Diego Calleja <diegocg@gmail.com>
Cc: Lee Trager <lt73@cs.drexel.edu>,
	Christian Hesse <mail@earthworm.de>,
	miguel.filipe@gmail.com, linux-btrfs@vger.kernel.org
Subject: Re: Selective Compression/Encryption
Date: Tue, 09 Dec 2008 18:50:19 -0500	[thread overview]
Message-ID: <493F043B.50804@hp.com> (raw)
In-Reply-To: <20081210000512.7be20413@diego-desktop>

Diego Calleja wrote:
> El Tue, 9 Dec 2008 13:09:51 -0500, "Lee Trager" <lt73@cs.drexel.edu> =
escribi=C3=B3:
>=20
>> It does seem that doing it with volumes would limit user control and=
 add
>> lots of complexity to such a simple task.
>=20
> IMHO, WRT compression it's the contrary. Compression on a per-file ba=
sis has
> never been very succesful (just look at how many windows users use it=
)
> because it implies taking a decision for every file on the system. OT=
OH,
> volume-level is just a single option to be enabled.
>=20
> I'm of course not arguing that file-level compression shouldn't be po=
ssible,
> im just saying that is way more difficult to administer and that most=
 people
> (including sysadmins) is most likely to use compression in a per-volu=
me basis.

While I have not gotten far enough to prove it is feasible...

My idea on controlling features like compression is that
the default mode is inherited from the parent in the
directory tree.  Thus you can turn it on/off at whatever
granularity you want.

jim
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-12-09 23:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 14:59 Selective Compression/Encryption Lee Trager
2008-12-09 15:45 ` Miguel Figueiredo Mascarenhas Sousa Filipe
     [not found]   ` <200812091722.21567.mail@earthworm.de>
2008-12-09 18:09     ` Lee Trager
2008-12-09 22:14       ` Miguel Figueiredo Mascarenhas Sousa Filipe
     [not found]         ` <1228863790.8130.14.camel@mattos-laptop>
2008-12-10 12:11           ` Miguel Figueiredo Mascarenhas Sousa Filipe
2008-12-09 23:05       ` Diego Calleja
2008-12-09 23:50         ` jim owens [this message]
2008-12-10  0:03           ` calin
2008-12-10 13:44           ` Chris Mason
2008-12-10 17:55             ` Christoph Hellwig
2008-12-10 18:02               ` Linda Knippers
2008-12-10 18:11             ` Joshua J. Berry
2008-12-10  9:06         ` Mattos, Oliver
2008-12-10  9:32   ` Jeremy Sanders
2008-12-10 12:19     ` Miguel Figueiredo Mascarenhas Sousa Filipe
2008-12-09 16:35 ` Chris Mason
2008-12-09 18:14   ` Lee Trager
2008-12-09 19:26   ` Joshua J. Berry
2008-12-09 20:22     ` jim owens
2008-12-10 13:45       ` Chris Mason
2008-12-10 14:33         ` btrfs with selinux jim owens
2008-12-11 22:03       ` Selective Compression/Encryption Lee Trager
2008-12-12 14:19         ` 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=493F043B.50804@hp.com \
    --to=jowens@hp.com \
    --cc=diegocg@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lt73@cs.drexel.edu \
    --cc=mail@earthworm.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox