On 01/10/2013 01:58 PM, paul.szabo@xxxxxxxxxxxxx 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@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>