From: Michal Hocko <mhocko@kernel.org>
To: Shaohua Li <shli@fb.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Kernel-team@fb.com, danielmicay@gmail.com, minchan@kernel.org,
hughd@google.com, hannes@cmpxchg.org, riel@redhat.com,
mgorman@techsingularity.net, akpm@linux-foundation.org
Subject: Re: [PATCH V2 5/7] mm: add vmstat account for MADV_FREE pages
Date: Tue, 21 Feb 2017 10:43:54 +0100 [thread overview]
Message-ID: <20170221094353.GG15595@dhcp22.suse.cz> (raw)
In-Reply-To: <20170210175015.GD86050@shli-mbp.local>
[Sorry for a late reply I was on vacation last week]
On Fri 10-02-17 09:50:15, Shaohua Li wrote:
> On Fri, Feb 10, 2017 at 02:27:27PM +0100, Michal Hocko wrote:
> > On Fri 03-02-17 15:33:21, Shaohua Li wrote:
> > > Show MADV_FREE pages info in proc/sysfs files.
> >
> > How are we going to use this information? Why it isn't sufficient to
> > watch for lazyfree events? I mean this adds quite some code and it is
> > not clear (at least from the changelog) we we need this information.
>
> It's just like any other meminfo we added to let user know what happens in the
> system. Users can use the info for monitoring/diagnosing. the
> lazyfree/lazyfreed events can't reflect the lazyfree page info because
> 'lazyfree - lazyfreed' doesn't equal current lazyfree pages and the events
> aren't per-node. I'll add more description in the changelog.
Well, I would prefer to not add new counters until there is a strong
reason for them. Maybe a trace point would be more appropriate for
debugging purposes.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-02-21 9:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 23:33 [PATCH V2 0/7] mm: fix some MADV_FREE issues Shaohua Li
2017-02-03 23:33 ` [PATCH V2 1/7] mm: don't assume anonymous pages have SwapBacked flag Shaohua Li
2017-02-03 23:33 ` [PATCH V2 2/7] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list Shaohua Li
2017-02-04 6:38 ` Hillf Danton
2017-02-09 6:33 ` Hillf Danton
2017-02-10 6:50 ` Minchan Kim
2017-02-10 17:30 ` Shaohua Li
2017-02-13 4:57 ` Minchan Kim
2017-02-10 13:02 ` Michal Hocko
2017-02-10 17:33 ` Shaohua Li
2017-02-03 23:33 ` [PATCH V2 3/7] mm: reclaim MADV_FREE pages Shaohua Li
2017-02-10 6:58 ` Minchan Kim
2017-02-10 17:43 ` Shaohua Li
2017-02-13 5:06 ` Minchan Kim
2017-02-10 13:23 ` Michal Hocko
2017-02-03 23:33 ` [PATCH V2 4/7] mm: enable MADV_FREE for swapless system Shaohua Li
2017-02-03 23:33 ` [PATCH V2 5/7] mm: add vmstat account for MADV_FREE pages Shaohua Li
2017-02-10 13:27 ` Michal Hocko
2017-02-10 17:50 ` Shaohua Li
2017-02-21 9:43 ` Michal Hocko [this message]
2017-02-03 23:33 ` [PATCH V2 6/7] proc: show MADV_FREE pages info in smaps Shaohua Li
2017-02-10 13:30 ` Michal Hocko
2017-02-10 17:52 ` Shaohua Li
2017-02-22 2:47 ` Minchan Kim
2017-02-22 4:11 ` Shaohua Li
2017-02-03 23:33 ` [PATCH V2 7/7] mm: add a separate RSS for MADV_FREE pages Shaohua Li
2017-02-10 13:35 ` Michal Hocko
2017-02-10 18:01 ` Shaohua Li
2017-02-21 9:45 ` Michal Hocko
2017-02-22 0:46 ` Minchan Kim
2017-02-22 1:27 ` Shaohua Li
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=20170221094353.GG15595@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=Kernel-team@fb.com \
--cc=akpm@linux-foundation.org \
--cc=danielmicay@gmail.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=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=shli@fb.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
all inboxes | Powered by JetHome®