From: David Rientjes <rientjes@google.com>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Pavel Ivanov <paivanof@gmail.com>,
Mahmood Naderan <nt_mahmood@yahoo.com>,
Randy Dunlap <rdunlap@xenotime.net>,
"\"linux-kernel@vger.kernel.org\"" <linux-kernel@vger.kernel.org>,
"\"linux-mm@kvack.org\"" <linux-mm@kvack.org>
Subject: Re: running of out memory => kernel crash
Date: Fri, 19 Aug 2011 12:21:08 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1108191219400.20477@chino.kir.corp.google.com> (raw)
In-Reply-To: <201108190025.27444.vda.linux@googlemail.com>
On Fri, 19 Aug 2011, Denys Vlasenko wrote:
> Exactly. Server has no means to know when the situation is
> bad enough to start killing. IIRC now the rule is simple:
> OOM killing starts only when allocations fail.
>
> Perhaps it is possible to add "start OOM killing if less than N free
> pages are available", but this will be complex, and won't be good enough
> for some configs with many zones (thus, will require even more complications).
>
Allocations start to fail, and oom killings then start to occur, only when
the set of allowed zones fall below their minimum watermarks which usually
includes several hundred kilobytes or several megabytes of free memory for
lowmem situations.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-19 19:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1312872786.70934.YahooMailNeo@web111712.mail.gq1.yahoo.com>
2011-08-09 7:06 ` Randy Dunlap
[not found] ` <1312874259.89770.YahooMailNeo@web111704.mail.gq1.yahoo.com>
2011-08-09 16:03 ` David Rientjes
2011-08-10 8:14 ` Mahmood Naderan
2011-08-11 4:09 ` David Rientjes
2011-08-11 7:07 ` Mahmood Naderan
2011-08-11 7:13 ` David Rientjes
2011-08-11 8:02 ` Mahmood Naderan
2011-08-11 12:47 ` Denys Vlasenko
2011-08-11 15:13 ` Mahmood Naderan
2011-08-11 17:38 ` Denys Vlasenko
2011-08-17 8:50 ` Mahmood Naderan
2011-08-18 2:18 ` Pavel Ivanov
2011-08-18 12:44 ` Denys Vlasenko
2011-08-18 14:26 ` Pavel Ivanov
2011-08-18 22:25 ` Denys Vlasenko
2011-08-19 19:21 ` David Rientjes [this message]
2011-08-19 19:29 ` Bryan Donlan
2011-08-19 21:19 ` Chris Friesen
2011-08-19 21:38 ` Alan Cox
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=alpine.DEB.2.00.1108191219400.20477@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nt_mahmood@yahoo.com \
--cc=paivanof@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=vda.linux@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox