Messages in this thread |  | | From | Hillf Danton <> | | Subject | Re: [PATCH v2] sched/fair: Check a task has a fitting cpu when updating misfit | | Date | Fri, 29 Dec 2023 19:02:18 +0800 |
| |
On 12/12/23 16:40 Qais Yousef <qais.yousef@arm.com> > > If a misfit task is affined to a subset of the possible cpus, we need to > verify that one of these cpus can fit it. Otherwise the load balancer > code will continuously trigger needlessly leading the balance_interval > to increase in return and eventually end up with a situation where real > imbalances take a long time to address because of this impossible > imbalance situation. > > This can happen in Android world where it's common for background tasks > to be restricted to little cores.
What sense could you make by forcing a pill down through Peter's throat to fix the insane userspace behavior that blindly drives load balance mad by binding background tasks to littles cores? Is eevdf failing to handle your background tasks?
|  |