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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6599ad830611061322r6d11ee38hf8748e3b34f22a0b@mail.gmail.com>
Date:	Mon, 6 Nov 2006 13:22:52 -0800
From:	"Paul Menage" <menage@...gle.com>
To:	"Paul Jackson" <pj@....com>
Cc:	balbir@...ibm.com, sekharan@...ibm.com,
	ckrm-tech@...ts.sourceforge.net, jlan@....com, Simon.Derr@...l.net,
	linux-kernel@...r.kernel.org, mbligh@...gle.com, winget@...gle.com,
	rohitseth@...gle.com
Subject: Re: [ckrm-tech] [PATCH 2/6] Cpusets hooked into containers

On 11/6/06, Paul Jackson <pj@....com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/