From: Con Kolivas <kernel@kolivas.org>
To: ck@vds.kolivas.org
Subject: Re: 2.6.15-ck1
Date: Thu, 5 Jan 2006 11:12:51 +1100
User-Agent: KMail/1.9
Cc: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>,
       Arjan van de Ven <arjan@infradead.org>, Dave Jones <davej@redhat.com>,
       linux kernel mailing list <linux-kernel@vger.kernel.org>
References: <200601041200.03593.kernel@kolivas.org> <1136406837.2839.67.camel@laptopd505.fenrus.org> <43BC40B5.90607@gorzow.mm.pl>
In-Reply-To: <43BC40B5.90607@gorzow.mm.pl>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200601051112.52404.kernel@kolivas.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1120
Lines: 26

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.

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