[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190421132606.GJ7751@bombadil.infradead.org>
Date: Sun, 21 Apr 2019 06:26:07 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Mike Rapoport <rppt@...ux.ibm.com>
Cc: Mel Gorman <mgorman@...hsingularity.net>,
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: Re: DISCONTIGMEM is deprecated
On Sun, Apr 21, 2019 at 09:38:59AM +0300, Mike Rapoport wrote:
> On Fri, Apr 19, 2019 at 07:05:21AM -0700, Matthew Wilcox wrote:
> > 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)
>
> i386 NUMA as well
I clearly over-trimmed. The original assumption that Mel had was that
DISCONTIGMEM => NUMA, and that's not true on the above six architectures.
It is true on i386 ;-)
Powered by blists - more mailing lists