From: Maciej Zenczykowski <maze@cela.pl>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: valdis.kletnieks@vt.edu, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <willy@debian.org>,
<ezk@cs.sunysb.edu>, <joern@wohnheim.fh-wedel.de>,
<phillip@lougher.demon.co.uk>, <kbiswas@neoscale.com>
Subject: Re: partially encrypted filesystem
Date: Sat, 6 Dec 2003 23:07:45 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0312062301310.4130-100000@gaia.cela.pl> (raw)
In-Reply-To: <39B8D78E-2826-11D8-8D5E-000393A22C62@ieee.org>
> > some other method ....
> > less likely to cause massive disk fragmentation.
>
> Such as?
If I knew how to do this correctly I'd be earning a lot of money... :)
Truthfully this is work for at least a good two weeks of designing, likely
much, much more... to just determine the very basics. Even assuming you
already have good fast compressors/decompressors which run in neglible
time and achieve the best compression ratio on the market - it's still
very, very non-trivial to make a compressed random-access read-write
filesystem out of that. Some files should be compressed max, some only
slightly, some not at all, this should all be user selectable on a per
file (or even per file section) basis and the default should allow the
file-system to learn which files to compress and how-badly... etc. etc.
The file-system has to auto-defragment and it has to minimize
fragmentation in the first place.
Cheers,
MaZe.
next prev parent reply other threads:[~2003-12-06 22:10 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 19:56 partially encrypted filesystem Pat LaVarre
2003-12-06 22:07 ` Maciej Zenczykowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 3:22 Valient Gough
2003-12-03 21:07 Kallol Biswas
2003-12-03 21:44 ` Richard B. Johnson
2003-12-03 23:20 ` bill davidsen
2003-12-03 21:44 ` Jörn Engel
2003-12-04 0:08 ` Linus Torvalds
2003-12-04 1:25 ` Jeff Garzik
2003-12-04 2:08 ` Linus Torvalds
2003-12-04 3:59 ` H. Peter Anvin
2003-12-04 2:37 ` Charles Manning
2003-12-04 14:17 ` Jörn Engel
2003-12-04 15:20 ` Linus Torvalds
2003-12-04 16:07 ` Phillip Lougher
2003-12-04 17:26 ` Jörn Engel
2003-12-04 18:20 ` Phillip Lougher
2003-12-04 18:40 ` Jörn Engel
2003-12-04 19:41 ` Erez Zadok
2003-12-05 11:20 ` Jörn Engel
2003-12-05 16:16 ` Erez Zadok
2003-12-05 19:14 ` Matthew Wilcox
2003-12-05 19:47 ` Erez Zadok
2003-12-05 20:28 ` Matthew Wilcox
2003-12-05 21:38 ` Pat LaVarre
2003-12-06 0:15 ` Maciej Zenczykowski
2003-12-06 1:35 ` Pat LaVarre
2003-12-06 2:39 ` Valdis.Kletnieks
2003-12-06 11:43 ` Maciej Zenczykowski
2003-12-07 0:04 ` Shaya Potter
2003-12-08 14:08 ` Jörn Engel
2003-12-06 0:50 ` Phillip Lougher
2003-12-08 11:37 ` David Woodhouse
2003-12-08 13:44 ` phillip
2003-12-08 14:07 ` David Woodhouse
2003-12-09 23:40 ` Pat LaVarre
2003-12-10 0:07 ` Pavel Machek
2003-12-10 1:28 ` Pat LaVarre
2003-12-10 2:13 ` Charles Manning
2003-12-05 19:58 ` Pat LaVarre
2003-12-08 11:28 ` David Woodhouse
2003-12-08 13:49 ` phillip
2003-12-04 19:18 ` David Wagner
2003-12-05 13:02 ` Jörn Engel
2003-12-05 17:28 ` Frank v Waveren
2003-12-05 23:59 ` David Wagner
2003-12-19 15:01 ` Rik van Riel
2003-12-04 3:10 ` Valdis.Kletnieks
2003-12-04 18:16 ` Hans Reiser
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=Pine.LNX.4.44.0312062301310.4130-100000@gaia.cela.pl \
--to=maze@cela.pl \
--cc=ezk@cs.sunysb.edu \
--cc=joern@wohnheim.fh-wedel.de \
--cc=kbiswas@neoscale.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.lavarre@ieee.org \
--cc=phillip@lougher.demon.co.uk \
--cc=valdis.kletnieks@vt.edu \
--cc=willy@debian.org \
/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;
as well as URLs for NNTP newsgroup(s).