public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: "Ravinandan Arakali (rarakali)" <rarakali@cisco.com>
Cc: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question about free/used memory on Linux
Date: Wed, 14 Nov 2007 11:58:04 +0000	[thread overview]
Message-ID: <473AE2CC.4080609@draigBrady.com> (raw)
In-Reply-To: <FA6FB5FA4DA6BF4386D129273B2E3EC3024B859E@xmb-sjc-214.amer.cisco.com>

Ravinandan Arakali (rarakali) wrote:
> Hi Vaidy,
> What do you think is the right way to get the memory usage of a
> process, I mean the actual physical memory used ? Basically,
> I'm interested in the incremental cost of a process, which
> means, I don't want to include the text segments of shared
> libraries which would remain even after the process is killed
> (since it would be used by other processes).
> 
> Is the RSS field of "ps aux" command the right one or use 
> "pmap" command and look at the "writeable" segments ?

I already commented on this thread with a python script
for reporting RAM usage for programs.

RSS = Private and Shared Resident pages.
You can get the shared value for a process from /proc/$$/smaps
(as is done in the script)

Pádraig.

  reply	other threads:[~2007-11-14 11:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-21 17:54 Question about free/used memory on Linux Ravinandan Arakali (rarakali)
2007-10-21 19:00 ` Vaidyanathan Srinivasan
2007-10-21 20:21   ` Ravinandan Arakali (rarakali)
2007-10-22  5:50     ` Vaidyanathan Srinivasan
2007-10-22  6:28       ` Ravinandan Arakali (rarakali)
2007-11-14  6:14       ` Ravinandan Arakali (rarakali)
2007-11-14 11:58         ` Pádraig Brady [this message]
2007-11-14 18:18           ` Ravinandan Arakali (rarakali)
2007-10-22 11:51     ` Helge Hafting
2007-10-22 17:34     ` linux-os (Dick Johnson)
2007-10-22 10:05 ` Pádraig Brady
2007-10-23  1:58   ` Ravinandan Arakali (rarakali)

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=473AE2CC.4080609@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rarakali@cisco.com \
    --cc=svaidy@linux.vnet.ibm.com \
    /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