From: Andrea Righi <righiandr@users.sourceforge.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bernd Eckenfels <ecki@lina.inka.de>,
linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 2/2] log out-of-virtual-memory events
Date: Mon, 21 May 2007 12:48:33 +0200 (MEST) [thread overview]
Message-ID: <465178E6.60305@users.sourceforge.net> (raw)
In-Reply-To: <20070520203209.ec952a84.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Sat, 19 May 2007 12:34:01 +0200 (MEST) Andrea Righi <righiandr@users.sourceforge.net> wrote:
>
>> Print informations about userspace processes that fail to allocate new virtual
>> memory.
>
> Why is this useful?
>
Well... in strict overcommit mode (overcommit_memory=2) this is the only way to
track down problems of the (bad-designed) user applications that exit when they
receive a -ENOMEM without logging anything... and, anyway, it could be an
additional aid in figuring out what is going wrong on inside a system. BTW, I
don't think it should be enabled by default, so this is the reason why it should
depend on print_fatal_signals patch.
-Andrea
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-05-21 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Hp5RZ-0001CF-00@calista.eckenfels.net>
2007-05-19 10:34 ` [PATCH 2/2] log out-of-virtual-memory events (was: [RFC] log out-of-virtual-memory events) Andrea Righi
2007-05-21 3:32 ` Andrew Morton
2007-05-21 10:48 ` Andrea Righi [this message]
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=465178E6.60305@users.sourceforge.net \
--to=righiandr@users.sourceforge.net \
--cc=akpm@linux-foundation.org \
--cc=ecki@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).