public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: willy@debian.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCEMENT:  Squashfs released (a highly compressed filesystem)
Date: Thu, 31 Oct 2002 05:12:40 +0000	[thread overview]
Message-ID: <3DC0BBC8.4080104@lougher.demon.co.uk> (raw)

Matthew Wilcox wrote:
 >Larry McVoy wrote:
 >> > A r/w compressed filesystem would be darned useful too :)
 >> > mmap(2) is, err, hard. Not impossible, it means the file system 
has >to
 >> support both compressed and uncompressed files, but it's interesting.
 >
 >Easier than you think, perhaps.  Depends how much compression you're
 >after, of course, but here's how Acorn did it in RISCiX (a 4.3BSD
 >derivative):
 >

Strange you should mention this... I used to work at Acorn with
the guy who did this (Mark Taunton). RISCiX was too early to be 4.3, I
think it was 4.1, but may have been 4.2, certainly no later, this was
1989.

 >Pages were 32k (an interesting feature of the MMU...), and the 
 >underlying filesystem was a fairly vanilla BSD FFS (probably 4k blocks
 >with 1k fragments; discs were around 50MB).  Each page was written at 
a >32k boundary, but compressed.  So there were holes in the file where 
 >other files could store their data.  Naturally you waste on average 
512 >bytes per 32k page, but I think they managed to get 80MB of unix 
distro >onto a 50MB disc this way, so it's nothing to be sneezed at.

They only needed to compress the fs on the R140 (an ARM 2 based
machine).  The better R260 had a bigger disk, and so didn't need the
compression. Interestingly, because of the slow disk I/O, compression
made the filesystem access faster.

I had an R140, and space was so tight in the filesystem, you had
to delete part of the distribution before you could even compile
a program!

Phillip


             reply	other threads:[~2002-10-31  5:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31  5:12 Phillip Lougher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-30 14:17 ANNOUNCEMENT: Squashfs released (a highly compressed filesystem) Matthew Wilcox
2002-10-30  2:29 Phillip Lougher
2002-10-30  3:10 ` Samuel Flory
2002-10-30  3:51   ` Phillip Lougher
2002-10-30  4:03     ` Jeff Garzik
2002-10-30  4:11       ` Larry McVoy
2002-10-30  4:15         ` Jeff Garzik
2002-10-30 14:53         ` Jesse Pollard
2002-10-30 15:10           ` Padraig Brady
2002-10-30 15:42             ` Denis RICHARD
2002-10-31 16:18               ` Nicholas Wourms
2002-10-30 23:56       ` Phillip Lougher
2002-11-01 15:57         ` Rob Landley
2002-11-02  8:57           ` Phillip Lougher
2002-10-30  6:28     ` Ingo Oeser
2002-10-31  4:08       ` Phillip Lougher

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=3DC0BBC8.4080104@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@debian.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