-
Notifications
You must be signed in to change notification settings - Fork 611
spec: add scheduler entity #1188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -291,6 +291,33 @@ For Linux-based systems, the `process` object supports the following process-spe | |
|
|
||
| This is a per-process setting, where as [`disableOOMKiller`](config-linux.md#memory) is scoped for a memory cgroup. | ||
| For more information on how these two settings work together, see [the memory cgroup documentation section 10. OOM Contol][cgroup-v1-memory_2]. | ||
| * **`scheduler`** (object, OPTIONAL) is an object describing the scheduler properties for the process. The `scheduler` contains the following properties: | ||
|
|
||
| * **`policy`** (string, REQUIRED) represents the scheduling policy. A valid list of values is: | ||
|
|
||
| * `SCHED_OTHER` | ||
| * `SCHED_FIFO` | ||
| * `SCHED_RR` | ||
| * `SCHED_BATCH` | ||
| * `SCHED_ISO` | ||
| * `SCHED_IDLE` | ||
| * `SCHED_DEADLINE` | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. SCHED_DEADLINE seems to sometimes return an EBUSY error. Do you want the error numbers to follow these when the set fails? There seems to be some difficulty in using SCHED_DEADLINE with cpuset. can we consider removing SCHED_DEADLINE from support?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think it is required to support it, I am just listing the possible values for now (e.g.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I will leave it up to you to specify about it in the oci-spec, but there are some things that probably cannot be handled. I thought users might expect to be able to use them. |
||
|
|
||
| * **`nice`** (int32, OPTIONAL) is the nice value for the process, affecting its priority. A lower nice value corresponds to a higher priority. If not set, the runtime must use the value 0. | ||
| * **`priority`** (int32, OPTIONAL) represents the static priority of the process, used by real-time policies like SCHED_FIFO and SCHED_RR. If not set, the runtime must use the value 0. | ||
| * **`flags`** (array of strings, OPTIONAL) is an array of strings representing scheduling flags. A valid list of values is: | ||
|
|
||
| * `SCHED_FLAG_RESET_ON_FORK` | ||
| * `SCHED_FLAG_RECLAIM` | ||
| * `SCHED_FLAG_DL_OVERRUN` | ||
| * `SCHED_FLAG_KEEP_POLICY` | ||
| * `SCHED_FLAG_KEEP_PARAMS` | ||
| * `SCHED_FLAG_UTIL_CLAMP_MIN` | ||
| * `SCHED_FLAG_UTIL_CLAMP_MAX` | ||
|
|
||
| * **`runtime`** (uint64, OPTIONAL) represents the amount of time in nanoseconds during which the process is allowed to run in a given period, used by the deadline scheduler. If not set, the runtime must use the value 0. | ||
| * **`deadline`** (uint64, OPTIONAL) represents the absolute deadline for the process to complete its execution, used by the deadline scheduler. If not set, the runtime must use the value 0. | ||
| * **`period`** (uint64, OPTIONAL) represents the length of the period in nanoseconds used for determining the process runtime, used by the deadline scheduler. If not set, the runtime must use the value 0. | ||
| * **`selinuxLabel`** (string, OPTIONAL) specifies the SELinux label for the process. | ||
| For more information about SELinux, see [SELinux documentation][selinux]. | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.