From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: [COFF] Re: Supervisor mode on ye olde PDP-11
Date: Wed, 19 Jun 2024 12:17:20 -0400 (EDT) [thread overview]
Message-ID: <20240619161720.B301E18C088@mercury.lcs.mit.edu> (raw)
> From: Warner Losh
> 2.11BSD used a mode between kernel and user for the TCP stack to get
> more effective address space...
Is there a document for 2.11 which explains in detail why they did that? I
suspect it's actually a little more complicated than just "more address
space".
The thing is that PDP-11 Unix had been using overlays in the kernel for quite
a while to provide more address space. I forget where they first came in (I
suspect there were a number of local hacks, before everyone started using the
BSD approach), but by 2.9 BSD they were a standard part of the system. (See:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=2.9BSD/usr/src/sys/conf/Ovmakefile
for some clues about how this works. There is unfortunately no documentation
that I know of which explains clearly how it works; if anyone knows of any,
can you please let me know? Otherwise you'll have to read the sources.)
I can think of two possible reasons they started using supervisor mode: i)
There were a limited number of the 2.9-type overlays, and they were not
large; trying to support all the networking code with the existing overlay
system may have been too hard. ii) I think this one is unlikely, but I'll
list it as a possibility. Switching overlays took a certain amount of
overhead (since mapping registers had to be re-loaded); if all the networking
code ran in supervisor mode, the supervisor mode mapping registers could be
loaded with the right thing and just left.
Noel
next reply other threads:[~2024-06-19 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 16:17 Noel Chiappa [this message]
2024-06-19 16:55 ` Phil Budne
2024-06-19 17:20 ` Warner Losh
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=20240619161720.B301E18C088@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@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).