From: Bakul Shah <bakul@iitbombay.org>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Clever code
Date: Tue, 13 Dec 2022 08:30:32 -0800 [thread overview]
Message-ID: <7373D902-BC96-4149-925F-FC6F29BC2290@iitbombay.org> (raw)
In-Reply-To: <20221213161442.7A96422139@orac.inputplus.co.uk>
On Dec 13, 2022, at 8:14 AM, Ralph Corderoy <ralph@inputplus.co.uk> wrote:
>
> Hi Bakul,
>
>> Fortune 32:16 was a 5.6Mhz machine and couldn't process 1020KB/sec
>> (17 sectors/track of early ST412/ST506 disks) fast enough. As Warner
>> said, one dealt with it by formatting the disk so that the logical
>> blocks N & N+1 (from the OS PoV) were physically more than 1 sector
>> apart.
>
> Sticking with ST506 hard drives, by the time the 8 MHz ARM2 from Acorn
> was reading a 56 MB Rodime, it was the drive which couldn't keep up so
> executables were stored compressed on disk so the CPU had something to
> do, uncompressing the sector's content, while it waited for the next
> sector to arrive. :-)
IIRC the slow part was due to running some common apps! Not much buffering
allowed on a 256KB machine so by the time the app asks for the next block,
on a 1:1 interleave the block would be past the read head and you had to
spend an extra revolution to grab it!
next prev parent reply other threads:[~2022-12-13 16:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 3:30 Rudi Blom
2022-12-13 3:41 ` Warner Losh
2022-12-13 3:53 ` Dave Horsfall
2022-12-13 4:03 ` George Michaelson
2022-12-13 8:05 ` Ralph Corderoy
2022-12-13 9:45 ` Dagobert Michelsen
2022-12-13 7:47 ` Ralph Corderoy
2022-12-13 19:56 ` Dave Horsfall
2022-12-13 11:46 ` John P. Linderman
2022-12-13 14:07 ` Douglas McIlroy
2022-12-13 14:31 ` arnold
2022-12-13 14:48 ` Ralph Corderoy
2022-12-13 15:10 ` Douglas McIlroy
2022-12-13 15:34 ` Stuff Received
2022-12-13 15:56 ` Ralph Corderoy
2022-12-13 23:02 ` Harald Arnesen
2022-12-14 7:31 ` arnold
2022-12-15 18:06 ` Marc Donner
2022-12-15 18:08 ` Marc Donner
2022-12-15 6:30 ` [TUHS] Delay line memory (was: Clever code) Greg 'groggy' Lehey
2022-12-13 15:52 ` [TUHS] Re: Clever code Bakul Shah
2022-12-13 16:14 ` Ralph Corderoy
2022-12-13 16:30 ` Bakul Shah [this message]
2022-12-15 6:39 ` [TUHS] Sector interleaving (was: Clever code) Greg 'groggy' Lehey
-- strict thread matches above, loose matches on Subject: below --
2022-12-13 18:02 [TUHS] Re: Clever code Noel Chiappa
2022-12-13 17:58 Noel Chiappa
2022-12-13 18:51 ` G. Branden Robinson
2022-12-13 20:14 ` segaloco via TUHS
2022-12-13 20:58 ` Warren Toomey via TUHS
2022-12-14 2:28 ` Luther Johnson
2022-12-11 20:03 [TUHS] Re: Stdin Redirect in Cu History/Alternatives? Larry McVoy
2022-12-12 2:15 ` [TUHS] Clever code (was " Bakul Shah
2022-12-12 9:48 ` [TUHS] Re: Clever code Michael Kjörling
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=7373D902-BC96-4149-925F-FC6F29BC2290@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=ralph@inputplus.co.uk \
--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).