From: "jdow" <jdow@earthlink.net>
To: <root@chaos.analogic.com>
Cc: "jw schultz" <jw@pegasys.ws>, <linux-kernel@vger.kernel.org>
Subject: Re: Heuristic readahead for filesystems
Date: Mon, 16 Sep 2002 22:19:13 -0700 [thread overview]
Message-ID: <043801c25e09$c3002b40$1125a8c0@wednesday> (raw)
In-Reply-To: <Pine.LNX.3.95.1020916082446.22214A-100000@chaos.analogic.com>
From: "Richard B. Johnson" <root@chaos.analogic.com>
> On Thu, 12 Sep 2002, jdow wrote:
> > Dick, those studies are simply not meaningful. The speedup for
> > general applications that I generated in the mid 80s with a pair
> > of SCSI controllers for the Amiga was rather dramatic. At that
> > time every PC controller I ran down was reading 512 bytes per
> > transaction. They could not read contiguous sectors unless they
> > were VERY fast. For these readahead would generate no benefit.
> > (Even some remarkably expensive SCSI controllers for PCs fell
> > into that trap and defective mindset.) The controllers I re-
> > engineered were capable of reading large blocks of data multiple
> > sectors in size in a single transaction. I experimented with
> > several programs and discovered that a 16k readahead was about
> > my optimum compromise between the read time overhead vs the
> > transaction time overhead. I even found that for the average case
> > ONE buffer was sufficient, which boggled me. (As a developer I
> > was used to reading multiple files at a time to create object
> > files and linked targets.)
>
> 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.
Please allow me to add to my previous comment that the StarDrive and
HardFrame controllers were SCSI controllers. They ALWAYS made multi-
block reads. The smallest read they made was 16k. If more was requested
the StarDrive would read as much as was requested in one read. The
HardFrame had to break it into smaller, 128k, pieces due to a strange
DMA problem with the DMA controller that didn't like to be recycled
too quickly. So if a drive could send contiguous sectors on a 1:1
interleave that was what was used. (The ONLY thing I ever had that
could not was an Adaptec A4000 SCSI to ST506 controller that was rather
poorly written inside and could not, itself, manage 1:1 interleave on
the attached ST506 drive.) With CP/M I was doing 1:1 interleave on
8" floppies in the late 70s at last as reliably as other folks did
their 13:1 (CP/M) or 2:1 (UCSD Pascal). The controller was "dump",
a WD 1771 chip in a board called a "VersaFloppy".
{^_^} Joanne Dow, jdow@earthlink.net, who "gets it off" doing things
like this that the experts tell her are impossible.
next prev parent reply other threads:[~2002-09-17 5:14 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
2002-09-17 5:19 ` jdow [this message]
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='043801c25e09$c3002b40$1125a8c0@wednesday' \
--to=jdow@earthlink.net \
--cc=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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
Powered by JetHome