public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shli@fb.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
	<Kernel-team@fb.com>, <mhocko@suse.com>, <minchan@kernel.org>,
	<hughd@google.com>, <hannes@cmpxchg.org>, <riel@redhat.com>,
	<mgorman@techsingularity.net>, <akpm@linux-foundation.org>
Subject: Re: [PATCH V4 6/6] proc: show MADV_FREE pages info in smaps
Date: Fri, 24 Feb 2017 13:47:25 -0800	[thread overview]
Message-ID: <20170224214724.GA35601@shli-mbp.local> (raw)
In-Reply-To: <e118502c-6be7-2ca5-bd3c-1f390a3961df@intel.com>

On Fri, Feb 24, 2017 at 09:08:30AM -0800, Dave Hansen wrote:
> On 02/22/2017 10:50 AM, Shaohua Li wrote:
> > @@ -770,6 +774,7 @@ static int show_smap(struct seq_file *m, void *v, int is_pid)
> >  		   "Private_Dirty:  %8lu kB\n"
> >  		   "Referenced:     %8lu kB\n"
> >  		   "Anonymous:      %8lu kB\n"
> > +		   "LazyFree:       %8lu kB\n"
> >  		   "AnonHugePages:  %8lu kB\n"
> >  		   "ShmemPmdMapped: %8lu kB\n"
> >  		   "Shared_Hugetlb: %8lu kB\n"
> 
> I've been as guily of this in the past as anyone, but are we just going
> to keep adding fields to smaps forever?  For the vast, vast, majority of
> folks, this will simply waste the 21 bytes * nr_vmas that it costs us to
> print "LazyFree:       0 kB\n" over and over.
> 
> Should we maybe start a habit of not printing an entry when it's "0 kB"?

Interesting idea! I'd like this is a separate patch if we go this way, because
this is likely to be controversial. That said, sounds there is no reason we
shouldn't do this.

Thanks,
Shaohua

      reply	other threads:[~2017-02-24 21:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 18:50 [PATCH V4 0/6] mm: fix some MADV_FREE issues Shaohua Li
2017-02-22 18:50 ` [PATCH V4 1/6] mm: delete unnecessary TTU_* flags Shaohua Li
2017-02-23 15:35   ` Johannes Weiner
2017-02-24  1:25   ` Minchan Kim
2017-02-24  3:29   ` Hillf Danton
2017-02-22 18:50 ` [PATCH V4 2/6] mm: don't assume anonymous pages have SwapBacked flag Shaohua Li
2017-02-22 18:50 ` [PATCH V4 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list Shaohua Li
2017-02-23 15:58   ` Johannes Weiner
2017-02-23 16:26     ` Shaohua Li
2017-02-23 18:22       ` Johannes Weiner
2017-02-23 19:04         ` Shaohua Li
2017-02-24  1:49   ` Minchan Kim
2017-02-24  6:15     ` Shaohua Li
2017-02-24 23:37       ` Minchan Kim
2017-02-22 18:50 ` [PATCH V4 4/6] mm: reclaim MADV_FREE pages Shaohua Li
2017-02-23 16:13   ` Johannes Weiner
2017-02-23 17:19     ` Shaohua Li
2017-02-24  2:12   ` Minchan Kim
2017-02-24  6:14     ` Shaohua Li
2017-02-24 15:36     ` Johannes Weiner
2017-02-24 23:26       ` Minchan Kim
2017-02-22 18:50 ` [PATCH V4 5/6] mm: enable MADV_FREE for swapless system Shaohua Li
2017-02-22 18:50 ` [PATCH V4 6/6] proc: show MADV_FREE pages info in smaps Shaohua Li
2017-02-23 16:16   ` Johannes Weiner
2017-02-24  2:13   ` Minchan Kim
2017-02-24 17:08   ` Dave Hansen
2017-02-24 21:47     ` Shaohua Li [this message]

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=20170224214724.GA35601@shli-mbp.local \
    --to=shli@fb.com \
    --cc=Kernel-team@fb.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=riel@redhat.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