The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] Subject: Re: KernelSizesA self-imposed limit of 16K held in v1, and was quite fullyutilized.Subject:Re:  Kernel Sizes
Date: Sun, 21 Jan 2018 12:48:15 -0800	[thread overview]
Message-ID: <b882ab42937551a61421354fd51a176d15715082@webmail.yaccman.com> (raw)
In-Reply-To: <201801211651.w0LGpTx4011480@coolidge.cs.Dartmouth.EDU>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

I seem to remember that at some point early on, we spent some of our
capital budget on buying another 16K bytes for the PDP-11.  As I
recall, the deal was that the OS got 8K and users got 8K.  I also
recall that that purchase was 20% of our capital budget for the
year...

Doug, did I remember this correctly?

Steve

----- Original Message -----
From: "Doug McIlroy" <doug@cs.dartmouth.edu>
To:<tuhs at minnie.tuhs.org>
Cc:
Sent:Sun, 21 Jan 2018 11:51:29 -0500
Subject:[TUHS] Subject: Re: KernelSizesA self-imposed limit of 16K
held in v1, and was quite fullyutilized.Subject:Re: Kernel Sizes

 A self-imposed limit of 16K held in v1, and was quite fully utilized.
 When the iernel was rewritten in C, the limit (perhaps larger by
then)
 influenced the C compiler. More than one optimization was stimulated
 by the need to keep the kernel in bounds.

 Doug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180121/51cdc36f/attachment.html>


      parent reply	other threads:[~2018-01-21 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21 16:51 Doug McIlroy
2018-01-21 19:44 ` Warner Losh
2018-01-21 20:48 ` Steve Johnson [this message]

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=b882ab42937551a61421354fd51a176d15715082@webmail.yaccman.com \
    --to=scj@yaccman.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).