From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Rahul Karnik <rahul@genebrew.com>
Cc: rusty@linux.co.intel.com, riel@conectiva.com.br,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Enabling other oom schemes
Date: Fri, 12 Sep 2003 00:31:27 -0400 [thread overview]
Message-ID: <3F614C1F.6010802@nortelnetworks.com> (raw)
In-Reply-To: 3F614912.3090801@genebrew.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
WARNING: multiple messages have this Message-ID (diff)
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Rahul Karnik <rahul@genebrew.com>
Cc: rusty@linux.co.intel.com, riel@conectiva.com.br,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Enabling other oom schemes
Date: Fri, 12 Sep 2003 00:31:27 -0400 [thread overview]
Message-ID: <3F614C1F.6010802@nortelnetworks.com> (raw)
In-Reply-To: 3F614912.3090801@genebrew.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>
next prev parent reply other threads:[~2003-09-12 4:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 2:19 [RFC] Enabling other oom schemes Rusty Lynch
2003-09-12 2:19 ` Rusty Lynch
2003-09-12 4:18 ` Rahul Karnik
2003-09-12 4:18 ` Rahul Karnik
2003-09-12 4:31 ` Chris Friesen [this message]
2003-09-12 4:31 ` Chris Friesen
2003-09-12 4:40 ` Rahul Karnik
2003-09-12 4:40 ` Rahul Karnik
2003-09-12 4:48 ` Robert Love
2003-09-12 4:48 ` Robert Love
2003-09-12 11:18 ` Helge Hafting
2003-09-12 11:18 ` Helge Hafting
2003-09-12 14:07 ` Chris Friesen
2003-09-12 14:07 ` Chris Friesen
2003-09-12 14:30 ` M. Edward Borasky
2003-09-12 4:47 ` Robert Love
2003-09-12 4:47 ` Robert Love
2003-09-12 4:50 ` Robert Love
2003-09-12 10:42 ` Alan Cox
2003-09-12 8:58 ` Tvrtko A. Uršulin
2003-09-13 2:21 ` Rusty Lynch
2003-09-15 10:59 ` Tvrtko A. Uršulin
2003-09-13 17:48 ` Jamie Lokier
2003-09-13 17:48 ` Jamie Lokier
2003-09-13 20:52 ` Robert Love
2003-09-13 20:52 ` Robert Love
2003-09-13 22:04 ` Helge Hafting
2003-09-14 0:55 ` Robert Love
2003-09-14 9:12 ` Helge Hafting
2003-09-14 5:28 ` Chris Friesen
2003-09-14 5:28 ` Chris Friesen
2003-09-15 0:11 ` Mike S
2003-09-15 0:11 ` Mike S
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F614C1F.6010802@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rahul@genebrew.com \
--cc=riel@conectiva.com.br \
--cc=rusty@linux.co.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.