All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mel Gorman <mgorman@suse.de>
Cc: Jiri Slaby <jslaby@suse.cz>,
	Valdis.Kletnieks@vt.edu, mm-commits@vger.kernel.org,
	minchan@kernel.org, riel@redhat.com,
	"jirisl >> Jiri Slaby" <jirislaby@gmail.com>
Subject: Re: + mm-vmscan-scale-number-of-pages-reclaimed-by-reclaim-compaction-only-in-direct-reclaim.patch added to -mm tree
Date: Mon, 29 Oct 2012 16:12:36 -0700	[thread overview]
Message-ID: <20121029161236.a9c1210f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20121028212215.GA3888@suse.de>

On Sun, 28 Oct 2012 21:22:15 +0000
Mel Gorman <mgorman@suse.de> wrote:

> > Hi, this one breaks UML build:
> > In function ???is_thp_alloc???,
> >     inlined from ???__alloc_pages_slowpath??? at mm/page_alloc.c:2427:20,
> >     inlined from ???__alloc_pages_nodemask??? at mm/page_alloc.c:2645:8:
> > mm/page_alloc.c:2383:15: error: call to ???__build_bug_failed??? declared
> > with attribute error: BUILD_BUG failed
> > 
> > That arch does not support THP.
> > 
> 
> ---8<---
> mm: page_alloc: Do not wake kswapd if the request is for THP but deferred
>
> Since commit c6543459 (mm: remove __GFP_NO_KSWAPD), kswapd gets woken
> for every THP request in the slow path. If compaction has been deferred
> the waker will not compact or enter direct reclaim on its own behalf
> but kswapd is still woken to reclaim free pages that no one may consume.
> If compaction was deferred because pages and slab was not reclaimable
> then kswapd is just consuming cycles for no gain.
> 
> This patch avoids waking kswapd if the compaction has been deferred.
> It'll still wake when compaction is running to reduce the latency of
> THP allocations.

umwhat?  I'd struggling to see how this patch will fix the UML build.

> index bb90971..e72674c 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -2378,6 +2378,15 @@ bool gfp_pfmemalloc_allowed(gfp_t gfp_mask)
>  	return !!(gfp_to_alloc_flags(gfp_mask) & ALLOC_NO_WATERMARKS);
>  }
>  
> +/* Returns true if the allocation is likely for THP */

Comment is a bit awkward/ambiguous.  Perhaps "if this allocation is
probably asking for a THP hugepage".

And why the "likely"/"probably"?  Is it so hard to know for certain?


Anyway, I think I'll duck this patch under the assumption you pasted the
wrong thing into that email.


I currently have
mm-vmscan-scale-number-of-pages-reclaimed-by-reclaim-compaction-only-in-direct-reclaim.patch
queued for 3.7, but on hold due to Valdis's bug report.

      parent reply	other threads:[~2012-10-29 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 22:23 + mm-vmscan-scale-number-of-pages-reclaimed-by-reclaim-compaction-only-in-direct-reclaim.patch added to -mm tree akpm
     [not found] ` <14005.1350400638@turing-police.cc.vt.edu>
     [not found]   ` <31622.1350421487@turing-police.cc.vt.edu>
     [not found]     ` <20121017104528.GH29125@suse.de>
     [not found]       ` <508BCB5C.6010401@suse.cz>
     [not found]         ` <20121028212215.GA3888@suse.de>
2012-10-29 23:12           ` Andrew Morton [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=20121029161236.a9c1210f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=minchan@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.