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: Wed, 3 Dec 2025 15:29:16 +0100 [thread overview]
Message-ID: <aTBJPCiI9iVNYTWR@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <CAKJHwtMAHpOpm4QJLFKES9Uz_9XPa9gX_QvLYCzvWEjMEjv6YA@mail.gmail.com>
On 25/11/25 13:33, David Haufe wrote:
> f237e524f3c7 ("sched/deadline: Make dl-server nohz full aware") <--
> patch applied
> 219a63335b67 ("sched/deadline: Don't count nr_running twice for
> dl_server proxy tasks") <-- exists in mainline 6.17
> 7620177e8108 ("sched/deadline: Fix RT task potential starvation when
> expiry time passed") <-- exists in mainline 6.17
> cccb45d7c429 ("sched/deadline: Less agressive dl_server handling") <--
> slightly different code but exists in mainline 6.17
>
> The "nohz full aware" patch does stop the hrtimer interrupts. I will
> watch for that merge and can patch locally for now. Thank you!
Thanks for testing and reporting!
Unfortunately (as I mentioned) I will be soon traveling + pto until
essentially next year. So, apologies, but I will most probably need to
defer cleaning up and send out a proper version to beginning of 2026.
Hope that's OK.
Best,
Juri
next prev parent reply other threads:[~2025-12-03 14:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 16:51 Kernel 6.14.11 dl_server_timer(...) causing IPI/Function Call Interrupts on isolcpu/nohz_full cores, performance regression 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
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 [this message]
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=aTBJPCiI9iVNYTWR@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 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.