From: Con Kolivas <kernel@kolivas.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
ck list <ck@vds.kolivas.org>, Tony Lindgren <tony@atomide.com>,
Adam Belay <abelay@novell.com>,
Daniel Petrini <d.pensator@gmail.com>,
vatsa@in.ibm.com
Subject: Re: fix cpufreq-ondemand by accounting skipped ticks as idle ticks [Was: [PATCH] i386 no idle HZ aka Dynticks 051203]
Date: Mon, 5 Dec 2005 13:02:57 +1100 [thread overview]
Message-ID: <200512051302.58583.kernel@kolivas.org> (raw)
In-Reply-To: <20051204122434.GB9503@dominikbrodowski.de>
On Sunday 04 December 2005 23:24, Dominik Brodowski wrote:
> Account ticks skipped dynamically as idle ticks.
>
> This allows the ondemand cpufreq governor to work correctly with dyntick.
Dominik one thing I noticed a while back was that ondemand also polls at a
frequency that creates a timer at around 140 HZ. Tweaking the ondemand/
tunables and making it poll ten times less frequently made a big difference
to this (obviously) but did obviously slow down the scaling speed - this was
the frequency required to bring it to that of the background timers (<=20HZ).
I see scope for this polling to be dynamic too :D
Cheers,
Con
next prev parent reply other threads:[~2005-12-05 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 6:37 [PATCH] i386 no idle HZ aka Dynticks 051203 Con Kolivas
2005-12-04 12:24 ` fix cpufreq-ondemand by accounting skipped ticks as idle ticks [Was: [PATCH] i386 no idle HZ aka Dynticks 051203] Dominik Brodowski
2005-12-04 12:32 ` Con Kolivas
2005-12-05 2:02 ` Con Kolivas [this message]
2005-12-04 12:32 ` Account time spent in C-States " Dominik Brodowski
2005-12-04 12:55 ` busmaster and " Dominik Brodowski
[not found] ` <200512041737.07996.kernel-S9WDWIYMKk5AfugRpC6u6w@public.gmane.org>
2005-12-04 13:01 ` C-State policy and dynticks " Dominik Brodowski
2005-12-04 13:01 ` Dominik Brodowski
2005-12-04 14:33 ` Dyntick effectiveness " Dominik Brodowski
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=200512051302.58583.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=abelay@novell.com \
--cc=ck@vds.kolivas.org \
--cc=d.pensator@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=tony@atomide.com \
--cc=vatsa@in.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.