summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPetr Oros <poros@redhat.com>2014-05-22 14:04:44 +0200
committerJiri Kosina <jkosina@suse.cz>2014-05-22 23:01:55 +0200
commit7a9e6da11c9478741947de3a37ac7de26abd23f0 (patch)
treee80b0918bec7a76b4262e76900000d83e4cb4304
parent221069bed0c73e876e1df1f6cd0140cb353fcd32 (diff)
downloadblackbird-op-linux-7a9e6da11c9478741947de3a37ac7de26abd23f0.tar.gz
blackbird-op-linux-7a9e6da11c9478741947de3a37ac7de26abd23f0.zip
doc: fix incorrect formula to calculate CommitLimit value
The formula to calculate "CommitLimit" value mentioned in kernel documentation is incorrect. Right formula is: CommitLimit = ([total RAM pages] - [total huge TLB pages]) * overcommit_ratio / 100 + [total swap pages] Signed-off-by: Petr Oros <poros@redhat.com> Acked-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
-rw-r--r--Documentation/filesystems/proc.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
index d4fa7f52034e..324328d18464 100644
--- a/Documentation/filesystems/proc.txt
+++ b/Documentation/filesystems/proc.txt
@@ -854,7 +854,8 @@ WritebackTmp: Memory used by FUSE for temporary writeback buffers
if strict overcommit accounting is enabled (mode 2 in
'vm.overcommit_memory').
The CommitLimit is calculated with the following formula:
- CommitLimit = ('vm.overcommit_ratio' * Physical RAM) + Swap
+ CommitLimit = ([total RAM pages] - [total huge TLB pages]) *
+ overcommit_ratio / 100 + [total swap pages]
For example, on a system with 1G of physical RAM and 7G
of swap with a `vm.overcommit_ratio` of 30 it would
yield a CommitLimit of 7.3G.
OpenPOWER on IntegriCloud