Re: [-rt] time-related problems with CPU frequency scaling

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

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

---

• References:
  • [-rt] time-related problems with CPU frequency scaling
    • From: Wolfgang Hoffmann <[email protected]>
  • Re: [-rt] time-related problems with CPU frequency scaling
    • From: Lee Revell <[email protected]>
  • Re: [-rt] time-related problems with CPU frequency scaling
    • From: Wolfgang Hoffmann <[email protected]>

• Prev by Date: Re: 2.6.16.1 & D state processes
• Next by Date: Re: Linux 2.6.16.7
• Previous by thread: Re: [-rt] time-related problems with CPU frequency scaling
• Next by thread: Re: [-rt] time-related problems with CPU frequency scaling
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]