On 11/6/06, Paul Jackson <[EMAIL PROTECTED]> 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

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
ckrm-tech mailing list
https://lists.sourceforge.net/lists/listinfo/ckrm-tech

Reply via email to