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 12:05:42 +0200 [thread overview]
Message-ID: <20231002100542.59fbxJ0f@linutronix.de> (raw)
In-Reply-To: <8eb75f2118086edf828ac059999fd52b64382576.camel@gmx.de>
On 2023-09-26 15:15:46 [+0200], Mike Galbraith wrote:
> On Tue, 2023-09-26 at 12:30 +0000, Clark Williams wrote:
> > On Tue, Sep 26, 2023 at 7:05 AM Mike Galbraith <efault@gmx.de> wrote:
> > > On Mon, 2023-09-25 at 18:30 +0200, g.medini@eurosoft.it wrote:
> > > > # tracer: wakeup_rt
> > > > #
> > > > # wakeup_rt latency trace v1.1.5 on 5.19.0-rt10
> > > > # --------------------------------------------------------------------
> > > > # latency: 357 us, #401/401, CPU#0 | (M:preempt_rt VP:0, KP:0, SP:0 HP:0 #P:2)
> > > > # -----------------
> > > > # | task: ktimers/0-15 (uid:0 nice:0 policy:1 rt_prio:1)
> > > > # -----------------
> > >
> > > The first thing that pokes me in the eye is that priority. I'd bump
> > > that a lot. As it sits, anything high priority ktimers may wake when
> > > it finally gets the CPU gets to enjoy all the latency ktimers is eating
> > > in this trace due to it having been deemed relatively unimportant.
> >
> > Hmmm, IRQs are running at FIFO:50 by default. Do we want the ktimer
> > running above the IRQ service thread?
>
> I think so yeah, quick like bunny wakeup resource should punch through.
Why not perform all wakes from hardirq then? If SCHED_OTHER is so
important…
> -Mike
Sebastian
next prev parent reply other threads:[~2023-10-02 10:05 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 [this message]
2023-10-02 11:58 ` Mike Galbraith
2023-10-02 14:16 ` Sebastian Andrzej Siewior
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=20231002100542.59fbxJ0f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.