mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@kernel.org, peterz@infradead.org,
	linux-kernel@vger.kernel.org, kprateek.nayak@amd.com,
	juri.lelli@redhat.com, vschneid@redhat.com, tglx@kernel.org,
	dietmar.eggemann@arm.com, anna-maria@linutronix.de,
	frederic@kernel.org, wangyang.guo@intel.com
Subject: Re: [PATCH v4 1/3] sched/fair: Move checking for nohz cpus after time check
Date: Tue, 13 Jan 2026 14:53:05 +0530	[thread overview]
Message-ID: <f1ff39d1-0fb6-4159-9c87-851f48f2f03a@linux.ibm.com> (raw)
In-Reply-To: <CAKfTPtANCdWEptRSY=XK8Z8v1YJZrpJtpYKP7D-4uOJ-jDVf4w@mail.gmail.com>



On 1/13/26 2:37 PM, Vincent Guittot wrote:
> On Mon, 12 Jan 2026 at 06:05, Shrikanth Hegde <sshegde@linux.ibm.com> wrote:
>>
>> NOHZ idle load balancer is kicked off only after time check. So move
>> the atomic read after the time check to access it only when needed.
>>
>> When there are no idle CPUs(100% busy), even if the flag gets set to
>> NOHZ_STATS_KICK | NOHZ_NEXT_KICK, find_new_ilb will fail and
>> there will be no NOHZ idle balance. The current behaviour is retained.
>>
>> Note: This patch doesn't solve any cacheline overheads. No improvement
>> in performance apart from saving a few cycles of atomic_read.
> 
> But won't these cycles be then wasted by calling needlessly kick_ilb
> 

when there are nohz cpus, i.e nohz.nr_cpus > 0, there is no change in codeflow.

Only when system is 100%(which is expected to be rare), nohz.nr_cpus == 0,
then it is expected that has_blocked_load = 0. So flags shouldn't be set.
Note we are still doing a return if nohz.nr_cpus == 0. So kick_ilb shouldn't be
called.

Do you see any path still calling kick_ilb un-necessarily?


>>
>> Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
>> ---
>>   kernel/sched/fair.c | 18 +++++++++++-------
>>   1 file changed, 11 insertions(+), 7 deletions(-)
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index 9743fc0b225c..17e4e8ac5fca 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -12451,20 +12451,24 @@ static void nohz_balancer_kick(struct rq *rq)
>>           */
>>          nohz_balance_exit_idle(rq);
>>
>> -       /*
>> -        * None are in tickless mode and hence no need for NOHZ idle load
>> -        * balancing:
>> -        */
>> -       if (likely(!atomic_read(&nohz.nr_cpus)))
>> -               return;
>> -
>>          if (READ_ONCE(nohz.has_blocked_load) &&
>>              time_after(now, READ_ONCE(nohz.next_blocked)))
>>                  flags = NOHZ_STATS_KICK;
>>
>> +       /*
>> +        * If none are in tickless mode, though flag maybe set,
>> +        * idle load balancing is not done as find_new_ilb fails
>> +        */
>>          if (time_before(now, nohz.next_balance))
>>                  goto out;
>>
>> +       /*
>> +        * None are in tickless mode and hence no need for NOHZ idle load
>> +        * balancing:
>> +        */
>> +       if (likely(!atomic_read(&nohz.nr_cpus)))
>> +               return;
>> +
>>          if (rq->nr_running >= 2) {
>>                  flags = NOHZ_STATS_KICK | NOHZ_BALANCE_KICK;
>>                  goto out;
>> --
>> 2.47.3
>>


  reply	other threads:[~2026-01-13  9:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  5:04 [PATCH v4 0/3] sched/fair: Improve nohz fields for large systems Shrikanth Hegde
2026-01-12  5:04 ` [PATCH v4 1/3] sched/fair: Move checking for nohz cpus after time check Shrikanth Hegde
2026-01-13  9:07   ` Vincent Guittot
2026-01-13  9:23     ` Shrikanth Hegde [this message]
2026-01-13 10:21       ` Vincent Guittot
2026-01-13 11:18         ` Shrikanth Hegde
2026-01-13 13:20           ` Vincent Guittot
2026-01-12  5:04 ` [PATCH v4 2/3] sched/fair: Change likelyhood of nohz.nr_cpus Shrikanth Hegde
2026-01-12  5:04 ` [PATCH v4 3/3] sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead Shrikanth Hegde
2026-01-12 11:49   ` Valentin Schneider
2026-01-13  9:23   ` Vincent Guittot
2026-01-13  9:30     ` Shrikanth Hegde
2026-01-13  6:45 ` [PATCH v4 0/3] sched/fair: Improve nohz fields for large systems K Prateek Nayak

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=f1ff39d1-0fb6-4159-9c87-851f48f2f03a@linux.ibm.com \
    --to=sshegde@linux.ibm.com \
    --cc=anna-maria@linutronix.de \
    --cc=dietmar.eggemann@arm.com \
    --cc=frederic@kernel.org \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=wangyang.guo@intel.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

all inboxes | Powered by JetHome®