On Tue, May 15, 2007 at 01:40:52PM -0600, Li-Ta Lo wrote:
> Hi,
>
> I don't know if this is well known or interesting. You can find
> the processor locality of a network interface easily without
> reading the hardware schematics. The linux kernel export it for you:
>
> [ollie_at_boxtop1 device]$ cd /sys/class/net/ib0/
> [ollie_at_boxtop1 ib0]$ ls
> address create_child features link_mode statistics uevent
> addr_len delete_child flags mtu subsystem weight
> broadcast device ifindex operstate tx_queue_len
> carrier dormant iflink pkey type
> [ollie_at_boxtop1 ib0]$ cd device
> [ollie_at_boxtop1 device]$ ls
> broken_parity_status infiniband_mad:issm0 local_cpus resource0
> bus infiniband_mad:issm1 modalias resource2
> class infiniband_mad:umad0 net:ib0 subsystem
> config infiniband_mad:umad1 net:ib1
> subsystem_device
> device infiniband:mthca0 pools
> subsystem_vendor
> driver infiniband_verbs:uverbs0 power uevent
> enable irq resource vendor
> [ollie_at_boxtop1 device]$ cat local_cpus
> 00000000,00000003
>
>
IPoIB is not always available on the clusters, but the same info is also
reachable through /sys/class/infiniband/mthca0/device/local_cpus.
--
Gleb.
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}