From: "Phil Oester" <kernel@theoesters.com>
To: <linux-kernel@vger.kernel.org>
Subject: 1gb RAM + 1gb SWAP + make -j bzImage = OOM
Date: Fri, 4 Jan 2002 12:32:27 -0800 [thread overview]
Message-ID: <004b01c1955e$ecbc9190$6400a8c0@philxp> (raw)
On 2.4.17, I can't make -j bzImage without OOM kicking in. Relatively
light .config here - bzImage compiles to less than 1mb.
Seems with 1 gb of RAM and swap, the box should be able to handle this
(box is dual P3 600 btw).
Is this unreasonable? How much RAM should it take to accomplish this???
-Phil Oester
next reply other threads:[~2002-01-04 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 20:32 Phil Oester [this message]
2002-01-04 21:02 ` 1gb RAM + 1gb SWAP + make -j bzImage = OOM 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
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='004b01c1955e$ecbc9190$6400a8c0@philxp' \
--to=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.