Re: [Patch 1/4] Delay accounting: Initialization

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andrew Morton wrote:
> Shailabh Nagar <[email protected]> wrote:
> 
>>+	*ts = sched_clock();
> 
> 
> I'm not sure that it's kosher to use sched_clock() for fine-grained
> timestamping like this.  Ingo had issues with it last time this happened?  
> 
> <too lazy to read all the code> Do you normalise these numbers in some
> manner before presenting them to userspace?  If so, by what means?

The cpu delay data collected by schedstats (which is jiffies based)
is normalized to nanosecs. The timestamps based on sched_clock() are exported
as is. As Marcelo pointed out, thats not good enough since sched_clock() itself
could return jiffie-based resolution.  So some normalization will be needed for
that data as well.



-
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]
  Powered by Linux