Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.arch Subject: Re: ancient OS history, ARM is sort of channeling the IBM 360 Date: Sat, 29 Jun 2024 23:53:59 -0000 (UTC) Organization: A noiseless patient Spider Lines: 17 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sun, 30 Jun 2024 01:53:59 +0200 (CEST) Injection-Info: dont-email.me; posting-host="4341965ad4e2fb75a1b93d496a5627b7"; logging-data="179758"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/5iB6TTzsUppc8+7TI0yxs" User-Agent: Pan/0.158 (Avdiivka; ) Cancel-Lock: sha1:y92TuPv2Qvj6phnq1FT0Sl1Kt0k= Bytes: 1845 On Sat, 29 Jun 2024 18:22:04 -0000 (UTC), John Levine wrote: > ... more often than not locate I/O is faster and easier. Given all the caveats and restrictions, “easier” is not how I would describe it. But perhaps we’re talking at cross-purposes. If Mitch did his TSS and PL/I stuff in the 1970s, while you’re talking about the 1960s, then that could explain it. By the 1970s, CPU/RAM speeds had improved to the point where copying records a few hundred bytes at a time between buffers was not the performance bottleneck; disk I/O was. > When you touched the address, the page fault caused the I/O. There seems to be this assumption that the paging mechanism is some kind of clever way of doing I/O. It’s not.