[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090428110553.GD25347@elte.hu>
Date: Tue, 28 Apr 2009 13:05:53 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Wu Fengguang <fengguang.wu@...el.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Andi Kleen <andi@...stfloor.org>,
Steven Rostedt <rostedt@...dmis.org>,
Fr馘駻ic Weisbecker <fweisbec@...il.com>,
Larry Woodman <lwoodman@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Matt Mackall <mpm@...enic.com>,
Alexey Dobriyan <adobriyan@...il.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH 5/5] proc: export more page flags in /proc/kpageflags
* Wu Fengguang <fengguang.wu@...el.com> wrote:
> > See my other mail i just sent: it would be a natural extension
> > of tracing to also dump all current object state when tracing is
> > turned on. That way no drop_caches is needed at all.
>
> I can understand the merits here - I also did readahead
> tracing/accounting in _one_ piece of code. Very handy.
>
> The readahead traces are now raw printks - converting to the
> ftrace framework would be a big win.
>
> But. It's still not a fit-all solution. Imagine when full data
> _since_ booting is required, but the user cannot afford a reboot.
The above 'get object state' interface (which allows passive
sampling) - integrated into the tracing framework - would serve that
goal, agreed?
Ingo
--
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