If multipathd doesn't become a real time process, it was scheduled as a
normal process, without any priority increase. Bump up the CPUWeight so
that even as a normal process, it will still run with increased
priority.
If multipathd did become a real time process, it set itself to the
highest priority, which is excessive. A priority of 10 is plenty.
Signed-off-by: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
---
Notes:
v2: Lowered LimitRTPRIO as suggested by Martin Wilck.
multipathd/multipathd.service.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/multipathd/multipathd.service.in b/multipathd/multipathd.service.in
index 18bb367e..a63ddd9a 100644
--- a/multipathd/multipathd.service.in
+++ b/multipathd/multipathd.service.in
@@ -19,7 +19,8 @@ NotifyAccess=main
ExecStart=/sbin/multipathd -d -s
ExecReload=/sbin/multipathd reconfigure
TasksMax=infinity
-LimitRTPRIO=infinity
+LimitRTPRIO=10
+CPUWeight=1000
[Install]
WantedBy=sysinit.target
--
2.43.0
