From: Lee Revell <rlrevell@joe-job.com>
To: woho@woho.de
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [-rt] time-related problems with CPU frequency scaling
Date: Tue, 18 Apr 2006 02:32:27 -0400 [thread overview]
Message-ID: <1145341947.23853.3.camel@mindpipe> (raw)
In-Reply-To: <200604180811.13110.woho@woho.de>
On Tue, 2006-04-18 at 08:11 +0200, Wolfgang Hoffmann wrote:
> So I misunderstood preempt_max_latency. I thought it to be absolute
> time, but it actually is codepath cycles, translated to microseconds
> using the current CPU frequency. Thanks for clarifying.
They are one and the same. At 800Mhz the same code patch causes twice
the latency.
Lee
next prev parent reply other threads:[~2006-04-18 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-16 18:41 [-rt] time-related problems with CPU frequency scaling Wolfgang Hoffmann
2006-04-17 22:35 ` Lee Revell
2006-04-18 6:11 ` Wolfgang Hoffmann
2006-04-18 6:32 ` Lee Revell [this message]
2006-04-20 18:39 ` Wolfgang Hoffmann
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=1145341947.23853.3.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=woho@woho.de \
/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