linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Improve documentation request for /proc/meminfo (proc.txt)
Date: Wed, 03 May 2017 13:32:38 +0200	[thread overview]
Message-ID: <5909BFD6020000A100025CBF@gwsmtp1.uni-regensburg.de> (raw)
In-Reply-To: <5909BFD6020000A100025CBF@gwsmtp1.uni-regensburg.de>

Hi!

Reading /usr/src/linux/Documentation/filesystems/proc.txt leaves some questions open. For example some values are break-downs of others. I'd like to see documentation on how these relate. For example (3.0.101):

MemTotal:       132156332 kB
MemFree:        22448480 kB
Buffers:         1484072 kB
Cached:         81252832 kB
SwapCached:            0 kB
Active:         24216920 kB
Inactive:       65789500 kB
Active(anon):   20268724 kB
Inactive(anon):  4617808 kB
Active(file):    3948196 kB
Inactive(file): 61171692 kB
Unevictable:       48840 kB
Mlocked:           30444 kB
SwapTotal:      20964788 kB
SwapFree:       20964788 kB
Dirty:               496 kB
Writeback:             0 kB
AnonPages:       7317972 kB
Mapped:         15927688 kB
Shmem:          17602008 kB
Slab:            1162160 kB
SReclaimable:     907496 kB
SUnreclaim:       254664 kB
KernelStack:        8864 kB
PageTables:      1361780 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    79158152 kB
Committed_AS:   66056192 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      305164 kB
VmallocChunk:   34292267888 kB
HardwareCorrupted:     0 kB
AnonHugePages:   4997120 kB
HugePages_Total:    7700
HugePages_Free:       62
HugePages_Rsvd:       44
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:      301296 kB
DirectMap2M:    19611648 kB
DirectMap1G:    114294784 kB

Which numbers sum up to MemTotal? It seems Active(anon) + Active(file) == Active (and similar for inactive).
What is the relation between Unevictable and Mlocked? Is "Unevictable >= Mlocked" all the time?
It would give some insight how things work if you document the relations between some of these numbers.

(I'm hunting for a condition for very bad disk response times, suspecting some memory pressure. I suspect too many dirty pages for some reason...)

Regards,
Ulrich





--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

           reply	other threads:[~2017-05-03 11:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5909BFD6020000A100025CBF@gwsmtp1.uni-regensburg.de>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5909BFD6020000A100025CBF@gwsmtp1.uni-regensburg.de \
    --to=ulrich.windl@rz.uni-regensburg.de \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox