4 Tasks encounter delays in execution when they wait
5 for some kernel resource to become available e.g. a
6 runnable task may wait for a free CPU to run on.
8 The per-task delay accounting functionality measures
9 the delays experienced by a task while
11 a) waiting for a CPU (while being runnable)
12 b) completion of synchronous block I/O initiated by the task
15 and makes these statistics available to userspace through
16 the taskstats interface.
18 Such delays provide feedback for setting a task's cpu priority,
19 io priority and rss limit values appropriately. Long delays for
20 important tasks could be a trigger for raising its corresponding priority.
22 The functionality, through its use of the taskstats interface, also provides
23 delay statistics aggregated for all tasks (or threads) belonging to a
24 thread group (corresponding to a traditional Unix process). This is a commonly
25 needed aggregation that is more efficiently done by the kernel.
27 Userspace utilities, particularly resource management applications, can also
28 aggregate delay statistics into arbitrary groups. To enable this, delay
29 statistics of a task are available both during its lifetime as well as on its
30 exit, ensuring continuous and complete monitoring can be done.
36 Delay accounting uses the taskstats interface which is described
37 in detail in a separate document in this directory. Taskstats returns a
38 generic data structure to userspace corresponding to per-pid and per-tgid
39 statistics. The delay accounting functionality populates specific fields of
41 include/linux/taskstats.h
42 for a description of the fields pertaining to delay accounting.
43 It will generally be in the form of counters returning the cumulative
44 delay seen for cpu, sync block I/O, swapin etc.
46 Taking the difference of two successive readings of a given
47 counter (say cpu_delay_total) for a task will give the delay
48 experienced by the task waiting for the corresponding resource
51 When a task exits, records containing the per-task and per-process statistics
52 are sent to userspace without requiring a command. More details are given in
53 the taskstats interface description.
55 The getdelays.c userspace utility in this directory allows simple commands to
56 be run and the corresponding delay statistics to be displayed. It also serves
57 as an example of using the taskstats interface.
62 Compile the kernel with
63 CONFIG_TASK_DELAY_ACCT=y
66 Enable the accounting at boot time by adding
67 the following to the kernel boot options
70 and after the system has booted up, use a utility
71 similar to getdelays.c to access the delays
72 seen by a given task or a task group (tgid).
73 The utility also allows a given command to be
74 executed and the corresponding delays to be
77 General format of the getdelays command
79 getdelays [-t tgid] [-p pid] [-c cmd...]
82 Get delays, since system boot, for pid 10
84 (output similar to next case)
86 Get sum of delays, since system boot, for all pids with tgid 5
90 CPU count real total virtual total delay total
91 7876 92005750 100000000 24001500
97 Get delays seen in executing a given simple command
100 bin data1 data3 data5 dev home media opt root srv sys usr
101 boot data2 data4 data6 etc lib mnt proc sbin subdomain tmp var
104 CPU count real total virtual total delay total
108 MEM count delay total