From: ebiederm@xmission.com (Eric W. Biederman)
To: Padraig Brady <padraig@antefacto.com>
Cc: timk@advfn.com, linux-kernel@vger.kernel.org
Subject: Re: R/W compressed fs support??
Date: 12 Apr 2002 01:26:03 -0600 [thread overview]
Message-ID: <m1d6x5l6no.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200204101306.g3AD67s01683@mail.advfn.com> <3CB4824D.2030509@antefacto.com>
Padraig Brady <padraig@antefacto.com> writes:
> e2compr for 2.4 is being implemented by alcatel (France).
> I've successfully used it with 2.4.16 (against filesystems
> created with the 2.2 version). although I haven't stressed
> it yet. "Denis Richard" <dri@sxb.bsf.alcatel.fr> should
> have more info (and the 769777 byte patch).
>
> Padraig.
>
> Tim Kay wrote:
> > Hello,
> > Does anyone know of a Linux equivalent to DoubleSpace or whatever that
> > allows you read and _write_ to a compressed partiton or filesystem (in a way
> > that is transparent to the progs using the fs). I know there was e2compr but
> > that doesn't seem to have been touched in nearly 2 years, and is 2.2 specific,
>
> > Infotec and the CBD patch seem to have died and zlibc seems to be a read only
> > solution. I'd have thought this would have been a biggie for embedded device
> > people but there doesn't seem to be anything out there. Any pointers
> > greatfully received....
> > T.I.A.
> > Tim
To do this efficiently this requires allocate on write support which
is just being developed for the kernel. But the dirty data in the page
cache certainly helps. And since the 2.2.x code didn't use the page cache
it was a challenge to port forward. For most users disks have gotten
so big that it isn't much of an issue anymore.
Though seeing as I have filled my 20GB disk with code it might be worth
taking a look at.
Eric
prev parent reply other threads:[~2002-04-12 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 13:08 R/W compressed fs support?? Tim Kay
2002-04-10 18:19 ` Padraig Brady
2002-04-12 7:26 ` Eric W. Biederman [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=m1d6x5l6no.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=padraig@antefacto.com \
--cc=timk@advfn.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