History

sched/deadline: Clarify nanoseconds in uapi

Specify the time values of the deadline parameters of deadline, runtime, and period as being in nanoseconds explicitly as they always have been.

Christian Loehle committed 2 years ago

Commit 6ebf2d01 parent 8bee4ca1 file · +3 −3Browse files

Showing the changes to include/uapi (1 of 1 file). Show all

Unified · Split

include/uapi/linux/sched/types.h+3−3
@@ -58,9 +58,9 @@ · 57 unmodified lines
5858 *
5959 * This is reflected by the following fields of the sched_attr structure:
6060 *
61− * @sched_deadline representative of the task's deadline
62− * @sched_runtime representative of the task's runtime
63− * @sched_period representative of the task's period
61+ * @sched_deadline representative of the task's deadline in nanoseconds
62+ * @sched_runtime representative of the task's runtime in nanoseconds
63+ * @sched_period representative of the task's period in nanoseconds
6464 *
6565 * Given this task model, there are a multiplicity of scheduling algorithms
6666 * and policies, that can be used to ensure all the tasks will make their