***SPAM*** Re: [ofa-general] atomic operations on ppc64
Dotan Barak
dotanba at gmail.com
Fri Sep 19 07:21:03 PDT 2008
>> Bugs can be anywhere: application / Driver / HW ...
>>
>> Can you try to use server in x86 and client in PPC64 and then server in
>> PPC64 and client in x86?
>>
>> Which OFED version do you use?
>> Can you send the output of ibv_devinfo?
>>
>> Dotan
>>
>>
>
> I tried the combination ppc64-x86 and x86-ppc64.
> The result was a hang on the client side on poll (see code above) on both cases.
> Could endianess be playing a role here? This is the first time I try
> to put different architectures to communicate.
>
> I have ofed 1.2.5.5
>
> ibv_devinfo (x86 machine used for the ppc64-x86 communication)
>
> hca_id: mthca0
> fw_ver: 1.2.0
> node_guid: 0002:c902:0021:b820
> sys_image_guid: 0002:c902:0021:b823
> vendor_id: 0x02c9
> vendor_part_id: 25204
> hw_ver: 0xA0
> board_id: MT_03B0110001
> phys_port_cnt: 1
> port: 1
> state: PORT_ACTIVE (4)
> max_mtu: 2048 (4)
> active_mtu: 2048 (4)
> sm_lid: 142
> port_lid: 134
> port_lmc: 0x01
>
> ibv_devinfo (ppc64)
>
> hca_id: mlx4_0
> fw_ver: 2.3.000
> node_guid: 0002:c903:0000:9334
> sys_image_guid: 0002:c903:0000:9337
> vendor_id: 0x02c9
> vendor_part_id: 25418
> hw_ver: 0xA0
> board_id: IBM08A0000001
> phys_port_cnt: 2
> port: 1
> state: PORT_ACTIVE (4)
> max_mtu: 2048 (4)
> active_mtu: 2048 (4)
> sm_lid: 142
> port_lid: 68
> port_lmc: 0x01
>
> port: 2
> state: PORT_DOWN (1)
> max_mtu: 2048 (4)
> active_mtu: 2048 (4)
> sm_lid: 0
> port_lid: 0
> port_lmc: 0x00
>
>
> Cheers,
>
It seems that you didn't check the same HCA in each arch.
Can you try to use the mthca device in PPC64 and check the results?
(Anyway, i would have suggest you to upgrade the OFED package that you
are using)
Dotan
More information about the general
mailing list