Hello.
I recently liked the idea of considering isolated CPUs a static (boot
time) resource and only use cpusets to place (or remove) sensitive
workload from those selected CPUs depending on current needs. (Yes, this
may not efficiently utilize the isolated CPUs when reserve them based on
maximum needs of a node.)
On Wed, Aug 21, 2024 at 10:23:11AM GMT, Waiman Long <longman@xxxxxxxxxx> wrote:
> This patch is a step in that direction by making the housekeeping CPU
> mask APIs exclude the dynamically isolated CPUs when they are called
> at run time. The housekeeping CPU masks will fall back to the bootup
> default when all the dynamically isolated CPUs are released.
But when I look at it with the dynamism in mind, I would expect that
some API like housekeeping_setup_type(), i.e. modify the set of isolated
CPUs are requested and leave it up to the isolation implementation to
propagate any changes to respective subsystems. And return an error of
type contains a flag for which dynamism isn't implemented yet or not
possible.
The boot time value would only be the initial default, but the value
would be mutated by this API. There's IMO no need to revert to that.
(Also someone mentioned that this could share lots of code with CPU
offlining/onlining.)
> A new housekeeping_exlude_isolcpus() function is added which is to be
exclude
> called by the cpuset subsystem to provide a list of isolated CPUs to
> be excluded.
HTH,
Michal
(-Cc: lizefan.x@xxxxxxxxxxxxx)
Attachment:
signature.asc
Description: PGP signature
