Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [hwloc-devel] 1.3.1 and 1.4rc1
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2011-12-13 10:55:38

On Dec 13, 2011, at 10:48 AM, Brice Goglin wrote:

> We can get the locality for those by reading
> /sys/class/net/<name>/device/local_cpus with name=eth0 and so on. That's
> very similar to what we do for OFED. I can add a helper for these
> devices as well if needed.

That would be great. It would cover many, many people in the world (i.e., outside of those with specialty/nice network types -- ok, couldn't resist that one ;-) ).

> How do you identify these devices in your application ? by interface name ?

Yes, mostly by interface name.

How about a generic lookup? I.e., take the device name pattern (or specific string) to look for as input?

Jeff Squyres
For corporate legal information go to: