[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] Enabling other oom schemes

To: rusty@linux.co.intel.com
Subject: Re: [RFC] Enabling other oom schemes
From: Rahul Karnik <rahul@genebrew.com>
Date: Fri, 12 Sep 2003 00:18:26 -0400
CC: riel@conectiva.com.br, linux-mm@kvack.org,linux-kernel@vger.kernel.org
Fake-Sender: owner-linux-mm@kvack.org
In-Reply-To: <200309120219.h8C2JANc004514@penguin.co.intel.com>
Original-Recipient: rfc822;linux-mm-archive@humbolt.geo.uu.nl
References: <200309120219.h8C2JANc004514@penguin.co.intel.com>
Sender: Rik van Riel <riel@nl.linux.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030908 Thunderbird/0.2

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?

Thanks,
Rahul

--
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>

Follow-Ups:
- Re: [RFC] Enabling other oom schemes
  - From: Chris Friesen <cfriesen@nortelnetworks.com>
- Re: [RFC] Enabling other oom schemes
  - From: Robert Love <rml@tech9.net>

References:
- [RFC] Enabling other oom schemes
  - From: Rusty Lynch <rusty@penguin.co.intel.com>

Prev by Date: Re: [RFC] Enabling other oom schemes
Next by Date: Re: [RFC] Enabling other oom schemes
Prev by thread: [RFC] Enabling other oom schemes
Next by thread: Re: [RFC] Enabling other oom schemes
Index(es):
- Date
- Thread