Re: Misleading OOM messages

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Dave Hansen
Date: Friday, May 15, 2009 - 11:22 am

On Fri, 2009-05-15 at 13:59 -0400, Christoph Lameter wrote:

There is, but it gets overridden anyway since there are users that
"need" tons of mlock() space.  We also shouldn't be allowing things to
get into crazy configurations.  Having a max dirty ratio doesn't even
have an effect when you can dirty all unlocked memory several times over
and still not be hitting the max dirty mark.

Perhaps we should ensure that total RAM mlock()ed + vm_dirty_bytes is
always under total ram.  That'll force people to either stop mlocking or
do the safe thing which is drop vm_dirty_bytes.  

-- Dave

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Misleading OOM messages, Christoph Lameter, (Tue May 12, 2:14 pm)
Re: [patch 02/11 -mmotm] lowmemorykiller: Don't count free ..., =?ISO-8859-1?Q?Arve_ ..., (Tue May 12, 5:27 pm)
Re: [patch 01/11 -mmotm] lowmemorykiller: Only iterate ove ..., =?ISO-8859-1?Q?Arve_ ..., (Tue May 12, 5:43 pm)
Re: Misleading OOM messages, Pavel Machek, (Thu May 14, 2:29 am)
Re: Misleading OOM messages, Christoph Lameter, (Thu May 14, 12:46 pm)
Re: Misleading OOM messages, Dave Hansen, (Thu May 14, 1:38 pm)
Re: Misleading OOM messages, Christoph Lameter, (Thu May 14, 1:49 pm)
Re: Misleading OOM messages, David Rientjes, (Thu May 14, 1:49 pm)
Re: Misleading OOM messages, Pavel Machek, (Thu May 14, 1:56 pm)
Re: Misleading OOM messages, Dave Hansen, (Thu May 14, 2:05 pm)
Re: Misleading OOM messages, David Rientjes, (Thu May 14, 2:12 pm)
Re: Misleading OOM messages, Christoph Lameter, (Thu May 14, 2:30 pm)
Re: Misleading OOM messages, Pavel Machek, (Thu May 14, 2:34 pm)
Re: Misleading OOM messages, Dave Hansen, (Thu May 14, 2:37 pm)
Re: Misleading OOM messages, Dave Hansen, (Thu May 14, 2:41 pm)
Re: Misleading OOM messages, David Rientjes, (Thu May 14, 3:00 pm)
Re: [patch 02/11 -mmotm] lowmemorykiller: Don't count free ..., =?ISO-8859-1?Q?Arve_ ..., (Thu May 14, 4:25 pm)
Re: Misleading OOM messages, Pavel Machek, (Fri May 15, 6:05 am)
Re: Misleading OOM messages, Christoph Lameter, (Fri May 15, 10:57 am)
Re: Misleading OOM messages, Christoph Lameter, (Fri May 15, 10:58 am)
Re: Misleading OOM messages, Christoph Lameter, (Fri May 15, 10:59 am)
Re: Misleading OOM messages, Dave Hansen, (Fri May 15, 11:15 am)
Re: Misleading OOM messages, Balbir Singh, (Fri May 15, 11:19 am)
Re: Misleading OOM messages, Dave Hansen, (Fri May 15, 11:22 am)
Re: Misleading OOM messages, Dave Hansen, (Fri May 15, 11:23 am)
Re: Misleading OOM messages, Balbir Singh, (Fri May 15, 11:57 am)
Re: Misleading OOM messages, Christoph Lameter, (Fri May 15, 12:26 pm)
Re: Misleading OOM messages, Christoph Lameter, (Fri May 15, 12:29 pm)
Re: Misleading OOM messages, David Rientjes, (Fri May 15, 12:37 pm)
Re: Misleading OOM messages, Pavel Machek, (Fri May 15, 1:02 pm)
Re: Misleading OOM messages, Balbir Singh, (Fri May 15, 1:31 pm)
Re: Misleading OOM messages, Christoph Lameter, (Fri May 15, 2:15 pm)
Re: Misleading OOM messages, Christoph Lameter, (Mon May 18, 7:34 am)
Re: Misleading OOM messages, Balbir Singh, (Mon May 18, 8:45 am)
Re: Misleading OOM messages, Pavel Machek, (Tue May 19, 1:39 pm)
Re: Misleading OOM messages, Christoph Lameter, (Fri May 22, 6:53 am)
Warn when we run out of swap space (was Re: Misleading OOM ..., Christoph Lameter, (Fri May 22, 7:17 am)
Re: Misleading OOM messages, Christoph Lameter, (Fri May 22, 12:01 pm)
Re: Misleading OOM messages, Randy Dunlap, (Fri May 22, 12:40 pm)
Re: Misleading OOM messages, Christoph Lameter, (Fri May 22, 12:44 pm)
Re: Misleading OOM messages, Alan Cox, (Fri May 22, 2:43 pm)
Re: Misleading OOM messages, Alan Cox, (Fri May 22, 2:45 pm)