Re: [PATCH RFC 1/5] sched,numa: build table of node hop distance

From: Peter Zijlstra
Date: Sun Oct 12 2014 - 09:17:38 EST

On Wed, Oct 08, 2014 at 03:37:26PM -0400, riel@xxxxxxxxxx wrote:
> + sched_domains_numa_hops = kzalloc(sizeof(int) * nr_node_ids * nr_node_ids, GFP_KERNEL);
> + if (!sched_domains_numa_hops)
> + return;

That's potentially a _BIG_ table (1M for a 512 node system).
The node_distance has magic allocations and is of u8 size, is there any
way we can re-use node_distance and avoid a second O(n^2) allocation?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at