Documentation/vm/overcommit-accounting:6: ERROR: trailing whitespace Documentation/vm/overcommit-accounting:7: ERROR: trailing whitespace Documentation/vm/overcommit-accounting:32: ERROR: trailing whitespace Documentation/vm/overcommit-accounting:36: ERROR: trailing whitespace Signed-off-by: Andrea Gelmini <andrea.gelmini@xxxxxxxxx> --- Documentation/vm/overcommit-accounting | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/vm/overcommit-accounting b/Documentation/vm/overcommit-accounting index 21c7b1f..cd91491 100644 --- a/Documentation/vm/overcommit-accounting +++ b/Documentation/vm/overcommit-accounting @@ -3,8 +3,8 @@ 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 ensures a seriously wild allocation fails while allowing - overcommit to reduce swap usage. root is allowed to - allocate slighly more memory in this mode. This is the + overcommit to reduce swap usage. root is allowed to + allocate slighly more memory in this mode. This is the default. 1 - Always overcommit. Appropriate for some scientific @@ -29,11 +29,11 @@ Gotchas ------- 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 +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 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. +In mode 2 the MAP_NORESERVE flag is ignored. How It Works -- 1.7.1.251.gf80a2 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
