From: Juri Lelli <juri.lelli@redhat.com>
To: David Haufe <dhaufe@simplextrading.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 6.14.11 dl_server_timer(...) causing IPI/Function Call Interrupts on isolcpu/nohz_full cores, performance regression
Date: Mon, 4 Aug 2025 17:58:55 +0100 [thread overview]
Message-ID: <aJDmzxq1mB_DxIFV@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <CAKJHwtMker+LXNk9L4Vp6nAKjW1P-T0n1VXSLn3piMwHsTWmqA@mail.gmail.com>
On 04/08/25 10:44, David Haufe wrote:
> My apologies, I see what you mean now. add_nr_running() is not being
> invoked if it is the dl_server. We are still trying to get this branch
> to boot to verify ourselves. We will be on the lookout for this to be
> merged for release.
No worries, guess I wasn't clear the first time. :)
I added a very much experimental commit on
https://github.com/jlelli/linux/tree/upstream/fix-dlserver-1
that seems to be able to remove the one per second dl_server_timer and
start it back as needed. But, I just played briefly with it, so I am not
fully convinced is what we want. Anyway, if you could test with it as
well it would be a useful data point. In principle you could try porting
the following commits to your current tree and check if they do improve
things (in reverse order starting from the bottom from the branch above):
f237e524f3c7 ("sched/deadline: Make dl-server nohz full aware")
219a63335b67 ("sched/deadline: Don't count nr_running twice for dl_server proxy tasks")
7620177e8108 ("sched/deadline: Fix RT task potential starvation when expiry time passed")
cccb45d7c429 ("sched/deadline: Less agressive dl_server handling")
Thanks!
Juri
next prev parent reply other threads:[~2025-08-04 16:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 16:51 David Haufe
2025-07-31 7:01 ` Juri Lelli
2025-07-31 17:50 ` David Haufe
[not found] ` <CAKJHwtOZkrR9kEj+tffq=o0i1fPi3P+8BTHz3RyPDmn=uDOF7g@mail.gmail.com>
2025-08-01 9:06 ` Juri Lelli
2025-08-01 15:28 ` David Haufe
2025-08-04 14:49 ` Juri Lelli
2025-08-04 15:44 ` David Haufe
2025-08-04 16:58 ` Juri Lelli [this message]
2025-11-24 20:30 ` David Haufe
2025-11-25 13:58 ` Juri Lelli
2025-11-25 19:33 ` David Haufe
2025-12-03 14:29 ` Juri Lelli
2026-04-10 16:39 ` Cao Ruichuang
2026-04-24 12:38 ` Juri Lelli
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=aJDmzxq1mB_DxIFV@jlelli-thinkpadt14gen4.remote.csb \
--to=juri.lelli@redhat.com \
--cc=dhaufe@simplextrading.com \
--cc=linux-kernel@vger.kernel.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®