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 37: Line 37:
** Checkbox: if checked will propagate a "1", if not checked it will be a "0" , i.e. set True or False for this option.
** Checkbox: if checked will propagate a "1", if not checked it will be a "0" , i.e. set True or False for this option.
-
[[Image:swappolubeMain.png|400px|Main View]]  
+
''note'': since version [[Swappolube#1.4-1]] the application supports rotation depending the orientation of the device.
 +
 
 +
[[Image:swappolubeMain.png|400px|Main View]] [[Image:swappolubeMain_rotated.png|280px|Main View - rotated]]
The centre part of the UI is a scrollable list.  
The centre part of the UI is a scrollable list.  
Line 43: Line 45:
[[Image:swappolubeMain2.png|400px]]  
[[Image:swappolubeMain2.png|400px]]  
-
 
-
''note'': since version [[Swappolube#1.4-1|1.4]] the application supports rotation depending the orientation of the device.
 
-
 
-
[[Image:swappolubeMain_rotated.png|280px|Main View - rotated]]
 
[[Image:swappolubeMain2_rotated.png|280px]]  
[[Image:swappolubeMain2_rotated.png|280px]]  
Line 104: Line 102:
(like all the rest of the windows it supports rotation).
(like all the rest of the windows it supports rotation).
   
   
-
[[Image:swappolube_about1.png|280px]]
+
[[Image:swappolube_about1.png|360px]]
-
[[Image:swappolube_about2.png|280px]]
+
[[Image:swappolube_about2.png|360px]]
==Explanation of options==
==Explanation of options==
Line 127: Line 125:
===Laptop Mode===
===Laptop Mode===
-
* Description: When the value for laptop_mode is set to be something other than zero, 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 after the value in seconds. 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.
+
* 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.
* Default: "0"
* Default: "0"
* Suggested: "1"
* Suggested: "1"
Line 134: Line 132:
===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 and the potential randomness of the task that the manager picked to kill. 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]
+
* 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 167:
===tcp_timestamps===
===tcp_timestamps===
-
* Description: Enable timestamps as defined in RFC1323. [http://www.linuxinsight.com/proc_sys_net_ipv4_tcp_timestamps.html] Turning off TCP timestamps can be counterproductive, since timestamps are used to estimate data packet round-trip times and transmission timeouts. Disabling RFC1323 timestamps may then result in poor performance in conditions of frequent packet losses. The Swappolube suggested default is to turn them off, but it may not in fact be optimal.
+
* 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"
Line 190: Line 188:
==Versions==
==Versions==
-
===1.4-2  ([http://maemo.org/downloads/product/Maemo5/swappolube/ stable version])===
+
===1.4-2  ([http://maemo.org/downloads/product/Maemo5/swappolube/ current])===
====Changelog====
====Changelog====

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)