Sujet : Re: Architectural implications of locate mode I/O
De : mitchalsup (at) *nospam* aol.com (MitchAlsup1)
Groupes : comp.archDate : 02. Jul 2024, 23:14:51
Autres entêtes
Organisation : Rocksolid Light
Message-ID : <d40c10749892ca814002f1f0404ed61c@www.novabbs.org>
References : 1 2
User-Agent : Rocksolid Light
Thomas Koenig wrote:
John Levine <johnl@taugh.com> schrieb:
>
The 709 introduced data channels in 1958 which allowed the CPU to do
other stuff while the channel did the I/O. Wikipedia says the first
I/O interrupt was on the NBS DYSEAC in 1954 but it's hard to see how
an I/O interrupt would be of much use before channels. Once you had a
channel, I/O buffering made sense, have the channel read or write one
area while you're working on the other.
>
Not sure what you mean by "channel" in this context - hardware
channels like the /360 had, or any asynchronous I/O in general,
even without hardware support?
I think he is talking about anything between the PPs of CDC 6600
through that of System 360 channels, where there is enough smarts
in the channel to perform the mundane tasks of shuttling data to
or from the device (DMA) and sending an interrupt at the end
(exchange Jump in 6600 parlance).
>
Sending the next character to a teletype after the user program
fills a buffer and waiting for the next interrupt to tell you it's
ready makes sense, without a busy loop, makes sense anyway.
At that time, TTYs were slow enough to poll (PDP/8) or interrupt
per character.
Date | Sujet | # | | Auteur |
2 Jul 24 | Architectural implications of locate mode I/O | 64 | | John Levine |
2 Jul 24 | Re: Architectural implications of locate mode I/O | 38 | | Thomas Koenig |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 17 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 6 | | Lynn Wheeler |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Terje Mathisen |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 9 | | Bill Findlay |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 8 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Bill Findlay |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 6 | | Stephen Fuld |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 5 | | MitchAlsup1 |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 4 | | John Levine |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 2 | | John Savard |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 1 | | John Savard |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 19 | | John Levine |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 9 | | Anton Ertl |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 6 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 4 | | MitchAlsup1 |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 3 | | Michael S |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | MitchAlsup1 |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Joe Pfeiffer |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Robert Swindells |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | John Levine |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 9 | | Thomas Koenig |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 8 | | MitchAlsup1 |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 7 | | Thomas Koenig |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 5 | | John Levine |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 4 | | MitchAlsup1 |
7 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 3 | | Paul A. Clayton |
7 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Lynn Wheeler |
7 Jul 24 | Re: patents, Architectural implications of locate mode I/O and channels | 1 | | John Levine |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of people who don’t understand locate mode I/O | 1 | | Lawrence D'Oliveiro |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 24 | | Joe Pfeiffer |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 21 | | John Levine |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 18 | | Lynn Wheeler |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 14 | | Stephen Fuld |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 7 | | John Levine |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 6 | | Stephen Fuld |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 5 | | John Levine |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 4 | | Stephen Fuld |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 3 | | Thomas Koenig |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 2 | | Thomas Koenig |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 5 | | Lawrence D'Oliveiro |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 4 | | Stephen Fuld |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 2 | | John Levine |
2 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
11 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | Lawrence D'Oliveiro |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | MitchAlsup1 |
6 Jul 24 | Re: Old printers, Architectural implications of locate mode I/O | 1 | | John Levine |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |