Subject: + fix-mistake-in-the-description-of-committed_as.patch added to -mm tree
To: mvaliyav@xxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Mon, 19 Aug 2013 16:06:21 -0700
The patch titled
Subject: Documentation/filesystems/proc.txt: fix mistake in the description of Committed_AS
has been added to the -mm tree. Its filename is
fix-mistake-in-the-description-of-committed_as.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/fix-mistake-in-the-description-of-committed_as.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/fix-mistake-in-the-description-of-committed_as.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Minto Joseph <mvaliyav@xxxxxxxxxx>
Subject: Documentation/filesystems/proc.txt: fix mistake in the description of Committed_AS
Fix mistake in the description of Committed_AS in kernel documentation.
Signed-off-by: Minto Joseph <mvaliyav@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/filesystems/proc.txt | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
diff -puN Documentation/filesystems/proc.txt~fix-mistake-in-the-description-of-committed_as Documentation/filesystems/proc.txt
--- a/Documentation/filesystems/proc.txt~fix-mistake-in-the-description-of-committed_as
+++ a/Documentation/filesystems/proc.txt
@@ -854,16 +854,15 @@ Committed_AS: The amount of memory prese
The committed memory is a sum of all of the memory which
has been allocated by processes, even if it has not been
"used" by them as of yet. A process which malloc()'s 1G
- of memory, but only touches 300M of it will only show up
- as using 300M of memory even if it has the address space
- allocated for the entire 1G. This 1G is memory which has
- been "committed" to by the VM and can be used at any time
- by the allocating application. With strict overcommit
- enabled on the system (mode 2 in 'vm.overcommit_memory'),
- allocations which would exceed the CommitLimit (detailed
- above) will not be permitted. This is useful if one needs
- to guarantee that processes will not fail due to lack of
- memory once that memory has been successfully allocated.
+ of memory, but only touches 300M of it will show up as
+ using 1G. This 1G is memory which has been "committed" to
+ by the VM and can be used at any time by the allocating
+ application. With strict overcommit enabled on the system
+ (mode 2 in 'vm.overcommit_memory'),allocations which would
+ exceed the CommitLimit (detailed above) will not be permitted.
+ This is useful if one needs to guarantee that processes will
+ not fail due to lack of memory once that memory has been
+ successfully allocated.
VmallocTotal: total size of vmalloc memory area
VmallocUsed: amount of vmalloc area which is used
VmallocChunk: largest contiguous block of vmalloc area which is free
_
Patches currently in -mm which might be from mvaliyav@xxxxxxxxxx are
fix-mistake-in-the-description-of-committed_as.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
