You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MemAvailable: An estimate of how much memory is available for starting new
applications, without swapping. Calculated from MemFree,
SReclaimable, the size of the file LRU lists, and the low
watermarks in each zone.
The estimate takes into account that the system needs some
page cache to function well, and that not all reclaimable
slab will be reclaimable, due to items being in use. The
impact of those factors will vary from system to system.
MemAvailable details the amount of memory that is available for a new workload without the need for swapping. In the past it was possible to calculate this figure by adding the "MemFree" and "Cached" values together, however this is is pretty much guaranteed to be wrong in systems running Kernels since 3.14.
Could this be added? The Slab allocation in the Linux Kernel tends to be higher giving inaccurate values in MemFree.
The text was updated successfully, but these errors were encountered:
In Linux kernel release 3.14 a new metric has been introduced in “/proc/meminfo” called "MemAvailable".
https://www.kernel.org/doc/Documentation/filesystems/proc.txt
Further details in the original commit:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=34e431b0ae398fc54ea69ff85ec700722c9da773
MemAvailable details the amount of memory that is available for a new workload without the need for swapping. In the past it was possible to calculate this figure by adding the "MemFree" and "Cached" values together, however this is is pretty much guaranteed to be wrong in systems running Kernels since 3.14.
Could this be added? The Slab allocation in the Linux Kernel tends to be higher giving inaccurate values in MemFree.
The text was updated successfully, but these errors were encountered: