The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Peter Jeremy <peter@rulingia.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Old mainframe I/O speed (was: core)
Date: Thu, 21 Jun 2018 10:00:04 -0400	[thread overview]
Message-ID: <CABH=_VSzhumPL4xUfLpwpJRH9Qgv5TLy8M5ombeiw2VnGikdYg@mail.gmail.com> (raw)
In-Reply-To: <20180621030505.GA89671@server.rulingia.com>

On 6/20/18, Peter Jeremy <peter@rulingia.com> wrote:
>
> Note that most S360 machines were microcoded with the native ALU size
> varying between 8 and 32 bits.  The model 25 was also the only S360 with
> writable microcode and there was a microcoded APL implementation for it so
> it "natively" executed APL.  I'm not sure if there were any other novel
> microcode sets for it.

Yes, the model 25's microcode was in core.  I remember we had to
reaload it from punch cards at one point when IBM issued an update.  I
didn't know about the custom APL microcode.  I do recall that the disk
controller logic, as well as the "selector channel", was in CPU
microcode.  After the model 25 was withdrawn, IBM released the sources
for the microcode to customers.  There were several hacks in there to
slow down the disk I/O so that it didn't outperform the model 30.

> [3] "selector" channels were used for high speed devices - tape, DASD[4]
> [4] Direct Access Storage Device - IBM speak for "disk"

They used the term DASD because it covered non-disk devices such as
drums and the 2321 data cell drive (aka "noodle picker").

-Paul W.

  reply	other threads:[~2018-06-21 14:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 15:25 [TUHS] core Noel Chiappa
2018-06-15 23:05 ` Dave Horsfall
2018-06-15 23:22   ` Lyndon Nerenberg
2018-06-16  6:36     ` Dave Horsfall
2018-06-16 19:07       ` Clem Cole
2018-06-18  9:25         ` Tim Bradshaw
2018-06-19 20:45           ` Peter Jeremy
2018-06-19 22:55             ` David Arnold
2018-06-20  5:04               ` Peter Jeremy
2018-06-20  5:41                 ` Warner Losh
2018-06-20  8:10                   ` [TUHS] Old mainframe I/O speed (was: core) Greg 'groggy' Lehey
2018-06-20 16:33                     ` Paul Winalski
2018-06-21  3:05                       ` Peter Jeremy
2018-06-21 14:00                         ` Paul Winalski [this message]
2018-06-21 14:49                           ` Arrigo Triulzi
2018-06-21 20:39                             ` Paul Winalski
2018-06-22  5:32                               ` Erik E. Fair
2018-06-22 13:32                                 ` Clem Cole
2018-06-23  6:08                             ` Dave Horsfall
2018-06-23 17:02                               ` ron minnich
2018-06-22 13:11 Noel Chiappa
2018-06-22 17:49 ` Erik E. Fair
     [not found] <mailman.1.1529690481.3725.tuhs@minnie.tuhs.org>
2018-06-23 10:32 ` Johnny Billquist
2018-06-23 11:39   ` Clem cole
2018-06-24  7:50   ` Mutiny
2018-06-27 13:59     ` Clem Cole
2018-06-24  3:14 Norman Wilson
2018-06-24 13:03 ` Paul Winalski
2018-06-24 14:41   ` Lawrence Stewart
2018-06-24 15:47     ` Arthur Krewat
2018-06-24 18:49 Norman Wilson
2018-06-24 18:49 Norman Wilson

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='CABH=_VSzhumPL4xUfLpwpJRH9Qgv5TLy8M5ombeiw2VnGikdYg@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=peter@rulingia.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).