From: Minchan Kim <minchan@kernel.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, hillf.zj@alibaba-inc.com,
mgorman@suse.de, vbabka@suse.cz, mm-commits@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: + mm-vmscan-add-mm_vmscan_inactive_list_is_low-tracepoint.patch added to -mm tree
Date: Thu, 12 Jan 2017 14:12:47 +0900 [thread overview]
Message-ID: <20170112051247.GA8387@bbox> (raw)
In-Reply-To: <20170111155239.GD16365@dhcp22.suse.cz>
Hello,
On Wed, Jan 11, 2017 at 04:52:39PM +0100, Michal Hocko wrote:
> On Wed 11-01-17 08:52:50, Minchan Kim wrote:
> [...]
> > > @@ -2055,8 +2055,8 @@ static bool inactive_list_is_low(struct
> > > if (!file && !total_swap_pages)
> > > return false;
> > >
> > > - inactive = lruvec_lru_size(lruvec, file * LRU_FILE);
> > > - active = lruvec_lru_size(lruvec, file * LRU_FILE + LRU_ACTIVE);
> > > + total_inactive = inactive = lruvec_lru_size(lruvec, file * LRU_FILE);
> > > + total_active = active = lruvec_lru_size(lruvec, file * LRU_FILE + LRU_ACTIVE);
> > >
> >
> > the decision of deactivating is based on eligible zone's LRU size,
> > not whole zone so why should we need to get a trace of all zones's LRU?
>
> Strictly speaking, the total_ counters are not necessary for making the
> decision. I found reporting those numbers useful regardless because this
> will give us also an information how large is the eligible portion of
> the LRU list. We do not have any other tracepoint which would report
> that.
The patch doesn't say anything why it's useful. Could you tell why it's
useful and inactive_list_is_low should be right place?
Don't get me wrong, please. I don't want to bother you.
I really don't want to add random stuff although it's tracepoint for
debugging.
>
> [...]
> > > @@ -2223,7 +2228,7 @@ static void get_scan_count(struct lruvec
> > > * lruvec even if it has plenty of old anonymous pages unless the
> > > * system is under heavy pressure.
> > > */
> > > - if (!inactive_list_is_low(lruvec, true, sc) &&
> > > + if (!inactive_list_is_low(lruvec, true, sc, false) &&
> >
> > Hmm, I was curious why you added trace boolean arguement and found it here.
> > Yes, here is not related to deactivation directly but couldn't we help to
> > trace it unconditionally?
>
> I've had it like that when I was debugging the mentioned bug and found
> it a bit disturbing. It generated more output than I would like and it
> wasn't really clear from which code path this has been called from.
Indeed.
Personally, I want to move inactive_list_is_low in shrink_active_list
and shrink_active_list calls inactive_list_is_low(...., true),
unconditionally so that it can make code simple/clear but cannot remove
trace boolean variable , which what I want. So, it's okay if you love
your version.
>
> > With that, we can know why VM reclaim only
> > file-backed page on slow device although enough anonymous pages on fast
> > swap like zram are enough.
>
> That would be something for a separate tracepoint in g_s_c
Agree.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-01-12 5:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <586edadc.figmHAGrTxvM7Wei%akpm@linux-foundation.org>
2017-01-10 23:52 ` + mm-vmscan-add-mm_vmscan_inactive_list_is_low-tracepoint.patch added to -mm tree Minchan Kim
2017-01-11 15:52 ` Michal Hocko
2017-01-12 5:12 ` Minchan Kim [this message]
2017-01-12 8:15 ` Michal Hocko
2017-01-12 8:48 ` Minchan Kim
2017-01-12 9:10 ` Michal Hocko
2017-01-13 1:37 ` Minchan Kim
2017-01-13 7:47 ` Michal Hocko
2017-01-13 8:57 ` Minchan Kim
2017-01-13 9:10 ` Michal Hocko
2017-01-17 6:45 ` Minchan Kim
2017-01-17 10:12 ` Michal Hocko
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=20170112051247.GA8387@bbox \
--to=minchan@kernel.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).