From: Nicholas Knight <nknight@pocketinet.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: kernel@theoesters.com, linux-kernel@vger.kernel.org
Subject: Re: 1gb RAM + 1gb SWAP + make -j bzImage = OOM
Date: Sat, 5 Jan 2002 09:57:17 -0800 [thread overview]
Message-ID: <WHITEkvVMLaWYzfZRzD00000ce9@white.pocketinet.com> (raw)
In-Reply-To: <004b01c1955e$ecbc9190$6400a8c0@philxp> <WHITExcPbVzv2N2Ku2000000c76@white.pocketinet.com> <20020105161958.43d7ab25.skraw@ithnet.com>
In-Reply-To: <20020105161958.43d7ab25.skraw@ithnet.com>
On Saturday 05 January 2002 07:19 am, Stephan von Krawczynski wrote:
> On Fri, 4 Jan 2002 16:42:43 -0800
>
> Nicholas Knight <nknight@pocketinet.com> wrote:
> > I have absilutely no trouble reproducing on an 800MHz Athlon with
> > 256MB RAM/256MB swap on 2.4.17
>
> The simple question is: is the RAM sufficient at all to spawn such a
> lot of cc processes? In my setup I get around 1000 concurrently
> working during -j. This sounds like a real problem for 256/256, or
> not?
Matter of scale, did you try a full kernel build with make -j bzImage
using whatever your normal config is?
I still believe this is an innappropriate test, sure if you have tons
of RAM and swap it may eventualy complete (though if the swapfile is
very active and this is tried on a 2.4 kernel, the amount of CPU time
the compile will actually get will likely be unpredictable at best.)
This is an option that does nothing less than flood the system with
hundreds or thousands of processes that on any large compile will
simply not allow the system to survive intact without killing all the
processes. Does the OOM killer even work correctly yet? Or does it
still try to kill init at times? And for that matter, what order does
it kill in?
>
> Regards,
> Stephan
next prev parent reply other threads:[~2002-01-05 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 20:32 Phil Oester
2002-01-04 21:02 ` Stephan von Krawczynski
2002-01-05 0:42 ` Nicholas Knight
2002-01-05 1:24 ` Phil Oester
2002-01-05 21:41 ` Eric W. Biederman
2002-01-05 12:30 ` Luigi Genoni
2002-01-05 15:17 ` Stephan von Krawczynski
2002-01-07 6:22 ` Phil Oester
2002-01-07 14:24 ` Stephan von Krawczynski
2002-01-08 5:11 ` Phil Oester
2002-01-05 15:19 ` Stephan von Krawczynski
2002-01-05 17:57 ` Nicholas Knight [this message]
2002-01-06 14:40 ` Stephan von Krawczynski
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=WHITEkvVMLaWYzfZRzD00000ce9@white.pocketinet.com \
--to=nknight@pocketinet.com \
--cc=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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
all inboxes | Powered by JetHome®