From: Michal Hocko <mhocko@kernel.org>
To: robert.foss@collabora.com
Cc: corbet@lwn.net, akpm@linux-foundation.org, vbabka@suse.cz,
hughd@google.com, koct9i@gmail.com, n-horiguchi@ah.jp.nec.com,
kirill.shutemov@linux.intel.com, john.stultz@linaro.org,
minchan@kernel.org, ross.zwisler@linux.intel.com,
jmarchan@redhat.com, hannes@cmpxchg.org, keescook@chromium.org,
oleg@redhat.com, viro@zeniv.linux.org.uk, mguzik@redhat.com,
jdanis@google.com, calvinowens@fb.com, adobriyan@gmail.com,
ebiederm@xmission.com, sonnyrao@chromium.org,
seth.forshee@canonical.com, tixxdz@gmail.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Ben Zhang <benzh@chromium.org>, Bryan Freed <bfreed@chromium.org>,
Filipe Brandenburger <filbranden@chromium.org>,
Jann Horn <jann@thejh.net>,
linux-api@vger.kernel.org,
Jacek Anaszewski <j.anaszewski@samsung.com>
Subject: Re: [PATCH v5 0/3] mm, proc: Implement /proc/<pid>/totmaps
Date: Mon, 12 Sep 2016 14:02:48 +0200 [thread overview]
Message-ID: <20160912120248.GK14524@dhcp22.suse.cz> (raw)
In-Reply-To: <1473106449-12847-1-git-send-email-robert.foss@collabora.com>
On Mon 05-09-16 16:14:06, robert.foss@collabora.com wrote:
> From: Robert Foss <robert.foss@collabora.com>
>
> This series provides the /proc/PID/totmaps feature, which
> summarizes the information provided by /proc/PID/smaps for
> improved performance and usability reasons.
>
> A use case is to speed up monitoring of memory consumption in
> environments where RSS isn't precise.
>
> For example Chrome tends to many processes which have hundreds of VMAs
> with a substantial amount of shared memory, and the error of using
> RSS rather than PSS tends to be very large when looking at overall
> memory consumption. PSS isn't kept as a single number that's exported
> like RSS, so to calculate PSS means having to parse a very large smaps
> file.
>
> This process is slow and has to be repeated for many processes, and we
> found that the just act of doing the parsing was taking up a
> significant amount of CPU time, so this patch is an attempt to make
> that process cheaper.
I still maintain my concerns about a single pss value. It might work in
a very specific situations where the consumer knows what is shared but
other than that the value can be more misleading than helpful. So a NACK
from me until I am shown that this is usable in general and still
helpful.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-09-12 12:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 20:14 robert.foss
2016-09-05 20:14 ` [PATCH v5 1/3] " robert.foss
2016-09-07 12:58 ` Oleg Nesterov
2016-09-12 22:12 ` Robert Foss
2016-09-05 20:14 ` [PATCH v5 2/3] Documentation/filesystems: Fixed typo robert.foss
2016-09-07 23:22 ` Kees Cook
2016-09-08 0:22 ` Robert Foss
2016-09-08 6:23 ` Jonathan Corbet
2016-09-05 20:14 ` [PATCH v5 3/3] Documentation/filesystems: Added /proc/PID/totmaps documentation robert.foss
2016-09-12 12:02 ` Michal Hocko [this message]
2016-09-12 15:31 ` [PATCH v5 0/3] mm, proc: Implement /proc/<pid>/totmaps Sonny Rao
2016-09-12 17:15 ` Michal Hocko
2016-09-12 17:28 ` Sonny Rao
2016-09-13 7:12 ` Michal Hocko
2016-09-13 20:27 ` Sonny Rao
2016-09-14 9:12 ` Michal Hocko
2016-09-19 15:16 ` Robert Foss
2016-09-19 19:32 ` Michal Hocko
[not found] ` <20160919194001.GE2903@pc.thejh.net>
[not found] ` <20160919195109.GB28639@dhcp22.suse.cz>
2016-09-19 19:56 ` Jann Horn
2016-09-19 20:15 ` Sonny Rao
2016-09-20 0:27 ` Robert Foss
2016-09-20 0:29 ` Sonny Rao
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=20160912120248.GK14524@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=benzh@chromium.org \
--cc=bfreed@chromium.org \
--cc=calvinowens@fb.com \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=filbranden@chromium.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=j.anaszewski@samsung.com \
--cc=jann@thejh.net \
--cc=jdanis@google.com \
--cc=jmarchan@redhat.com \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=koct9i@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mguzik@redhat.com \
--cc=minchan@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=oleg@redhat.com \
--cc=robert.foss@collabora.com \
--cc=ross.zwisler@linux.intel.com \
--cc=seth.forshee@canonical.com \
--cc=sonnyrao@chromium.org \
--cc=tixxdz@gmail.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®