linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mel@csn.ul.ie>,
	linux-mm@kvack.org
Subject: Re: [patch 1/5] vmscan: fix unmapping behaviour for RECLAIM_SWAP
Date: Wed, 19 May 2010 23:32:51 +0200	[thread overview]
Message-ID: <20100519213251.GA2868@cmpxchg.org> (raw)
In-Reply-To: <20100512122434.2133.A69D9226@jp.fujitsu.com>

Hi,

On Thu, May 13, 2010 at 12:02:53PM +0900, KOSAKI Motohiro wrote:
> sorry for the long delayed review.

Yeah, I'm a bit on the slow side as well these days.  No problem.

> > The RECLAIM_SWAP flag in zone_reclaim_mode controls whether
> > zone_reclaim() is allowed to swap or not (obviously).
> > 
> > This is currently implemented by allowing or forbidding reclaim to
> > unmap pages, which also controls reclaim of shared pages and is thus
> > not appropriate.
> > 
> > We can do better by using the sc->may_swap parameter instead, which
> > controls whether the anon lists are scanned.
> > 
> > Unmapping of pages is then allowed per default from zone_reclaim().
> > 
> > Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
> > ---
> >  mm/vmscan.c |    4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -2563,8 +2563,8 @@ static int __zone_reclaim(struct zone *z
> >  	int priority;
> >  	struct scan_control sc = {
> >  		.may_writepage = !!(zone_reclaim_mode & RECLAIM_WRITE),
> > -		.may_unmap = !!(zone_reclaim_mode & RECLAIM_SWAP),
> > -		.may_swap = 1,
> > +		.may_unmap = 1,
> > +		.may_swap = !!(zone_reclaim_mode & RECLAIM_SWAP),
> >  		.nr_to_reclaim = max_t(unsigned long, nr_pages,
> >  				       SWAP_CLUSTER_MAX),
> >  		.gfp_mask = gfp_mask,
> 
> About half years ago, I did post exactly same patch. but at that time,
> it got Mel's objection. after some discution we agreed to merge
> documentation change instead code fix.

Interesting, let me dig through the archives.

> So, now the documentation describe clearly 4th bit meant no unmap.
> Please drop this, instead please make s/RECLAIM_SWAP/RECLAIM_MAPPED/ patch.

Yep.

Thanks,
	Hannes

--
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>

  reply	other threads:[~2010-05-19 21:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30 23:05 [patch 0/5] vmscan: cut down on struct scan_control Johannes Weiner
2010-04-30 23:05 ` [patch 1/5] vmscan: fix unmapping behaviour for RECLAIM_SWAP Johannes Weiner
2010-05-13  3:02   ` KOSAKI Motohiro
2010-05-19 21:32     ` Johannes Weiner [this message]
2010-04-30 23:05 ` [patch 2/5] vmscan: remove may_unmap scan control Johannes Weiner
2010-04-30 23:05 ` [patch 3/5] vmscan: remove all_unreclaimable " Johannes Weiner
2010-05-13  3:25   ` KOSAKI Motohiro
2010-05-19 21:34     ` Johannes Weiner
2010-05-31 18:32   ` Greg Thelen
2010-06-01  3:29     ` [PATCH] vmscan: Fix do_try_to_free_pages() return value when priority==0 reclaim failure KOSAKI Motohiro
2010-06-01  6:48       ` KAMEZAWA Hiroyuki
2010-06-01  8:10       ` Balbir Singh
2010-06-02  0:33         ` KAMEZAWA Hiroyuki
2010-06-01 14:50       ` Greg Thelen
2010-06-04 14:32       ` Johannes Weiner
2010-04-30 23:05 ` [patch 4/5] vmscan: remove isolate_pages callback scan control Johannes Weiner
2010-05-13  3:29   ` KOSAKI Motohiro
2010-05-19 21:42     ` Johannes Weiner
2010-05-20 23:23       ` KOSAKI Motohiro
2010-04-30 23:05 ` [patch 5/5] vmscan: remove may_swap " Johannes Weiner
2010-05-13  3:36   ` KOSAKI Motohiro
2010-05-19 21:44     ` Johannes Weiner
2010-05-21  0:15       ` KOSAKI Motohiro

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=20100519213251.GA2868@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /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).