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 3/3] sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead
Date: Tue, 13 Jan 2026 15:00:49 +0530	[thread overview]
Message-ID: <4bd0e615-193d-47c6-8933-a93d75a2f29c@linux.ibm.com> (raw)
In-Reply-To: <CAKfTPtAqD6wTn=Qfwes1iScpmk0Lrh8HoqMoE+h4OBK2c+26RA@mail.gmail.com>


Hi Vincent.

>> On system with 480 CPUs, running "hackbench 40 process 10000 loops"
>> (Avg of 3 runs)
>> baseline:
>>       0.81%  hackbench          [k] nohz_balance_exit_idle
>>       0.21%  hackbench          [k] nohz_balancer_kick
>>       0.09%  swapper            [k] nohz_run_idle_balance
>>
>> With patch:
>>       0.35%  hackbench          [k] nohz_balance_exit_idle
>>       0.09%  hackbench          [k] nohz_balancer_kick
>>       0.07%  swapper            [k] nohz_run_idle_balance
>>
>> [Ingo Molnar: scalability analysis changlog]
>> Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
> 
> This change makes sense to me but I'm not convinced by patch1.
> You wrote in patch 1 that It doesn't provide any real benefit, what
> are the figures with only patch 3 ?
> 

Whole point of patch 1 is, (assuming normal case i.e system wont be 100% busy)

- we read the value and then do time check.
- we bail out if time is not due.

Why bother reading, if time is not due.

I won't expect patch1 to make any major difference. But seemed like right thing to do,
considering that most of the time system won't be 100% busy.

So numbers will be same without patch1.

>> ---
>>   kernel/sched/fair.c | 5 +----
>>   1 file changed, 1 insertion(+), 4 deletions(-)
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index c03f963f6216..3408a5beb95b 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -7144,7 +7144,6 @@ static DEFINE_PER_CPU(cpumask_var_t, should_we_balance_tmpmask);
>>
>>   static struct {
>>          cpumask_var_t idle_cpus_mask;
>> -       atomic_t nr_cpus;
>>          int has_blocked_load;           /* Idle CPUS has blocked load */
>>          int needs_update;               /* Newly idle CPUs need their next_balance collated */
>>          unsigned long next_balance;     /* in jiffy units */
>> @@ -12466,7 +12465,7 @@ static void nohz_balancer_kick(struct rq *rq)
>>           * None are in tickless mode and hence no need for NOHZ idle load
>>           * balancing
>>           */
>> -       if (unlikely(!atomic_read(&nohz.nr_cpus)))
>> +       if (unlikely(cpumask_empty(nohz.idle_cpus_mask)))
>>                  return;
>>
>>          if (rq->nr_running >= 2) {
>> @@ -12579,7 +12578,6 @@ void nohz_balance_exit_idle(struct rq *rq)
>>
>>          rq->nohz_tick_stopped = 0;
>>          cpumask_clear_cpu(rq->cpu, nohz.idle_cpus_mask);
>> -       atomic_dec(&nohz.nr_cpus);
>>
>>          set_cpu_sd_state_busy(rq->cpu);
>>   }
>> @@ -12637,7 +12635,6 @@ void nohz_balance_enter_idle(int cpu)
>>          rq->nohz_tick_stopped = 1;
>>
>>          cpumask_set_cpu(cpu, nohz.idle_cpus_mask);
>> -       atomic_inc(&nohz.nr_cpus);
>>
>>          /*
>>           * Ensures that if nohz_idle_balance() fails to observe our
>> --
>> 2.47.3
>>


  reply	other threads:[~2026-01-13  9:31 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
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 [this message]
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=4bd0e615-193d-47c6-8933-a93d75a2f29c@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®