diff options
| author | Daniel Walker <dwalker@fifo99.com> | 2009-07-05 16:32:44 (GMT) |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2009-09-15 19:01:26 (GMT) |
| commit | 272bb3d8759448b2017aee149d226d7bf2d2bbb7 (patch) | |
| tree | 63f3b9a5c052a8f903a3cd95fcd94297c62b5663 /drivers/staging/android/lowmemorykiller.txt | |
| parent | edd540ea92954f896bfb7ee0ebf5dfdde6e6cb41 (diff) | |
| download | linux-fsl-qoriq-272bb3d8759448b2017aee149d226d7bf2d2bbb7.tar.xz | |
Staging: android: lowmemorykiller: delete the decription file
Move the lowmemorykiller.txt into the actual source file which is really the
correct place for it, and delete lowmemorykiller.txt.
Signed-off-by: Daniel Walker <dwalker@fifo99.com>
Cc: Arve Hjønnevåg <arve@android.com>
Cc: Brian Swetland <swetland@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/staging/android/lowmemorykiller.txt')
| -rw-r--r-- | drivers/staging/android/lowmemorykiller.txt | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/drivers/staging/android/lowmemorykiller.txt b/drivers/staging/android/lowmemorykiller.txt deleted file mode 100644 index bd5c0c0..0000000 --- a/drivers/staging/android/lowmemorykiller.txt +++ /dev/null @@ -1,16 +0,0 @@ -The lowmemorykiller driver lets user-space specify a set of memory thresholds -where processes with a range of oom_adj values will get killed. Specify the -minimum oom_adj values in /sys/module/lowmemorykiller/parameters/adj and the -number of free pages in /sys/module/lowmemorykiller/parameters/minfree. Both -files take a comma separated list of numbers in ascending order. - -For example, write "0,8" to /sys/module/lowmemorykiller/parameters/adj and -"1024,4096" to /sys/module/lowmemorykiller/parameters/minfree to kill processes -with a oom_adj value of 8 or higher when the free memory drops below 4096 pages -and kill processes with a oom_adj value of 0 or higher when the free memory -drops below 1024 pages. - -The driver considers memory used for caches to be free, but if a large -percentage of the cached memory is locked this can be very inaccurate -and processes may not get killed until the normal oom killer is triggered. - |