From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Longhaul - Need timer tick
Date: Mon, 05 Mar 2007 23:42:56 +0100 [thread overview]
Message-ID: <45EC9CF0.7@interia.pl> (raw)
In-Reply-To: <45E89FAA.7050008@interia.pl>
> There is no support for dynamic ticks in Longhaul.
> Current code is assuming that timer tick is present and
> constant.
Please ignore this patch. Somehow NO_HZ option don't change
anything. Average tick frequency is reduced to 20% for me
(uptime / interrupt 0 count), but somehow when Longhaul
is changing CPU frequency it is always equal to value set
by "Timer frequency" option. Probably this is how NO_HZ
author want it to work. Anyway, tested (with help of ACPI
PM timer) and even if help for this option may sound scary
for me, there is no change in transition latency. At least
on my system.
Sorry
Rafa³
----------------------------------------------------------------------
Oficjalne konto pocztowe europejskich internautow!
>>> http://link.interia.pl/f19e8
prev parent reply other threads:[~2007-03-05 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 22:05 [PATCH] Longhaul - Need timer tick Rafał Bilski
2007-03-05 22:42 ` Rafał Bilski [this message]
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=45EC9CF0.7@interia.pl \
--to=rafalbilski@interia.pl \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
/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.