From: Christoph Lameter <cl@linux.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Linux MM <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vladimir Davydov <vdavydov@parallels.com>
Subject: Re: BUG: enable_cpucache failed for radix_tree_node, error 12 (was: Re: [PATCH v3 9/9] slab: remove BAD_ALIEN_MAGIC)
Date: Fri, 8 Aug 2014 09:11:12 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.11.1408080909480.16459@gentwo.org> (raw)
In-Reply-To: <CAMuHMdWNNuPgDsjM1eM0uo2090-6OxAX8Kfw8Pcd2zo5G6zPkw@mail.gmail.com>
On Fri, 8 Aug 2014, Geert Uytterhoeven wrote:
> > Ok this is broken on m68k. CONFIG_NUMA is required for this to work. If
> > the arch code does this despite !CONFIG_NUMA then lots of things should
> > break.
>
> Can you please elaborate? We've been using for years...
!CONFIG_NUMA leads to the assumption of a system with a single node in
numerous places.
F.e. in include/linux/mm.h:
static inline int zone_to_nid(struct zone *zone)
{
#ifdef CONFIG_NUMA
return zone->node;
#else
return 0;
#endif
}
--
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>
prev parent reply other threads:[~2014-08-08 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 11:52 Geert Uytterhoeven
2014-08-07 12:36 ` Joonsoo Kim
2014-08-07 12:53 ` Geert Uytterhoeven
2014-08-07 13:03 ` Joonsoo Kim
2014-08-08 7:19 ` Joonsoo Kim
2014-08-08 8:56 ` Geert Uytterhoeven
2014-08-08 11:50 ` Christoph Lameter
2014-08-08 12:06 ` Geert Uytterhoeven
2014-08-08 14:11 ` Christoph Lameter [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=alpine.DEB.2.11.1408080909480.16459@gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vdavydov@parallels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox