On Mon 5.May'08 at 16:58:08 -0700, Daniel Walker wrote:
Ok, but they take the frequency as the input while the "natural" variable
we have is the period, because that's what we get from the hardware (at
least for the HPET, if I understood it correctly).
If I want to use clocksource_hz2mult then I have
to do one more operation (to find the frequency) before calling it (and
that's what the other part of the patch which you didn't quote is
actually doing).
So the savings in my patch is due to using the period directly, and
not the frequency. That's what my idea was, so if you object then
my attempt was a failure and should be forgotten :-)
Or maybe I should create a clocksource_period2mult to replace
clocksource_hz2mult and save the extra operation in more places too?
--