From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: mtoseland@cableinet.co.uk, linux-kernel@vger.kernel.org
Subject: Re: Fun with OOM on 2.4.18-pre9
Date: Thu, 14 Feb 2002 08:56:10 -0600 (CST) [thread overview]
Message-ID: <200202141456.IAA24921@tomcat.admin.navo.hpc.mil> (raw)
toad <mtoseland@cableinet.co.uk>:
>
> I do a make -j bzImage
> I have 2 large processes (Kaffe) running in the background. They are
> driven by scripts like this:
>
> while true;
> do su freenet -c java freenet.node.Main;
> done
>
> I have 512MB of RAM and no swap on 2.4.18-pre9.
> Kernel eventually slows to a near complete halt, and starts killing
> processes.
> It kills Kaffe several times
> Out of Memory: Killed process xyz (Kaffe)
> (no I don't have logs, sorry)
> Each time it's a different pid, having respawned from its parent
> process. Then later, it apparently becomes unkillable - each time it
> respawns it is *the same PID*. VT switching works, but otherwise the
> system is unresponsive. It is not clear whether the make -j is still
> running. Immediately before this, it did the same thing with dictd, but
> eventually got around to Kaffe. After a fairly long wait I rebooted with
> the reset switch.
>
> Any more information useful? Is this known behaviour?
Known behaviour - ie. don't do that.
On most systems a "make -j4", or 6, or even 8 will work. But SOMETHING has
to give after memory fills up. The number of processes to use for -j
depends on the system. On mine (256MB, dual pentium pro) I don't do more
than 6, and 4 works best (lets me run solitare too).
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2002-02-14 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 14:56 Jesse Pollard [this message]
2002-02-14 15:05 ` toad
2002-02-17 23:10 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-02-14 13:54 toad
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=200202141456.IAA24921@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=linux-kernel@vger.kernel.org \
--cc=mtoseland@cableinet.co.uk \
/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
all inboxes | Powered by JetHome®