On Fri, 2005-08-26 at 08:39 -0700, Christoph Lameter wrote:
> I think a priority is something useful for the interpolators. Some of
> the decisions about which time sources to use also have criteria different
> from drift/latency/jitter/cpu. F.e. timers may not survive various
> power-saving configurations. Thus I would think that we need a priority
> plus some flags.
>
> Some of the criteria for choosing a time source may be:
Hi Christoph,
I sent another followup to this thread with a patch containing a
fairly crude algorithm that I think better explains my starting point.
I'm sure the weighting and scaling factors need work, but I think many
of the criteria you describe will favor the right clock.
> 1. If a system boots up with a single cpu then there is no question that
> the ITC/TSC should be used because of the fast access.
I'm hoping the jitter/cpu and latency calculation will always end up
favoring the cycle counter in the scenario.
> 2. If the BIOS is capable of perfect ITC/TSC synchronization then use
> the ITC/TSC. However, this is typically restricted to SMP configs and
> there is an issue on IA64 that the PAL can indicate a nodrift
> configuration but Linux is not capable of perfects sync on bootup.
If we're setting the jitter flag appropriately, which I think we are,
then the low latency of the ITC and lack of jitter penalty should do the
right thing here.
> 3. If a memory mapped global clock is available then make sure to
> first use a distributed timer over a centralized time source because
> distributed timer have fast local access even under contention.
> I.e. use Altix RTC over HPET/Cyclone.
>
> 4. Use any memory mapped global clock source
Scaling the latency to the average across a NUMA system will
automatically order these correctly. They will definitely have higher
latency than the ITC, so should fall about here on the list. It's easy
to make the Altix RTC have no node association and therefore not
penalize the access latency further.
> 5. Abuse some other system component for time keeping (PIT, i/o devices
> etc)
>
> The criteria for drift/latency can only be established after we gone
> through the above. The low-power stuff adds additional complexity.
>
> We may need to dynamically change timer interpolators / time sources if
> the power situation changes. Nothing like that exists today for time
> interpolators since they are mostly used in server configurations.
Yes, I don't know how to handle low power situations other than have
a flag on the interpolators and a hook to switch to the best low power
timer when the need arises. We may need to use the same hook to
re-evaluate the timer when a CPU hotplug occurs. This way we could
dynamically fall back to case 1 above if most of the CPUs are removed
(and likewise move to an hpet if CPUs are added).
I was looking into the suggestion to use logarithms to try to
normalize some of the factors such that weighting is more logical.
Hopefully that won't explode the complexity. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |