FYI:
make[2]: *** No rule to make target
`doxygen-doc/man/man3/HWLOC_TOPOLOGY_FLAG_ICACHES.3', needed by `all-am'. Stop.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
Sorry -- I should have done a "make -k" first:
make[2]: *** No rule to make target
`doxygen-doc/man/man3/HWLOC_TOPOLOGY_FLAG_ICACHES.3', needed by `all-am'.
make[2]: *** No rule to make target
`doxygen-doc/man/man3/hwloc_get_cache_type_depth.3', needed by `all-am'.
make[2]: *** No rule to make t
These come from the icache branch merge. It was merged on 2012/03/16,
and nightly builds and our local testing look happy since then. Do you
need a fresh checkout and/or make maintainer-clean?
Brice
Le 20/03/2012 12:51, Jeffrey Squyres a écrit :
> Sorry -- I should have done a "make -k" first:
No, what I need is to install doxygen (duh!).
Sorry -- this is a relatively new laptop and I forgot to install doxygen.
Ignore my mails; sorry for the noise...
On Mar 20, 2012, at 8:18 AM, Brice Goglin wrote:
> These come from the icache branch merge. It was merged on 2012/03/16,
> and nightly
On a machine I have, I'm getting output like this with hwloc trunk:
PCIBridge
PCI 15b3:6750
Net L#11 "eth0"
Net L#12 "eth1"
OpenFabrics L#13 "mlx4_0"
which is all well and good (mlx4_0 is a RoCE card).
Is there a way in the hwloc topology data to tell which port
Le 20/03/2012 15:33, Jeffrey Squyres a écrit :
> On a machine I have, I'm getting output like this with hwloc trunk:
>
> PCIBridge
> PCI 15b3:6750
> Net L#11 "eth0"
> Net L#12 "eth1"
> OpenFabrics L#13 "mlx4_0"
>
> which is all well and good (mlx4_0 is a RoCE card)
Samuel:
What do you think of this patch? It separates out the individual version
checking to make the #define logic a little easier to read.
Index: include/hwloc/autogen/config.h.in
===
--- include/hwloc/autogen/config.h.in (revi
On Mar 20, 2012, at 10:46 AM, Brice Goglin wrote:
>> Is there a way in the hwloc topology data to tell which port eth0 and eth1
>> correspond to?
>
> You should have a "Address" info attribute in each eth object containing
> something like 80:34:00:48:fe:80:00:00:00:00:00:01:00:02:c9:03:00:0b:53
Le 20/03/2012 15:53, Jeffrey Squyres a écrit :
> On Mar 20, 2012, at 10:46 AM, Brice Goglin wrote:
>
>>> Is there a way in the hwloc topology data to tell which port eth0 and eth1
>>> correspond to?
>> You should have a "Address" info attribute in each eth object containing
>> something like 80:34
On Mar 20, 2012, at 11:09 AM, Brice Goglin wrote:
>> I looked at that. It's not immediately clear to me how to map that to "ib0"
>> and "ib1", for example.
>
> Also I see that /sys/class/infiniband/mlx4_0/node_guid contains
> 0002:c903:000b:5348, that's ib0's end-of-address minus one, and ib1's
Le 20/03/2012 16:52, Jeffrey Squyres a écrit :
> On Mar 20, 2012, at 11:09 AM, Brice Goglin wrote:
>
>>> I looked at that. It's not immediately clear to me how to map that to
>>> "ib0" and "ib1", for example.
>> Also I see that /sys/class/infiniband/mlx4_0/node_guid contains
>> 0002:c903:000b:534
On Mar 20, 2012, at 12:02 PM, Brice Goglin wrote:
> Actually, what we don't know is how to map that to port 1/2 (we have
> ib0/ib1 mac addresses, those are = GUID+1/2 on my machine)
Yes, that is more correctly stated.
A Mellanox guy pointed me to the ibdev2netdev script in current OFED
distrib
Le 20/03/2012 19:02, Jeffrey Squyres a écrit :
> On Mar 20, 2012, at 12:02 PM, Brice Goglin wrote:
>
>> Actually, what we don't know is how to map that to port 1/2 (we have
>> ib0/ib1 mac addresses, those are = GUID+1/2 on my machine)
>
> Yes, that is more correctly stated.
>
> A Mellanox guy point
On Mar 20, 2012, at 3:09 PM, Brice Goglin wrote:
> Looks like we just need to read /sys/class/net/ib*/dev_id, make that
> decimal, add one, and we get the port number.
>
> How would you like this to appear in the topology? Is a object info such
> as "Port=%d" in each network interface in a OFED o
Le 20/03/2012 20:12, Jeffrey Squyres a écrit :
> On Mar 20, 2012, at 3:09 PM, Brice Goglin wrote:
>
>> Looks like we just need to read /sys/class/net/ib*/dev_id, make that
>> decimal, add one, and we get the port number.
>>
>> How would you like this to appear in the topology? Is a object info such
On Mar 20, 2012, at 3:29 PM, Brice Goglin wrote:
> By the way, do you want Port numbers to start at 0 or 1?
IIRC, IB (and probably RoCE) port numbers start with 1. Shrug.
So let's report whatever they report.
The sample output you showed looks perfect to me.
Is your patch small enough to por
Le 20/03/2012 20:30, Jeffrey Squyres a écrit :
> On Mar 20, 2012, at 3:29 PM, Brice Goglin wrote:
>
>> By the way, do you want Port numbers to start at 0 or 1?
>
> IIRC, IB (and probably RoCE) port numbers start with 1. Shrug.
>
> So let's report whatever they report.
>
> The sample output you sho
On Mar 20, 2012, at 3:45 PM, Brice Goglin wrote:
> That looks good to me, as long as starting port numbers to 1 for
> non-IB/OFED is OK.
Hmm. Not sure about that. I always thought it was strange that IB devices
started with port 1.
Are *we* (hwloc) supplying the port number, or are you get
Le 20/03/2012 21:48, Jeffrey Squyres a écrit :
> On Mar 20, 2012, at 3:45 PM, Brice Goglin wrote:
>
>> That looks good to me, as long as starting port numbers to 1 for
>> non-IB/OFED is OK.
>
> Hmm. Not sure about that. I always thought it was strange that IB devices
> started with port 1.
>
>
Le 20/03/2012 21:48, Jeffrey Squyres a écrit :
> On Mar 20, 2012, at 3:45 PM, Brice Goglin wrote:
>
>> That looks good to me, as long as starting port numbers to 1 for
>> non-IB/OFED is OK.
>
> Hmm. Not sure about that. I always thought it was strange that IB devices
> started with port 1.
>
>
On Mar 20, 2012, at 5:07 PM, Brice Goglin wrote:
> New patch attached, it doesn't add port numbers for non-IB devices.
Does the new patch add port numbers at all if /device/infiniband doesn't
exist? I.e., is the dev_id/port number irrelevant if it's not an OpenFabrics
device?
--
Jeff Squyre
Le 20/03/2012 22:12, Jeffrey Squyres a écrit :
> On Mar 20, 2012, at 5:07 PM, Brice Goglin wrote:
>
>> New patch attached, it doesn't add port numbers for non-IB devices.
>
> Does the new patch add port numbers at all if /device/infiniband doesn't
> exist?
No. For each ethX, the hwloc "ethX" obje
On Mar 20, 2012, at 5:30 PM, Brice Goglin wrote:
>> Does the new patch add port numbers at all if /device/infiniband
>> doesn't exist?
>
> No. For each ethX, the hwloc "ethX" object will only get a Port number
> if the corresponding sysfs device has some infiniband "child".
> Otherwise, no Port
Jeffrey Squyres, le Tue 20 Mar 2012 15:51:54 +0100, a écrit :
> What do you think of this patch? It separates out the individual version
> checking to make the #define logic a little easier to read.
Interesting indeed, I vote for it.
Samuel
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.5a1r4415
Start time: Tue Mar 20 21:01:01 EDT 2012
End time: Tue Mar 20 21:04:22 EDT 2012
Your friendly daemon,
Cyrador
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.4.2a1r4416
Start time: Tue Mar 20 21:04:22 EDT 2012
End time: Tue Mar 20 21:07:08 EDT 2012
Your friendly daemon,
Cyrador
Hello,
I am trying out hwloc on a very early access Blue Gene /Q system.
I've built hwloc from source and am running test programs that use it.
The most serious issue I'm observing is that when MPI and hwloc
are used in the same program, hwloc aborts with "Topology became empty,
aborting!".
This d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/03/12 13:37, Daniel Ibanez wrote:
> Please let me know if theres a hint of what could be causing it,
> where to post, and what info to provide.
Are you running Linux or CNK on the compute nodes for this?
cheers!
Chris
- --
Christopher Sa
28 matches
Mail list logo
