Lines Matching full:latency

2  * latencytop.c: Latency display infrastructure
14  * CONFIG_LATENCYTOP enables a kernel latency tracking infrastructure that is
15  * used by the "latencytop" userspace tool. The latency that is tracked is not
16  * the 'traditional' interrupt latency (which is primarily caused by something
17  * else consuming CPU), but instead, it is the latency an application encounters
21  * 1) System level latency
22  * 2) Per process latency
24  * The latency is stored in fixed sized data structures in an accumulated form;
25  * if the "same" latency cause is hit twice, this will be tracked as one entry
26  * in the data structure. Both the count, total accumulated latency and maximum
27  * latency are tracked in this data structure. When the fixed size structure is
31  * A latency cause is identified by a stringified backtrace at the point that
33  * identify the cause of the latency in human readable form.
35  * The information is exported via /proc/latency_stats and /proc/<pid>/latency.
38  * Latency Top version : v0.1
42  * |    |    +---------> The maximum latency for this entry in microseconds
43  * |    +--------------> The accumulated latency for this entry (microseconds)
46  * (note: the average latency is the accumulated latency divided by the number
142  * Iterator to store a backtrace into a latency record entry
156  * __account_scheduler_latency - record an occurred latency
157  * @tsk - the task struct of the task hitting the latency
158  * @usecs - the duration of the latency in microseconds
161  * This function is the main entry point for recording latency entries
164  * This function has a few special cases to deal with normal 'non-latency'
241 	seq_puts(m, "Latency Top version : v0.1\n");  in lstats_show()