From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <martin.wilck@suse.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
device-mapper development <dm-devel@lists.linux.dev>
Subject: Re: [PATCH] multipathd: Set CPUWeight to 1000
Date: Mon, 15 Apr 2024 16:26:38 -0400 [thread overview]
Message-ID: <Zh2NfqoNHCWg6-Tw@bmarzins-01.fast.eng.rdu2.dc.redhat.com> (raw)
In-Reply-To: <7959de14debd4e414e40de89a6267f587de14bb9.camel@suse.com>
On Mon, Apr 15, 2024 at 08:18:08PM +0200, Martin Wilck wrote:
> On Mon, 2024-04-15 at 14:06 -0400, Benjamin Marzinski wrote:
> > 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.
> >
> > Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> > ---
> > multipathd/multipathd.service.in | 1 +
> > 1 file changed, 1 insertion(+)
>
> Reviewed-by: Martin Wilck <mwilck@suse.com>
>
> But let's also decrease the default value for LimitRTPRIO.
Sure.
>
> Martin
>
>
> >
> > diff --git a/multipathd/multipathd.service.in
> > b/multipathd/multipathd.service.in
> > index 18bb367e..1b3fccd2 100644
> > --- a/multipathd/multipathd.service.in
> > +++ b/multipathd/multipathd.service.in
> > @@ -20,6 +20,7 @@ ExecStart=/sbin/multipathd -d -s
> > ExecReload=/sbin/multipathd reconfigure
> > TasksMax=infinity
> > LimitRTPRIO=infinity
> > +CPUWeight=1000
> >
> > [Install]
> > WantedBy=sysinit.target
prev parent reply other threads:[~2024-04-15 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 18:06 [PATCH] multipathd: Set CPUWeight to 1000 Benjamin Marzinski
2024-04-15 18:18 ` Martin Wilck
2024-04-15 20:26 ` Benjamin Marzinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zh2NfqoNHCWg6-Tw@bmarzins-01.fast.eng.rdu2.dc.redhat.com \
--to=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=martin.wilck@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).