The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] 2.9BSD on an actual rl02 - swap confusion
Date: Sun, 8 Feb 2015 18:45:35 -0500	[thread overview]
Message-ID: <CAC20D2OZo9FaNfr8CkehuTBK3VaGg723KTgohTF01=pezA6vOw@mail.gmail.com> (raw)
In-Reply-To: <20150208224209.6AB7718C0BE@mercury.lcs.mit.edu>

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

On Sun, Feb 8, 2015 at 5:42 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:

> But this is kind of confusing, because when I was bringing up V6 under the
> Ersatz11 simulator, I had a problem where the swapper (process 0) was
> trying
> to fork (with the child becoming 1 and running /etc/init), and it did the
> 'swap out' thing. But there was a ton of free memory at that point, so...
> why
> was it doing a swap? Eh, something to investigate sometime...
>

​I'm relying on very old memory here ...  but my memory is that before
either fork or exec or maybe both (I forget all of this and don't have the
code on my laptop to check) the kernel did something in the swap area/maps.
  It may have been just preallocate the data area for the process.  ​But if
there was not enough space/got an error of some type, the system call
failed.

What this meant was the even if you has free ram, you had to have a working
swap device very early in the start up.   I wish I could remember those
details - hard to believe I spent so many hours (of fun) hacking on the
kernel of those systems ;-)



Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150208/d0aa6d3a/attachment.html>


  reply	other threads:[~2015-02-08 23:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 22:42 Noel Chiappa
2015-02-08 23:45 ` Clem Cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-08 20:42 Noel Chiappa
2015-02-08 20:52 ` Jacob Ritorto
2015-02-08 22:03 ` Clem Cole
2015-02-08 22:09   ` Ronald Natalie
2015-02-08 19:28 Jacob Ritorto

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='CAC20D2OZo9FaNfr8CkehuTBK3VaGg723KTgohTF01=pezA6vOw@mail.gmail.com' \
    --to=clemc@ccc.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).