From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] output of ps(1) memory usage
Date: Fri, 21 Feb 2003 16:09:37 +0900 [thread overview]
Message-ID: <e3382ee2b6c9126f8c207411bebd92a2@orthanc.cc.titech.ac.jp> (raw)
> /proc/pid/segment shows you virtual memory allocation,
> not physical.
I still had mistaken without your explanation.
Segment gives virtual memory information and `ps' physical.
I feel fine now.
--
YAMANASHI Takeshi
next reply other threads:[~2003-02-21 7:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 7:09 YAMANASHI Takeshi [this message]
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
[not found] <uncover@beat.cc.titech.ac.jp>
2003-02-21 2:27 ` YAMANASHI Takeshi
2003-02-21 2:30 ` Russ Cox
2003-02-21 2:42 ` Scott Schwartz
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=e3382ee2b6c9126f8c207411bebd92a2@orthanc.cc.titech.ac.jp \
--to=uncover@beat.cc.titech.ac.jp \
--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).