From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Larry Woodman <lwoodman@redhat.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
fweisbec@gmail.com, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [Patch] mm tracepoints
Date: Fri, 6 Mar 2009 12:04:23 +0100 [thread overview]
Message-ID: <20090306110423.GD21168@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.0903052124240.14535@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Fri, 6 Mar 2009, KOSAKI Motohiro wrote:
>
> > > I've implemented several 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:
> > >
> > > # tracer: mm
> > > #
> > > # TASK-PID CPU# TIMESTAMP FUNCTION
> > > # | | | | |
> > > pdflush-624 [004] 184.293169: wb_kupdate:
> > > (mm_pdflush_kupdate) count=3e48
> > > pdflush-624 [004] 184.293439: get_page_from_freelist:
> > > (mm_page_allocation) pfn=447c27 zone_free=1940910
> > > events/6-33 [006] 184.962879: free_hot_cold_page:
> > > (mm_page_free) pfn=44bba9
> > > irqbalance-8313 [001] 188.042951: unmap_vmas:
> > > (mm_anon_userfree) mm=ffff88044a7300c0 address=7f9a2eb70000 pfn=24c29a
> > > cat-9122 [005] 191.141173: filemap_fault:
> > > (mm_filemap_fault) primary fault: mm=ffff88024c9d8f40 address=3cea2dd000
> > > pfn=44d68e
> > > cat-9122 [001] 191.143036: handle_mm_fault:
> > > (mm_anon_fault) mm=ffff88024c8beb40 address=7fffbde99f94 pfn=24ce22
> > > ...
> >
> > Hi Larry,
> >
> > I've started to evaluate your patch.
> >
> > firstly, this patch can't apply tip/master.
yeah, would be nice to have a patch against:
http://people.redhat.com/mingo/tip.git/README
> > secondly, I don't think the address of mm_struct and pfn
> > help to analysis. administrator don't know the page is which
> > file's cache.
>
> The mm_struct may not be helpful since there should be a 1 to
> 1 mapping between user tasks and the mm struct. Hmm, maybe
> not, due to threads?
Correct - so the mm ID looks useful.
> But the pfn is helpful since it is a unique identifier for
> what physical page was mapped.
Yeah. Nevertheless some sort of filename:offset indicator would
be nice too. (as an add-on)
Ingo
next prev parent reply other threads:[~2009-03-06 11:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 15:38 marching through all physical memory in software Chris Friesen
2009-01-26 15:59 ` Arjan van de Ven
2009-01-27 18:29 ` Chris Friesen
2009-01-27 20:16 ` Eric W. Biederman
2009-01-28 19:38 ` Pavel Machek
2009-01-30 9:05 ` Nigel Cunningham
2009-01-30 9:13 ` Pavel Machek
2009-01-30 13:00 ` Nigel Cunningham
2009-03-05 22:16 ` [Patch] mm tracepoints Larry Woodman
2009-03-06 2:11 ` KOSAKI Motohiro
2009-03-06 2:26 ` Steven Rostedt
2009-03-06 11:04 ` Ingo Molnar [this message]
2009-03-06 12:33 ` Larry Woodman
2009-03-06 13:55 ` Ingo Molnar
2009-03-06 16:57 ` Larry Woodman
2009-03-06 17:10 ` Ingo Molnar
2009-03-06 17:38 ` Peter Zijlstra
2009-03-06 17:46 ` Ingo Molnar
2009-03-06 17:56 ` Peter Zijlstra
2009-03-06 18:01 ` Ingo Molnar
2009-03-06 18:20 ` Peter Zijlstra
2009-03-06 18:24 ` Ingo Molnar
2009-03-06 20:01 ` Larry Woodman
2009-03-06 19:06 ` Larry Woodman
2009-03-06 21:53 ` Chris Friesen
2009-03-06 19:22 ` Larry Woodman
2009-03-25 18:09 ` Latest mm tracepoints patch merged to your tip tree Larry Woodman
2009-03-06 21:16 ` [Patch] mm tracepoints Andrew Morton
2009-02-06 9:00 ` marching through all physical memory in software Andi Kleen
2009-02-07 3:03 ` Henrique de Moraes Holschuh
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=20090306110423.GD21168@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=peterz@infradead.org \
--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