The fact that "isolcpus=" behaviour can't be modified at runtime is an
eternal source of discussion and debate opposing a useful feature against
a terrible interface.
I've long since tried to figure out a proper way to control this at
runtime using cpusets, which isn't easy as a boot time single cpumask
is difficult to map to a hierarchy of cpusets that can even overlap.
The idea here is to map the boot-set isolation behaviour to any cpuset
directory whose cpumask is a subset of "isolcpus=". I let you browse
for details on the last patch.
Note this is still WIP and half-baked, but I figured it's important to
validate the interface early.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
cpuset/isolation
HEAD: 6d3dba1115b7ea464febf3763244c783e87c7baf
Thanks,
Frederic
---
Frederic Weisbecker (6):
pci: Decouple HK_FLAG_WQ and HK_FLAG_DOMAIN cpumask fetch
workqueue: Decouple HK_FLAG_WQ and HK_FLAG_DOMAIN cpumask fetch
net: Decouple HK_FLAG_WQ and HK_FLAG_DOMAIN cpumask fetch
sched/isolation: Split domain housekeeping mask from the rest
sched/isolation: Make HK_FLAG_DOMAIN mutable
cpuset: Add cpuset.isolation_mask file
drivers/pci/pci-driver.c | 21 ++++++--
include/linux/sched/isolation.h | 4 ++
kernel/cgroup/cpuset.c | 111 ++++++++++++++++++++++++++++++++++++++--
kernel/sched/isolation.c | 73 ++++++++++++++++++++++----
kernel/workqueue.c | 4 +-
net/core/net-sysfs.c | 6 +--
6 files changed, 196 insertions(+), 23 deletions(-)
