[ofa-general] uDAPL Question

[Don Kerr]

OK, so no good way to determine this from uDAPL alone, its expected that 
the provider will register/deregister with the file as needed.

Next question. is there a way to get the entire dat.conf entry from the 
uDAPL API?

Example: Typical dat.conf entry might look something like:
    OpenIB-cma u1.2 nonthreadsafe default /usr/local/lib64/libdaplcma.so 
dapl.1.2 "ib0 0" ""

I can find the first field, in this example "OpenIB-cma", from the ia 
attribute name but what if I wanted to correlate say the 6th field, "ib0 
0", with the first field?

Thanks
-DON

Caitlin Bestler wrote:

> 
>
>  
>
>>-----Original Message-----
>>From: general-bounces at lists.openfabrics.org 
>>[mailto:general-bounces at lists.openfabrics.org] On Behalf Of Don Kerr
>>Sent: Monday, July 09, 2007 8:04 AM
>>To: Roland Dreier
>>Cc: general
>>Subject: Re: [ofa-general] uDAPL Question
>>
>>Sorry. I was wrongly lumping port and HCA together.
>>
>>2 HCA cards each with 2 ports but only one port on one card 
>>is operational and by that I mean can be pinged or seen as 
>>"UP" when you run ifconfig. But both are still listed in the dat.conf.
>>
>>-DON
>>
>>    
>>
>The DAT Registry allows for a provider to deregister itself, but
>there are no guidelines as to when it should do so for indefinite
>but non-permanent unavailabiilty. I have always presumed that Host
>OS standards for temporarily unavailable devices should be applied.
>
>  
>