Messages in this thread | | | Subject | Re: [PATCH] Dynamic tick for x86 version 050609-2 | From | Andi Kleen <> | Date | Mon, 13 Jun 2005 19:55:38 +0200 |
| |
Srivatsa Vaddagiri <vatsa@in.ibm.com> writes: > > 2. reprogram_apic_timer seems to reprogram the count-down > APIC timer (APIC_TMICT) with an integral number of apic_timer_val. > How accurate will this be? Shouldnt this take into account > that we may not be reprogramming the timer on exactly "jiffy" > boundary?
All PIT based reprogramming schemes will lose time.
Only with HPET you can do better (but even there it is difficult to do properly)
> 3. Is there any strong reason why you reprogram timers only when > _all_ CPUs are idle?
There is none imho - my x86-64 no idle tick patch doesn't do it.
Actually there is a small reason - RCU currently does not get updated by a fully idle CPU and can stall other CPUs. But that is in practice not too big an issue yet because so many subsystems cause ticks now and then, so the CPUs tend to wake up often enough to not stall the rest of the system too badly.
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |