From: Peter Zijlstra <peterz@infradead.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, rientjes@google.com,
dchinner@redhat.com
Subject: Re: [PATCH v4] oom: add tracepoints for oom_score_adj
Date: Tue, 4 Feb 2014 09:39:19 +0100 [thread overview]
Message-ID: <20140204083918.GA31442@dyad.arnhem.chello.nl> (raw)
In-Reply-To: <20111208153230.9c68eab3.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, Dec 08, 2011 at 03:32:30PM +0900, KAMEZAWA Hiroyuki wrote:
> From 5dc1f8c879ae424d5853af255df8860494209e39 Mon Sep 17 00:00:00 2001
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> Date: Wed, 7 Dec 2011 09:58:16 +0900
> Subject: [PATCH] oom: trace point for oom_score_adj
>
> oom_score_adj is set to prevent a task from being killed by OOM-Killer.
> Some daemons sets this value and their children inerit it sometimes.
> Because inheritance of oom_score_adj is done automatically, users
> can be confused at seeing the value and finds it's hard to debug.
>
> This patch adds trace point for oom_score_adj. This adds 3 trace
> points. at
> - update oom_score_adj
> - fork()
> - rename task->comm(typically, exec())
>
And nobody was bothered by the fact that we already had fork and exec tracepoints?
--
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>
next prev parent reply other threads:[~2014-02-04 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 0:54 [PATCH] " KAMEZAWA Hiroyuki
2011-12-07 1:22 ` David Rientjes
2011-12-07 1:27 ` KAMEZAWA Hiroyuki
2011-12-07 1:55 ` [PATCH v3] " KAMEZAWA Hiroyuki
2011-12-07 16:52 ` [PATCH] " KOSAKI Motohiro
2011-12-08 1:47 ` KAMEZAWA Hiroyuki
2011-12-08 6:32 ` [PATCH v4] " KAMEZAWA Hiroyuki
2014-02-04 8:39 ` Peter Zijlstra [this message]
2011-12-08 17:33 ` [PATCH] " KOSAKI Motohiro
2011-12-08 23:41 ` KAMEZAWA Hiroyuki
2011-12-09 0:33 ` KAMEZAWA Hiroyuki
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=20140204083918.GA31442@dyad.arnhem.chello.nl \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dchinner@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=rientjes@google.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