From: "Wander Winkelhorst" <w.winkelhorst@gmail.com>
To: "Rik van Riel" <riel@surriel.com>
Cc: Valdis.Kletnieks@vt.edu,
"Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>,
"Pavel Machek" <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: WANTED: kernel projects for CS students
Date: Sat, 3 Nov 2007 10:44:14 +0100 [thread overview]
Message-ID: <5699f8f00711030244j4d8bed83j3a9e4a2191201a3c@mail.gmail.com> (raw)
In-Reply-To: <20071102233615.6dc90e35@bree.surriel.com>
On 11/3/07, Rik van Riel <riel@surriel.com> wrote:
> On Fri, 02 Nov 2007 23:08:23 -0400
> Valdis.Kletnieks@vt.edu wrote:
>
> > IBM's AIX supported file system compression on the JFS filesystem
> > years ago. I was able to get up to 30% throughput increases by
> > converting the /usr filesystem to compressed - because even a 33mhz
> > Power chipset could read in 5 512-byte blocks and decompress it to
> > the original 4K faster than the disk could read in 8 512-byte
> > blocks.
>
> > Given that today there's an even *bigger* disparity in CPU speed
> > versus disk speed, I'd be surprised if it doesn't help today too.
>
> The problem is that disk seek times have not gotten much
> faster over the years, while disk throughput rates have
> skyrocketed.
>
> Transferring a little less data is not going to help you
> when 80% of your disk time is spent seeking, not reading
> or writing.
This sounds like flash based media are an ideal candidate for compression.
No seek times to speak of, transfer rates that are lower than those of
disks and limited capacity.
I believe JFFS2 (a flash filesystem) allready does compression though.
next prev parent reply other threads:[~2007-11-03 9:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 23:01 Rik van Riel
2007-10-15 10:40 ` WANG Cong
2007-10-15 17:13 ` Rik van Riel
2007-10-15 14:23 ` Sam Ravnborg
2007-10-15 15:10 ` Rik van Riel
2007-10-15 18:31 ` Sam Ravnborg
2007-10-15 16:31 ` Philippe Elie
2007-10-15 16:36 ` Philippe Elie
2007-10-15 16:52 ` Jan Engelhardt
2007-10-15 16:53 ` Xavier Bestel
2007-10-15 18:19 ` Sam Ravnborg
2007-10-15 15:40 ` Jörn Engel
2007-10-15 17:04 ` Doug Whitesell (LKML)
2007-10-15 17:04 ` Mark Gross
2007-10-15 18:30 ` Sam Ravnborg
2007-10-15 18:45 ` Mark Gross
2007-10-15 19:54 ` Giacomo Catenazzi
2007-10-16 20:06 ` Mark Gross
2007-10-16 20:09 ` Jan Engelhardt
2007-10-16 20:23 ` Rik van Riel
2007-10-16 20:25 ` Jan Engelhardt
2007-10-16 21:10 ` david
2007-10-16 21:30 ` david
2007-11-02 7:54 ` Giacomo Catenazzi
2007-10-16 20:31 ` Giacomo Catenazzi
2007-10-15 19:17 ` Alexey Dobriyan
2007-10-15 19:54 ` Folkert van Heusden
2007-10-16 20:10 ` Mark Gross
2007-10-16 0:39 ` david
2007-10-15 17:10 ` Zan Lynx
2007-10-15 17:23 ` Rik van Riel
2007-10-16 0:51 ` david
2007-10-15 17:30 ` Guilherme Amadio
2007-10-15 18:03 ` J. Bruce Fields
2007-10-17 17:45 ` Mark Gross
2007-10-18 4:51 ` Toshiharu Harada
2007-10-28 18:07 ` Pavel Machek
2007-10-28 18:57 ` Rafael J. Wysocki
2007-10-29 19:48 ` Lennart Sorensen
2007-10-29 20:19 ` Pavel Machek
2007-10-29 21:44 ` Lennart Sorensen
2007-11-03 3:08 ` Valdis.Kletnieks
2007-11-03 3:36 ` Rik van Riel
2007-11-03 9:44 ` Wander Winkelhorst [this message]
2007-11-03 10:05 ` david
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=5699f8f00711030244j4d8bed83j3a9e4a2191201a3c@mail.gmail.com \
--to=w.winkelhorst@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=pavel@ucw.cz \
--cc=riel@surriel.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
all inboxes | Powered by JetHome®