Andrew Morton wrote:
Martin Peschke <[email protected]> wrote:
need sched_clock for latency statistics
sched_clock() probably isn't suitable for this application. It's a
scheduler thing and has a number of accuracy problems.
But I thought we discussed this last time around? Maybe not.
I have been too obsessed with the other issues to remember.
> Maybe you've considered sched_clock()'s drawbacks and you've decided
> they're all acceptable.
Admittedly, I didn't, but merely believed the comment above the function.
http://marc.theaimsgroup.com/?l=linux-kernel&m=114657675408686&w=2
sheds some light.
I would be happy to exploit an API that may result from that discussion.
I would plead for exporting such an API to modules. I don't see how
to implement statistics for latencies, otherwise.
Any other hints on how to replace my sched_clock() calls are welcome.
(I want to measure elapsed times in units that are understandable to
users without hardware manuals and calculator, such as milliseconds.)
Martin
-
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]
