From: Andi Kleen <andi@firstfloor.org>
To: Aaron Sowry <aaron@cendio.se>
Cc: linux-kernel@vger.kernel.org, Pierre Ossman <ossman@cendio.se>
Subject: Re: Help decoding oom-killer output
Date: Wed, 08 Sep 2010 15:30:17 +0200 [thread overview]
Message-ID: <87r5h4wefq.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4C8744D1.1010405@cendio.se> (Aaron Sowry's message of "Wed, 08 Sep 2010 10:09:53 +0200")
Aaron Sowry <aaron@cendio.se> writes:
> After running in to problems with the amount of vmalloc memory on a SLED
> 11 SP1 system (due to a large number of ncp mounts), we have increased
> this with the kernel parameter 'vmalloc=512M'.
This means the 32bit kernel has only about 400MB low mem virtual
address space left, large parts of it being used by the mem_map
arrays. So whole kernel has to run in 100-200MB or so which
is likely not enough.
>
> Since this change, oom-killer seems to think we are running out of
> memory,
Yes you will run out of address space all the time for kernel
operations.
Real fix is to use 64bit instead. 32bit is so 90ies.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-09-08 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 8:09 Help decoding oom-killer output Aaron Sowry
2010-09-08 8:54 ` Aaron Sowry
2010-09-08 13:30 ` Andi Kleen [this message]
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=87r5h4wefq.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=aaron@cendio.se \
--cc=linux-kernel@vger.kernel.org \
--cc=ossman@cendio.se \
/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.