From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mike Galbraith <efault@gmx.de>
Cc: Clark Williams <williams@redhat.com>,
"g.medini" <g.medini@eurosoft.it>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: High latency of a system based on 5.19 rt
Date: Mon, 2 Oct 2023 16:16:11 +0200 [thread overview]
Message-ID: <20231002141611.f1H8qyiR@linutronix.de> (raw)
In-Reply-To: <8586b9812dccc6248e0518efaf973c4467324b70.camel@gmx.de>
On 2023-10-02 13:58:57 [+0200], Mike Galbraith wrote:
> > Why not perform all wakes from hardirq then?
>
> Sounds good to me iff we're talking about a dinky irq width delta.
>
> Threads bundling up what are otherwise irq context cycles is loaded
> with goodness, but static priority leaves you holding a bill and paying
> context switch fees on top. Pick your poison carefully applies I
> suppose. A tiny swig of hemlock can't do _too_ much harm, right ;-)
A swarm of wake-ups for SCHED_OTHER at prio 50+ will delay your threaded
interrupt handler and everything else that runs 50 and lower.
Since SCHED_OTHER is less important than any RT task, the delay is
usually of lower concern.
> -Mike
Sebastian
next prev parent reply other threads:[~2023-10-02 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 16:30 High latency of a system based on 5.19 rt g.medini
2023-09-25 17:02 ` Ralf Mardorf
2023-09-26 7:04 ` Mike Galbraith
2023-09-26 12:34 ` Clark Williams
[not found] ` <CAMLffL8=zW0Bv47R=r3=Lh9==OjDrM=FTJZgmm6PYGOyTedeBA@mail.gmail.com>
2023-09-26 13:15 ` Mike Galbraith
2023-10-02 10:05 ` Sebastian Andrzej Siewior
2023-10-02 11:58 ` Mike Galbraith
2023-10-02 14:16 ` Sebastian Andrzej Siewior [this message]
2023-10-02 15:20 ` Mike Galbraith
2023-10-02 10:02 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2023-10-03 13:47 g.medini
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=20231002141611.f1H8qyiR@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=efault@gmx.de \
--cc=g.medini@eurosoft.it \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.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 NNTP newsgroup(s).