[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0701251921430.30148@p34.internal.lan>
Date: Thu, 25 Jan 2007 19:22:04 -0500 (EST)
From: Justin Piszcz <jpiszcz@...idpixels.com>
To: Mark Hahn <hahn@...aster.ca>
cc: Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org, xfs@....sgi.com
Subject: Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like
2.16.19.2
On Thu, 25 Jan 2007, Mark Hahn wrote:
> > 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-raid" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
# sysctl -a | grep vm.over
vm.overcommit_ratio = 50
vm.overcommit_memory = 0
I'll have to experiment with these options, thanks for the info!
Justin.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists