From: Dan Halbert <halbert@halwitz.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Memory management in Dennis Ritchie's C Compiler
Date: Mon, 17 Aug 2020 15:44:09 -0400 [thread overview]
Message-ID: <283d2a61-3a52-9629-6f62-36e00687f949@halwitz.org> (raw)
In-Reply-To: <20200817193050.GC11413@mcvoy.com>
On 8/17/20 3:30 PM, Larry McVoy wrote:
> On Mon, Aug 17, 2020 at 03:27:15PM -0400, Noel Chiappa wrote:
>> > From: Jim Geist
>>
>> > When did mmap(2) come about?
>>
>> Pretty sure it's a Berserkleyism. I think it came in with the VM stuff that
>> DARPA mandated for VAX Unix (for the research project they funded).
> Bill Joy imagined it, the prototype is in one the 4.x BSD releases.
> Sun (Joe Moran) actually implemented it first in any Unix variant.
> It's possible the concept existed in some other OS but I'm not aware
> of it.
I have a clear memory of having a discussion with Bill Joy about the
idea of vread(2) and vwrite(2) when we were both grad students at
Berkeley. I remember we were eating sausages from Top Dog and sitting
outside Etcheverry Hall on or near the grassy plaza. I think vfork may
have already existed, and we were talking about adding some kind of
memory-mapped file I/O. I think I suggested the actual names, as a
parallel to vfork. Some of my thinking might have come from my
experience with TENEX while working summers at BBN. I was just a
sounding board; I wasn't implementing any of this. vread and vwrite were
in BSD4.1, but dropped in 4.2 (so my Googling says). I think it became
clear later that mmap was an easier concept than the initial vread and
vwrite ideas.
Dan H.
next prev parent reply other threads:[~2020-08-17 19:53 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 19:27 Noel Chiappa
2020-08-17 19:30 ` Larry McVoy
2020-08-17 19:44 ` Dan Halbert [this message]
2020-08-17 19:50 ` Paul Winalski
2020-08-17 22:05 ` Arthur Krewat
2020-08-18 0:52 ` Rob Gingell
2021-01-29 23:52 ` [TUHS] mmap() (was: Memory management in Dennis Ritchie's C Compiler) Greg A. Woods
-- strict thread matches above, loose matches on Subject: below --
2020-08-27 8:37 [TUHS] Memory management in Dennis Ritchie's C Compiler Paul Ruizendaal
2020-08-26 15:59 Noel Chiappa
2020-08-26 16:09 ` Warner Losh
2020-08-26 19:13 ` Clem Cole
2020-08-26 16:14 ` Jim Geist
2020-08-26 17:31 ` John Cowan
2020-08-26 13:24 Doug McIlroy
2020-08-26 15:41 ` John Cowan
2020-08-25 9:36 Steve Simon
2020-08-17 22:32 Norman Wilson
2020-08-17 22:55 ` Bakul Shah
2020-08-17 23:12 ` Chet Ramey
2020-08-18 6:33 ` arnold
2020-08-17 19:51 Noel Chiappa
2020-08-17 2:02 Noel Chiappa
2020-08-17 18:02 ` Paul Winalski
2020-08-17 18:13 ` Jim Geist
2020-08-17 18:48 ` Paul Winalski
2020-08-17 19:08 ` Jim Geist
2020-08-17 19:28 ` Paul Winalski
2020-08-17 19:35 ` Jim Geist
2020-08-17 19:41 ` Richard Salz
2020-08-17 23:40 ` Steffen Nurpmeso
2020-08-15 21:50 Dibyendu Majumdar
2020-08-16 15:20 ` arnold
2020-08-16 15:27 ` Jim Geist
2020-08-17 16:13 ` Dan Cross
2020-08-17 20:16 ` Dibyendu Majumdar
2020-08-17 20:34 ` Paul Winalski
2020-08-17 20:43 ` Dibyendu Majumdar
2020-08-17 21:05 ` Warner Losh
2020-08-17 22:47 ` Dave Horsfall
2020-08-17 23:06 ` Nemo Nusquam
2020-08-17 21:29 ` Dibyendu Majumdar
2020-08-24 15:58 ` Dan Cross
2020-08-24 17:08 ` John Cowan
2020-08-24 17:15 ` Clem Cole
2020-08-24 17:24 ` Clem Cole
2020-08-24 17:20 ` Dan Cross
2020-08-25 23:06 ` Arthur Krewat
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=283d2a61-3a52-9629-6f62-36e00687f949@halwitz.org \
--to=halbert@halwitz.org \
--cc=tuhs@minnie.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).