Re: [PATCH v2] multipathd: make multipathd set priority to RLIMIT_RTPRIO

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 10, 2024 at 10:37:38AM +0200, Martin Wilck wrote:
> On Tue, 2024-04-09 at 18:56 -0400, Benjamin Marzinski wrote:
> > With this change, if the SCHED_RT_PRIO compiler flag has been
> > removed.
> > Instead 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.
> > 
> > To keep the existing behavior, multipathd.service now sets
> > LimitRTPRIO=infinity
> > 
> > Signed-off-by: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
> 
> Reviewed-by: Martin Wilck <mwilck@xxxxxxxx>
> 
> I will wait a while for feedback on 
> https://github.com/opensvc/multipath-tools/issues/82
> before pushing it to the queue branch.
> 
> When it's pushed, I'll squash it with 1c4301a ("multipathd: make
> multipathd scheduling configurable"), if you don't mind.

That's fine.

> 
> Thanks,
> Martin





[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux