From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Rik van Riel <riel@redhat.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
"Larry Woodman" <lwoodman@redhat.com>,
"Ingo Molnar" <mingo@elte.hu>,
"Fr馘駻ic Weisbecker" <fweisbec@gmail.com>,
"Li Zefan" <lizf@cn.fujitsu.com>,
"Pekka Enberg" <penberg@cs.helsinki.fi>,
eduard.munteanu@linux360.ro, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, rostedt@goodmis.org
Subject: Re: [Patch] mm tracepoints update - use case.
Date: Mon, 22 Jun 2009 12:37:10 +0900 (JST) [thread overview]
Message-ID: <20090622122755.21F6.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <4A3A9844.8030004@redhat.com>
> Larry Woodman wrote:
>
> >> - Please don't display mm and/or another kernel raw pointer.
> >> if we assume non stop system, we can't use kernel-dump. Thus kernel pointer
> >> logging is not so useful.
> >
> > OK, I just dont know how valuable the trace output is with out some raw
> > data like the mm_struct.
>
> I believe that we do want something like the mm_struct in
> the trace info, so we can figure out which process was
> allocating pages, etc...
Yes.
I think we need to print tgid, it is needed to imporove CONFIG_MM_OWNER.
current CONFIG_MM_OWNER back-pointer point to semi-random task_struct.
> >> - Please consider how do this feature works on mem-cgroup.
> >> (IOW, please don't ignore many "if (scanning_global_lru())")
>
> Good point, we want to trace cgroup vs non-cgroup reclaims,
> too.
thank you.
>
> >> - tracepoint caller shouldn't have any assumption of displaying representation.
> >> e.g.
> >> wrong) trace_mm_pagereclaim_pgout(mapping, page->index<<PAGE_SHIFT, PageAnon(page));
> >> good) trace_mm_pagereclaim_pgout(mapping, page)
> >
> > OK.
> >
> >> that's general and good callback and/or hook manner.
>
> How do we figure those out from the page pointer at the time
> the tracepoint triggers?
>
> I believe that it would be useful to export that info in the
> trace point, since we cannot expect the userspace trace tool
> to figure out these things from the struct page address.
>
> Or did I overlook something here?
current, TRACE_EVENT have two step information trasformation.
- step1 - TP_fast_assign()
it is called from tracepoint directly. it makes ring-buffer representaion.
- step2 - TP_printk
it is called when reading debug/tracing/trace file. it makes printable
representation from ring-buffer data.
example:
trace_sched_switch() has three argument, rq, prev, next.
--------------------------------------------------
static inline void
context_switch(struct rq *rq, struct task_struct *prev,
struct task_struct *next)
{
(snip)
trace_sched_switch(rq, prev, next);
-------------------------------------------------
TP_fast_assing extract data from argument pointer.
-----------------------------------------------------
TP_fast_assign(
memcpy(__entry->next_comm, next->comm, TASK_COMM_LEN);
__entry->prev_pid = prev->pid;
__entry->prev_prio = prev->prio;
__entry->prev_state = prev->state;
memcpy(__entry->prev_comm, prev->comm, TASK_COMM_LEN);
__entry->next_pid = next->pid;
__entry->next_prio = next->prio;
),
-----------------------------------------------------
I think mm tracepoint can do the same way.
--
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:[~2009-06-22 3:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 22:45 [Patch] mm tracepoints update Larry Woodman
2009-04-22 1:00 ` KOSAKI Motohiro
2009-04-22 9:57 ` Ingo Molnar
2009-04-22 12:07 ` Larry Woodman
2009-04-22 19:22 ` [Patch] mm tracepoints update - use case Larry Woodman
2009-04-23 0:48 ` KOSAKI Motohiro
2009-04-23 4:50 ` Andrew Morton
2009-04-23 8:42 ` Ingo Molnar
2009-04-23 11:47 ` Larry Woodman
2009-04-24 20:48 ` Larry Woodman
2009-06-15 18:26 ` Rik van Riel
2009-06-17 14:07 ` Larry Woodman
2009-06-18 7:57 ` KOSAKI Motohiro
2009-06-18 19:22 ` Larry Woodman
2009-06-18 19:40 ` Rik van Riel
2009-06-22 3:37 ` KOSAKI Motohiro [this message]
2009-06-22 15:04 ` Larry Woodman
2009-06-23 5:52 ` KOSAKI Motohiro
2009-06-22 3:37 ` KOSAKI Motohiro
2009-06-22 15:28 ` Larry Woodman
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=20090622122755.21F6.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=lwoodman@redhat.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
/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