Re: [PATCH v6 0/6] timers: Exclude isolated cpus from timer migation

Frederic Weisbecker
2025-06-18T12:22:14Z

Hi Gabriele,

Le Wed, Jun 18, 2025 at 02:17:29PM +0200, Gabriele Monaco a écrit :
> On Fri, 2025-05-30 at 16:20 +0200, Gabriele Monaco wrote:
> > The timer migration mechanism allows active CPUs to pull timers from
> > idle ones to improve the overall idle time. This is however undesired
> > when CPU intensive workloads run on isolated cores, as the algorithm
> > would move the timers from housekeeping to isolated cores, negatively
> > affecting the isolation.
> >
> > [...]
> >
> > Exclude isolated cores from the timer migration algorithm, extend the
> > concept of unavailable cores, currently used for offline ones, to
> > isolated ones:
> > * A core is unavailable if isolated or offline;
> > * A core is available if isolated and offline;
> >
> > A core is considered unavailable as isolated if it belongs to:
> > * the isolcpus (domain) list
> > * an isolated cpuset
> > Except if it is:
> > * in the nohz_full list (already idle for the hierarchy)
> > * the nohz timekeeper core (must be available to handle global
> > timers)
>
> Frederic, Thomas, Waiman, would you have time to review this series?
> Thanks,
> Gabriele

Yes, sorry I got distracted with other things (although quite related).
I will give it a priority soonish!

Thanks.

--
Frederic Weisbecker
SUSE Labs