From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.10 improved reiserfs a lot, but could still be better
Date: Tue, 25 Sep 2001 18:41:32 -0400 [thread overview]
Message-ID: <200109252241.f8PMfWY07018@deathstar.prodigy.com> (raw)
In-Reply-To: <Pine.LNX.4.20.0109250820001.28393-100000@otter.mbay.net>
In article <Pine.LNX.4.20.0109250820001.28393-100000@otter.mbay.net> jalvo@mbay.net wrote:
| There used to be stupid hard disk formatting tricks where the sector
| numbers were interleaved
|
| 1001 1008 1002 1009 1003 1010 1004 1011 1005 1012 1006 1013 1007 1014
|
| just to gain that enhancement. I also remember an ancient IBM Dasd trick
| where the sectors were offset just slightly so that a track to track
| switch could pick up the next sector in time.
|
| Ancient history...
The spacing between consecutively numbered sectors is called
interleave, and the offset between cylinders is called skew.
Take a look at superformat, it's still done. The object is to take any
media without hardware cache and match the timing of the media under the
head with the need for data. This could easily double the transfer rate
on any media which runs in an unbuffered reader.
And I would be surprised if modern hard drives don't allow using an
offset between tracks so that when a track is read the next track
"starts" under the read heads after the delay to step one track. This
can save you the rotational latency of the drive, which on a 7200rpm
drive is ~8.5ms, or as great as the step time. If actual track to track
is matched to the step time you save that one rotation on big block
reads, like swaps.
Guess it's not quite so ancient history after all, just done by the
vendor typically. If I were writing a low level formatting routine, and
I haven't in over a decade, I would run some tests on how much skew is
needed to have the first sector under the head. The penelty for making
that number a little too large is a sector or two, the penalty for
making it too small is one rotation less a sector or two.
--
bill davidsen <davidsen@tmr.com>
"If I were a diplomat, in the best case I'd go hungry. In the worst
case, people would die."
-- Robert Lipe
next prev parent reply other threads:[~2001-09-25 22:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 14:09 [PATCH] 2.4.10 improved reiserfs a lot, but could still be better Beau Kuiper
2001-09-24 14:46 ` [reiserfs-list] " Chris Mason
2001-09-24 15:32 ` Matthias Andree
2001-09-24 15:45 ` Alan Cox
2001-09-24 15:47 ` Matthias Andree
2001-09-24 16:08 ` Alan Cox
2001-09-24 16:08 ` [reiserfs-list] " Chris Dukes
2001-09-24 16:54 ` Matthias Andree
2001-09-24 16:15 ` Nicholas Knight
2001-09-24 16:40 ` [reiserfs-list] " Lehmann
2001-09-24 16:53 ` Matthias Andree
2001-09-24 16:57 ` [reiserfs-list] " Lehmann
2001-09-25 14:04 ` bill davidsen
2001-09-25 17:39 ` bill davidsen
2001-09-24 20:05 ` Nicholas Knight
2001-09-25 0:11 ` Matthias Andree
2001-09-25 4:49 ` Nicholas Knight
2001-09-25 6:00 ` Beau Kuiper
2001-09-25 6:17 ` Nicholas Knight
2001-09-25 10:44 ` Matthias Andree
2001-09-25 11:01 ` ben-lists
2001-09-25 10:42 ` Matthias Andree
2001-09-25 11:07 ` Nicholas Knight
2001-09-25 14:47 ` Alex Bligh - linux-kernel
2001-09-25 15:13 ` Matthias Andree
2001-09-25 15:23 ` John Alvord
2001-09-25 22:41 ` bill davidsen [this message]
2001-09-25 12:54 ` Jorge Nerín
2001-09-25 13:06 ` [reiserfs-list] " Chris Mason
2001-09-25 13:17 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2001-09-24 21:58 Dieter Nützel
2001-09-25 0:19 ` Matthias Andree
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=200109252241.f8PMfWY07018@deathstar.prodigy.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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