Lines Matching refs:and
5 Taskstats is a netlink-based interface for sending per-task and
10 - efficiently provide statistics during lifetime of a task and on its exit
17 "pid", "tid" and "task" are used interchangeably and refer to the standard
21 "tgid", "process" and "thread group" are used interchangeably and refer to the
30 socket (NETLINK_GENERIC family) and sends commands specifying a pid or a tgid.
35 sends a register command and specifies a cpumask. Whenever a task exits on
38 to be limited and assists in flow control over the netlink interface and is
44 group, both past and present.
48 send commands and process responses, listen for per-tid/tgid exit data,
49 write the data received to a file and do basic flow control by increasing
61 struct taskstats is the common accounting structure for both per-pid and
62 per-tgid data. It is versioned and can be extended by each accounting subsystem
63 that is added to the kernel. The fields and their semantics are defined in the
66 The data exchanged between user and kernel space is a netlink message belonging
67 to the NETLINK_GENERIC family and using the netlink attributes interface.
84 TASKSTATS_CMD_ATTR_REGISTER/DEREGISTER_CPUMASK and contain a cpumask in the
102 same structure is used for both per-pid and per-tgid stats.
119 resource management is often done at a process granularity and aggregating task
120 stats in userspace alone is inefficient and potentially inaccurate (due to lack
124 kernel has space and time overheads. To address this, the taskstats code
130 the group is added up and added to the accumulated total for previously exited
145 2. Defining separate statistic structs and using the netlink attributes
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
165 extended and the number of cpus grows large.
172 - create more listeners and reduce the number of cpus being listened to by