From: mah@mhorton.net (Mary Ann Horton)
Subject: [TUHS] shared memory on Unix
Date: Wed, 1 Feb 2017 08:21:46 -0800 [thread overview]
Message-ID: <1b4095d8-047e-fa23-fc34-b1f8eb5c9d02@mhorton.net> (raw)
In-Reply-To: <E198DD1D-4C01-4EF1-AAF4-F3230C28979F@planet.nl>
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.)
Mary Ann
On 02/01/2017 06:18 AM, Paul Ruizendaal wrote:
> The presence of some sort of shared memory facility in the
> BBN V6 Unix kernel got me thinking about the origins of
> shared memory on Unix.
>
> I had a vague recollection that primordial versions were present
> in either PWB or CB3, but a quick glance at the source indicates
> that this is not correct.
>
> What are the origins of shared memory on Unix, i.e. what came
> before mmap() and SysV IPC? Was the BBN kernel the first to
> implement such a facility on Unix?
>
> Paul
>
next prev parent reply other threads:[~2017-02-01 16:21 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 [this message]
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
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=1b4095d8-047e-fa23-fc34-b1f8eb5c9d02@mhorton.net \
--to=mah@mhorton.net \
/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).