mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: jdow@earthlink.net (jdow)
Cc: jw@pegasys.ws, linux-kernel@vger.kernel.org
Subject: Re: Heuristic readahead for filesystems
Date: Tue, 17 Sep 2002 11:37:56 +0100 (BST)	[thread overview]
Message-ID: <200209171037.g8HAbuIf001453@darkstar.example.net> (raw)
In-Reply-To: <02f401c25deb$e5f87bc0$1125a8c0@wednesday> from "jdow" at Sep 16, 2002 06:45:27 PM

> > Well they could read contiguous sectors if the sector interleave
> > was correctly determined and the correct interleave was set
> > while low-level formatting. Now-days, interleave is either ignored
> > or unavailable because there is a sector buffer that can contain
> > an entire track of data. Some SCSI drives have sector buffers
> > that can contain a whole cylinder of data.
> 
> When I say contiguous I mean contiguous not interleaved, sonny. I had
> CP/M (and UCSD Pascal) reading physically contiguous sectors on the
> disk with no lost speed. That means I read, with my DSSD format of
> 9 sectors each 512 bytes in size per side 18 full tracks 19 revolutions
> of the disk. I did skew the sector numbers to allow for seeks. But I
> did not interleave the tracks. It was not necessary with clean and
> correct code. I rather resent the presumption that I am a dumb bitch
> here.

Ah, but the *really* clever thing to do at the time, on systems where you couldn't optimally achieve 1:1 interleave on a floppy, was to allocate sectors on alternating sides of the disk.  So, you could, for example, read two tracks in 3 revolutions, instead of 6, in the case of 3:1 interleave :-).

John.

  reply	other threads:[~2002-09-17 10:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 15:42 Xuan Baldauf
2002-09-11 16:33 ` Davide Libenzi
2002-09-11 17:03   ` jdow
2002-09-11 17:20     ` Davide Libenzi
2002-09-11 17:51       ` jdow
2002-09-11 17:16   ` Hans Reiser
2002-09-11 16:42 ` Rik van Riel
2002-09-11 17:20   ` Oliver Neukum
2002-09-11 17:56   ` Xuan Baldauf
2002-09-11 18:30     ` Oliver Neukum
2002-09-11 18:43       ` Xuan Baldauf
2002-09-11 19:04         ` Oliver Neukum
2002-09-11 19:21           ` Richard B. Johnson
2002-09-12  0:45             ` jw schultz
2002-09-12  1:58               ` Andrew Morton
2002-09-12 11:41               ` Richard B. Johnson
2002-09-12 13:35                 ` jw schultz
2002-09-12 21:33                 ` jdow
2002-09-16 12:52                   ` Richard B. Johnson
2002-09-17  1:45                     ` jdow
2002-09-17 10:37                       ` jbradford [this message]
2002-09-17  5:19                     ` jdow
2002-09-12 12:41               ` Jesse Pollard
2002-09-11 19:03   ` Tomas Szepe

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=200209171037.g8HAbuIf001453@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=jdow@earthlink.net \
    --cc=jw@pegasys.ws \
    --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

Powered by JetHome