From: Dave Hansen <dave@linux.vnet.ibm.com>
To: paul.szabo@sydney.edu.au
Cc: linux-mm@kvack.org, 695182@bugs.debian.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Reproducible OOM with partial workaround
Date: Thu, 10 Jan 2013 15:12:17 -0800 [thread overview]
Message-ID: <50EF4AD1.4060807@linux.vnet.ibm.com> (raw)
In-Reply-To: <201301102158.r0ALwI4i031014@como.maths.usyd.edu.au>
On 01/10/2013 01:58 PM, paul.szabo@sydney.edu.au wrote:
> I developed a workaround patch for this particular OOM demo, dropping
> filesystem caches when about to exhaust lowmem. However, subsequently
> I observed OOM when running many processes (as yet I do not have an
> easy-to-reproduce demo of this); so as I suspected, the essence of the
> problem is not with FS caches.
>
> Could you please help in finding the cause of this OOM bug?
As was mentioned in the bug, your 32GB of physical memory only ends up
giving ~900MB of low memory to the kernel. Of that, around 600MB is
used for "mem_map[]", leaving only about 300MB available to the kernel
for *ALL* of its allocations at runtime.
Your configuration has never worked. This isn't a regression, it's
simply something that we know never worked in Linux and it's a very hard
problem to solve. One Linux vendor (at least) went to a huge amount of
trouble to develop, ship, and supported a kernel that supported large
32-bit machines, but it was never merged upstream and work stopped on it
when such machines became rare beasts:
http://lwn.net/Articles/39925/
I believe just about any Linux vendor would call your configuration
"unsupported". Just because the kernel can boot does not mean that we
expect it to work.
It's possible that some tweaks of the vm knobs (like lowmem_reserve)
could help you here. But, really, you don't want to run a 32-bit kernel
on such a large machine. Very, very few folks are running 32-bit
kernels on these systems and you're likely to keep running in to bugs
because this is such a rare configuration.
We've been very careful to ensure that 64-bit kernels shoul basically be
drop-in replacements for 32-bit ones. You can keep userspace 100%
32-bit, and just have a 64-bit kernel.
If you're really set on staying 32-bit, I might have a NUMA-Q I can give
you. ;)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-10 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 21:58 [RFC] Reproducible OOM with partial workaround paul.szabo
2013-01-10 23:12 ` Dave Hansen [this message]
2013-01-11 0:46 ` paul.szabo
2013-01-11 1:26 ` Dave Hansen
2013-01-11 1:46 ` paul.szabo
2013-01-11 8:01 ` Andrew Morton
2013-01-11 8:30 ` Simon Jeons
2013-01-11 11:51 ` paul.szabo
2013-01-11 20:31 ` Andrew Morton
2013-01-12 3:24 ` paul.szabo
2013-01-11 16:04 ` Dave Hansen
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=50EF4AD1.4060807@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=695182@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul.szabo@sydney.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).