public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Andi Kleen <ak@suse.de>
Cc: Arjan van de Ven <arjan@infradead.org>,
	ck list <ck@vds.kolivas.org>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	vojtech@suse.cz
Subject: Re: 2.6.15-ck1
Date: Thu, 5 Jan 2006 12:36:04 +1100	[thread overview]
Message-ID: <200601051236.04988.kernel@kolivas.org> (raw)
In-Reply-To: <p73y81vxyci.fsf@verdi.suse.de>

On Thu, 5 Jan 2006 12:22 pm, Andi Kleen wrote:
> Arjan van de Ven <arjan@infradead.org> writes:
> > 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.
>
> I did one some time ago for my own noidletick patch. Can probably dig
> it out again. It just profiled which timers interrupted idle.
>
> Executive summary for my laptop: worst was the keyboard driver (it ran
> some polling driver to work around some hardware bug, but fired very
> often) , followed by the KDE desktop (should be mostly
> fixed now, I complained) and the X server and some random kernel
> drivers.
>
> I haven't checked recently if keyboard has been fixed by now.

I checked with Vojtech some time ago and he said we could change the polling 
from HZ/20 to about HZ/5 which I have included in the rolled up dynticks 
patch already. Not that 20 HZ is very frequent, but anything that splits up 
timer intervals potentially by 20 more adds up.

Cheers,
Con

  reply	other threads:[~2006-01-05  1:36 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04  1:00 2.6.15-ck1 Con Kolivas
2006-01-04 19:05 ` 2.6.15-ck1 Dave Jones
2006-01-04 19:57   ` 2.6.15-ck1 Dave Jones
2006-01-04 20:33     ` 2.6.15-ck1 Arjan van de Ven
2006-01-04 21:22       ` 2.6.15-ck1 Dave Jones
2006-01-04 21:40       ` [ck] 2.6.15-ck1 Radoslaw Szkodzinski
2006-01-05  0:12         ` 2.6.15-ck1 Con Kolivas
2006-01-05  0:27           ` 2.6.15-ck1 Dave Jones
2006-01-05  0:49             ` 2.6.15-ck1 Con Kolivas
2006-01-05  1:14               ` 2.6.15-ck1 Dave Jones
2006-01-05  1:22       ` 2.6.15-ck1 Andi Kleen
2006-01-05  1:36         ` Con Kolivas [this message]
2006-01-05  6:04         ` 2.6.15-ck1 Dave Jones
2006-01-05  6:42         ` 2.6.15-ck1 Vojtech Pavlik
2006-01-05  6:55           ` [ck] 2.6.15-ck1 Con Kolivas
2006-01-05 15:19           ` 2.6.15-ck1 Andi Kleen
2006-01-05 16:30             ` 2.6.15-ck1 Vojtech Pavlik
2006-01-05 16:39               ` 2.6.15-ck1 Andi Kleen
2006-01-05 17:13                 ` 2.6.15-ck1 Dmitry Torokhov
2006-01-05 17:28                   ` 2.6.15-ck1 Andi Kleen
2006-01-05  1:50       ` 2.6.15-ck1 Tony Lindgren
2006-01-04 23:10     ` 2.6.15-ck1 Con Kolivas
2006-01-05  1:57       ` 2.6.15-ck1 Tony Lindgren
2006-01-05 18:47       ` [ck] 2.6.15-ck1 Kevin Radloff
2006-01-12 18:51         ` Daniel Petrini
2006-01-04 20:38   ` 2.6.15-ck1 Grant Coady
2006-01-04 20:56     ` 2.6.15-ck1 Dave Jones
2006-01-12 22:11   ` 2.6.15-ck1 Adam Belay
2006-01-12 23:03     ` 2.6.15-ck1 Dave Jones
2006-01-13  0:42       ` 2.6.15-ck1 Adam Belay
2006-01-13  0:46         ` 2.6.15-ck1 Dave Jones
2006-01-16 20:28       ` 2.6.15-ck1 Ben Slusky
2006-01-14  3:42   ` 2.6.15-ck1 Philipp Rumpf
2006-01-14  4:41     ` 2.6.15-ck1 Dave Jones
2006-01-14 13:06       ` [ck] 2.6.15-ck1 Jens Axboe
2006-01-05 17:58 ` 2.6.15-ck1 Tomasz Torcz
2006-01-05 23:22   ` 2.6.15-ck1 Con Kolivas
2006-01-07 13:16     ` 2.6.15-ck1 Tomasz Torcz
     [not found]       ` <9268368b0601131119n639c345cgcf2a5dadd7cb423c@mail.gmail.com>
2006-01-14 20:54         ` 2.6.15-ck1 Tomasz Torcz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200601051236.04988.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ak@suse.de \
    --cc=arjan@infradead.org \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox