On Fri, 2024-03-29 at 14:28 -0400, Benjamin Marzinski wrote: > With this change, if the SCHED_RT_PRIO compiler flag is not set, > multipathd will call getrlimit(RLIMIT_RTPRIO, ...) and look at the > hard > limit. It it's 0, multipath will do nothing. Otherwise it will change > its scheduling policy to SCHED_RR and its priority to the hard limit. > > This allows users to change the priority of that multipathd runs with > by > adding > > LimitRTPRIO=<prio> > > to the [Service] section of the multipathd.service unit file. Setting > LimitRTPRIO=0 will make multipathd run as a normal process, while > setting LimitRTPRIO=infinity will make it use the maximum SCHED_RR > prio, > which is 99. > > Signed-off-by: Benjamin Marzinski <[email protected]>
This looks good to me, but do we really need both the RLIMIT_RTPRIO and the SCHED_RT_PRIO mechanism? Thanks, Martin
