Hi,
On Wed, 15 Feb 2006, Ingo Molnar wrote:
> yeah, agreed. That will be accurately fixed via GTOD's per-hwclock
> resolution values. It will have another advantage as well: e.g. the
> whole of m68k wont be penalized via CONFIG_TIME_LOW_RES for having a
> handful of sub-arches (Apollo, Sun3x, Q40) that dont have a higher
> resolution timer - every clock can define its own resolution. You could
> help that effort by porting m68k to use GTOD ;-)
I'll do that as soon as the perfomance is equal or better than what we
have right now and expensive 64bit math in the fast path, where it's
provably a waste, is not exactly encouraging. I already provided all the
math and code to keep it cheap and (relatively) simple, but I don't have
the time to work constantly on it, so if you'd help to integrate it into
John's work it would go a lot faster.
bye, Roman
-
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
