From: Mel Gorman <mgorman@suse.de>
To: Hillf Danton <dhillf@gmail.com>
Cc: linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: vmscan: no change of reclaim mode if unevictable page encountered
Date: Tue, 10 Jan 2012 16:57:43 +0000 [thread overview]
Message-ID: <20120110165743.GE4118@suse.de> (raw)
In-Reply-To: <CAJd=RBBNK6P=Kq09G88UDEsiU8KUPiko5WTfLgQqKzry8tVH5A@mail.gmail.com>
On Wed, Jan 11, 2012 at 12:27:53AM +0800, Hillf Danton wrote:
> On Tue, Jan 10, 2012 at 5:40 PM, Mel Gorman <mgorman@suse.de> wrote:
> > On Sat, Jan 07, 2012 at 11:46:17AM +0800, Hillf Danton wrote:
> >> Since unevictable page is not isolated from lru list for shrink_page_list(),
> >> it is accident if encountered in shrinking, and no need to change reclaim mode.
> >>
> >
> > This changelog does does not explain the problem, does not explain
> > what is fixed or what the impact is.
> >
> > It also does not make sense. It says "unevictable page is not isolated
> > from LRU list" but this is shrink_page_list() and the page has already
> > been isolated (probably by lumpy reclaim). It will be put back on
> > the LRU_UNEVICTABLE list.
> >
> > It might be the case that resetting the reclaim mode after encountering
> > mlocked pages is overkill but that would need more justification than
> > what this changelog offers. Resetting the mode impacts THP rates but
> > this is erring on the side of caution by doing less work in reclaim
> > as the savings from THP may not offset the cost of reclaim.
> >
>
> Hi Mel
>
> It is reprepared, please review again.
>
> Thanks
> Hillf
>
> ===cut please===
> From: Hillf Danton <dhillf@gmail.com>
> [PATCH] mm: vmscan: no change of reclaim mode if unevictable page encountered
>
> Unevictable pages are not isolated from lru list for shrink_page_list(), and
> they could be put back onto lru list if accidentally encountered in shrinking.
>
> But resetting reclaim mode maybe overkill, as it impacts THP rates. This is
> erring on the side of caution by doing less work in reclaim as the savings
> from THP may not offset the cost of reclaim.
>
When I said it needed more justification, I meant that you need to show
a workload or usecase that suffers as a result of reset_reclaim_mode
being called here. I explained already that the reset errs on the
side of caution by making reclaim work less.
You need to describe what problem your workload is suffering from and
why this patch fixes it.
--
Mel Gorman
SUSE Labs
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-01-10 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 3:46 [PATCH] mm: vmscan: no change of reclaim mode if unevictable page encountered Hillf Danton
2012-01-10 9:40 ` Mel Gorman
2012-01-10 16:27 ` Hillf Danton
2012-01-10 16:57 ` Mel Gorman [this message]
2012-01-11 12:14 ` Hillf Danton
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=20120110165743.GE4118@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dhillf@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).