From: imp@bsdimp.com (Warner Losh)
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:44:53 -0700 [thread overview]
Message-ID: <CANCZdfrZ76sfHi4Ps3-shoR4Rv5rN+hwZPBvfKC15LDvfqGFZw@mail.gmail.com> (raw)
In-Reply-To: <201801211651.w0LGpTx4011480@coolidge.cs.Dartmouth.EDU>
On Sun, Jan 21, 2018 at 9:51 AM, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
>
> 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.
>
16k words or 16k bytes? Given some of the other reported sizes I'm guessing
it's bytes.
Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180121/1c4ea1b0/attachment.html>
next prev parent reply other threads:[~2018-01-21 19:44 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 [this message]
2018-01-21 20:48 ` Steve Johnson
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=CANCZdfrZ76sfHi4Ps3-shoR4Rv5rN+hwZPBvfKC15LDvfqGFZw@mail.gmail.com \
--to=imp@bsdimp.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).