From: Jared Hulbert <jaredeh@gmail.com>
To: linux-mm <linux-mm@kvack.org>
Subject: /proc/meminfo
Date: Mon, 16 May 2005 10:25:33 -0700 [thread overview]
Message-ID: <6934efce05051610252b84713f@mail.gmail.com> (raw)
Please have mercy on a linux-mm newbie. I'd like to understand the
output of /proc/meminfo and /proc/<[0-9]+>/maps. I want to measure 2
things: First, how much memory in a system is used for code or other
readonly file mmaps or what RAM can be saved by using XIP flash.
Second, at the time a system snapshot is taken how much RAM is
absolutely needed (for example, I assume we could dump caches, flush
buffers, and clean up unused memory.)
Where can I find a good reference to what this all output means? Are
there other sources of information available?
Here are my assumptions:
# cat /proc/meminfo
MemTotal: = Memory managed by Linux kernel. Total RAM - kernel image.
MemFree: = Memory not allocated. Not the same as memory availiable to allocate.
Buffers: = ?
Cached: = inode cache
SwapCached: = Used swap space
Active: = Pages allocated by kernel and user processes
Inactive: = Pages allocated but read to be purged
HighTotal: = 2Gig limit stuff
HighFree: = ""
LowTotal: = ""
LowFree: = ""
SwapTotal: = What is the relationship between this and SwapCached?
SwapFree: = ""
Dirty: = ?
Writeback: = ?
Slab: = ?
CommitLimit: = ?
Commited_AS: = ?
PageTables: = Memory allocated for use as page tables.
VmallocTotal: = Virtual memory space allocated
VmallocUsed: = ?
VmallocChunk: = ?
# cat /proc/1/maps
08048000-0804E000 r-xp 00000000 75:00 637746 /sbin/init
(readonly, executable mmap of file /sbin/init Probably code)
0804E000-0804F000 rw-p 00000000 75:00 637746 /sbin/init
(readwrite, mmap of file /sbin/init Probably initialized variables
etc)
0804F000-08070000 rw-p 0804F000 00:00 0 (I don't know)
1st column = virtual memory map of map
2nd column = r = read; w = write; x = executable; p = I don't know
3rd column = I don't know
4th column = size of map (but it often doesn't match the size of column 1)
5th column = name of file
--
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:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2005-05-16 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 17:25 Jared Hulbert [this message]
2005-05-16 17:30 ` /proc/meminfo Dave Hansen
2006-06-05 14:36 /proc/meminfo Abu M. Muttalib
2006-06-06 9:37 ` /proc/meminfo Jes Sorensen
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=6934efce05051610252b84713f@mail.gmail.com \
--to=jaredeh@gmail.com \
--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