From: Fengguang Wu <wfg@mail.ustc.edu.cn>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>,
John Berthels <jjberthels@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] maps: PSS(proportional set size) accounting in smaps
Date: Fri, 17 Aug 2007 10:44:44 +0800 [thread overview]
Message-ID: <387318684.03065@ustc.edu.cn> (raw)
Message-ID: <20070817024443.GA5521@mail.ustc.edu.cn> (raw)
In-Reply-To: <20070817021346.GH30556@waste.org>
On Thu, Aug 16, 2007 at 09:13:47PM -0500, Matt Mackall wrote:
> On Fri, Aug 17, 2007 at 06:05:17AM +0800, Fengguang Wu wrote:
> > The "proportional set size" (PSS) of a process is the count of pages it has in
> > memory, where each page is divided by the number of processes sharing it. So if
> > a process has 1000 pages all to itself, and 1000 shared with one other process,
> > its PSS will be 1500.
> > - lwn.net: "ELC: How much memory are applications really using?"
> >
> > The PSS proposed by Matt Mackall is a very nice metic for measuring an process's
> > memory footprint. So collect and export it via /proc/<pid>/smaps.
> >
> > Matt Mackall's pagemap/kpagemap and John Berthels's exmap can also do the job.
> > They are comprehensive tools. But for PSS, let's do it in the simple way.
>
> It's a bit odd that you attribute the description of PSS to LWN rather
> than me. But anyway:
>
> Acked-by: Matt Mackall <mpm@selenic.com>
Sorry and thank you!
I'll change it in the next take.
next prev parent reply other threads:[~2007-08-17 2:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 22:05 [PATCH 0/4] process memory footprints in proc/<pid>/[s|p]maps Fengguang Wu
2007-08-16 22:05 ` Fengguang Wu
2007-08-16 22:05 ` [PATCH 1/4] maps: PSS(proportional set size) accounting in smaps Fengguang Wu
2007-08-16 22:05 ` Fengguang Wu
2007-08-17 2:13 ` Matt Mackall
2007-08-17 2:44 ` Fengguang Wu [this message]
2007-08-17 2:44 ` Fengguang Wu
2007-08-16 22:05 ` [PATCH 2/4] maps: address based vma walking Fengguang Wu
2007-08-16 22:05 ` Fengguang Wu
2007-08-17 2:16 ` Matt Mackall
2007-08-17 2:54 ` Fengguang Wu
2007-08-17 2:54 ` Fengguang Wu
2007-08-16 22:05 ` [PATCH 3/4] maps: introduce generic_maps_open() Fengguang Wu
2007-08-16 22:05 ` Fengguang Wu
2007-08-16 22:05 ` [PATCH 4/4] maps: /proc/<pid>/pmaps interface - memory maps in granularity of pages Fengguang Wu
2007-08-16 22:05 ` Fengguang Wu
2007-08-17 2:38 ` Matt Mackall
2007-08-17 3:44 ` Fengguang Wu
2007-08-17 3:44 ` Fengguang Wu
2007-08-17 3:56 ` Matt Mackall
2007-08-17 6:47 ` Fengguang Wu
2007-08-17 6:47 ` Fengguang Wu
2007-08-17 16:58 ` Matt Mackall
2007-08-18 2:48 ` Fengguang Wu
2007-08-18 2:48 ` Fengguang Wu
2007-08-18 6:40 ` Matt Mackall
2007-08-18 8:45 ` Fengguang Wu
2007-08-18 8:45 ` Fengguang Wu
2007-08-18 17:22 ` Matt Mackall
2007-08-19 0:40 ` Fengguang Wu
2007-08-19 0:40 ` Fengguang Wu
2007-08-18 10:31 ` Fengguang Wu
2007-08-18 10:31 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2007-08-19 7:54 [PATCH 0/4] process memory footprint info in proc/<pid>/[s|p]maps v2 Fengguang Wu
2007-08-19 7:54 ` [PATCH 1/4] maps: PSS(proportional set size) accounting in smaps Fengguang Wu
2007-08-19 7:54 ` Fengguang Wu
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=387318684.03065@ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=akpm@osdl.org \
--cc=jjberthels@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.