From: Larry Woodman <lwoodman@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>,
"Frédéric 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, riel@redhat.com, rostedt@goodmis.org
Subject: Re: [Patch] mm tracepoints update
Date: Wed, 22 Apr 2009 08:07:17 -0400 [thread overview]
Message-ID: <1240402037.4682.3.camel@dhcp47-138.lab.bos.redhat.com> (raw)
In-Reply-To: <20090422095727.GG18226@elte.hu>
On Wed, 2009-04-22 at 11:57 +0200, Ingo Molnar wrote:
> * KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>
> > > I've cleaned up the mm tracepoints to track page allocation and
> > > freeing, various types of pagefaults and unmaps, and critical
> > > page reclamation routines. This is useful for debugging memory
> > > allocation issues and system performance problems under heavy
> > > memory loads.
> >
> > In past thread, Andrew pointed out bare page tracer isn't useful.
>
> (do you have a link to that mail?)
>
> > Can you make good consumer?
I will work up some good examples of what these are useful for. I use
the mm tracepoint data in the debugfs trace buffer to locate customer
performance problems associated with memory allocation, deallocation,
paging and swapping frequently, especially on large systems.
Larry
>
> These MM tracepoints would be automatically seen by the
> ftrace-analyzer GUI tool for example:
>
> git://git.kernel.org/pub/scm/utils/kernel/ftrace/ftrace.git
>
> And could also be seen by other tools such as kmemtrace. Beyond, of
> course, embedding in function tracer output.
>
> Here's the list of advantages of the types of tracepoints Larry is
> proposing:
>
> - zero-copy and per-cpu splice() based tracing
> - binary tracing without printf overhead
> - structured logging records exposed under /debug/tracing/events
> - trace events embedded in function tracer output and other plugins
> - user-defined, per tracepoint filter expressions
>
> I think the main review question is: are they properly structured
> and do they expose essential information to analyze behavioral
> details of the kernel in this area?
>
> Ingo
>
> --
> 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>
--
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-04-22 12:11 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 [this message]
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
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=1240402037.4682.3.camel@dhcp47-138.lab.bos.redhat.com \
--to=lwoodman@redhat.com \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).