Messages in this thread | | | Date | Wed, 6 Jun 2012 15:43:29 +0800 | Subject | Re: [tip:sched/core] sched/numa: Rewrite the CONFIG_NUMA sched domain support | From | Alex Shi <> |
| |
> + /* > + * O(nr_nodes^2) deduplicating selection sort -- in order to find the > + * unique distances in the node_distance() table. > + * > + * Assumes node_distance(0,j) includes all distances in > + * node_distance(i,j) in order to avoid cubic time.
Curious for other platforms node_distance number, actually, this assumption is right for what I saw Intel platforms. but it is not match acpispec50.pdf:
Table 6-152 Example Relative Distances Between Proximity Domains Proximity Domain 0 1 2 3 0 10 15 20 18 1 15 10 16 24 2 20 16 10 12 3 18 24 12 10
Alex -- 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/
| |