SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sched: Only setting CPUSchedulingPriority=rr doesn't work

Browse Source 
A service that only sets the scheduling policy to round-robin
fails to be started. This is because the cpu_sched_priority is
initialized to 0 and is not adjusted when the policy is changed.

Clamp the cpu_sched_priority when the scheduler policy is set. Use
the current policy to validate the new priority.

Change the manual page to state that the given range only applies
to the real-time scheduling policies.

Add a testcase that verifies this change:

$ make test-sched-prio; ./test-sched-prio
[test/sched_idle_bad.service:6] CPU scheduling priority is out of range, ignoring: 1
[test/sched_rr_bad.service:7] CPU scheduling priority is out of range, ignoring: 0
[test/sched_rr_bad.service:8] CPU scheduling priority is out of range, ignoring: 100
This commit is contained in:
Holger Hans Peter Freyther
2012-11-15 16:16:45 +01:00
committed by Zbigniew Jędrzejewski-Szmek
parent 71c0159692
commit bb11271068
10 changed files with 168 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/systemd.exec.xml
+8 -6
View File
@@ -214,13 +214,15 @@
<listitem><para>Sets the CPU
scheduling priority for executed
processes. Takes an integer between 1
(lowest priority) and 99 (highest
priority). The available priority
processes. The available priority
range depends on the selected CPU
scheduling policy (see above). See
<citerefentry><refentrytitle>sched_setscheduler</refentrytitle><manvolnum>2</manvolnum></citerefentry>
for details.</para></listitem>
scheduling policy (see above). For
real-time scheduling policies an
integer between 1 (lowest priority)
and 99 (highest priority) can be used.
See <citerefentry><refentrytitle>sched_setscheduler</refentrytitle><manvolnum>2</manvolnum></citerefentry>
for details.
</para></listitem>
</varlistentry>
<varlistentry>