Editing Swappolube
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 127: | Line 127: | ||
===Laptop Mode=== | ===Laptop Mode=== | ||
- | * Description: When the | + | * Description: laptop_mode is a knob that controls "laptop mode". When the knob is set, any physical disk I/O (that might have caused the hard disk to spin up, see <code>/proc/sys/vm/block_dump</code>) causes Linux to flush all dirty blocks. The result of this is that after a disk has spun down, it will not be spun up anymore to write dirty blocks, because those blocks had already been written immediately after the most recent read operation. The value of the laptop_mode knob determines the time between the occurrence of disk I/O and when the flush is triggered. A sensible value for the knob is 5 seconds. Setting the knob to 0 disables laptop mode. Since this mode has been designed with mechanical hard drives in mind to maximize the time between spin-ups that the flash memory in a cellphone does not need to worry itself with, it might actually be better to set this to zero. |
* Default: "0" | * Default: "0" | ||
* Suggested: "1" | * Suggested: "1" | ||
Line 134: | Line 134: | ||
===oom_kill_allocating_task=== | ===oom_kill_allocating_task=== | ||
- | * Description: This enables or disables killing the OOM-triggering task in out-of-memory situations. If this is set to zero, the OOM killer will scan through the entire tasklist and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive tasklist scan | + | * Description: This enables or disables killing the OOM-triggering task in out-of-memory situations. If this is set to zero, the OOM killer will scan through the entire tasklist and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive tasklist scan. If panic_on_oom is selected, it takes precedence over whatever value is used in oom_kill_allocating_task. Taken from: [http://www.linuxinsight.com/proc_sys_vm_oom_kill_allocating_task.html] |
* Default: "0" | * Default: "0" | ||
* Suggested: "1" | * Suggested: "1" | ||
Line 169: | Line 169: | ||
===tcp_timestamps=== | ===tcp_timestamps=== | ||
- | * Description: Enable timestamps as defined in RFC1323. [http://www.linuxinsight.com/proc_sys_net_ipv4_tcp_timestamps.html] | + | * Description: Enable timestamps as defined in RFC1323. [http://www.linuxinsight.com/proc_sys_net_ipv4_tcp_timestamps.html] |
* Default: "1" | * Default: "1" | ||
* Suggested: "0" | * Suggested: "0" |
Learn more about Contributing to the wiki.