From: William Lee Irwin III <wli@holomorphy.com>
To: Andrea Arcangeli <andrea@novell.com>
Cc: Albert Cahalan <albert@users.sf.net>,
Hugh Dickins <hugh@veritas.com>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton OSDL <akpm@osdl.org>,
Albert Cahalan <albert@users.sourceforge.net>
Subject: Re: per-process shared information
Date: Fri, 15 Oct 2004 11:47:13 -0700 [thread overview]
Message-ID: <20041015184713.GO5607@holomorphy.com> (raw)
In-Reply-To: <20041015184009.GG17849@dualathlon.random>
On Fri, Oct 15, 2004 at 11:30:25AM -0700, William Lee Irwin III wrote:
>> I just checked in with some Oracle people and the primary concern
>> is splitting up RSS into shared and private. Given either shared
>> or private the other is calculable.
On Fri, Oct 15, 2004 at 08:40:09PM +0200, Andrea Arcangeli wrote:
> can you define private a bit more? Is private the page_count == 1 like
> 2.4? Or is "private" == anonymous? that's the only question.
> In Hugh's patch private == "anonymous". With 2.4 private == "page_count
> == 1" (which is a subset of anonymous).
Private should be "anonymous" as far as I can tell. What's actually
going on is that they're trying to estimate per-process user memory
footprints so that the amount of client load that should be distributed
to a given box may be estimated from that. They at least used to
believe (I've since debunked this) that 2.4.x reported this information.
Their task (and hence our reporting) is not providing the complete
information to determine per-process memory footprints for general
workloads, rather it's known up-front that no fork()-based COW sharing
is going on in Oracle's case, so in this case, "anonymous" very happily
corresponds to "process-private". In fact, the /proc/ changes to report
threads only under the directory hierarchy of some distinguished thread
assists in this estimation effort.
-- wli
next prev parent reply other threads:[~2004-10-15 18:47 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
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 [this message]
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=20041015184713.GO5607@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=albert@users.sf.net \
--cc=albert@users.sourceforge.net \
--cc=andrea@novell.com \
--cc=hugh@veritas.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