Hello, On Mon, Jul 10, 2023 at 08:53:18PM -0400, Waiman Long wrote: > For local partition, it doesn't make sense to have a cpust.cpus.exclusive > that is not the same as cpuset.cpus as it artificially reduce the set of > CPUs that can be used in a partition. In the case of a remote partition, the Yeah, I was wondering about local partitions. "Automatic but can be overridden" behavior becomes confusing if it's difficult for the user to easily tell which part is automatic when. I wonder whether it'd be better to make the condition static - e.g. for a partition cgroup, cpus.exclusive always contains all bits in cpus no matter what value is written to it. Or, if we separate out cpus.exclusive and cpus.exclusive.effective, no matter what cpus.exclusive is set, a partition root's cpus.exclusive.effective always includes all bits in cpus.effective. Thanks. -- tejun
