The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: Bakul Shah <bakul@iitbombay.org>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX on (not quite bare) System/370
Date: Mon, 19 Dec 2022 20:48:14 -0700	[thread overview]
Message-ID: <CANCZdfq+aLGSByS9ZLJSOAGcLYxYUqWWfdG5iQ40VPj5B5AU3g@mail.gmail.com> (raw)
In-Reply-To: <20221220030942.GR4401@mcvoy.com>

[-- Attachment #1: Type: text/plain, Size: 2847 bytes --]

On Mon, Dec 19, 2022, 8:10 PM Larry McVoy <lm@mcvoy.com> wrote:

> On Mon, Dec 19, 2022 at 06:52:47PM -0800, Bakul Shah wrote:
> > On Dec 19, 2022, at 1:19 PM, Rob Pike <robpike@gmail.com> wrote:
> > >
> > > Reiser and London's Unix, which I greatly admired, died on the vine
> > > for a variety of political reasons, as well as because it had
> > > slightly different semantics in some important cases, and because
> > > of a broad antipathy to virtual memory across the company due to
> > > various people having used VM on inadequate hardware, and of course
> > > then there was Multics. Sandy Fraser was very nervous about
> > > Research adopting the BSD kernel because of his experience with
> > > Atlas. But let it be said: Reiser's VM system was seriously
> > > impressive, cleanly integrated, structurally central, and
> > > wonderfully fast. And Sandy relented but the general warmth of 1127
> > > towards Berkeley led to Research adopting Berkeley Unix as its VAX
> > > VM platform, despite some, including myself, feeling that was
> > > inferior choice.
> >
> > Is there a publicly available description of Reiser's VM system?
> > I found "A Unix operating system for the DEC VAX 11/780 Computer"
> > by London & Reiser which includes a long paragraph on VM (included
> > below) but that is about it.
> >
> > And it would be interesting to hear why and what you found in
> > Reiser's VM system that was better than Berkeley's VM system.
>
> Berkeley didn't really have a good VM system, other than Bill Joy
> imagining it and then went on to go to Sun and inspired Joe Moran
> to implement it.
>

The 4.2 and 4.3 VM were too vax specific.

FreeBSD took Mach's VM system and while I have respect for what
> Mach was trying to do, holy moly, what a mess.
>

To be fair, 4.4BSD had the mach vm because while Sun wanted to donate their
VM, the lawyers killed the deal due to its value to the company... I'd sure
rather have had the SunOS vm in 4.4BSD, but they went with what was
available.  The Mach VM works, but it's fit to the 4.4 kernel is imperfect.

FreeBSD made it work via the early heroics of Dyson and Dillon, and the
late SMP tuning of Juniper. It works, but has undergone at least 5 or 6
reorgs over the years. It also scales as all the bottlenecks have been
fixed... but it could sure stand a rewrite (though that will have to wait
for the next paradigm shift).

NetBSD and OpenBSD adopted uvm instead maybe 5 or 10 years after 4.4 was
released. This VM was initially more easily scaleable than Mach, but I'm
not sure the vastly increased core counts of late work well with it.

Warner

I can't speak to Reiser's code because I haven't seen it, but I
> can speak to Joe Moran's code, it was just so clear to see what
> he was trying to do.  And he did it.  And you could understand it,
> I did as a year out of grad school.
>

[-- Attachment #2: Type: text/html, Size: 4106 bytes --]

  parent reply	other threads:[~2022-12-20  3:49 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 17:38 [TUHS] " Phil Budne
2022-12-19 18:53 ` [TUHS] " segaloco via TUHS
2022-12-19 21:01   ` Clem Cole
2022-12-19 21:19     ` Rob Pike
2022-12-19 22:15       ` segaloco via TUHS
2022-12-20  0:02         ` Brad Spencer
2022-12-20  1:04           ` Adam Thornton
2022-12-20  2:35             ` segaloco via TUHS
2022-12-20 14:25           ` Andrew Hume
2022-12-19 23:02       ` Clem Cole
2022-12-20  1:20         ` Larry Stewart
2022-12-20  1:33           ` Larry McVoy
2022-12-20  1:57             ` George Michaelson
2022-12-20  2:06               ` Dan Cross
2022-12-20 15:04                 ` Chet Ramey
2022-12-20  2:12               ` Adam Thornton
2022-12-20 15:29                 ` Andy Kosela
2022-12-20 15:35                   ` Adam Thornton
2022-12-21  2:43                     ` Luther Johnson
2022-12-20 23:18                 ` David Arnold
2022-12-20  2:52       ` Bakul Shah
2022-12-20  3:09         ` Larry McVoy
2022-12-20  3:27           ` Bakul Shah
2022-12-20  3:48           ` Warner Losh [this message]
2022-12-20  4:21           ` Jonathan Gray
2022-12-19 21:36 ` Marc Donner
2022-12-19 22:52   ` Charles H Sauer (he/him)
     [not found]   ` <01428a75-3507-7b8a-fd35-cef74c8c0bd2@ucsb.edu>
2022-12-20  1:49     ` [TUHS] Re: pre-1991 USENIX proceedings Marc Donner
2022-12-20  3:11 ` [TUHS] Re: UNIX on (not quite bare) System/370 Warner Losh
2022-12-20  8:56 ` arnold
2022-12-20  9:31   ` segaloco via TUHS
2022-12-20  9:39     ` arnold
2022-12-20  9:55       ` Jonathan Gray
2022-12-20 14:27     ` Clem Cole
2022-12-23  1:53       ` Rob Gingell
2022-12-22 19:00 ` Andrew Hume
2022-12-20 22:25 Noel Chiappa
2022-12-20 23:18 ` Bakul Shah
2022-12-22 17:26 Noel Chiappa
2022-12-22 17:33 ` Dan Cross
2022-12-22 20:25 ` Warner Losh
2022-12-22 23:06   ` Warner Losh

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=CANCZdfq+aLGSByS9ZLJSOAGcLYxYUqWWfdG5iQ40VPj5B5AU3g@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=bakul@iitbombay.org \
    --cc=lm@mcvoy.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).