ProcessKit API Reference
ResourceLimitCapabilities Type
What this host can enforce, per `ResourceLimits` dimension. **These answer for the HOST, not for the mechanism the snapshot's options happen to select.** On Linux, asking for a whole-tree cap is itself what selects the cgroup v2 mechanism, so reporting "unsupported" for a limit-free options set would understate what the host can do — the honest question each member answers is "if this cap were added to the options, could this host enforce it?". `Creation` and `Mechanism` are the members that answer for the options as they stand.
Instance members
| Instance member |
Description
|
|
`ResourceLimits.WithCpuAffinity` — pinning the tree to a set of cores.
|
|
`ResourceLimits.WithCpuQuota` — a fraction-of-a-core CPU ceiling for the tree.
|
|
`ResourceLimits.WithCpuTimeMax` — consumed CPU time. The deliberate POSIX exception: it needs no whole-tree container, because POSIX applies it per spawned child through `RLIMIT_CPU`.
|
|
`ResourceLimits.WithIoMax` — directional disk I/O ceilings for one device or volume.
|
|
`ProcessGroup.UpdateLimits` — replacing the caps on a LIVE group without recreating it or restarting its children.
|
|
`ResourceLimits.WithMaxProcesses` — a cap on the number of live processes in the tree.
|
|
`ResourceLimits.WithMemoryMax` — a whole-tree memory ceiling.
|
|
`ResourceLimits.WithOomGroupKill` — a cgroup v2-only policy that makes an OOM kill take the whole tree instead of one selected victim.
|
|
`ResourceLimits.WithUiRestrictions` — the Windows Job Object desktop-session restrictions (clipboard, desktops, display/system parameters, exit-Windows).
|