Lines Matching refs:of

10 - efficiently provide statistics during lifetime of a task and on its exit
23 use of tgid, there is no special treatment for the task that is thread group
31 The response contains statistics for a task (if pid is specified) or the sum of
32 statistics for all tasks of the process (if tgid is specified).
36 one of the cpus in the cpumask, its per-pid statistics are sent to the
43 The latter contains the sum of per-pid stats for all threads in the thread
46 getdelays.c is a simple utility demonstrating usage of the taskstats interface
58 an outline of the current version is given. taskstats.h always overrides the
75 The taskstats payload is one of the following three kinds:
78 a pid/tgid consist of one attribute, of type TASKSTATS_CMD_ATTR_PID/TGID,
82 Commands to register/deregister interest in exit data from a set of cpus
83 consist of one attribute, of type
85 attribute payload. The cpumask is specified as an ascii string of
89 set over time. However, for the sake of efficiency, an explicit deregistration
93 command. The payload is a series of three attributes of type:
104 3. New message sent by kernel whenever a task exits. The payload consists of a
105    series of attributes of the following type:
111 e) TASKSTATS_TYPE_TGID: contains tgid of process to which task belongs
121 of atomicity).
126 When the last task of a process exits, the process level data accumulated also
129 When a user queries to get per-tgid data, the sum of all other live threads in
131 threads of the same thread group.
140 1. Adding more fields to the end of the existing struct taskstats. Backward
142    structure. Userspace will use only the fields of the struct that correspond
148    understand (because it is using an older version of the interface).
151 Choosing between 1. and 2. is a matter of trading off flexibility and
153 path since the kernel and userspace don't need to incur the overhead of
156 unnecessarily receive large structures whose fields are of no interest, then
162 When the rate of task exits becomes large, a listener may not be able to keep
163 up with the kernel's rate of sending per-tid/tgid exit data leading to data
165 extended and the number of cpus grows large.
167 To avoid losing statistics, userspace should do one or more of the following:
172 - create more listeners and reduce the number of cpus being listened to by
174 Users may also consider setting the cpu affinity of the listener to the subset
175 of cpus to which it listens, especially if they are listening to just one cpu.
178 indicated overflow of receive buffers, it should take measures to handle the
179 loss of data.