[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090423092933.F6E9.A69D9226@jp.fujitsu.com>
Date: Thu, 23 Apr 2009 09:48:04 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Larry Woodman <lwoodman@...hat.com>
Cc: kosaki.motohiro@...fujitsu.com, Ingo Molnar <mingo@...e.hu>,
Fr馘駻ic Weisbecker
<fweisbec@...il.com>, Li Zefan <lizf@...fujitsu.com>,
Pekka Enberg <penberg@...helsinki.fi>,
eduard.munteanu@...ux360.ro, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, riel@...hat.com, rostedt@...dmis.org
Subject: Re: [Patch] mm tracepoints update - use case.
> On Wed, 2009-04-22 at 08:07 -0400, Larry Woodman wrote:
> > On Wed, 2009-04-22 at 11:57 +0200, Ingo Molnar wrote:
> > > * KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
>
> > > > 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
>
> Attached is an example of what the mm tracepoints can be used for:
I have some comment.
1. Yes, current zone_reclaim have strange behavior. I plan to fix
some bug-like bahavior.
2. your scenario only use the information of "zone_reclaim called".
function tracer already provide it.
3. but yes, you are going to proper direction. we definitely need
some fine grained tracepoint in this area. we are welcome to you.
but in my personal feeling, your tracepoint have worthless argument
a lot. we need more good information.
I think I can help you in this area. I hope to work together.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists