From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] Kernel Sizes
Date: Mon, 22 Jan 2018 00:42:53 +0100 [thread overview]
Message-ID: <39C0AA03-1D57-470E-8D40-58DF7EEC0EFE@planet.nl> (raw)
In-Reply-To: <mailman.4.1516572202.3873.tuhs@minnie.tuhs.org>
> 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
The LSX kernel was kept within a self-imposed limit of 16KB as well.
I've often thought that LSX was V5 'regressed' to the concepts of
V1, which was facing similar hardware constraints. Is that a
reasonable view?
For example, LSX has a maximum of three processes that are swapped
in and out in a stack-like fashion. Only one process is ever in core.
Is that how V1 was organized?
I realize that LSX was API compatible with V5/V6 and I don't mean
'regressed' in that sense.
Paul
next parent reply other threads:[~2018-01-21 23:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4.1516572202.3873.tuhs@minnie.tuhs.org>
2018-01-21 23:42 ` Paul Ruizendaal [this message]
2018-01-22 10:46 Rudi Blom
-- strict thread matches above, loose matches on Subject: below --
2018-01-21 22:36 Doug McIlroy
2018-01-21 22:03 Doug McIlroy
2018-01-20 18:11 Warner Losh
2018-01-20 18:33 ` Donald ODona
2018-01-20 19:22 ` Random832
2018-01-20 21:14 ` Michael Kjörling
2018-01-21 0:19 ` Warren Toomey
2018-01-21 1:41 ` Andy Kosela
2018-01-22 3:51 ` Warner Losh
2018-01-22 4:39 ` Grant Taylor
2018-01-22 6:53 ` Warner Losh
2018-01-21 2:08 ` Dan Stromberg
2018-01-21 2:13 ` Steve Johnson
2018-01-21 4:24 ` Warner Losh
2018-01-21 22:53 ` Greg 'groggy' Lehey
2018-01-22 1:19 ` Steve Nickolas
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=39C0AA03-1D57-470E-8D40-58DF7EEC0EFE@planet.nl \
--to=pnr@planet.nl \
/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).