>> With the "flat" addressing mode that Martin has been using (the
>> dummied down for NT version) everything is squished together. That
>> makes it a bit harder to do node local data structures, although he
>> may have enough data from the MPS table to split memory appropriately.
> sure, the only issue is the API that the hardware provides to advertise
> the start/end of the memory for each node. It doesn't matter if it's
> squashed or not as long as you still know the start/end of the phys ram
> per node. It also won't make any difference with nonlinear or
> discontigmem because you need to fill the pgdat anyways to enable the
> numa heuristics (node-affine-allocations being the most sensible etc..).
Yup, we can grab that info from the BIOS generated tables - see
Pat Gaughen's patch posted here a few days ago that parses those
tables and feeds the pgdats if you want the gory details.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:18 EST