9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] output of ps(1) memory usage
Date: Thu, 20 Feb 2003 21:30:58 -0500	[thread overview]
Message-ID: <ea8525a3117c17c9bdf4e0d4cd1153f7@plan9.bell-labs.com> (raw)
In-Reply-To: <dfb68cded1c026df2ea5763d7db55859@orthanc.cc.titech.ac.jp>

ps shows how much is physically mapped within
a process, and reading /proc/pid/segment will
show you exactly where it is mapped.

the hard part comes when you want to figure out
the total for a set of processes, because figuring
out the intersection is not so easy.

for procs sharing memory, only the stacks are
different, and stacks tend to be only a page or two,
so as rob said, what's listed in ps applies to the
collection of procs pretty well.



  reply	other threads:[~2003-02-21  2:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <uncover@beat.cc.titech.ac.jp>
2003-02-21  2:27 ` YAMANASHI Takeshi
2003-02-21  2:30   ` Russ Cox [this message]
2003-02-21  2:42   ` Scott Schwartz
2003-02-21  7:09 YAMANASHI Takeshi
2003-02-21 15:06 ` Russ Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-02-21  5:47 YAMANASHI Takeshi
2003-02-21  5:55 ` Russ Cox
2003-02-21  3:09 okamoto
2003-02-21  2:43 David Presotto
2003-02-21  2:34 okamoto
2003-02-21  2:37 ` Russ Cox
2003-02-21  2:06 okamoto
2003-02-21  2:08 ` Russ Cox
2003-02-21  1:55 okamoto
2003-02-21  0:51 okamoto
2003-02-21  1:10 ` Russ Cox
2003-02-21  1:18   ` rob pike, esq.
2003-02-21  2:23 ` David Presotto

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=ea8525a3117c17c9bdf4e0d4cd1153f7@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).