2 # Linux VServer configuration
9 config VSERVER_SECURITY
13 select SECURITY_CAPABILITIES
18 bool "Enable Legacy Kernel API"
21 This enables the legacy API used in vs1.xx, which allows
22 to use older tools (for migration purposes).
24 config VSERVER_LEGACYNET
25 bool "Enable Legacy Networking Kernel API"
28 This enables the legacy networking API, which allows
29 to configure per vserver IPs as we know it.
30 For now, even recent tools use this interface of the
31 legacy API, so unless you know what you are doing,
32 leave that option enabled.
34 config VSERVER_PROC_SECURE
35 bool "Enable Proc Security"
39 Hide proc entries by default for xid>1
41 config VSERVER_HARDCPU
42 bool "Enable Hard CPU Limits"
43 depends on EXPERIMENTAL
46 Activate the Hard CPU Limits
48 config VSERVER_HARDCPU_IDLE
49 bool "Limit the IDLE task"
50 depends on VSERVER_HARDCPU
53 Limit the idle slices, so the the next context
54 will be scheduled as soon as possible.
55 might improve interactivity/latency but
56 increases scheduling overhead.
59 prompt "Persistent Inode Context Tagging"
62 This adds persistent context information to filesystems
63 mounted with the tagxid option. Tagging is a requirement
64 for per context disk limits and per context quota.
70 no context information is store for inodes
75 reduces UID to 16 bit, but leaves GID at 32 bit.
80 reduces GID to 16 bit, but leaves UID at 32 bit.
85 uses the upper 8bit from UID and GID for XID tagging
86 which leaves 24bit for UID/GID each, which should be
87 more than sufficient for normal use.
92 this uses otherwise reserved inode fields in the on
93 disk representation, which limits the use to a few
94 filesystems (currently ext2 and ext3)
98 depends on EXPERIMENTAL
100 inodes are tagged when first accessed, this doesn't
101 require any persistant information, but might give
102 funny results for mixed access.
107 bool "Compile Debugging Code"
110 Set this to yes if you want to be able to activate
111 debugging output at runtime. It adds a probably small
112 overhead (~ ??%) to all vserver related functions and
113 increases the kernel size by about 20k.
115 config VSERVER_HISTORY
116 bool "Compile History Tracing"
117 depends on VSERVER_DEBUG
120 Set this to yes if you want to record the history of
121 linux-vserver activities, so they can be replayed on
122 a kernel panic (oops)
124 config VSERVER_HISTORY_SIZE
125 int "Per CPU History Size (32-65536)"
126 depends on VSERVER_HISTORY
130 This allows you to specify the number of entries in
131 the per CPU history buffer.