All of lore.kernel.org
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Ron Johnson <ron.l.johnson@cox.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext5
Date: Fri, 12 Feb 2010 11:02:43 -0500	[thread overview]
Message-ID: <20100212160243.GQ739@thunk.org> (raw)
In-Reply-To: <4B74DD53.3080308@cox.net>

On Thu, Feb 11, 2010 at 10:47:15PM -0600, Ron Johnson wrote:
> On 2010-02-11 15:41, Goswin von Brederlow wrote:
> >tytso@mit.edu writes:
> >>The idea with read-only compressed files is that they are useful for
> >>large executables or large static files, where compressing them means
> >>that it takes less time to read them off of an HDD.
> >
> >Or when you only have so much flash.
> 
> Isn't that what squashfs is for?

The problem with the squashfs, fuse, ecryptfs approaches for the use
case that I am envisioning is that it's an all-or-nothing sort of
thing.  You may not want to encrypt all of the files in a file system.
Sure, you can play games with bind mounts, and/or accept the
performance hit of passing everything through fuse even for files that
aren't encrypted, but I think that's going to significantly inhibit
adoption of the technology.

Something which allows compressed and uncompressed files to co-exist
without any performance hits to the uncompressed files, and which
allows for a gradual transition after you upgrade rpm/dpkg and as
packages get upgraded is going to much easier time with adoption
rates.

							- Ted

      reply	other threads:[~2010-02-12 16:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 23:40 ext5 Anonymous Remailer (austria)
2010-02-10 21:50 ` ext5 tytso
2010-02-11  3:38   ` ext5 Manish Katiyar
2010-02-11  4:30     ` ext5 tytso
2010-02-11 17:55       ` ext5 Jan Kara
2010-02-11 19:31         ` ext5 tytso
2010-02-11  5:18   ` ext5 Ron Johnson
2010-02-11  6:44     ` ext5 tytso
2010-02-11 16:49       ` ext5 Ron Johnson
2010-02-11 21:41       ` ext5 Goswin von Brederlow
2010-02-12  4:47         ` ext5 Ron Johnson
2010-02-12 16:02           ` tytso [this message]

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=20100212160243.GQ739@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=ron.l.johnson@cox.net \
    /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.