/proc/meminfo

/proc/meminfo

[Jared Hulbert]

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>

Re: /proc/meminfo

[Dave Hansen]

On Mon, 2005-05-16 at 10:25 -0700, Jared Hulbert wrote:
> 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?

Documentation/filesystems/proc.txt

-- Dave

--
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>

Re: /proc/meminfo

[Jes Sorensen]

>>>>> "Abu" == Abu M Muttalib <abum@aftek.com> writes:

Abu> Hi, Does /proc/meminfo provides reliable information?

Yes

Jes

--
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>

/proc/meminfo

[Abu M. Muttalib]

Hi,

Does /proc/meminfo provides reliable information?

~Abu.

--
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>