It's not a great patch, it would need some work to be really clean from
quality point of view, but it does seem to work. With it you can use
to get the actual time your process has used between two points. It
x86 and PPC.
Plus, obviously, this adds significant time to system calls and interrupts.
Chris Friesen wrote:
> Maciej Soltysiak wrote:
>> being inspired by some book about optimizing c++ code i decided to do
>> timing of functions i wrote. I am using gettimeofday to set
>> two timeval structs and calculate the time between them.
>> But the results depend heavily on the load, also i reckon that this
>> is an innacurate timing.
>> Any ideas on timing a function, or a block of code? Maybe some kernel
>> timers or something.
> gettimeofday() is accurate. However, your task may be interrupted by
> other tasks, interrupts, etc.
> Your best bet may be to do many iterations of the routine in question
> and then
> do some statistical analysis of the results.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/