14 Apr
2023
14 Apr
'23
4:54 p.m.
On Thu, Apr 13, 2023 at 09:22:19PM -0400, Waiman Long wrote:
I now have a slightly different idea of how to do that. We already have an internal cpumask for partitioning - subparts_cpus. I am thinking about exposing it as cpuset.cpus.reserve. The current way of creating subpartitions will be called automatic reservation and require a direct parent/child partition relationship. But as soon as a user write anything to it, it will break automatic reservation and require manual reservation going forward.
In that way, we can keep the old behavior, but also support new use cases. I am going to work on that.
I'm not sure I fully understand the proposed behavior but it does sound more quirky.
Thanks.
--
tejun