Re: cpusets not cpu hotplug aware

[Paul Jackson]

Anton wrote:
> Im struggling to understand why we have this problem at all. If a task
> has not been touched by cpuset calls it should be allowed to use any
> cpu.

Cpusets are not like sched_setaffinity.  It's not something that is
optional for a task.

Rather, if your kernel config has CPUSETS enabled, then every task is
in a cpuset, always,   By default, every task is in the top_cpuset.

Today, the top_cpuset has a static copy of the online cpus as of the
the system boot.

We need to make the cpus in the top_cpuset become a dynamic copy of the
online cpus and nodes, not a static copy.

I'm confident udev can do this.

Right now I'm working through some local problems testing this, and
unraveling some complexities with multiple versions of the udev user
code, including at least:
 1) one version uses the kernel default /sbin/hotplug to callback,
 2) another version uses a udevd daemon and /etc/dev.d, and
 3) a third version uses udevd, but no /etc/dev.d.

The cpuset side of coding this is easy enough for me; the udev side
more difficult.

Any suggestions on the best place for me to go with more detailed udev
questions?

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@xxxxxxx> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/