From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934231AbcILPlO (ORCPT ); Mon, 12 Sep 2016 11:41:14 -0400 Received: from mail-yw0-f171.google.com ([209.85.161.171]:32969 "EHLO mail-yw0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933772AbcILPb6 (ORCPT ); Mon, 12 Sep 2016 11:31:58 -0400 MIME-Version: 1.0 In-Reply-To: <20160912120248.GK14524@dhcp22.suse.cz> References: <1473106449-12847-1-git-send-email-robert.foss@collabora.com> <20160912120248.GK14524@dhcp22.suse.cz> From: Sonny Rao Date: Mon, 12 Sep 2016 08:31:36 -0700 X-Google-Sender-Auth: 9GTR8IfWGtJmvBns5gWOhSN76OI Message-ID: Subject: Re: [PATCH v5 0/3] mm, proc: Implement /proc//totmaps To: Michal Hocko Cc: Robert Foss , Jonathan Corbet , Andrew Morton , Vlastimil Babka , Hugh Dickins , Konstantin Khlebnikov , Naoya Horiguchi , "Kirill A. Shutemov" , John Stultz , Minchan Kim , ross.zwisler@linux.intel.com, jmarchan@redhat.com, Johannes Weiner , Kees Cook , oleg@redhat.com, Al Viro , Mateusz Guzik , Janis Danisevskis , calvinowens@fb.com, Alexey Dobriyan , ebiederm@xmission.com, seth.forshee@canonical.com, tixxdz@gmail.com, linux-doc@vger.kernel.org, "linux-kernel@vger.kernel.org" , Ben Zhang , Bryan Freed , Filipe Brandenburger , Jann Horn , linux-api@vger.kernel.org, Jacek Anaszewski Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 12, 2016 at 5:02 AM, Michal Hocko wrote: > On Mon 05-09-16 16:14:06, robert.foss@collabora.com wrote: >> From: Robert Foss >> >> 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. I know you think Pss isn't useful in general (though I'll point out two other independent people said they found it useful) but how about the other fields like Swap, Private_Dirty and Private_Shared? If we removed Pss would you still NACK it? > > -- > Michal Hocko > SUSE Labs