From: Jeff Angielski <jangiels@speakeasy.net>
To: "antonio.dibacco" <antonio.dibacco@aruba.it>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Interpreting /proc/meminfo. How much free memory do I have?
Date: Mon, 27 Mar 2006 11:49:23 -0500 [thread overview]
Message-ID: <1143478163.7082.23.camel@sumo-jaa.nrl.navy.mil> (raw)
In-Reply-To: <20060327093822.480.qmail@mx1.aruba.it>
On Mon, 2006-03-27 at 09:38 +0000, antonio.dibacco wrote:
> I don't understand the meaning of "Inactive". They are not used but the
> kernel cannot give this memory to a requesting process because we tipically
> don't have a swap device on a linux embedded board. Where we can store the
> Inactive page? Am I wrong?
> If I run a process that continuosly allocates memory and print out the total
> allocated memory when it receives SIGINT or SIGTERM, I think I get the real
> "free memory"!
The "big picture" is that the kernel assumes that any physical memory
that is not used is being wasted. The kernel tries to anticipate what
data you will need and loads it into memory before you actually require
it. This way there is no time delay when you want to access it. So the
numbers are reflecting what the system/kernel is currentl using.
Even if you are on a system with no swap parition like your embedded
board, pages in memory that are read-only can still be swapped out since
they can always be read back in when needed. Sections like a
processes .text fit this category.
If you are trying to look at a specific process, perhaps looking at
the /proc/<pid>/status might help you analyze your memory needs.
Jeff Angielski
The PTR Group
prev parent reply other threads:[~2006-03-27 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 6:49 Interpreting /proc/meminfo. How much free memory do I have? antonio.dibacco
2006-03-27 7:53 ` Roger Larsson
2006-03-27 9:00 ` Eberhard Stoll
2006-03-27 9:38 ` antonio.dibacco
2006-03-27 16:49 ` Jeff Angielski [this message]
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=1143478163.7082.23.camel@sumo-jaa.nrl.navy.mil \
--to=jangiels@speakeasy.net \
--cc=antonio.dibacco@aruba.it \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).