public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: P@draigBrady.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: How do you accurately determine a process' RAM usage?
Date: Thu, 7 Jul 2005 01:40:05 -0700	[thread overview]
Message-ID: <20050707014005.338ea657.akpm@osdl.org> (raw)
In-Reply-To: <42CCE737.70802@draigBrady.com>

P@draigBrady.com wrote:
>
> Andrew Morton wrote:
> > Calculating this stuff accurately is very expensive.  You'll get a better
> > answer using proc-pid-smaps.patch from -mm, but even that won't tell you
> > things about sharing levels of the pages.
> 
> Great, thanks! I'll play around with this:
> http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc1/2.6.13-rc1-mm1/broken-out/proc-pid-smaps.patch

OK, please let us know how it goes.

> Looks like it's been stable for 4 months?

yup, although I don't think it's been used much.

> Given that it's an independent /proc/$pid/smaps file,
> it only needs to be queried when required and so
> I wouldn't worry too much about cost. `top` wouldn't use it
> for e.g., but specialised tools like mine would.

I agree, but people get upset ;)

Plus some userspace tool developer might see it and start using it without
knowing the cost on big iron.

  reply	other threads:[~2005-07-07  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 18:55 How do you accurately determine a process' RAM usage? P
2005-07-07  1:16 ` Andrew Morton
2005-07-07  8:26   ` P
2005-07-07  8:40     ` Andrew Morton [this message]
2005-07-07 10:42       ` Hugh Dickins
2005-07-12  9:44       ` P
2005-07-19 20:09         ` Mauricio Lin
2005-07-20 14:34           ` P
2005-07-20 15:32             ` Mauricio Lin
2005-07-20 15:48               ` P

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=20050707014005.338ea657.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=P@draigBrady.com \
    --cc=linux-kernel@vger.kernel.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