Re: Off topic: Numactl "distance" wrong

From: Yinghai Lu
Date: Fri Apr 03 2009 - 18:16:05 EST


On Fri, Apr 3, 2009 at 2:55 PM, Andi Kleen <andi@xxxxxxxxxxxxxx> wrote:
> Yinghai Lu <yhlu.kernel@xxxxxxxxx> writes:
>
>> On Fri, Apr 3, 2009 at 2:43 PM, David Rientjes <rientjes@xxxxxxxxxx> wrote:
>>>
>>> Yinghai, can you elaborate on exactly what type of interface you can
>>> imagine for modifying the distance for nodes through sysfs?  It seems like
>>> you'd have to report the entire physical topology in one write, for which
>>> we currently don't have an interface for beyond pxms, instead of per-node
>>> distances to remote nodes.
>>
>> acpi_numa_slit_init() in srat_64.c will have one copy (called
>> acpi_slit) of SLIT, if there is SLIT from ACPI.
>>
>> so if numa is enabled, could expose that acpi_slit via sysfs for the
>> user to update it.
>
> That's not enough. You would need to redo all the zone fallback tables
> in the VM that are initialized based on topology, do new scheduler
> topologies and all kind of other stuff.
>
> Besides I don't know any user space software which actually does anything
> with the distances. The kernel does, but for it it doesn't make much difference
> on smaller systems.

how the cpu and memory hotplug works when it could change kind of topology?
sched: wonder if arch_reinit_sched_domains() is used to
rebuild_sched_domains() it will call node_distance()

or ACPI asl code could update SLIT table , and let os use slit table.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/