From: Albert Cahalan <albert@users.sf.net>
To: Andrea Arcangeli <andrea@novell.com>
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: 15 Oct 2004 12:31:52 -0400 [thread overview]
Message-ID: <1097857912.2669.13548.camel@cube> (raw)
In-Reply-To: <20041015162000.GB17849@dualathlon.random>
On Fri, 2004-10-15 at 12:20, Andrea Arcangeli wrote:
> the problem is that when ps xav wants to know the RSS it reads statm,
> so we just cannot hurt ps xav to show the "old shared" information that
> would be extremely slow to collect.
Currently, ps uses /proc/*/stat for that. The /proc/*/statm
file is read to determine TRS and DRS, which are broken now.
That it, unless you count "ps -o OL_m" format.
The top program uses /proc/*/statm for many more fields:
%MEM Memory usage (RES)
VIRT Virtual Image (kb)
SWAP Swapped size (kb)
RES Resident size (kb)
CODE Code size (kb)
DATA Data+Stack size (kb)
SHR Shared Mem size (kb)
nDRT Dirty Pages count
> I was only not happy about dropping the old feature completely instead
> of providing it with a different new API. Now I think the solution Hugh
> just proposed with the anon_rss should mimic the old behaviour well
> enough and it's probably the right way to go, it's still not literally
> the same, but I doubt most people from userspace could notice the
> difference, and most important it provides useful information, which is
> the number of _physical_ pages mapped that aren't anonymous memory, this
> is very valuable info and it's basically the same info that people was
> getting from the old "shared". So I like it.
What exactly would be the difference, and when might users see it?
next prev parent reply other threads:[~2004-10-15 16:41 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 [this message]
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
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=1097857912.2669.13548.camel@cube \
--to=albert@users.sf.net \
--cc=akpm@osdl.org \
--cc=albert@users.sourceforge.net \
--cc=andrea@novell.com \
--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