On Wed, 3 Aug 2005, Alex Williamson wrote:
> be a reasonable performance vs absolute accuracy trade-off. What
> happens to your worst case time if you (just for a test) hard code a
> min_delta of something around 20-50? There could be some kind of
Think about a threaded process that gets time on multiple processors
and then compares the times. This means that the time value obtained later
on one thread may indicate a time earlier than that obtained on another
thread. An essential requirement for time values is that they are
monotonically increasing. You are changing that basic nature.
> boot/run time tunable to set this min_delta if there's no good way to
> calculate it. It should be trivial to add something like this to the
> fsys path as well and shouldn't disrupt the nojitter path at all.
I assure you it is not going to be trivial. IA64 asm instructions bundling
and cycle optimization will have to be changed.
-
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]
| |
 |