Re: [PATCH 4/4] tracing, page-allocator: Add a postprocessing script for page-allocator-related ftrace events

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

On Tue, 4 Aug 2009 21:57:17 +0200
Ingo Molnar <mingo@elte.hu> wrote:


So?  The fact that certain things can be done doesn't mean that there's
a demand for them, nor that anyone will _use_ this stuff.

As usual, we're adding tracepoints because we feel we must add
tracepoints, not because anyone has a need for the data which they
gather.

There is some benefit in providing MM developers with some code which
they can copy-n-paste for their day-to-day activity.  But as I said,
they can do that with vmstat too.


If we can get rid of vmstat all together (and meminfo) and replace all
that with common infrastructure then that would be a good cleanup.  But
if we end up leaving vmstat and meminfo in place and then adding
_another_ statistic gathering mechanism in parallel then we haven't
cleaned anything up at all - it just gets worse.


I don't really oppose the patches - they're small.  But they seem
rather useless too.

It would be nice to at least partially remove the vmstat/meminfo
infrastructure but I don't think we can do that?
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH 4/4] tracing, page-allocator: Add a postprocess ..., Andrew Morton, (Tue Aug 4, 1:18 pm)
[tip:perfcounters/urgent] perf: &quot;Longum est iter per praec ..., tip-bot for Carlos R ..., (Sat Aug 8, 5:37 am)
[tip:perfcounters/core] perf: &quot;Longum est iter per praecep ..., tip-bot for Carlos R ..., (Sun Aug 9, 4:11 am)