2.6.9

 Documentation

 vm

diff -Nru a/Documentation/vm/overcommit-accounting b/Documentation/vm/overcommit-accounting
--- a/Documentation/vm/overcommit-accounting   2004-10-18 14:57:19 -07:00
+++ b/Documentation/vm/overcommit-accounting   2004-10-18 14:57:19 -07:00
@@ -1,4 +1,4 @@
-The Linux kernel supports three overcommit handling modes
+The Linux kernel supports the following overcommit handling modes
 
 0   -   Heuristic overcommit handling. Obvious overcommits of
       address space are refused. Used for a typical system. It
@@ -7,10 +7,10 @@
       allocate slighly more memory in this mode. This is the 
       default.
 
-1   -   No overcommit handling. Appropriate for some scientific
+1   -   Always overcommit. Appropriate for some scientific
       applications.
 
-2   -   (NEW) strict overcommit. The total address space commit
+2   -   Don't overcommit. The total address space commit
       for the system is not permitted to exceed swap + a
       configurable percentage (default is 50) of physical RAM.
       Depending on the percentage you use, in most situations
@@ -27,7 +27,7 @@
 
 The C language stack growth does an implicit mremap. If you want absolute
 guarantees and run close to the edge you MUST mmap your stack for the 
-largest size you think you will need. For typical stack usage is does
+largest size you think you will need. For typical stack usage this does
 not matter much but it's a corner case if you really really care
 
 In mode 2 the MAP_NORESERVE flag is ignored.