[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1603281951380.31323@east.gentwo.org>
Date: Mon, 28 Mar 2016 19:53:39 -0500 (CDT)
From: Christoph Lameter <cl@...ux.com>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: js1304@...il.com, Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Jesper Dangaard Brouer <brouer@...hat.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Joonsoo Kim <iamjoonsoo.kim@....com>
Subject: Re: [PATCH 02/11] mm/slab: remove BAD_ALIEN_MAGIC again
On Mon, 28 Mar 2016, Andrew Morton wrote:
> On Mon, 28 Mar 2016 14:26:52 +0900 js1304@...il.com wrote:
>
> > From: Joonsoo Kim <iamjoonsoo.kim@....com>
> >
> > Initial attemp to remove BAD_ALIEN_MAGIC is once reverted by
> > 'commit edcad2509550 ("Revert "slab: remove BAD_ALIEN_MAGIC"")'
> > because it causes a problem on m68k which has many node
> > but !CONFIG_NUMA.
>
> Whaaa? How is that even possible? I'd have thought that everything
> would break at compile time (at least) with such a setup.
Yes we have that and the support for this caused numerous issues. Can we
stop supporting such a configuration?
Powered by blists - more mailing lists