how stable are the BogoMIPS and the udelay functions on "dynamic clock speed change cpus"

because udelay work on the principle that it know "how much work the
cpu can do in a time" and it work by just doing a loop of nothing, how
stable is it when the cpu clock rate is keep changing all the time?
does it update its loops_per_jiffy varible each time the cpu clock is change?
or does it have another solution to this problem?
or since before the cpu enter to this udelay function it must do some
work like entering the systemcall and so on , the cpu clock rate is
jump to the original?
-
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/

---

• Follow-Ups:
  • Re: how stable are the BogoMIPS and the udelay functions on "dynamic clock speed change cpus"
    • From: Andi Kleen <[email protected]>

• Prev by Date: XFS write speed drop
• Next by Date: Re: [PATCH] sched: fix interactive ceiling code
• Previous by thread: XFS write speed drop
• Next by thread: Re: how stable are the BogoMIPS and the udelay functions on "dynamic clock speed change cpus"
• 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]