linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] vmscan: respect higher order in zone_reclaim()
Date: Wed, 18 Feb 2009 11:26:03 +0100	[thread overview]
Message-ID: <20090218102603.GA2160@cmpxchg.org> (raw)
In-Reply-To: <20090218101204.GA27970@csn.ul.ie>

On Wed, Feb 18, 2009 at 10:12:04AM +0000, Mel Gorman wrote:
> On Tue, Feb 17, 2009 at 08:48:27PM +0100, Johannes Weiner wrote:
> > zone_reclaim() already tries to free the requested 2^order pages but
> > doesn't pass the order information into the inner reclaim code.
> > 
> > This prevents lumpy reclaim from happening on higher orders although
> > the caller explicitely asked for that.
> > 
> > Fix it up by initializing the order field of the scan control
> > according to the request.
> > 
> 
> I'm fine with the patch but the changelog could have been better.  Optionally
> take this changelog but either way.
> 
> Acked-by: Mel Gorman <mel@csn.ul.ie>
> 
> Optional alternative changelog
> ==============================
> 
> During page allocation, there are two stages of direct reclaim that are applied
> to each zone in the preferred list. The first stage using zone_reclaim()
> reclaims unmapped file backed pages and slab pages if over defined limits as
> these are cheaper to reclaim. The caller specifies the order of the target
> allocation but the scan control is not being correctly initialised.
> 
> The impact is that the correct number of pages are being reclaimed but that
> lumpy reclaim is not being applied. This increases the chances of a full
> direct reclaim via try_to_free_pages() is required.
> 
> This patch initialises the order field of the scan control as requested
> by the caller.

Agreed, this is better.  Thank you, Mel.

--
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:[~2009-02-18 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 19:48 Johannes Weiner
2009-02-18 10:12 ` Mel Gorman
2009-02-18 10:26   ` Johannes Weiner [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=20090218102603.GA2160@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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