aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/accounting/delay-accounting.txt
diff options
context:
space:
mode:
authorShailabh Nagar <nagar@watson.ibm.com>2006-07-14 03:24:42 -0400
committerLinus Torvalds <torvalds@g5.osdl.org>2006-07-15 00:53:57 -0400
commita3baf649ca9ca0a96fba538f03b0f17c043b755c (patch)
tree6022cb01cd494f59dd474030f2d9980413000036 /Documentation/accounting/delay-accounting.txt
parent6f44993fe1d7b2b097f6ac60cd5835c6f5ca0874 (diff)
[PATCH] per-task-delay-accounting: documentation
Some documentation for delay accounting. Signed-off-by: Shailabh Nagar <nagar@watson.ibm.com> Signed-off-by: Balbir Singh <balbir@in.ibm.com> Cc: Jes Sorensen <jes@sgi.com> Cc: Peter Chubb <peterc@gelato.unsw.edu.au> Cc: Erich Focht <efocht@ess.nec.de> Cc: Levent Serinol <lserinol@gmail.com> Cc: Jay Lan <jlan@engr.sgi.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/accounting/delay-accounting.txt')
-rw-r--r--Documentation/accounting/delay-accounting.txt115
1 files changed, 115 insertions, 0 deletions
diff --git a/Documentation/accounting/delay-accounting.txt b/Documentation/accounting/delay-accounting.txt
new file mode 100644
index 000000000000..f3dc0ca04fa4
--- /dev/null
+++ b/Documentation/accounting/delay-accounting.txt
@@ -0,0 +1,115 @@
1Delay accounting
2----------------
3
4Tasks encounter delays in execution when they wait
5for some kernel resource to become available e.g. a
6runnable task may wait for a free CPU to run on.
7
8The per-task delay accounting functionality measures
9the delays experienced by a task while
10
11a) waiting for a CPU (while being runnable)
12b) completion of synchronous block I/O initiated by the task
13c) swapping in pages
14
15and makes these statistics available to userspace through
16the taskstats interface.
17
18Such delays provide feedback for setting a task's cpu priority,
19io priority and rss limit values appropriately. Long delays for
20important tasks could be a trigger for raising its corresponding priority.
21
22The functionality, through its use of the taskstats interface, also provides
23delay statistics aggregated for all tasks (or threads) belonging to a
24thread group (corresponding to a traditional Unix process). This is a commonly
25needed aggregation that is more efficiently done by the kernel.
26
27Userspace utilities, particularly resource management applications, can also
28aggregate delay statistics into arbitrary groups. To enable this, delay
29statistics of a task are available both during its lifetime as well as on its
30exit, ensuring continuous and complete monitoring can be done.
31
32
33Interface
34---------
35
36Delay accounting uses the taskstats interface which is described
37in detail in a separate document in this directory. Taskstats returns a
38generic data structure to userspace corresponding to per-pid and per-tgid
39statistics. The delay accounting functionality populates specific fields of
40this structure. See
41 include/linux/taskstats.h
42for a description of the fields pertaining to delay accounting.
43It will generally be in the form of counters returning the cumulative
44delay seen for cpu, sync block I/O, swapin etc.
45
46Taking the difference of two successive readings of a given
47counter (say cpu_delay_total) for a task will give the delay
48experienced by the task waiting for the corresponding resource
49in that interval.
50
51When a task exits, records containing the per-task and per-process statistics
52are sent to userspace without requiring a command. More details are given in
53the taskstats interface description.
54
55The getdelays.c userspace utility in this directory allows simple commands to
56be run and the corresponding delay statistics to be displayed. It also serves
57as an example of using the taskstats interface.
58
59Usage
60-----
61
62Compile the kernel with
63 CONFIG_TASK_DELAY_ACCT=y
64 CONFIG_TASKSTATS=y
65
66Enable the accounting at boot time by adding
67the following to the kernel boot options
68 delayacct
69
70and after the system has booted up, use a utility
71similar to getdelays.c to access the delays
72seen by a given task or a task group (tgid).
73The utility also allows a given command to be
74executed and the corresponding delays to be
75seen.
76
77General format of the getdelays command
78
79getdelays [-t tgid] [-p pid] [-c cmd...]
80
81
82Get delays, since system boot, for pid 10
83# ./getdelays -p 10
84(output similar to next case)
85
86Get sum of delays, since system boot, for all pids with tgid 5
87# ./getdelays -t 5
88
89
90CPU count real total virtual total delay total
91 7876 92005750 100000000 24001500
92IO count delay total
93 0 0
94MEM count delay total
95 0 0
96
97Get delays seen in executing a given simple command
98# ./getdelays -c ls /
99
100bin data1 data3 data5 dev home media opt root srv sys usr
101boot data2 data4 data6 etc lib mnt proc sbin subdomain tmp var
102
103
104CPU count real total virtual total delay total
105 6 4000250 4000000 0
106IO count delay total
107 0 0
108MEM count delay total
109 0 0
110
111
112
113
114
115