The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] shared memory on Unix
Date: Thu, 2 Feb 2017 00:11:02 +0100	[thread overview]
Message-ID: <82F3421B-9EF3-4752-B4E6-E2F15529FCDE@planet.nl> (raw)
In-Reply-To: <1b4095d8-047e-fa23-fc34-b1f8eb5c9d02@mhorton.net>

Many thanks to all for that helpful info!

OK, so my vague recollection was more correct than my quick code
inspection...

With CB3 I meant CB Unix 3.0. I had a look at the "pdp11v" code
in the Unix Tree archive and it has a system call "maus". Its implementation
is here:
http://minnie.tuhs.org/cgi-bin/utree.pl?file=pdp11v/usr/src/uts/pdp11/os/maus.c

There is also a CB Unix 2.1 manual and source code listing in the archive.
The manual page for maus says it stands for "multiple access user space"
(http://www.tuhs.org/Archive/PDP-11/Distributions/other/CB_Unix/cbunix_man2_02.pdf)
At first glance 'maus' looks a bit like mmap.

I did not find a print of the maus implementation yet in the source print, but
I haven't exaustively searched yet (it is mentioned in the index, so it
probably is there somewhere).

In any case, the man page for maus is from November 1979, so it goes back at
least as far as that. When was CB Unix 1.0 put together?

--

It will be interesting to see how the BBN and CB approaches compare.

Noel wrote: "Yes, there are two module in 'ken', map_page.c and set_lcba.c
(I was unable to work out what 'LCBA' stood for) which seem to do something with
mapping."

How about "Local Common Block Access"? :^)

Paul


> The so-called Columbus shared memory feature was in their system in the
> mid-1970s, along with a few other things such as semaphores and
> inter-process messages. I seem to recall the acronym MAUG, but I may have a
> letter or two wrong. Something like Multi Access User ____. The much later
> System V features had a completely different API.
> 
> Hey, Doug, do you remember this? In the early 1970s, there were a couple of
> UNIX meetings at Murray Hill, at which various Bell Labs groups presented
> on what they were doing with UNIX, and a group, perhaps Columbus, said that
> UNIX wasn't capable of doing what they wanted, so they had modified it. You
> asked the question, "Why are you using UNIX?"
> 
> To my knowledge, having witnessed another decade or so of groups trying to
> bend UNIX to their will, it was the last time the question was asked.
> 
> --Marc
> 
> 
> > Mary Ann Horton <mah at mhorton.net
> > wrote:
> 
> > > I*'m not sure what you mean by CB3, but these features (shared memory,
> > > semaphores, IPC) were added to CB-UNIX (Bell Labs, Columbus) precisely
> > > because they were needed in real time telco systems and not preset in
> > > the versions from New Jersey.  This would have been in the early 1980s.
> > > When I got there in 1981 I think CB-UNIX was already well established
> > > and had these features.  (These would show up, ironically, in /usr/ucb,
> > > which did not stand for Berkeley.)


  parent reply	other threads:[~2017-02-01 23:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 14:18 Paul Ruizendaal
2017-02-01 16:21 ` Mary Ann Horton
2017-02-01 17:18   ` Clem Cole
2017-02-01 17:24   ` Joerg Schilling
2017-02-01 17:39     ` Marc Rochkind
2017-02-01 18:04       ` Clem Cole
2017-02-01 18:01     ` Clem Cole
2017-02-01 18:07       ` Marc Rochkind
2017-02-01 18:15       ` Joerg Schilling
2017-02-01 18:32         ` Marc Rochkind
2017-02-01 18:35           ` Joerg Schilling
2017-02-01 18:33       ` arnold
2017-02-01 19:11         ` Steve Johnson
2017-02-01 19:24           ` Marc Rochkind
2017-02-01 19:30         ` Clem Cole
2017-02-02  0:25           ` Nick Downing
2017-02-01 23:11   ` Paul Ruizendaal [this message]
2017-02-02  1:10     ` Clem Cole
2017-02-01 19:44 Noel Chiappa
2017-02-01 19:55 ` ron minnich
2017-02-01 21:40 ` Larry McVoy

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=82F3421B-9EF3-4752-B4E6-E2F15529FCDE@planet.nl \
    --to=pnr@planet.nl \
    /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).