mirror of
https://github.com/Llewellynvdm/conky.git
synced 2024-12-27 20:44:56 +00:00
Fix size of the reported "buffers/cache" memory.
It now reports only reclaimable memory, by excluding shared memory, and including the reclaimable part of the SLAB cache. So '$mem' with 'no_buffers yes' is now the "really used" (unreclaimable) memory. And when reaching OOM conditions, conky will always report high memory usage. Related post: http://calimeroteknik.free.fr/blag/?article20/really-used-memory-on-gnu-linux
This commit is contained in:
parent
eef323eafd
commit
3e85698458
17
src/linux.cc
17
src/linux.cc
@ -171,6 +171,8 @@ int update_meminfo(void)
|
||||
/* unsigned int a; */
|
||||
char buf[256];
|
||||
|
||||
unsigned long long shmem = 0, sreclaimable = 0;
|
||||
|
||||
info.mem = info.memwithbuffers = info.memmax = info.memdirty = info.swap = info.swapfree = info.swapmax =
|
||||
info.bufmem = info.buffers = info.cached = info.memfree = info.memeasyfree = 0;
|
||||
|
||||
@ -197,6 +199,10 @@ int update_meminfo(void)
|
||||
sscanf(buf, "%*s %llu", &info.cached);
|
||||
} else if (strncmp(buf, "Dirty:", 6) == 0) {
|
||||
sscanf(buf, "%*s %llu", &info.memdirty);
|
||||
} else if (strncmp(buf, "Shmem:", 6) == 0) {
|
||||
sscanf(buf, "%*s %llu", &shmem);
|
||||
} else if (strncmp(buf, "SReclaimable:", 13) == 0) {
|
||||
sscanf(buf, "%*s %llu", &sreclaimable);
|
||||
}
|
||||
}
|
||||
|
||||
@ -204,7 +210,16 @@ int update_meminfo(void)
|
||||
info.memeasyfree = info.memfree;
|
||||
info.swap = info.swapmax - info.swapfree;
|
||||
|
||||
info.bufmem = info.cached + info.buffers;
|
||||
/* Reclaimable memory: does not include shared memory, which is part of cached but unreclaimable.
|
||||
Includes the reclaimable part of the Slab cache though.
|
||||
Note: when shared memory is swapped out, shmem decreases and swapfree decreases - we want this.
|
||||
*/
|
||||
info.bufmem = (info.cached - shmem) + info.buffers + sreclaimable;
|
||||
|
||||
/* Now (info.mem - info.bufmem) is the *really used* (aka unreclaimable) memory.
|
||||
When this value reaches the size of the physical RAM, and swap is full or non-present, OOM happens.
|
||||
Therefore this is the value users want to monitor, regarding their RAM.
|
||||
*/
|
||||
|
||||
fclose(meminfo_fp);
|
||||
return 0;
|
||||
|
Loading…
Reference in New Issue
Block a user