[libfabric-users] troubled by FI_SOURCE use

Biddiscombe, John A. biddisco at cscs.ch
Wed Mar 13 23:41:03 PDT 2019

Dear list

Everything is working very nicely, but when looking at the feature matrix, I see that FI_SOURCE is not available with the verbs provider. That's a huge PITA because it means a design that work on N platforms won't work on that one and working around FI_SOURCE might mean that every message needs to add that somewhere (I didn't really think it through yet for my parcelport design).

Is verbs FI_SOURCE likely to be implemented one day, or is it something that would require too much intrusive change to the provider code?


From: Libfabric-users [libfabric-users-bounces at lists.openfabrics.org] on behalf of Biddiscombe, John A. [biddisco at cscs.ch]
Sent: 13 March 2019 11:44
To: Hefty, Sean; libfabric-users at lists.openfabrics.org
Subject: {Spam?}  Re: [libfabric-users] troubled by FI_SOURCE use


Thanks. I found the bug. I had not copied an fi_Addr_T in one place before my send operation and so it was always going to 0 - hence the root was receiving it.


From: Hefty, Sean [sean.hefty at intel.com]
Sent: 13 March 2019 01:33
To: Biddiscombe, John A.; libfabric-users at lists.openfabrics.org
Subject: RE: troubled by FI_SOURCE use

> >This is using the sockets provider.  Can you update to a newer version of
> libfabric?
> I'm using a recent master. I just forgot to change the FI_VERSION(1,4) to
> FI_VERSION(MAJOR,MINOR) in my get info call. It comes out as 1.7 now

I realize this is a test app, but you almost never want to use FI_VERSION(MAJOR,MINOR).  Otherwise, if you build with a newer version of the library, it will assume that the app knows of fields and behavior that was introduced in that version.
Libfabric-users mailing list
Libfabric-users at lists.openfabrics.org

More information about the Libfabric-users mailing list