From: David Rientjes <rientjes@google.com>
To: Frantisek Hrbata <fhrbata@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
CAI Qian <caiqian@redhat.com>,
lwoodman@redhat.com
Subject: Re: [PATCH] oom: add uid to "Killed process" message
Date: Mon, 20 Jun 2011 14:09:19 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1106201409090.2639@chino.kir.corp.google.com> (raw)
In-Reply-To: <1308567876-23581-1-git-send-email-fhrbata@redhat.com>
On Mon, 20 Jun 2011, Frantisek Hrbata wrote:
> Add user id to the oom killer's "Killed process" message, so the user of the
> killed process can be identified.
>
Notified in what way? Unless you are using the memory controller, there's
no userspace notification that an oom event has happened so nothing would
know to scrape the kernel log for this information.
We've had a long-time desire for an oom notifier, not only at the time of
oom but when approaching it with configurable thresholds, that would
wakeup a userspace daemon that might be polling on notifier. That seems
more useful for realtime notification of an oom event rather than relying
on the kernel log?
--
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-06-20 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 11:04 Frantisek Hrbata
2011-06-20 21:09 ` David Rientjes [this message]
2011-06-21 11:36 ` Frantisek Hrbata
2011-06-21 19:07 ` David Rientjes
-- strict thread matches above, loose matches on Subject: below --
2011-06-20 10:16 Frantisek Hrbata
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.1106201409090.2639@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=caiqian@redhat.com \
--cc=fhrbata@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.com \
--cc=minchan.kim@gmail.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