Something is seriously wrong with that OOM killer.
do you know you don't have to operate in OOM-slaughter mode?"vm.overcommit_memory = 2" in your /etc/sysctl.conf puts you into a mode where the kernel tracks your "committed" memory needs, and will eventually cause some allocations to fail.
this is often much nicer than the default random OOM slaughter.(you probably also need to adjust vm.overcommit_ratio with some knowlege of your MemTotal and SwapTotal.)
regards, mark hahn. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
- From: Justin Piszcz <[email protected]>
- Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
- From: Pavel Machek <[email protected]>
- Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
- From: Justin Piszcz <[email protected]>
- Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
- From: Justin Piszcz <[email protected]>
- Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
- From: Pavel Machek <[email protected]>
- Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
- From: Justin Piszcz <[email protected]>
- 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
- Prev by Date: Re: [PATCH] Fix apparent typo of "CONFIG_MT_SMP".
- Next by Date: [PATCH] Fix apparent typo "CONFIG_SERIAL_CPM_SMC".
- Previous by thread: Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
- Next by thread: Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
- Index(es):
 |