Re: 2.6.15-ck1

From: Dave Jones
Date: Wed Jan 04 2006 - 20:13:11 EST


On Thu, Jan 05, 2006 at 11:49:17AM +1100, Con Kolivas wrote:
> On Thursday 05 January 2006 11:27, Dave Jones wrote:
> > On Thu, Jan 05, 2006 at 11:12:51AM +1100, Con Kolivas wrote:
> > > On Thursday 05 January 2006 08:40, Radoslaw Szkodzinski wrote:
> > > > Arjan van de Ven wrote:
> > > > > On Wed, 2006-01-04 at 14:57 -0500, Dave Jones wrote:
> > > > >
> > > > > sounds like we need some sort of profiler or benchmarker or at least
> > > > > a tool that helps finding out which timers are regularly firing,
> > > > > with the aim at either grouping them or trying to reduce their
> > > > > disturbance in some form.
> > > >
> > > > You mean something like a modification to timer debugging patch to
> > > > record the last time the timer fired, right?
> > > > Timertop could then detect the pattern and provide frequency, standard
> > > > deviation and other statistical data.
> > > > It would be much more expensive to test of course.
> > >
> > > I don't think the timer debugging patch needs to give out any more info.
> > > The userspace tool should be able to do this with the amount of info the
> > > timer debugging patch is giving already.
> >
> > In the absense of a pointer to a userspace tool, I found the following
> > handy. (It also fixes a bug where it was printing garbage as process
> > names).
>
> Timertop and pmstats are here:
> http://ck.kolivas.org/patches/dyn-ticks/

me no likee. it's very pretty, but it feels awkward to drive.
Even after I'd stopped it dancing long enough to read, its
output format seemed odd.

With the diff I did, I just piped it through sort -n -k2 | tail
to see the interesting parts.

Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/