[VM Documentation 1/2]: Remove old 2.2 and very early 2.4 cruft Signed-off-by: Marc-Christian Petersen --- a/Documentation/sysctl/vm.txt 2002-11-28 16:53:08.000000000 +0200 +++ b/Documentation/sysctl/vm.txt 2003-11-12 17:35:11.000000000 +0200 @@ -18,13 +18,10 @@ Currently, these files are in /proc/sys/vm: - bdflush -- buffermem -- freepages - kswapd - max_map_count - overcommit_memory - page-cluster -- pagecache - pagetable_cache ============================================================== @@ -102,38 +99,6 @@ of buffer cache that is dirty which will stop bdflush. The default is 20%, the miniumum is 0%, and the maxiumum is 100%. ============================================================== -buffermem: - -The three values in this file correspond to the values in -the struct buffer_mem. It controls how much memory should -be used for buffer memory. The percentage is calculated -as a percentage of total system memory. - -The values are: -min_percent -- this is the minimum percentage of memory - that should be spent on buffer memory -borrow_percent -- UNUSED -max_percent -- UNUSED - -============================================================== -freepages: - -This file contains the values in the struct freepages. That -struct contains three members: min, low and high. - -The meaning of the numbers is: - -freepages.min When the number of free pages in the system - reaches this number, only the kernel can - allocate more memory. -freepages.low If the number of free pages gets below this - point, the kernel starts swapping aggressively. -freepages.high The kernel tries to keep up to this amount of - memory free; if memory comes below this point, - the kernel gently starts swapping in the hopes - that it never has to do real aggressive swapping. - -============================================================== kswapd: @@ -208,24 +173,6 @@ ============================================================== -pagecache: - -This file does exactly the same as buffermem, only this -file controls the struct page_cache, and thus controls -the amount of memory used for the page cache. - -In 2.2, the page cache is used for 3 main purposes: -- caching read() data from files -- caching mmap()ed data and executable files -- swap cache - -When your system is both deep in swap and high on cache, -it probably means that a lot of the swapped data is being -cached, making for more efficient swapping than possible -with the 2.0 kernel. - -============================================================== - pagetable_cache: The kernel keeps a number of page tables in a per-processor --- a/Documentation/filesystems/proc.txt 2004-05-21 22:54:13.000000000 +0200 +++ b/Documentation/filesystems/proc.txt 2004-05-23 00:08:09.000000000 +0200 @@ -999,54 +999,6 @@ nfract_sync nfract_stop_bdflush ------------------- -buffermem ---------- - -The three values in this file control how much memory should be used for -buffer memory. The percentage is calculated as a percentage of total system -memory. - -The values are: - -min_percent ------------ - -This is the minimum percentage of memory that should be spent on buffer -memory. - -borrow_percent --------------- - -When Linux is short on memory, and the buffer cache uses more than it has been -allotted, the memory management (MM) subsystem will prune the buffer cache -more heavily than other memory to compensate. - -max_percent ------------ - -This is the maximum amount of memory that can be used for buffer memory. - -freepages ---------- - -This file contains three values: min, low and high: - -min ---- -When the number of free pages in the system reaches this number, only the -kernel can allocate more memory. - -low ---- -If the number of free pages falls below this point, the kernel starts swapping -aggressively. - -high ----- -The kernel tries to keep up to this amount of memory free; if memory falls -below this point, the kernel starts gently swapping in the hopes that it never -has to do really aggressive swapping. - kswapd ------ @@ -1073,16 +1025,6 @@ This is the minimum number of times ks is called. Basically it's just there to make sure that kswapd frees some pages even when it's being called with minimum priority. -swap_cluster ------------- - -This is probably the greatest influence on system performance. - -swap_cluster is the number of pages kswapd writes in one turn. You'll want -this value to be large so that kswapd does its I/O in large chunks and the -disk doesn't have to seek as often, but you don't want it to be too large -since that would flood the request queue. - overcommit_memory ----------------- @@ -1097,15 +1039,6 @@ On the other hand, enabling this feat and thrash the system to death, so large and/or important servers will want to set this value to 0. -pagecache ---------- - -This file does exactly the same job as buffermem, only this file controls the -amount of memory allowed for memory mapping and generic caching of files. - -You don't want the minimum level to be too low, otherwise your system might -thrash when memory is tight or fragmentation is high. - pagetable_cache ---------------