From: Rene Herman <rene.herman@gmail.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Lindsay Roberts <lindsay.roberts.os@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs: Add romfs version 2
Date: Mon, 30 Jul 2007 20:29:50 +0200 [thread overview]
Message-ID: <46AE2E1E.6050909@gmail.com> (raw)
In-Reply-To: <46AE2A23.9060204@cfl.rr.com>
On 07/30/2007 08:12 PM, Phillip Susi wrote:
> Lindsay Roberts wrote:
>> * Increases romfs partition size limit from 2GB to 4GB.
>> * Adds new derivative of romfs filesystem (rom2fs) with
>> block aligned regular file data to bring performance
>> parity with ext2/3. This is about 225% of the read
>> speed of the existing romfs.
>
> Why does block alignment of files have any influence on speed for a rom
> based ( no seek time ) filesystem?
A CD-ROM is also a ROM...
But on a general note, please also note that the expensive seek versus cheap
read we know from magnetic is (well, can be that is) still present with
memory technologies, although much less pronounced.
Memory technologies (including flash) have historically had "burst" modes
where sequential accesses are sped up significanly versus random accesses,
causing really the exact same seek-versus-read principle as on magnetic.
Quite uncertain if/when the difference will ever be as pronounced as on
magnetic, but I believe we should at least be prepared to deal with this
problem for a _long_ time still...
Rene.
next prev parent reply other threads:[~2007-07-30 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 6:01 [PATCH] fs: Add romfs version 2 Lindsay Roberts
2007-07-17 8:36 ` Andrew Morton
2007-07-17 19:21 ` Matt Mackall
2007-07-18 3:16 ` Lindsay Roberts
2007-07-18 17:02 ` Tim Bird
2007-07-25 7:28 ` [Celinux-dev] " Greg Ungerer
2007-07-25 18:40 ` Pavel Machek
2007-08-06 7:43 ` Lindsay Roberts
2007-08-06 17:20 ` Matt Mackall
2007-07-30 18:12 ` Phillip Susi
2007-07-30 18:29 ` Rene Herman [this message]
2007-08-06 19:41 ` Sergey Vlasov
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=46AE2E1E.6050909@gmail.com \
--to=rene.herman@gmail.com \
--cc=lindsay.roberts.os@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.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