From: Ingo Molnar <mingo@kernel.org>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: peterz@infradead.org, vincent.guittot@linaro.org,
linux-kernel@vger.kernel.org, kprateek.nayak@amd.com,
dietmar.eggemann@arm.com, vschneid@redhat.com,
rostedt@goodmis.org, tglx@linutronix.de,
tim.c.chen@linux.intel.com,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH 4/4] sched/fair: Remove atomic nr_cpus and use cpumask instead
Date: Tue, 2 Dec 2025 17:14:08 +0100 [thread overview]
Message-ID: <aS8QUIQ8smrDTuxr@gmail.com> (raw)
In-Reply-To: <fdb378e7-7797-4aeb-a79f-12af4cb1b81a@linux.ibm.com>
* Shrikanth Hegde <sshegde@linux.ibm.com> wrote:
> > So I'd argue that reductions in both (A) and (B)
> > are useful, but for different reasons.
> >
> > The *real* breakthrough in this area would be to
> > reduce the unlimited upwards frequency of (2), by
> > fundamentally changing the model of NOHZ idle
> > balancing:
> >
> > For example by measuring the rate (frequency) of
> > idle cycles on each CPU (this can be done without
> > any cross-CPU logic), we would turn off NOHZ-idle
> > for that CPU when the rate goes beyond a threshold.
> >
> > The resulting regular idle load-balancing passes
> > will be rate-limited by balance intervals and won't
> > be as aggressive as nohz_balance_enter+exit_idle().
> > (I hope...)
> >
> > Truly idle CPUs would go into NOHZ mode
> > automatically, as their measured rate of idling
> > drops below the threshold.
> >
> > Thoughts?
>
> Interesting.
>
> Let me see if i get this right.
>
> So track the idle duration over certain past
> interval. If is below certain threshould mark those
> CPUs in nohz state while doing idle entry/exit. If
> not, reset their bits in nohz mask and don't update
> the mask?
>
> I think rq->avg_idle there already and we do similar checks for newidle_balance.
> sched_balance_newidle
> ...
> if (!get_rd_overloaded(this_rq->rd) ||
> this_rq->avg_idle < sd->max_newidle_lb_cost) {
>
> update_next_balance(sd, &next_balance);
> rcu_read_unlock();
> goto out;
> }
Yeah, seems so - but I haven't put much thought into
the idea, so caveat emptor. :-)
Thanks,
Ingo
prev parent reply other threads:[~2025-12-02 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 18:31 [PATCH 0/4] sched/fair: improve nohz fields for large systems Shrikanth Hegde
2025-12-01 18:31 ` [PATCH 1/4] sched/fair: Move checking for nohz cpus after time check Shrikanth Hegde
2025-12-01 18:31 ` [PATCH 2/4] sched/fair: Change likelyhood of nohz nr_cpus check Shrikanth Hegde
2025-12-01 18:31 ` [PATCH 3/4] sched/fair: Check for blocked task after time check Shrikanth Hegde
2025-12-02 6:26 ` Ingo Molnar
2025-12-02 6:55 ` Shrikanth Hegde
2025-12-01 18:31 ` [PATCH 4/4] sched/fair: Remove atomic nr_cpus and use cpumask instead Shrikanth Hegde
2025-12-01 19:58 ` Ingo Molnar
2025-12-02 5:29 ` Shrikanth Hegde
2025-12-02 7:54 ` Ingo Molnar
2025-12-02 14:35 ` Shrikanth Hegde
2025-12-02 16:14 ` Ingo Molnar [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=aS8QUIQ8smrDTuxr@gmail.com \
--to=mingo@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox