From: Stuart Remphrey <stu@remphrey.net>
To: "Greg 'groggy' Lehey" <grog@lemis.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] SMP: BSD vs System V (once was: moving directories in svr2)
Date: Mon, 10 Jan 2022 01:31:03 +0800 [thread overview]
Message-ID: <CAD0_1cmgKBpCz0WKOTJS76ZG_3ME7hyvhQ92+RqPJ-j-fS34aw@mail.gmail.com> (raw)
In-Reply-To: <20220103235600.GA68567@eureka.lemis.com>
[-- Attachment #1: Type: text/plain, Size: 2911 bytes --]
There were others that also did Unix SMP (some on BSD). Encore offering
BSD, AT&T or Mach (their storage arrays contained a core cluster of 2 SMP
nodes, later bought by Sun); Sequent; and Pyramid dualPort OS/x around
1985/87.
Pyramid had dual-CPU 90Mx/98x and I think a single lock (memory fades a
bit). Later more fine-grained around the time of the 1-CPU 9810 up to 4-CPU
9845. Before eventually going to MIPS CPU SMPs, then adding MPP to the MIPS
range.
IIRC, this was on a mostly-BSD 4.2/4.3 base(?) when I worked in the Pyramid
team producing their POSIX threads library & parallel debugger (late 80s).
Although Pyramid did have their ATT "unverse" incorporated into the same
Unix, hence dualPort. So there was a bunch of SVR3/4 support included:
extra set of syscalls; u.u_universe to select which; conditional symbolic
links using u.u_universe to resolve to UCB or ATT paths for lib & bin dirs;
merged TTY driver with a superset of stty attributes; etc.
Apollo Domain had something similar to conditional symbolic links, but
expanding environment variables to determine the target path. Different
flexibility/overhead tradeoff.
I wonder if any dualPort or DC/OSx Pyramid source survives...
or the old Australian promo poster from PTC BURP, where I got elected the
PHB, standing like a dork at the console of a 9840 cabinet (I think I was
the only one in a long sleeve shirt that day, and had an emergency tie at
the back of my desk drawer, so...)
On Tue, 4 Jan 2022, 08:04 Greg 'groggy' Lehey, <grog@lemis.com> wrote:
> On Monday, 3 January 2022 at 15:44:11 -0800, Larry McVoy wrote:
> > On Mon, Jan 03, 2022 at 05:21:51PM -0600, Doug McIntyre wrote:
> >> On Mon, Jan 03, 2022 at 04:15:08PM -0500, Dan Cross wrote:
> >> I'd agree, 2.4 was pretty slow and chunky, 2.5 was alright, but 2.5.1
> was quite usable and stable.
> >> Also by this time, the hardware was going in directions that SunOS
> wouldn't keep up with.
> >
> > Yeah, Doug is right, SunOS was pretty simple, it didn't really take
> advantage
> > of SMP, Greg Limes tried to thread it but it was too big a job for one
> guy.
> >
> > That's not to say that SunOS couldn't have evolved into SMP, I'm 100%
> > sure it could have. It just didn't. It's a shame.
>
> An interesting question. I had always thought that SMP was (one of?)
> the technical reasons why Sun moved from a BSD to a System V base.
> Since then, of course, we've done lots of work on SMP support for at
> least FreeBSD. Does anybody have an overview of how good the support
> is compared to modern Solaris? Is there any intrinsic reason why one
> should be better than the other?
>
> Greg
> --
> Sent from my desktop computer.
> Finger grog@lemis.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed. If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA.php
>
[-- Attachment #2: Type: text/html, Size: 3898 bytes --]
next prev parent reply other threads:[~2022-01-09 17:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 3:45 [TUHS] moving directories in svr2 Noel Chiappa
2021-12-30 4:02 ` Bakul Shah
2021-12-30 16:40 ` Theodore Ts'o
2021-12-30 22:31 ` Dan Cross
2021-12-31 0:43 ` Bakul Shah
2021-12-31 1:00 ` Rob Pike
2021-12-31 1:45 ` Bakul Shah
2021-12-31 2:23 ` Adam Thornton
2021-12-31 18:56 ` Chet Ramey
2021-12-31 3:08 ` Theodore Ts'o
2021-12-31 3:23 ` Rob Pike
2021-12-31 5:16 ` Theodore Ts'o
2021-12-31 5:21 ` Dan Cross
2021-12-31 5:55 ` Rob Pike
2021-12-31 13:32 ` Michael Kjörling
2021-12-31 15:53 ` Adam Thornton
2021-12-31 16:13 ` Arthur Krewat
2021-12-31 18:17 ` Dan Cross
2021-12-31 18:23 ` Larry McVoy
2021-12-31 18:37 ` Dan Cross
2021-12-31 18:29 ` Arthur Krewat
2022-01-01 0:09 ` Theodore Ts'o
2022-01-03 13:35 ` Dan Cross
2022-01-03 20:23 ` Theodore Ts'o
2022-01-03 20:45 ` Warner Losh
2022-01-03 21:15 ` Dan Cross
2022-01-03 22:26 ` Theodore Ts'o
2022-01-03 23:10 ` Dan Cross
2022-01-04 15:45 ` Chet Ramey
2022-01-09 19:28 ` Larry McVoy
2022-01-03 23:21 ` Doug McIntyre
2022-01-03 23:37 ` Adam Thornton
2022-01-04 14:49 ` Stuart Remphrey
2022-01-03 23:44 ` Larry McVoy
2022-01-03 23:56 ` [TUHS] SMP: BSD vs System V (once was: moving directories in svr2) Greg 'groggy' Lehey
2022-01-07 19:01 ` Warner Losh
2022-01-09 17:31 ` Stuart Remphrey [this message]
2022-01-13 2:35 ` Kevin Bowling
2022-01-03 23:56 ` [TUHS] moving directories in svr2 Warner Losh
2022-01-04 2:28 ` Theodore Ts'o
2022-01-04 2:42 ` Larry McVoy
2022-01-04 9:28 ` [TUHS] Mythical Distress Sale (was Re: moving directories in svr2) Rob Gingell
2022-01-04 15:17 ` Larry McVoy
2022-01-04 15:26 ` arnold
2022-01-04 15:40 ` Larry McVoy
2022-01-04 15:48 ` Richard Salz
2022-01-03 22:57 ` [TUHS] moving directories in svr2 Phil Budne
2022-01-04 15:40 ` [TUHS] VRFs (was Re: moving directories in svr2) Derek Fawcus
2021-12-31 5:12 ` [TUHS] moving directories in svr2 Bakul Shah
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=CAD0_1cmgKBpCz0WKOTJS76ZG_3ME7hyvhQ92+RqPJ-j-fS34aw@mail.gmail.com \
--to=stu@remphrey.net \
--cc=grog@lemis.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).