On Thursday, August 12, 2004 7:58 pm, Alex Williamson wrote: > This probably isn't ready for inclusion yet, but I wanted to see if > anybody else could make use of it. This works on HP sx1000 boxes setup > for NUMA and I think it's ACPI namespace does the right thing. All this > does is walk through namespace looking for devices with an _MAT method > that returns an IOSAPIC and also has a _PXM method to tell us the > proximity domain where it lives. The node data gets stored in the > iosapic data structure because doing this lookup is pretty slow. Does > this jive with what other ACPI NUMA boxes are exporting in namespace? > I'm hoping everyone will put the _PXM on the same device as the _MAT, > but I'm wondering if I need to add support for looking on parent > objects. Thoughts? Thanks, Matt Dobson is working on a pci_to_nodemask, might that be used instead? If we did it that way, we could put it in generic code, dependent on CONFIG_NUMA or something, rather than keeping it ACPI specific. Jesse - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Aug 13 11:32:26 2004
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:29 EST