Re: [PATCH v5] cpuset: Avoid invalidating sibling partitions on cpuset.cpus conflict.

[Michal Koutný]

On Wed, Dec 10, 2025 at 06:11:08PM +0800, Sun Shaojie <sunshaojie@xxxxxxxxxx> wrote:
> Regardless of whether A1 through A5 belong to the same user or different
> users, arbitration conflicts between sibling nodes can still occur (e.g.,
> due to user misconfiguration). The key question is: when such a conflict
> arises, should all sibling nodes be invalidated, or only the node that
> triggered the conflict?

Any serious [1] affinity users should watch for cpuset.cpus.partition
already (since it can be invalidated by hotplug or IMO more probable
ancestor re-configuration). Do you agree?

Then I'd say it's reasonable to invalidate all (same reasoning -- it
doesn't matter on the order in which siblings are configured, I consider
local partitions). What would you see as the upsides of invalidating
only the last offender (under the assumption above about watching)?

Thanks,
Michal

[1] The others may make use of the proposed cpu.max.concurrency [2]
[2] https://lpc.events/event/18/contributions/1978/

Attachment: signature.asc
Description: PGP signature