From: Dave Hansen <haveblue@us.ibm.com>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: /proc/meminfo
Date: Mon, 16 May 2005 10:30:29 -0700 [thread overview]
Message-ID: <1116264629.1005.75.camel@localhost> (raw)
In-Reply-To: <6934efce05051610252b84713f@mail.gmail.com>
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>
next prev parent reply other threads:[~2005-05-16 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 17:25 /proc/meminfo Jared Hulbert
2005-05-16 17:30 ` Dave Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-06 11:16 /proc/meminfo Abu M. Muttalib
2006-06-06 11:28 ` /proc/meminfo Jiri Slaby
2006-06-05 14:36 /proc/meminfo Abu M. Muttalib
2006-06-06 9:37 ` /proc/meminfo Jes Sorensen
2003-11-18 12:11 /proc/meminfo Dan Am
[not found] <224CFA9643B4CE4BA18137CF73DB2F32020E0DC0@broexc01.emea.cpqcorp.net>
2003-06-04 6:52 ` /proc/meminfo William Lee Irwin III
2003-06-03 13:51 /proc/meminfo Roets, Chris (Tru64&Linux support)
2003-06-03 14:05 ` /proc/meminfo William Lee Irwin III
2003-06-02 11:55 /proc/meminfo Roets, Chris (Tru64&Linux support)
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=1116264629.1005.75.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.