From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] shared memory on Unix
Date: Wed, 1 Feb 2017 12:18:47 -0500 [thread overview]
Message-ID: <CAC20D2N0aC=SuTy0HLWSAtKr5yJFa7q=6JtQj4DqPfPsUxCz+w@mail.gmail.com> (raw)
In-Reply-To: <1b4095d8-047e-fa23-fc34-b1f8eb5c9d02@mhorton.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]
I do not remember the BBN share memory code, but the Columbus shared
memory and semaphore changes were certainly known in 1978 and 1979. I
remember seeing a man page for them from one of the OYOC types - Phil Karn
maybe, but its possible it was tjk. As quick scan of my paper archives,
did not turn anything up; and I do not remember any system at CMU that had
the code, only looking at a hard copy of the man pages.
My memory is that the API changed a little by the time they became the
System V API; as I remember thinking that the IPC was "new" when I first
saw it in a system that had all three.
On Wed, Feb 1, 2017 at 11:21 AM, 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.)
>
> 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 part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170201/0dc4c0f7/attachment.html>
next prev parent reply other threads:[~2017-02-01 17:18 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 [this message]
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='CAC20D2N0aC=SuTy0HLWSAtKr5yJFa7q=6JtQj4DqPfPsUxCz+w@mail.gmail.com' \
--to=clemc@ccc.com \
/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).