2 # Linux VServer configuration
9 config VSERVER_SECURITY
13 select SECURITY_CAPABILITIES
15 config VSERVER_LEGACYNET
17 depends on !VSERVER_NGNET
23 bool "Enable Legacy Kernel API"
26 This enables the legacy API used in vs1.xx, which allows
27 to use older tools (for migration purposes).
30 bool "Disable Legacy Networking Kernel API"
31 depends on EXPERIMENTAL
34 This disables the legacy networking API which is required
35 by the chbind tool. Do not disable it unless you exactly
36 know what you are doing.
38 config VSERVER_PROC_SECURE
39 bool "Enable Proc Security"
43 Hide proc entries by default for xid>1
45 config VSERVER_HARDCPU
46 bool "Enable Hard CPU Limits"
47 depends on EXPERIMENTAL
50 Activate the Hard CPU Limits
52 config VSERVER_HARDCPU_IDLE
53 bool "Limit the IDLE task"
54 depends on VSERVER_HARDCPU
57 Limit the idle slices, so the the next context
58 will be scheduled as soon as possible.
59 might improve interactivity/latency but
60 increases scheduling overhead.
63 prompt "Persistent Inode Context Tagging"
66 This adds persistent context information to filesystems
67 mounted with the tagxid option. Tagging is a requirement
68 for per context disk limits and per context quota.
74 no context information is store for inodes
79 reduces UID to 16 bit, but leaves GID at 32 bit.
84 reduces GID to 16 bit, but leaves UID at 32 bit.
89 uses the upper 8bit from UID and GID for XID tagging
90 which leaves 24bit for UID/GID each, which should be
91 more than sufficient for normal use.
96 this uses otherwise reserved inode fields in the on
97 disk representation, which limits the use to a few
98 filesystems (currently ext2 and ext3)
100 config INOXID_RUNTIME
102 depends on EXPERIMENTAL
104 inodes are tagged when first accessed, this doesn't
105 require any persistant information, but might give
106 funny results for mixed access.
111 bool "Tag NFSD User Auth and Files"
114 Enable this if you do want the kernel nfsd to
115 use the xid tagging specified above.
116 (will require patched clients too)
119 bool "VServer Debugging Code"
122 Set this to yes if you want to be able to activate
123 debugging output at runtime. It adds a probably small
124 overhead (~ ??%) to all vserver related functions and
125 increases the kernel size by about 20k.
127 config VSERVER_HISTORY
128 bool "VServer History Tracing"
129 depends on VSERVER_DEBUG
132 Set this to yes if you want to record the history of
133 linux-vserver activities, so they can be replayed on
134 a kernel panic (oops)
136 config VSERVER_HISTORY_SIZE
137 int "Per CPU History Size (32-65536)"
138 depends on VSERVER_HISTORY
142 This allows you to specify the number of entries in
143 the per CPU history buffer.