[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190419140521.GI7751@bombadil.infradead.org>
Date: Fri, 19 Apr 2019 07:05:21 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Mel Gorman <mgorman@...hsingularity.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Mikulas Patocka <mpatocka@...hat.com>,
James Bottomley <James.Bottomley@...senpartnership.com>,
linux-parisc@...r.kernel.org, linux-mm@...ck.org,
Vlastimil Babka <vbabka@...e.cz>,
LKML <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org
Subject: DISCONTIGMEM is deprecated
On Fri, Apr 19, 2019 at 10:43:35AM +0100, Mel Gorman wrote:
> DISCONTIG is essentially deprecated and even parisc plans to move to
> SPARSEMEM so there is no need to be fancy, this patch simply disables
> watermark boosting by default on DISCONTIGMEM.
I don't think parisc is the only arch which uses DISCONTIGMEM for !NUMA
scenarios. Grepping the arch/ directories shows:
alpha (does support NUMA, but also non-NUMA DISCONTIGMEM)
arc (for supporting more than 1GB of memory)
ia64 (looks complicated ...)
m68k (for multiple chunks of memory)
mips (does support NUMA but also non-NUMA)
parisc (both NUMA and non-NUMA)
I'm not sure that these architecture maintainers even know that DISCONTIGMEM
is deprecated. Adding linux-arch to the cc.
Powered by blists - more mailing lists