diff -urN linux-2.6.11-no1-org/init/Kconfig linux-2.6.11-no1-darkmenu/init/Kconfig --- linux-2.6.11-no1-org/init/Kconfig 2005-03-30 22:05:59.000000000 -0500 +++ linux-2.6.11-no1-darkmenu/init/Kconfig 2005-03-30 22:50:13.000000000 -0500 @@ -229,6 +229,22 @@ Say N if unsure. +config BASE_TIMESLICE + int "Base timeslice" + range 30 260 + default 128 + help + Here you must select a base timeslice value for + nicksched. Timeslices are a value which represent + how long a task can run before its preempted. + Lower values mean more overhead, higher values + means less interactivity. Preemptible desktops + should enter 64 here. Non-preemptible desktops + should leave the default here. Servers should + enter 256 here. + + If unsure, say 128. + menuconfig EMBEDDED bool "Configure standard kernel features (for small systems)" help @@ -361,6 +377,8 @@ default 0 if BASE_FULL default 1 if !BASE_FULL +source "init/Kconfig.vm" + menu "Loadable module support" config MODULES diff -urN linux-2.6.11-no1-org/init/Kconfig.vm linux-2.6.11-no1-darkmenu/init/Kconfig.vm --- linux-2.6.11-no1-org/init/Kconfig.vm 1969-12-31 19:00:00.000000000 -0500 +++ linux-2.6.11-no1-darkmenu/init/Kconfig.vm 2005-03-30 22:52:27.000000000 -0500 @@ -0,0 +1,19 @@ +menu "VM Configuration" +config VM_MAPPED + int "Mapped percentage" + range 0 100 + default 66 + help + The mapped percentage value effects swap usage. + Higher values means less swap usage, but more + likeliness of processes getting OOM killed. + Lower values means less likeliness of OOM + killing, but more swap usage. For preemptible + desktop usage, a value of 75 is recommended. + For general desktop usage, a value of 66 is + recommended. For server usage, a value of 0 is + recommended. + + If unsure, say 66. + +endmenu diff -urN linux-2.6.11-no1-org/kernel/sched.c linux-2.6.11-no1-darkmenu/kernel/sched.c --- linux-2.6.11-no1-org/kernel/sched.c 2005-03-30 22:10:54.000000000 -0500 +++ linux-2.6.11-no1-darkmenu/kernel/sched.c 2005-03-30 22:35:59.000000000 -0500 @@ -80,7 +80,7 @@ * that the maximum priority process will get. Larger timeslices are attainable * by low priority processes however. */ -int sched_base_timeslice = 256; +int sched_base_timeslice = CONFIG_BASE_TIMESLICE; int sched_min_base = 1; int sched_max_base = 10000; diff -urN linux-2.6.11-no1-org/mm/vmscan.c linux-2.6.11-no1-darkmenu/mm/vmscan.c --- linux-2.6.11-no1-org/mm/vmscan.c 2005-03-30 22:10:54.000000000 -0500 +++ linux-2.6.11-no1-darkmenu/mm/vmscan.c 2005-03-30 22:51:40.000000000 -0500 @@ -122,7 +122,7 @@ #define prefetchw_prev_lru_page(_page, _base, _field) do { } while (0) #endif -int vm_mapped = 66; +int vm_mapped = CONFIG_VM_MAPPED; int vm_hardmaplimit = 1; static long total_memory;