Lines Matching refs:its

21 Each process occupies a *role* in its coalition: one process is tagged as the `COALITION_TASKROLE_L…
47 Each thread, task, and resource coalition has its own separate ledger. Thread ledgers currently *on…
49 …herefore the `cpu_time` in the task's ledger is always equal to the sum of its threads, plus that …
61 …ouble count if a task dies while we iterate. Nothing stops a task updating its own ledger while we…
91 When `launchd` receives the message, it 'adopts' the voucher which binds the bank to its thread (se…
97 A *bank task* is an object that provides linkage between a task and its associated *bank accounts*.…
99 Each task is essentially 1-1 with a `bank_task`. However, a `bank_task` may outlive its associated …
103 * The 'bank merchant' (returning to the previous example, this would be `launchd`) has its `*billed…
104 * The 'bank holder' (this would be the other task) has its `*billed_to_me` task ledger entry increm…
126 This is designed to encapsulate 'an app and all its subprocesses'. For example, App extensions are …
130 …-core capable process will be allowed to use P-cores. This could have been its own coalition type …