From: Andrea Arcangeli <andrea@novell.com>
To: Albert Cahalan <albert@users.sf.net>
Cc: Hugh Dickins <hugh@veritas.com>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton OSDL <akpm@osdl.org>,
William Lee Irwin III <wli@holomorphy.com>,
Albert Cahalan <albert@users.sourceforge.net>
Subject: Re: per-process shared information
Date: Fri, 15 Oct 2004 20:14:46 +0200 [thread overview]
Message-ID: <20041015181446.GF17849@dualathlon.random> (raw)
In-Reply-To: <1097862714.2666.13650.camel@cube>
On Fri, Oct 15, 2004 at 01:51:56PM -0400, Albert Cahalan wrote:
> Sure. That's not because of RSS. It's for TRS and DRS,
> which are supposed to be RSS-like values specific to
> text (code) and data.
And they're not RSS-like right now if you pick them from statm, the only
RSS-like variable is rss itself in 2.6 ;).
*data = mm->total_vm - mm->shared_vm
all those are virtual, not physical. dunno about 2.4, but I doubt 2.4
would be much different, rss + shared where the only physical driven
things in 2.4 IIRC. (now only rss is left, and Hugh's patch adds
anon_rss back)
to me TRS and DRS have always been _virtual_ when I read the ps output,
obviously since DRS tends to be orders of magnitude bigger than RSS
itself ;).
> The VM size of text is TSIZ, and of data is DSIZ.
> These numbers, while useful, are not the same thing.
those should come out of statm pretty nicely.
> A user can configure top to display other columns if
> he has a box that can't handle /proc/*/statm well.
> The file will not be read if it is not needed.
> Start top, then do:
>
> f enters field modification screen
> o disable VIRT
> q disable RES
> t disable SHR
> n disable %MEM
> enter exits field modification screen
> W writes a ~/.toprc file
>
> So, what is the problem again? :-)
that you can't get those values efficiently. Even assuming you're ok to
drop shared by disabling SHR, it wouldn't help, without a kernel API
change.
> Well, as long as it makes the users happy... I don't personally
> care, except to say that I don't care to document all sorts
> of kernel-specific variations. It gets hopelessly messy.
Yep, I believe users could be happy with Hugh's rss-anon_rss variant.
next prev parent reply other threads:[~2004-10-15 18:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 23:10 per-process shared information Andrea Arcangeli
2004-10-14 21:47 ` Marcelo Tosatti
2004-10-14 23:58 ` Andrea Arcangeli
2004-10-14 23:17 ` Marcelo Tosatti
2004-10-15 10:45 ` William Lee Irwin III
2004-10-14 21:49 ` Hugh Dickins
2004-10-14 22:11 ` William Lee Irwin III
2004-10-14 22:37 ` Andrea Arcangeli
2004-10-15 10:51 ` William Lee Irwin III
2004-10-15 11:56 ` Hugh Dickins
2004-10-15 13:19 ` Albert Cahalan
2004-10-15 14:28 ` William Lee Irwin III
2004-10-15 14:40 ` Albert Cahalan
2004-10-15 14:52 ` William Lee Irwin III
2004-10-15 17:02 ` Andrea Arcangeli
2004-10-15 16:20 ` Andrea Arcangeli
2004-10-15 16:31 ` Albert Cahalan
2004-10-15 17:10 ` William Lee Irwin III
2004-10-15 19:29 ` Albert Cahalan
2004-10-15 17:13 ` Andrea Arcangeli
2004-10-15 17:51 ` Albert Cahalan
2004-10-15 18:14 ` Andrea Arcangeli [this message]
2004-10-15 18:30 ` William Lee Irwin III
2004-10-15 18:40 ` Andrea Arcangeli
2004-10-15 18:47 ` William Lee Irwin III
2004-10-15 19:23 ` Andrea Arcangeli
2004-10-15 20:41 ` William Lee Irwin III
2004-10-15 20:52 ` Andrea Arcangeli
2004-10-15 21:16 ` William Lee Irwin III
2004-10-15 21:28 ` Andrea Arcangeli
2004-10-15 21:40 ` William Lee Irwin III
2004-10-15 22:04 ` Hugh Dickins
2004-10-19 15:09 ` Bill Davidsen
2004-10-15 16:04 ` Andrea Arcangeli
2004-10-19 15:18 ` Bill Davidsen
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=20041015181446.GF17849@dualathlon.random \
--to=andrea@novell.com \
--cc=akpm@osdl.org \
--cc=albert@users.sf.net \
--cc=albert@users.sourceforge.net \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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