Re: [ckrm-tech] [PATCH 2/6] Cpusets hooked into containers

[Paul Menage]

On 11/6/06, Paul Jackson <pj@xxxxxxx> wrote:
> But I presume this CONFIG_CPUSETS_LEGACY_API option means I either
> get to build a kernel that supports the new container API, or a kernel
> that supports the old cpuset API.  That does not seem useful to me.

No. The changes triggered by CONFIG_CPUSETS_LEGACY_API are:

- /proc/<pid>/cpuset is an alias for /proc/<pid>/containers
- a dummy "cpuset" filesystem exists
- mounting the "cpuset" filesystem causes:
 - the container filesystem to be mounted in its place
 - the release agent to be switched to /sbin/cpuset_release_agent
 - defaults the "cpuset" container type to be enabled

Paul
-
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/