mirror of
https://github.com/containers/podman.git
synced 2025-09-28 17:25:31 +08:00
c9c2f644da
In each options/foo.md, keep a list of where the option is used. This will be valuable to anyone making future edits, and to those reviewing those edits. This may be a controversial commit, because those crossref lists are autogenerated as a side effect of the script that reads them. It definitely violates POLA. And one day, some kind person will reconcile (e.g.) --label, using it in more man pages, and maybe forget to git-commit the rewritten file, and CI will fail. I think this is a tough tradeoff, but worth doing. Without this, it's much too easy for someone to change an option file in a way that renders it inapplicable/misleading for some podman commands. Signed-off-by: Ed Santiago <santiago@redhat.com>
15 lines
745 B
Markdown
15 lines
745 B
Markdown
####> This option file is used in:
|
|
####> podman container clone, create, run, update
|
|
####> If you edit this file, make sure your changes
|
|
####> are applicable to all of those.
|
|
#### **--cpu-rt-runtime**=*microseconds*
|
|
|
|
Limit the CPU real-time runtime in microseconds.
|
|
|
|
Limit the containers Real Time CPU usage. This option tells the kernel to limit the amount of time in a given CPU period Real Time tasks may consume. Ex:
|
|
Period of 1,000,000us and Runtime of 950,000us means that this container could consume 95% of available CPU and leave the remaining 5% to normal priority tasks.
|
|
|
|
The sum of all runtimes across containers cannot exceed the amount allotted to the parent cgroup.
|
|
|
|
This option is only supported on cgroups V1 rootful systems.
|