mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: markus.stockhausen@gmx.de, peterz@infradead.org,
	'Chris Packham' <Chris.Packham@alliedtelesis.co.nz>,
	mingo@redhat.com, vincent.guittot@linaro.org,
	anna-maria@linutronix.de, frederic@kernel.org,
	tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: task_non_contending() for fair_server leads to timer retries
Date: Thu, 17 Jul 2025 17:05:35 +0200	[thread overview]
Message-ID: <87ldomkgcg.fsf@miraculix.mork.no> (raw)
In-Reply-To: <aHi8yk8wlVJBFzSR@jlelli-thinkpadt14gen4.remote.csb> (Juri Lelli's message of "Thu, 17 Jul 2025 11:05:14 +0200")

Juri Lelli <juri.lelli@redhat.com> writes:
> On 15/07/25 16:39, markus.stockhausen@gmx.de wrote:
>> Hi Peter,
>> 
>> I'm currently investigating issues with the timer-rtl-otto driver in 
>> 6.12 longterm on the Realtek MIPS switch platform (Chris is working
>> hard to upstream this). While doing so I observed that timer retries 
>> continually increase (~6/second) according to /proc/timer_list. The 
>> system is otherwise totally idle. 6.6 longterm does not show that issue.
>> I'm unsure if this is related but documentation reads like "that's bad". 
>> 
>> To be sure about this one I nailed it down to the fair server.
>
> Apologies for interjecting before Peter had a chance to reply, but I had
> a first look and I wonder if this recent patch from Peter (on
> tip/sched/core atm) can already help with the issue, as it should
> reduce the number of dl-server dequeues:
>
> cccb45d7c4295 ("sched/deadline: Less agressive dl_server handling")
>
> Can you please check what you see with it?

Spot on.  Thanks
 
I tested cccb45d7c4295 ("sched/deadline: Less agressive dl_server
handling") on top of the 6.12 longterm we're running and the retries
rate is back to "normal".


Bjørn

      reply	other threads:[~2025-07-17 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 14:39 markus.stockhausen
2025-07-17  9:05 ` Juri Lelli
2025-07-17 15:05   ` Bjørn Mork [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=87ldomkgcg.fsf@miraculix.mork.no \
    --to=bjorn@mork.no \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=anna-maria@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.stockhausen@gmx.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    /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

all inboxes | Powered by JetHome®