-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/09/10 00:44, Ralph Castain wrote:
> Okay, I fixed this up for you on the devel trunk:
Thanks for that, I've not had a chance to look at this
any further recently as we're flat our bringing up our
new gear! Hopefully soon..
cheers,
Chris
- --
On 9/8/2010 10:41 AM, Jeff Squyres wrote:
On Sep 8, 2010, at 2:09 PM, Brice Goglin wrote:
Was the *real* problem that Brice's OpenFabrics bandwidth was auto-detected
incorrectly somehow?
The first problem came from IB not autodetecting at all by default and
using 800Mbit/s instead.
That sho
On Sep 8, 2010, at 2:09 PM, Brice Goglin wrote:
>> Was the *real* problem that Brice's OpenFabrics bandwidth was auto-detected
>> incorrectly somehow?
>
> The first problem came from IB not autodetecting at all by default and
> using 800Mbit/s instead.
That shouldn't be the case. Was it autode
On 9/8/2010 8:09 AM, Brice Goglin wrote:
Le 08/09/2010 14:02, Jeff Squyres a écrit :
On Sep 3, 2010, at 3:38 PM, George Bosilca wrote:
However, going over the existing BTLs I can see that some BTLs do not correctly
set this value:
BTL BandwidthAuto-detect Status
Elan200
Le 08/09/2010 14:02, Jeff Squyres a écrit :
> On Sep 3, 2010, at 3:38 PM, George Bosilca wrote:
>
>
>> However, going over the existing BTLs I can see that some BTLs do not
>> correctly set this value:
>>
>> BTL BandwidthAuto-detect Status
>> Elan2000NO
On Sep 3, 2010, at 3:38 PM, George Bosilca wrote:
> However, going over the existing BTLs I can see that some BTLs do not
> correctly set this value:
>
> BTL BandwidthAuto-detect Status
> Elan2000NO Correct
> GM 250 NO
