aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorRik van Riel <riel@redhat.com>2014-01-21 18:49:05 -0500
committerLinus Torvalds <torvalds@linux-foundation.org>2014-01-21 19:19:43 -0500
commit34e431b0ae398fc54ea69ff85ec700722c9da773 (patch)
treea2a0de67b4cc754b5aa7627df3b0d1778d4cf10f /Documentation
parent5eaf1a9e233d61438377f57facb167f8208ba9fd (diff)
/proc/meminfo: provide estimated available memory
Many load balancing and workload placing programs check /proc/meminfo to estimate how much free memory is available. They generally do this by adding up "free" and "cached", which was fine ten years ago, but is pretty much guaranteed to be wrong today. It is wrong because Cached includes memory that is not freeable as page cache, for example shared memory segments, tmpfs, and ramfs, and it does not include reclaimable slab memory, which can take up a large fraction of system memory on mostly idle systems with lots of files. Currently, the amount of memory that is available for a new workload, without pushing the system into swap, can be estimated from MemFree, Active(file), Inactive(file), and SReclaimable, as well as the "low" watermarks from /proc/zoneinfo. However, this may change in the future, and user space really should not be expected to know kernel internals to come up with an estimate for the amount of free memory. It is more convenient to provide such an estimate in /proc/meminfo. If things change in the future, we only have to change it in one place. Signed-off-by: Rik van Riel <riel@redhat.com> Reported-by: Erik Mouw <erik.mouw_2@nxp.com> Acked-by: Johannes Weiner <hannes@cmpxchg.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/filesystems/proc.txt9
1 files changed, 9 insertions, 0 deletions
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
index 22d89aa37218..8533f5f9bb2d 100644
--- a/Documentation/filesystems/proc.txt
+++ b/Documentation/filesystems/proc.txt
@@ -767,6 +767,7 @@ The "Locked" indicates whether the mapping is locked in memory or not.
767 767
768MemTotal: 16344972 kB 768MemTotal: 16344972 kB
769MemFree: 13634064 kB 769MemFree: 13634064 kB
770MemAvailable: 14836172 kB
770Buffers: 3656 kB 771Buffers: 3656 kB
771Cached: 1195708 kB 772Cached: 1195708 kB
772SwapCached: 0 kB 773SwapCached: 0 kB
@@ -799,6 +800,14 @@ AnonHugePages: 49152 kB
799 MemTotal: Total usable ram (i.e. physical ram minus a few reserved 800 MemTotal: Total usable ram (i.e. physical ram minus a few reserved
800 bits and the kernel binary code) 801 bits and the kernel binary code)
801 MemFree: The sum of LowFree+HighFree 802 MemFree: The sum of LowFree+HighFree
803MemAvailable: An estimate of how much memory is available for starting new
804 applications, without swapping. Calculated from MemFree,
805 SReclaimable, the size of the file LRU lists, and the low
806 watermarks in each zone.
807 The estimate takes into account that the system needs some
808 page cache to function well, and that not all reclaimable
809 slab will be reclaimable, due to items being in use. The
810 impact of those factors will vary from system to system.
802 Buffers: Relatively temporary storage for raw disk blocks 811 Buffers: Relatively temporary storage for raw disk blocks
803 shouldn't get tremendously large (20MB or so) 812 shouldn't get tremendously large (20MB or so)
804 Cached: in-memory cache for files read from the disk (the 813 Cached: in-memory cache for files read from the disk (the