Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.folklore.computers > #235725
| From | Lynn Wheeler <lynn@garlic.com> |
|---|---|
| Newsgroups | alt.folklore.computers |
| Subject | Re: Harvest time! |
| Date | 2026-10-03 16:16 -1000 |
| Organization | Wheeler&Wheeler |
| Message-ID | <87fqymp5w8.fsf@localhost> (permalink) |
| References | (3 earlier) <119nd6n$1ptm0$1@dont-email.me> <UySvS.40$gTHb.10@fx48.iad> <119p8ji$2g4hd$2@dont-email.me> <875wzjlld4.fsf@localhost> <1791055885-4353@newsgrouper.org> |
James Dow Allen <user4353@newsgrouper.org.invalid> writes: > This confuses me. The 370/168 -- dominant until the 3033 in the late 1970's > -- had 80 nsec "cycle time", and logic gate delays > were about 2 nsec minimum even without considering line delays or anything > more complicated than OR or NOR. Even the mini-"cycles" on the 370/135 > were 55 nsec IIRC. What are these super-short "cycle times" repeated > throughout that document? 165 370 microcode finished 370 instruction on avg. of one every 2.1 machine cycle. 168 improved 370 microcode so it finished 370 instruction on avg of one every 1.6 machine cycle. 3033 started out remapping 168 logic to 20% faster chips and then improving 370 microcode so it finished 370 instruction on avg of one every machine cycle for the 303x "channel director" they took 158 engine with just the integrated channel microcode. a 3031 was two 158 engines, one with just the 370 microcode and the other with just the integrated channel microcode.. a 3032 was 168 reworked to use 303x channel director (158 engine with just the integrated channel microcode). a "3033" could have up to three 303x channel directors (overall 3033 was about 50% faster than 168-3, combination of 20% faster chips and more optimizing of 370 microcode) but 303x channel director was slower on parts of channel program execution (i.e. 168 extermal channels had faster hardware the channel director 158 engine) -- virtualization experience starting Jan1968, online at home since Mar1970
Back to alt.folklore.computers | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Harvest time! David Lesher <wb8foz@panix.com> - 2026-10-01 02:06 +0000
Re: Harvest time! Anton Antimo <anton@safunu.org> - 2026-10-01 11:26 -0300
Re: Harvest time! Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-10-01 23:44 +0800
Re: Harvest time! David LaRue <huey.dll@tampabay.rr.com> - 2026-10-01 21:22 +0000
Re: Harvest time! Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-01 22:11 +0000
Re: Harvest time! Lars Poulsen <lars@beagle-ears.com> - 2026-10-01 20:05 -0700
Re: Harvest time! Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-02 04:50 +0000
Re: Harvest time! Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-10-02 18:17 +0000
Re: Harvest time! Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-02 21:44 +0000
Re: Harvest time! Lynn Wheeler <lynn@garlic.com> - 2026-10-02 13:43 -1000
Re: Harvest time! James Dow Allen <user4353@newsgrouper.org.invalid> - 2026-10-03 19:31 +0000
Re: Harvest time! Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-03 21:43 +0000
Re: Harvest time! Lynn Wheeler <lynn@garlic.com> - 2026-10-03 16:16 -1000
Re: Harvest time! James Dow Allen <user4353@newsgrouper.org.invalid> - 2026-10-06 21:23 +0000
Re: Harvest time! John Levine <johnl@taugh.com> - 2026-10-02 01:48 +0000
csiph-web