The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Cao Ruichuang <create0818@163.com>
To: Juri Lelli <juri.lelli@redhat.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: Sat, 11 Apr 2026 00:39:41 +0800	[thread overview]
Message-ID: <177583918187.65608.81441247578852229@163.com> (raw)
In-Reply-To: <CAKJHwtMAHpOpm4QJLFKES9Uz_9XPa9gX_QvLYCzvWEjMEjv6YA@mail.gmail.com>

Hi Juri,

I tested the "sched/deadline: Make dl-server nohz full aware" change
shape from f237e524f3c7 on the current mainline tree in a minimal QEMU
setup.

I used a latest-tree tiny x86 kernel with:

  nohz_full=1 isolcpus=domain,managed_irq,1 irqaffinity=0 rcu_nocbs=1

and a CPU1-pinned busy loop as the only user workload. To observe the
periodic activity, I installed a kprobe on start_dl_timer and counted
hits over the same 5 second window.

On the unmodified tree, I consistently saw:

  START_DL_TIMER_COUNT=118

With the sched_can_stop_tick() change from f237e524f3c7 applied, I saw:

  START_DL_TIMER_COUNT=20
  START_DL_TIMER_COUNT=22

So on current mainline this still looks like a real improvement in the
same direction David reported earlier: the periodic dl-server activity
is reduced substantially, although it is not eliminated completely in my
QEMU setup.

I am not sending this as a patch, only as an extra data point in favor
of that fix direction on a latest-tree test setup.

Thanks,
Cao Ruichuang


  parent reply	other threads:[~2026-04-10 16:39 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
2026-04-10 16:39                     ` Cao Ruichuang [this message]
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=177583918187.65608.81441247578852229@163.com \
    --to=create0818@163.com \
    --cc=juri.lelli@redhat.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