From: ebiederm@xmission.com (Eric W. Biederman)
To: Phil Oester <kernel@theoesters.com>
Cc: Nicholas Knight <nknight@pocketinet.com>,
Stephan von Krawczynski <skraw@ithnet.com>,
linux-kernel@vger.kernel.org
Subject: Re: 1gb RAM + 1gb SWAP + make -j bzImage = OOM
Date: 05 Jan 2002 14:41:04 -0700 [thread overview]
Message-ID: <m11yh4tr0v.fsf@frodo.biederman.org> (raw)
In-Reply-To: <004b01c1955e$ecbc9190$6400a8c0@philxp> <20020104220240.233ae66a.skraw@ithnet.com> <WHITExcPbVzv2N2Ku2000000c76@white.pocketinet.com> <20020104172418.A28715@ns1.theoesters.com>
In-Reply-To: <20020104172418.A28715@ns1.theoesters.com>
Phil Oester <kernel@theoesters.com> writes:
> On Fri, Jan 04, 2002 at 04:42:43PM -0800, Nicholas Knight wrote:
> > The one catch is that -j is specified without a number.
>
> [snip superfluous description of what 'make -j' implies]
>
> > number, your system is dead. A user issue because it seems the user is
> > using the option without fully comprehending the consequences.
>
> eh? Trust me - i understand the implications of make -j. It's not an
> unreasonable test, especially on a machine with 1gb ram/swap. For reference,
> read Rik's email regarding his reverse VM patch:
>
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=101007711817127&w=2
>
> Might be enlightening
Yes. It sounds like he Rick slowed down fork enough the system didn't fall
over. There may be some other policy changes as well. But my hunch is that
it is a fork speed thing. If all that happens is that the system hits
OOM when subjected to an unreasonable load I don't see this as a problem.
The truly interesting question is what happens when you and more swap.
With sufficient swap will it work?
Eric
next prev parent reply other threads:[~2002-01-05 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 20:32 1gb RAM + 1gb SWAP + make -j bzImage = OOM 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 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 21:41 ` Eric W. Biederman [this message]
2002-01-05 12:30 ` Luigi Genoni
2002-01-05 15:19 ` Stephan von Krawczynski
2002-01-05 17:57 ` Nicholas Knight
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=m11yh4tr0v.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nknight@pocketinet.com \
--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