Hello, On Tue, Aug 16, 2022 at 06:11:03PM -0400, Waiman Long wrote: > It is hard to synchronize different subsystems atomically without running > into locking issue. Let me think about what can be done in this case. I have a hard time seeing why this would be particularly difficult. cpuset just needs to make the latest cpumask available to sched core in an easily accessible form and whenever that changes, trigger a set_cpus_allowed call. There's no need to entangle operations across the whole subsystems. All that's needed to be communicated is the current cpumask. > Is using a sequence number to check for race with retry good enough? It seems unnecessarily fragile and complicated to me. If we're gonna change it, let's change it right. Thanks. -- tejun
