From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] Re: TUHS digest, Vol 1 #145 - 2 msgs
Date: Wed, 16 Apr 2003 20:45:00 -0700 [thread overview]
Message-ID: <20030417034500.GK26145@work.bitmover.com> (raw)
In-Reply-To: <200304170249.h3H2nQJ8001840@minnie.tuhs.org>
> I am fairly sure that 4.2BSD had manual pages for mmap, but it didn't
> work.
Right. Joy left Berkeley and joined Sun and the work got done at Sun.
I'm pretty sure that SunOS 4.0 was the first release with mmap working
as it was described. I was at Sun for the 4.1 release; 4.0 was the new
VM system, and it wasn't "new" like "we changed some stuff", it was new
as in everything was rewritten. The 4.0 VM system had segmap, read/write
were implemented with segmap in the kernel (you did a read, the kernel
mapped page, started a bcopy and would fault on itself if the page wasn't
there or had no TLB entry). Etc. I have postscript of the papers on
that, still very good reading if someone wants them.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next parent reply other threads:[~2003-04-17 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200304170249.h3H2nQJ8001840@minnie.tuhs.org>
2003-04-17 3:45 ` Larry McVoy [this message]
2003-04-18 1:10 ` Tim Bradshaw
2003-04-18 1:35 ` 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=20030417034500.GK26145@work.bitmover.com \
--to=lm@bitmover.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).