From: Petru Paler <ppetru@ppetru.net>
To: Pierre PEIFFER <pierre.peiffer@sxb.bsf.alcatel.fr>,
linux-kernel@vger.kernel.org
Subject: Re: e2compress in kernel 2.4
Date: Wed, 03 Oct 2001 12:05:35 +0300 [thread overview]
Message-ID: <46620000.1002099935@shiva> (raw)
In-Reply-To: <3BBACF29.7BB980C4@sxb.bsf.alcatel.fr>
In-Reply-To: <3BBACF29.7BB980C4@sxb.bsf.alcatel.fr>
--On Wednesday, October 03, 2001 10:41:14 +0200 Pierre PEIFFER
<pierre.peiffer@sxb.bsf.alcatel.fr> wrote:
> So, here, we are a little bit confused because we don't know where
> to introduce the compression, if we keep the same idea of the 2.2
> design... In fact, on one hand, once the buffers will be compressed, the
> pages will also become compressed, but on the other hand, we don't want
> the pages to be compressed, because, the pages, once registered and
> linked to the inode are supposed to be uncompressed...
Why don't you build it on top of ext3, and do compression right before a
transaction commit?
--
Real programmers use chmod +x /dev/random and cross their fingers.
next prev parent reply other threads:[~2001-10-03 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 8:41 e2compress in kernel 2.4 Pierre PEIFFER
2001-10-03 9:05 ` Petru Paler [this message]
2001-10-03 12:25 ` Padraig Brady
2001-10-03 13:20 ` Eric W. Biederman
2001-10-16 12:54 ` Padraig Brady
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=46620000.1002099935@shiva \
--to=ppetru@ppetru.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre.peiffer@sxb.bsf.alcatel.fr \
/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.