All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <cl@linux.com>, Michal Hocko <mhocko@suse.com>,
	Vlastimil Babka <vbabka@suse.cz>, Linux-MM <linux-mm@kvack.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v3
Date: Mon, 28 Nov 2016 14:54:21 -0500	[thread overview]
Message-ID: <20161128195421.GA22236@cmpxchg.org> (raw)
In-Reply-To: <20161127131954.10026-1-mgorman@techsingularity.net>

On Sun, Nov 27, 2016 at 01:19:54PM +0000, Mel Gorman wrote:
> While it is recognised that this is a mixed bag of results, the patch
> helps a lot more workloads than it hurts and intuitively, avoiding the
> zone->lock in some cases is a good thing.
> 
> Signed-off-by: Mel Gorman <mgorman@techsingularity.net>

This seems like a net gain to me, and the patch loos good too.

Acked-by: Johannes Weiner <hannes@cmpxchg.org>

> @@ -255,6 +255,24 @@ enum zone_watermarks {
>  	NR_WMARK
>  };
>  
> +/*
> + * One per migratetype for order-0 pages and one per high-order up to
> + * and including PAGE_ALLOC_COSTLY_ORDER. This may allow unmovable
> + * allocations to contaminate reclaimable pageblocks if high-order
> + * pages are heavily used.

I think that should be fine. Higher order allocations rely on being
able to compact movable blocks, not on reclaim freeing contiguous
blocks, so poisoning reclaimable blocks is much less of a concern than
poisoning movable blocks. And I'm not aware of any 0 < order < COSTLY
movable allocations that would put movable blocks into an HO cache.

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

WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <cl@linux.com>, Michal Hocko <mhocko@suse.com>,
	Vlastimil Babka <vbabka@suse.cz>, Linux-MM <linux-mm@kvack.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v3
Date: Mon, 28 Nov 2016 14:54:21 -0500	[thread overview]
Message-ID: <20161128195421.GA22236@cmpxchg.org> (raw)
In-Reply-To: <20161127131954.10026-1-mgorman@techsingularity.net>

On Sun, Nov 27, 2016 at 01:19:54PM +0000, Mel Gorman wrote:
> While it is recognised that this is a mixed bag of results, the patch
> helps a lot more workloads than it hurts and intuitively, avoiding the
> zone->lock in some cases is a good thing.
> 
> Signed-off-by: Mel Gorman <mgorman@techsingularity.net>

This seems like a net gain to me, and the patch loos good too.

Acked-by: Johannes Weiner <hannes@cmpxchg.org>

> @@ -255,6 +255,24 @@ enum zone_watermarks {
>  	NR_WMARK
>  };
>  
> +/*
> + * One per migratetype for order-0 pages and one per high-order up to
> + * and including PAGE_ALLOC_COSTLY_ORDER. This may allow unmovable
> + * allocations to contaminate reclaimable pageblocks if high-order
> + * pages are heavily used.

I think that should be fine. Higher order allocations rely on being
able to compact movable blocks, not on reclaim freeing contiguous
blocks, so poisoning reclaimable blocks is much less of a concern than
poisoning movable blocks. And I'm not aware of any 0 < order < COSTLY
movable allocations that would put movable blocks into an HO cache.

  parent reply	other threads:[~2016-11-28 19:54 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 13:19 [PATCH] mm: page_alloc: High-order per-cpu page allocator v3 Mel Gorman
2016-11-27 13:19 ` Mel Gorman
2016-11-28 11:00 ` Vlastimil Babka
2016-11-28 11:00   ` Vlastimil Babka
2016-11-28 11:45   ` Mel Gorman
2016-11-28 11:45     ` Mel Gorman
2016-11-30  8:55   ` Mel Gorman
2016-11-30  8:55     ` Mel Gorman
2016-11-28 15:39 ` Christoph Lameter
2016-11-28 15:39   ` Christoph Lameter
2016-11-28 16:21   ` Mel Gorman
2016-11-28 16:21     ` Mel Gorman
2016-11-28 16:38     ` Christoph Lameter
2016-11-28 16:38       ` Christoph Lameter
2016-11-28 18:47       ` Mel Gorman
2016-11-28 18:47         ` Mel Gorman
2016-11-28 18:54         ` Christoph Lameter
2016-11-28 18:54           ` Christoph Lameter
2016-11-28 20:59           ` Vlastimil Babka
2016-11-28 20:59             ` Vlastimil Babka
2016-11-28 19:54 ` Johannes Weiner [this message]
2016-11-28 19:54   ` Johannes Weiner
2016-11-30 12:40 ` Jesper Dangaard Brouer
2016-11-30 12:40   ` Jesper Dangaard Brouer
2016-11-30 14:06   ` Mel Gorman
2016-11-30 14:06     ` Mel Gorman
2016-11-30 15:06     ` Jesper Dangaard Brouer
2016-11-30 15:06       ` Jesper Dangaard Brouer
2016-11-30 16:35       ` Mel Gorman
2016-11-30 16:35         ` Mel Gorman
2016-12-01 17:34         ` Jesper Dangaard Brouer
2016-12-01 17:34           ` Jesper Dangaard Brouer
2016-12-01 22:17           ` Paolo Abeni
2016-12-01 22:17             ` Paolo Abeni
2016-12-02 15:37             ` Jesper Dangaard Brouer
2016-12-02 15:37               ` Jesper Dangaard Brouer
2016-12-02 15:44               ` Paolo Abeni
2016-12-02 15:44                 ` Paolo Abeni
2016-11-30 13:05 ` Michal Hocko
2016-11-30 13:05   ` Michal Hocko
2016-11-30 14:16   ` Mel Gorman
2016-11-30 14:16     ` Mel Gorman
2016-11-30 14:59     ` Michal Hocko
2016-11-30 14:59       ` 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=20161128195421.GA22236@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --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 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.