Searched full:tid (Results 1 – 18 of 18) sorted by relevance
| /Documentation/netlink/specs/ |
| D | binder.yaml | 33 name: from-tid
35 doc: The TID of the sender thread.
43 name: to-tid
46 The TID of the recipient thread. This attribute may not be present
82 - from-tid
84 - to-tid
|
| /Documentation/locking/ |
| D | pi-futex.rst | 80 normal futex-based locks: a 0 value means unlocked, and a value==TID
91 TID fails], then FUTEX_LOCK_PI is called. The kernel does all the
94 own TID into the futex value], and attaches a 'PI state' structure to
100 futex value to its own TID and returns. Userspace has no other work to
102 FUTEX_WAITERS|TID.
105 TID -> 0 atomic transition of the futex value], then no kernel work is
|
| D | robust-futex-ABI.rst | 64 word' holds 2 flag bits in the upper 2 bits, and the thread id (TID)
131 TID in the lower 30 bits of the 'lock word'.
144 3) add the lock entry, with its thread id (TID) in the bottom 30 bits
160 exiting threads TID, then the kernel will do two things:
183 current threads TID in the lower 30 bits, it does nothing with that
|
| D | robust-futexes.rst | 199 Otherwise, robust futexes are acquired by glibc by putting the TID into
204 and the remaining bits are for the TID.
|
| /Documentation/driver-api/surface_aggregator/ |
| D | ssh.rst | 15 .. |TID| replace:: ``TID`` substdef
223 * - |TID|
290 (``TID``) and source ID (``SID``). These two fields indicate where a message
292 (``TID``). Note that a response to a specific request therefore has the source
301 ``TID=1``, for example, may not be accepted for ``TID=2`` and vice versa. While
|
| /Documentation/bpf/ |
| D | bpf_iterators.rst | 315 process. Similarly, ``linfo.task.tid`` directs the kernel to create an iterator
317 ``linfo.task.tid`` is different from ``linfo.task.pid`` only if the thread has a
329 If both *tid* and *pid* are zero, an iterator created from this struct
420 the tid of tasks, or it will receive every opened file in the system (in the
473 Here, using *tid* makes no difference from using *pid*.
481 iterator with *tid* parameter to include only the tasks that match the given
482 *tid*.
|
| /Documentation/accounting/ |
| D | taskstats.rst | 18 "pid", "tid" and "task" are used interchangeably and refer to the standard
49 send commands and process responses, listen for per-tid/tgid exit data,
164 up with the kernel's rate of sending per-tid/tgid exit data leading to data
|
| /Documentation/trace/coresight/ |
| D | coresight-perf.rst | 26 …ERF_RECORD_AUXTRACE size: 0x11dd0 offset: 0 ref: 0x1b614fc1061b0ad1 idx: 0 tid: 531230 cpu: -1
99 CoreSight / Thread Loop 10 Threads - Check TID
|
| /Documentation/translations/zh_CN/accounting/ |
| D | taskstats.rst | 23 “pid”、“tid”、“任务”互换使用，用于描述由struct task_struct定义的标准
|
| /Documentation/networking/ |
| D | l2tp.rst | 287 mnl_attr_put_u32(nlh, L2TP_ATTR_CONN_ID, tid);
307 mnl_attr_put_u32(nlh, L2TP_ATTR_CONN_ID, tid);
331 mnl_attr_put_u32(nlh, L2TP_ATTR_CONN_ID, tid);
349 mnl_attr_put_u32(nlh, L2TP_ATTR_CONN_ID, tid);
|
| /Documentation/filesystems/ext4/ |
| D | journal.rst | 653 - Stores the TID of the transaction after which these fast commits should
686 - Stores the TID of the commit, CRC of the fast commit of which this tag
|
| /Documentation/translations/zh_CN/arch/loongarch/ |
| D | introduction.rst | 125 0x40 定时器编号 TID
|
| /Documentation/translations/zh_TW/arch/loongarch/ |
| D | introduction.rst | 125 0x40 定時器編號 TID
|
| /Documentation/filesystems/ |
| D | proc.rst | 43 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
44 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1937 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1946 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1949 of a task pointed by <pid>/<tid> pair. The format is a space separated
1953 not be listed here; one needs to read /proc/<children-pid>/task/<tid>/children
|
| /Documentation/arch/loongarch/ |
| D | introduction.rst | 132 0x40 Timer Identifier TID
|
| /Documentation/fault-injection/ |
| D | fault-injection.rst | 236 /proc/self/task/<tid>/fail-nth:
|
| /Documentation/admin-guide/ |
| D | cgroup-v2.rst | 901 same TID may show up more than once if the thread got moved to
902 another cgroup and then back or the TID got recycled while
905 A TID can be written to migrate the thread associated with the
906 TID to the cgroup. The writer should match all of the
|
| /Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 166 %i tid
167 %I global tid (init PID namespace)
|