Hi Paolo, I'm checking this out. Thanks for the work at implementing another libfabric provider - esp. for a very different network.
I'm having problems with building your fork of libfabric. Did you do something to make it only build for a restricted build environment? autogen.sh isn't present, and if I do manual autoreconf, configure (no options) then when I try to make I get a compile error owing to incorrect include path options. Is the intent to eventually have this provider included in the upstream ofiwg code? As others have pointed out, a dual gpl/bsd license is being used currently by the project. Thanks, Howard 2015-10-02 10:48 GMT-06:00 Paolo Inaudi <[email protected]>: > Hi all, > > Since you are working on libfabric, I figured you might be interested to > know I wrote a libfabric provider for the A3Cube Ronniee ( > http://a3cube-inc.com/ronniee-express.html) in-memory network. > > The provider has been developed for my Master's thesis at University of > Torino, in Italy, as part of a research collaboration of the university > with A3Cube. The fabric implements an hardware-based distributed shared > memory. Because of that, I easily implemented the RMA data transfer > interface, since it is basically the native operational mode; the fi_msg > interface is also available, using a remote memory region as a buffer. > Atomics and tagged messages are not supported (yet). Code is available > under LGPLv3 here: > > https://github.com/p91paul/libfabric-provider-dpa > > The provider is named "dpa" after the DPALIB API offered by A3Cube for > their products. I plan to add some documentation over the next week. > > Paolo > _______________________________________________ > ofiwg mailing list > [email protected] > http://lists.openfabrics.org/mailman/listinfo/ofiwg >
_______________________________________________ ofiwg mailing list [email protected] http://lists.openfabrics.org/mailman/listinfo/ofiwg
