Messages in this thread | | | Date | Fri, 13 May 2005 04:21:23 -0700 (PDT) | From | Christoph Lameter <> | Subject | Re: NUMA aware slab allocator V2 |
| |
On Fri, 13 May 2005, Andrew Morton wrote:
> It didn't produce anything interesting. For some reason the console output > stops when start_kernel() runs console_init() (I guess it all comes out > later) so the machine is running blind when we run kmem_cache_init(). > Irritating. I just moved the console_init() call to happen later on. > > It's going BUG() in kmem_cache_init()->set_up_list3s->is_node_online > because for some reason the !CONFIG_NUMA ppc build has MAX_NUMNODES=16, > even though there's only one node.
Yuck.
The definition for the number of NUMA nodes is dependent on CONFIG_FLATMEM instead of CONFIG_NUMA in mm. CONFIG_FLATMEM is not set on ppc64 because CONFIG_DISCONTIG is set! And consequently nodes exist in a non NUMA config.
s/CONFIG_NUMA/CONFIG_FLATMEM/ ??
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |