* Cyril Hrubis <chrubis@xxxxxxx> wrote: > - Describe explicitly that sched_rt_runtime_us is allocated from > sched_rt_period_us and hence always less or equal to that value. Just some spelling nits: > - The limit for sched_rt_runtime_us is not INT_MAX - 1 but rather it's > limited by the value of sched_rt_period_us. If sched_rt_period_us is > INT_MAX then sched_rt_runtime_us can be set to INT_MAX as well. s/is not INT_MAX - 1 but rather it's /is not INT_MAX-1, but rather it's > /proc/sys/kernel/sched_rt_runtime_us: > - A global limit on how much time realtime scheduling may use. Even without > - CONFIG_RT_GROUP_SCHED enabled, this will limit time reserved to realtime > - processes. With CONFIG_RT_GROUP_SCHED it signifies the total bandwidth > - available to all realtime groups. > + A global limit on how much time realtime scheduling may use. This is always s/realtime /real-time > + less or equal than the period_us as it denotes the time allocated from the s/than the period_us as it denotes /than the period_us, as it denotes > + period_us for the realtime tasks. Even without CONFIG_RT_GROUP_SCHED enabled, > + this will limit time reserved to realtime processes. With s/realtime /real-time > + CONFIG_RT_GROUP_SCHED it signifies the total bandwidth available to all s/CONFIG_RT_GROUP_SCHED /CONFIG_RT_GROUP_SCHED=y > + realtime groups. s/realtime /real-time Thanks, Ingo
