From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>,
mingo@kernel.org, peterz@infradead.org,
vincent.guittot@linaro.org, linux-kernel@vger.kernel.org
Cc: juri.lelli@redhat.com, vschneid@redhat.com, tglx@linutronix.de,
dietmar.eggemann@arm.com, frederic@kernel.org,
longman@redhat.com
Subject: Re: [PATCH 1/2] sched/fair: consider hk_mask early in triggering ilb
Date: Fri, 20 Mar 2026 14:49:30 +0530 [thread overview]
Message-ID: <aed529eb-b9a9-4939-9347-4a02bea1ec3c@linux.ibm.com> (raw)
In-Reply-To: <6f78a46d-9f12-4e42-ae9b-17f3543136e7@amd.com>
On 3/20/26 9:07 AM, K Prateek Nayak wrote:
> Hello Shrikanth,
>
> On 3/19/2026 12:23 PM, Shrikanth Hegde wrote:
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index b19aeaa51ebc..02cca2c7a98d 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -7392,6 +7392,7 @@ static inline unsigned int cfs_h_nr_delayed(struct rq *rq)
>> static DEFINE_PER_CPU(cpumask_var_t, load_balance_mask);
>> static DEFINE_PER_CPU(cpumask_var_t, select_rq_mask);
>> static DEFINE_PER_CPU(cpumask_var_t, should_we_balance_tmpmask);
>> +static DEFINE_PER_CPU(cpumask_var_t, kick_ilb_tmpmask);
>
> nit. We can rename and reuse select_rq_mask. Wakeups happen with IRQs
> disabled and kick happens from the hrtimer handler so it should be safe
> to reuse that and save some space.
>
> Thoughts?
May be. but it could be a confusing name. sched_tmpmask?
We could similar stuff already to load_balance_mask, select_rq_mask.
So, i would prefer to keep it separate.
>
> [..snip..]
>
>> @@ -12715,27 +12716,41 @@ static void nohz_balancer_kick(struct rq *rq)
>> */
>> nohz_balance_exit_idle(rq);
>>
>> + /* ILB considers only HK_TYPE_KERNEL_NOISE housekeeping CPUs */
>> +
>> if (READ_ONCE(nohz.has_blocked_load) &&
>> - time_after(now, READ_ONCE(nohz.next_blocked)))
>> + time_after(now, READ_ONCE(nohz.next_blocked))) {
>> flags = NOHZ_STATS_KICK;
>> + cpumask_and(ilb_cpus, nohz.idle_cpus_mask,
>> + housekeeping_cpumask(HK_TYPE_KERNEL_NOISE));
>> + }
>>
>> /*
>> - * Most of the time system is not 100% busy. i.e nohz.nr_cpus > 0
>> - * Skip the read if time is not due.
>> + * Most of the time system is not 100% busy. i.e there are idle
>> + * housekeeping CPUs.
>> + *
>> + * So, Skip the reading idle_cpus_mask if time is not due.
>> *
>> * If none are in tickless mode, there maybe a narrow window
>> * (28 jiffies, HZ=1000) where flags maybe set and kick_ilb called.
>> * But idle load balancing is not done as find_new_ilb fails.
>> - * That's very rare. So read nohz.nr_cpus only if time is due.
>> + * That's very rare. So check (idle_cpus_mask & HK_TYPE_KERNEL_NOISE)
>> + * only if time is due.
>> + *
>> */
>> if (time_before(now, nohz.next_balance))
>> goto out;
>>
>> + /* Avoid the double computation */
>> + if (flags != NOHZ_STATS_KICK)
>> + cpumask_and(ilb_cpus, nohz.idle_cpus_mask,
>> + housekeeping_cpumask(HK_TYPE_KERNEL_NOISE));
>> +
>> /*
>> * None are in tickless mode and hence no need for NOHZ idle load
>> * balancing
>> */
>> - if (unlikely(cpumask_empty(nohz.idle_cpus_mask)))
>> + if (unlikely(cpumask_empty(ilb_cpus)))
>> return;
>
> We can just use the return value from the previous cpumask_and() for
> this and save on another cpumask iteration.
>
Makes sense. Will do.
>>
>> if (rq->nr_running >= 2) {
next prev parent reply other threads:[~2026-03-20 9:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 6:53 [PATCH 0/2] sched/fair: Minor improvements while triggering idle load balance Shrikanth Hegde
2026-03-19 6:53 ` [PATCH 1/2] sched/fair: consider hk_mask early in triggering ilb Shrikanth Hegde
2026-03-19 8:15 ` Mukesh Kumar Chaurasiya
2026-03-19 13:13 ` Shrikanth Hegde
2026-03-19 22:58 ` Shubhang Kaushik
2026-03-20 2:47 ` Shrikanth Hegde
2026-03-20 3:37 ` K Prateek Nayak
2026-03-20 9:19 ` Shrikanth Hegde [this message]
2026-03-20 11:43 ` Peter Zijlstra
2026-03-20 14:12 ` Shrikanth Hegde
2026-03-20 14:28 ` Shrikanth Hegde
2026-03-19 6:53 ` [PATCH 2/2] sched/fair: get this cpu once in find_new_ilb Shrikanth Hegde
2026-03-19 8:18 ` Mukesh Kumar Chaurasiya
2026-03-19 9:20 ` Peter Zijlstra
2026-03-19 13:03 ` Shrikanth Hegde
2026-03-19 13:39 ` Peter Zijlstra
2026-03-20 3:40 ` 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=aed529eb-b9a9-4939-9347-4a02bea1ec3c@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--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=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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