Re: [RFC] Enabling other oom schemes

[Chris Friesen <cfriesen@nortelnetworks.com>]

Rahul Karnik wrote:
> Rusty Lynch wrote:
> 
>> The patch below uses a notifier list for other components to register
>> to be called when an out of memory condition occurs.
> 
> 
> How does this interact with the overcommit handling? Doesn't strict 
> overcommit also not oom, but rather return a memory allocation error? 
> Could we not add another overcommit mode where oom conditions cause a 
> kernel panic?

If you have real, true strict overcommit, then it can cause you to have 
errors much earlier than expected.

Imagine a process that consumes 51% of memory.  With strict overcommit, 
that process cannot fork() since there is not enough memory.

Chris



-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

--
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:"aart@kvack.org"> aart@kvack.org </a>