From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, rientjes@google.com,
dchinner@redhat.com
Subject: Re: [PATCH] oom: add tracepoints for oom_score_adj
Date: Thu, 8 Dec 2011 10:47:05 +0900 [thread overview]
Message-ID: <20111208104705.b2e50039.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <4EDF99B2.6040007@jp.fujitsu.com>
On Wed, 07 Dec 2011 11:52:02 -0500
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> On 12/6/2011 7:54 PM, KAMEZAWA Hiroyuki wrote:
> >>From 28189e4622fd97324893a0b234183f64472a54d6 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())
>
> I don't think they have oom specific thing. Can you please add generic fork and
> task rename tracepoint instead?
>
I think it makes oom-targeted debug difficult.
This tracehook using task->signal->oom_score_adj as filter.
This reduces traces much and makes debugging easier.
If you need another trace point for other purpose, another trace point
should be better. For generic purpose, oom_socre_adj filtering will not
be necessary.
> >
> > Outputs will be following.
> > bash-2404 [006] 199.620841: oom_score_adj_update: task 2404[bash] updates oom_score_ad j=-1000
>
> "task 2404[bash]" don't look good to me.
>
> In almost case, we use either
>
> - [pid] comm
> - pid:comm
> - comm:pid
> - comm-pid (ftrace specific)
>
> Why do we need to introduce alternative printing style?
>
No reason. ok, I'll fix.
Thanks,
-Kame
--
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-12-08 1:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 0:54 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 [this message]
2011-12-08 6:32 ` [PATCH v4] " KAMEZAWA Hiroyuki
2014-02-04 8:39 ` Peter Zijlstra
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=20111208104705.b2e50039.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dchinner@redhat.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