|
@@ -854,16 +854,15 @@ Committed_AS: The amount of memory presently allocated on the system.
|
|
|
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
|