From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, yury.norov@gmail.com,
kprateek.nayak@amd.com
Cc: tglx@kernel.org, gregkh@linuxfoundation.org, pbonzini@redhat.com,
seanjc@google.com, vschneid@redhat.com, huschle@linux.ibm.com,
rostedt@goodmis.org, dietmar.eggemann@arm.com, mgorman@suse.de,
bsegall@google.com, maddy@linux.ibm.com, srikar@linux.ibm.com,
hdanton@sina.com, chleroy@kernel.org, vineeth@bitbyteword.org,
frederic@kernel.org, arighi@nvidia.com, pauld@redhat.com,
christian.loehle@arm.com, tj@kernel.org,
tommaso.cucinotta@gmail.com, maz@kernel.org, rafael@kernel.org
Subject: Re: [PATCH v3 17/20] sched/core: Introduce default arch handling code for inc/dec preferred CPUs
Date: Mon, 8 Jun 2026 18:22:43 +0200 [thread overview]
Message-ID: <688322d7-660c-4600-a920-6c5f49caa11c@linux.ibm.com> (raw)
In-Reply-To: <20260514152204.481115-18-sshegde@linux.ibm.com>
On 5/14/26 17:22, Shrikanth Hegde wrote:
> Define default handlers for high/low steal time. If arch has better
> decision logic, may override the default implementation.
>
> - If the steal time higher than threshold, reduce the number of preferred
> CPUs by 1 core. The last core in the intersection of online and
> preferred CPUs will be marked as non-preferred.
> Ensure at least one core is left as preferred always.
>
> - If the steal time lower than threshold, increase the number of preferred
> CPUs by 1 core. First online core which is not in cpu_preferred_mask will
> be marked as preferred.
> If all cores are already set to preferred, bail out.
>
> Increase/Decrease may need to modify the splicing across NUMA nodes. It is
> being kept simple for now.
>
> Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
> ---
> include/linux/sched.h | 2 ++
> kernel/sched/core.c | 58 +++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 60 insertions(+)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 738f17d63943..2afbcd70f0ac 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -2529,6 +2529,8 @@ struct steal_monitor_t {
> };
>
> extern struct steal_monitor_t steal_mon;
> +void arch_dec_preferred_cpus(struct steal_monitor_t *sm, u64 steal_ratio);
> +void arch_inc_preferred_cpus(struct steal_monitor_t *sm, u64 steal_ratio);
> #endif
>
> #endif
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index a3f65e9c7d30..195e3648b1b5 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -11368,6 +11368,64 @@ void sched_init_steal_monitor(void)
> steal_mon.sampling_period_ms = 1000; /* once per second */
> }
>
> +/*
> + * Default implementation of decrementing the preferred CPUs based on steal
> + * time. This is simple logic and decrease the preferred CPUs by 1 core.
> + * It takes out the last core in the online & preferred.
> + *
> + * Ensure at least one housekeeping core is always kept as preferred
> + *
> + * Could be overwritten by arch specific handling.
> + */
> +#ifndef arch_dec_preferred_cpus
> +void arch_dec_preferred_cpus(struct steal_monitor_t *sm, u64 steal_ratio)
> +{
> + int last_cpu, tmp_cpu;
> + int this_cpu = raw_smp_processor_id();
> +
> + cpumask_and(sm->tmp_mask, cpu_online_mask, cpu_preferred_mask);
> + last_cpu = cpumask_last(sm->tmp_mask);
> +
> + /*
> + * If the core belongs to the housekeeping CPUs, no action is
> + * taken. This leaves at least one core preferred always.
> + * This ensures at least some CPUs are available to run
> + */
> + if (cpumask_equal(cpu_smt_mask(last_cpu), cpu_smt_mask(this_cpu)))
> + return;
> +
> + for_each_cpu_and(tmp_cpu, cpu_smt_mask(last_cpu), cpu_online_mask) {
> + set_cpu_preferred(tmp_cpu, false);
> + if (tick_nohz_full_cpu(tmp_cpu))
> + tick_nohz_dep_set_cpu(tmp_cpu, TICK_DEP_BIT_SCHED);
Should the opposite be done in arch_inc_preferred_cpus()?
If not, it would be good to write a comment explaining why; this
asymmetry catches the eye.
> + }
> +}
> +#endif
> +
> +/*
> + * Default implementation of incrementing preferred CPUs based on steal
> + * time. This is simple logic and increases the preferred CPUs by 1 core.
> + * It adds the first core in online & !preferred
> + *
> + * Nothing to do if online == preferred
> + *
> + * Could be overwritten by arch specific handling.
> + */
> +#ifndef arch_inc_preferred_cpus
> +void arch_inc_preferred_cpus(struct steal_monitor_t *sm, u64 steal_ratio)
> +{
> + int first_cpu, tmp_cpu;
> +
> + first_cpu = cpumask_first_andnot(cpu_online_mask, cpu_preferred_mask);
> + /* All CPUs are preferred. Nothing to increase further */
> + if (first_cpu >= nr_cpu_ids)
> + return;
> +
> + for_each_cpu_and(tmp_cpu, cpu_smt_mask(first_cpu), cpu_online_mask)
> + set_cpu_preferred(tmp_cpu, true);
> +}
> +#endif
> +
> /* This is only a skeleton. Subsequent patches introduce more of it */
> void sched_steal_detection_work(struct work_struct *work)
> {
next prev parent reply other threads:[~2026-06-08 16:23 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 15:21 [PATCH v3 00/20] sched: Introduce cpu_preferred_mask and steal-driven vCPU backoff Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 01/20] sched/debug: Remove unused schedstats Shrikanth Hegde
2026-06-04 4:01 ` K Prateek Nayak
2026-05-14 15:21 ` [PATCH v3 02/20] sched/docs: Document cpu_preferred_mask and Preferred CPU concept Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 03/20] kconfig: Provide PREFERRED_CPU option Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 04/20] cpumask: Introduce cpu_preferred_mask Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 05/20] sysfs: Add preferred CPU file Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 06/20] sched/core: allow only preferred CPUs in is_cpu_allowed Shrikanth Hegde
2026-06-04 5:06 ` K Prateek Nayak
2026-06-04 5:54 ` Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 07/20] sched/fair: Select preferred CPU at wakeup when possible Shrikanth Hegde
2026-06-04 5:14 ` K Prateek Nayak
2026-06-04 5:48 ` Shrikanth Hegde
2026-06-08 16:39 ` Ilya Leoshkevich
2026-06-09 4:42 ` Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 08/20] sched/fair: load balance only among preferred CPUs Shrikanth Hegde
2026-06-04 5:20 ` K Prateek Nayak
2026-06-04 5:45 ` Shrikanth Hegde
2026-06-04 6:09 ` K Prateek Nayak
2026-06-04 13:07 ` Shrikanth Hegde
2026-06-09 11:22 ` Peter Zijlstra
2026-06-09 11:33 ` Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 09/20] sched/rt: Select a preferred CPU for wakeup and pulling rt task Shrikanth Hegde
2026-06-09 11:25 ` Peter Zijlstra
2026-06-09 11:30 ` Shrikanth Hegde
2026-06-10 17:13 ` Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 10/20] sched/core: Keep tick on non-preferred CPUs until tasks are out Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 11/20] sched/core: Push current task from non preferred CPU Shrikanth Hegde
2026-06-04 6:58 ` K Prateek Nayak
2026-06-04 9:43 ` Shrikanth Hegde
2026-06-04 9:56 ` K Prateek Nayak
2026-06-04 12:16 ` Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 12/20] sched/debug: Add migration stats due to non preferred CPUs Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 13/20] sched/debug: Create debugfs folder steal_monitor Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 14/20] sched/debug: Provide debugfs to enable/disable steal monitor Shrikanth Hegde
2026-06-08 17:37 ` Ilya Leoshkevich
2026-06-09 4:48 ` Shrikanth Hegde
2026-06-08 18:28 ` Ilya Leoshkevich
2026-06-09 5:04 ` Shrikanth Hegde
2026-05-14 15:21 ` [PATCH v3 15/20] sched/core: Introduce a simple " Shrikanth Hegde
2026-06-08 16:25 ` Ilya Leoshkevich
2026-06-09 5:54 ` Shrikanth Hegde
2026-05-14 15:22 ` [PATCH v3 16/20] sched/core: Compute steal values at regular intervals Shrikanth Hegde
2026-05-14 15:22 ` [PATCH v3 17/20] sched/core: Introduce default arch handling code for inc/dec preferred CPUs Shrikanth Hegde
2026-06-08 16:22 ` Ilya Leoshkevich [this message]
2026-06-09 5:14 ` Shrikanth Hegde
2026-06-08 18:40 ` Ilya Leoshkevich
2026-06-09 6:42 ` Shrikanth Hegde
2026-05-14 15:22 ` [PATCH v3 18/20] sched/core: Handle steal values and mark CPUs as preferred Shrikanth Hegde
2026-05-14 15:22 ` [PATCH v3 19/20] sched/core: Mark the direction of steal values to avoid oscillations Shrikanth Hegde
2026-05-14 15:22 ` [PATCH v3 20/20] sched/debug: Add debug knobs for steal monitor Shrikanth Hegde
2026-06-04 3:17 ` [PATCH v3 00/20] sched: Introduce cpu_preferred_mask and steal-driven vCPU backoff Shrikanth Hegde
2026-06-09 19:51 ` Shrikanth Hegde
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=688322d7-660c-4600-a920-6c5f49caa11c@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=chleroy@kernel.org \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=huschle@linux.ibm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=maz@kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=pauld@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=srikar@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=tglx@kernel.org \
--cc=tj@kernel.org \
--cc=tommaso.cucinotta@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=vineeth@bitbyteword.org \
--cc=vschneid@redhat.com \
--cc=yury.norov@gmail.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®