Hi,
I've written a patch that adds some more documentation to the
vserver kernel config options. I hope it makes the effect of these
options a bit clearer for people.

CONFIG_VSERVER_HARDCPU stuff is taken from the wiki (and was the
reason I wrote this patch in the first place), and is thusly
licensed under the FDL. Just in case someone cares.

Patch is attatched.

Cheers,
Christian Aichinger
--- linux/kernel/vserver/Kconfig        2005-06-18 22:05:30.000000000 +0200
+++ linux2/kernel/vserver/Kconfig       2005-06-18 23:01:35.000000000 +0200
@@ -24,7 +24,9 @@
        default y
        help
          This enables the legacy API used in vs1.xx, which allows
-         to use older tools (for migration purposes).
+         to use older tools.
+
+         This is only needed when migrating from older versions.
 
 config VSERVER_NGNET
        bool    "Disable Legacy Networking Kernel API"
@@ -42,6 +44,10 @@
        help
          Hide proc entries by default for xid>1
 
+         This enables hiding specific entries in procfs for guest
+         contexts by default. So you'll have to allow guests to access
+         procfs entries manually, which is potenitally more secure.
+
 config VSERVER_HARDCPU
        bool    "Enable Hard CPU Limits"
        depends on EXPERIMENTAL
@@ -49,6 +55,14 @@
        help
          Activate the Hard CPU Limits
 
+         Linux-VServer supports a token bucket scheduler to adjust
+         cpu usage of the vservers. If you don't enable this option,
+         the scheduler will only adjust priorities for the vservers,
+         with this option enabled, you can also choose to use the
+         hard scheduler which will put the context on hold if it has
+         used up its cpu tokens. For details, please take a look at
+         documentation specific to this feature.
+
 config VSERVER_HARDCPU_IDLE
        bool    "Limit the IDLE task"
        depends on VSERVER_HARDCPU
@@ -121,7 +135,7 @@
        help
          Set this to yes if you want to be able to activate
          debugging output at runtime. It adds a probably small
-         overhead (~ ??%) to all vserver related functions and
+         overhead to all vserver related functions and
          increases the kernel size by about 20k.
 
 config VSERVER_HISTORY

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to