Messages in this thread | | | Subject | Re: Externalize SLIT table | From | Matthew Dobson <> | Date | Tue, 09 Nov 2004 11:45:00 -0800 |
| |
On Thu, 2004-11-04 at 09:04, Andi Kleen wrote: > On Thu, Nov 04, 2004 at 04:31:42PM +0100, Erich Focht wrote: > > On Thursday 04 November 2004 15:13, Jack Steiner wrote: > > > I think it would also be useful to have a similar cpu-to-cpu distance > > > metric: > > > ????????% cat /sys/devices/system/cpu/cpu0/distance > > > ????????10 20 40 60 > > > > > > This gives the same information but is cpu-centric rather than > > > node centric. > > > > I don't see the use of that once you have some way to find the logical > > CPU to node number mapping. The "node distances" are meant to be > > I think he wants it just to have a more convenient interface, > which is not necessarily a bad thing. But then one could put the > convenience into libnuma anyways. > > -Andi
Using libnuma sounds fine to me. On a 512 CPU system, with 4 CPUs/node, we'd have 128 nodes. Re-exporting ALL the same data, those huge strings of node-to-node distances, 512 *additional* times in the per-CPU sysfs directories seems like a waste.
-Matt
- 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/
| |