From: Andreas Dilger <adilger@clusterfs.com>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: Dave Kleikamp <shaggy@austin.ibm.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: ext4 roadmap
Date: Thu, 2 Nov 2006 09:17:53 +0800 [thread overview]
Message-ID: <20061102011753.GM5212@schatzie.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.63.0611020026000.14187@alpha.polcom.net>
On Nov 02, 2006 00:52 +0100, Grzegorz Kulewski wrote:
> Is there any chance to get compression and/or encryption in ext4?
Note that all of the features mentioned in the list at least have some
kind of prototype already or people working on it. It isn't really a
"feature request list". I'm not sure how many people are interested
in compression/encryption, but if they are they should come forward
with a patch.
Note that there was previously a compression patch for ext2, maybe that
could be moved forward for ext4?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2006-11-02 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 23:16 ext4 roadmap Dave Kleikamp
2006-11-01 23:52 ` Grzegorz Kulewski
2006-11-02 1:17 ` Andreas Dilger [this message]
2006-11-02 1:44 ` Grzegorz Kulewski
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=20061102011753.GM5212@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=kangur@polcom.net \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@austin.ibm.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