From: Charles Manning <manningc2@actrix.gen.nz>
To: phillip@lougher.demon.co.uk, "David Woodhouse" <dwmw2@infradead.org>
Cc: joern@wohnheim.fh-wedel.de, kbiswas@neoscale.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [OT?]Re: partially encrypted filesystem
Date: Wed, 10 Dec 2003 14:16:46 +1300 [thread overview]
Message-ID: <20031210010947.CA5875748@blood.actrix.co.nz> (raw)
In-Reply-To: <E1ATLgF-0003XX-0V@anchor-post-31.mail.demon.net>
On Tuesday 09 December 2003 02:44, phillip@lougher.demon.co.uk wrote:
> > JFFS2 was designed to avoid that inefficient extra layer, and work
> > directly on the flash. Since overwriting stuff in-place is so difficult,
> > or requires a whole new translation layer to map 'logical' addresses to
> > physical addresses, it was decided just to ditch the idea that physical
> > locality actually means _anything_.
>
> Maybe okay for a flash filesystem which is slow anyway, but many filesystem
> designers *are* concerned about physical locality of blocks, for example
> video filesystems.
Sure, just because JFFS2 choses to do something a certain way for a certain
reason does not mean that others cannot choose to do something the different
(or even the same) for a different reason. The choices made in JFFS2 were
done to work around the constraints of flash memory. When those are not
present then
Like JFFS2, YAFFS is also a log-structured flash file system that does not
use a block device and does not assume physical data blocks can be updated in
place. YAFFS uses a log structure for exactly the same reasons David
presented (to get away from a physical location dependence - a killer for
flash file systems). However, YAFFS uses fixed-size chucks as "log records"
and is thus not really compression friendly. The differences between JFFS2
and YAFFS are there for good reasons, beyond the scope of this discussion.
>
> > Given that design, compression just dropped into place; it was trivial.
>
> Or maybe 'not in(to)-place' :-) I don't think I was saying compression is
> difficult, it is not difficult if you've designed the filesystem correctly.
Effectively saying that a fs that can't easily support compression is badly
designed is a dangerous over-simplfication/generalisation/slur.
There are over 40 file systems for Linux - each is valid and exists because
it does something that other fs don't do well or solve some particular
problem. Often, these fs jump through enough hoops of fire just to work
effectively and adding compression could easily compromise the main goals of
the fs.
As an example (that I'm familiar with :-)), I'd say that adding compression
to YAFFS would at best compromise some of the YAFFS design goals and make it
at best slower and at worst not be possible at all - without major upheaval.
For those that simply *must* have compression on a YAFFS-based storage, I
advise the use of a loop-mounted fs that provides compression (eg. cramfs)
backed by a YAFFS file. This is being used in some products to great effect.
It might seem that this adds extra overheads, but there is some saving
because the whole file system does not have to carry the burden of
compression etc.
-- CHarles
next prev parent reply other threads:[~2003-12-10 1:10 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
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-10 1:16 ` Charles Manning [this message]
2003-12-10 17:45 ` [OT?]Re: " Phillip Lougher
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=20031210010947.CA5875748@blood.actrix.co.nz \
--to=manningc2@actrix.gen.nz \
--cc=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=kbiswas@neoscale.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
/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
all inboxes | Powered by JetHome®