There's CONFIG_PID_NS option to turn on the pid virtualzation
and the "choise" for the model type depending on it.

Signed-off-by: Pavel Emelianov <xemul@openvz.org>

---

 Kconfig |   30 ++++++++++++++++++++++++++++++
 1 files changed, 30 insertions(+)

diff --git a/init/Kconfig b/init/Kconfig
index 2a46e35..6b2cbcf 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -127,6 +127,36 @@ config SWAP_PREFETCH
 	  Workstations and multiuser workstation servers will most likely want
 	  to say Y.
 
+config PID_NS
+	bool "Pid namespaces"
+	depends on EXPERIMENTAL
+	default n
+	help
+	  Enable pid namespaces support. When on task is allowed to unshare
+	  its pid namespace from parent and become its init. After this task
+	  all its children will see only the tasks from this namespace.
+	  However tasks from parent namespace see all the tasks in the system.
+	  Ony one level of nesting is alowed. Tasks cannot leave the namespace.
+
+choice
+	prompt "Select pid namespace model"
+	default PID_NS_FLAT
+	depends on PID_NS
+	help
+	  This option selects a pid namespace model
+
+config PID_NS_FLAT
+	bool "Flat pid namespace"
+	help
+	  Enable only one level of pid namespaces.
+
+config PID_NS_MULTILEVEL
+	bool "Multilevel pid namespaces"
+	help
+	  Enable creating pid namespaces of infinite nesting.
+
+endchoice
+
 config SYSVIPC
 	bool "System V IPC"
 	---help---

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers