The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] TUHS Digest, Vol 38, Issue 10
Date: Wed, 09 Jan 2019 07:09:55 -0800	[thread overview]
Message-ID: <20190109151002.E94D2156E41B@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 08 Jan 2019 22:45:31 -0700." <CANCZdfocjjyFu43JF17iF=woZXvXQzbZpswoL41Pbin7DgJR=Q@mail.gmail.com>

On Tue, 08 Jan 2019 22:45:31 -0700 Warner Losh <imp@bsdimp.com> wrote:
>
>
> > > For example, I could envisage a disk where the sectors are deliberately
> > > not numbered sequentially i.e. they've taken rotational latency into
> > > account for you?
> >
> > We did in fact use an interleave factor of more than 1 (skip
> > more than 1 block for consecutively numbered sectors) to
> > improve throughput but that had to do with slow processing.
> > We did discuss "dead reckoning" (invoking the service routine
> > right when the N+1 numbered sector was near the r/w heads) but
> > I don't think we implemented it.
> >
>
>  For floppy drivers that I've seen the source to in early unixes, this was
> often the case. One minor device would be to access the 'raw' device, while
> another would be to access the 'cooked' sector numbers where the mapping
> was anything but linear. you'd have an interleave of, say, 4 or so, and
> then a 'slip' from track to track. The interleave factor was based on how

We used interleaving on the hard disk because a 5Mbps ST412
drive could stream data faster than typical user program could
handle (on a 5.6Mhz bus machine). We used h/w support as the
machine was already too slow to do any s/w interleaving!

Example: for an interleave of 1, at the time formatting the
disk, sector ids would be written in this sequence:
 1 8 2 9 3 A 4 B 5 C 6 D 7 E
We picked the interleave number based on some typical use
cases at the time.

The floppy driver was was a completely separate driver for
various reasons.

      reply	other threads:[~2019-01-09 15:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1546912802.21858.tuhs@minnie.tuhs.org>
2019-01-08 10:15 ` Steve Simon
2019-01-08 11:00   ` Andreas Kusalananda Kähäri
2019-01-08 14:58   ` Warner Losh
2019-01-09  2:10     ` Dave Horsfall
2019-01-09  4:23       ` Warner Losh
2019-01-09 19:13         ` Christian Barthel
2019-01-09  5:19       ` Bakul Shah
2019-01-09  5:45         ` Warner Losh
2019-01-09 15:09           ` Bakul Shah [this message]

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=20190109151002.E94D2156E41B@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=imp@bsdimp.com \
    --cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).