Re: Modifying isolcpus, nohz_full, and rcu_nocb kernel parameters at runtime

[Waiman Long]

On 12/12/23 08:27, Frederic Weisbecker wrote:
> On Fri, Dec 08, 2023 at 09:18:53AM -0500, Gianfranco Dutka wrote:
> > > The isolcpus, nohz_full and rcu_nocbs are boot-time kernel parameters. I am in the process of improving dynamic CPU isolation at runtime. Right now, we are able to do isolcpus=domain with the isolated cpuset partition functionality. Other aspects of CPU isolation are being looked at with the goal of reducing the gap of what one can do at boot time versus what can be done at run time. It will certain take time to reach that goal.
> > >
> > > Cheers,
> > > Longman
> > Thank you Waiman for the response. It would seem that getting similar
> > functionality through cgroups/cpusets is the only option at the moment. Is it
> > completely out of the question to possibly patch the kernel to modify these
> > parameters at runtime? Or would that entail a significant change that might
> > not be so trivial to accomplish? For instance, the solution wouldn’t be as
> > simple as patching the kernel to make these writeable and then calling the
> > same functions which run at boot-time when these parameters are originally
> > written?
> As for nohz_full (which implies rcu_nocb), it's certainly possible to make it
> tunable at runtime via cpusets. If people really want it, I'm willing to help.

As said by Phil, your help in in enabling dynamic rcu_nocb will be 
greatly appreciated. My current thought is to have a root level 
cpuset.cpus.isolation_control file to enable additional CPU isolation 
like rcu_nocb to be applied to CPUs in isolated partitions.

Cheers,
Longman