Re: [ofiwg] OFIWG - Call for Agenda Topics for tomorrow (2/9/16) (EOM)

2016-02-09 Thread Paul Grun
Greetings - I have nothing for today's agenda. Should we meet anyway, or cancel for today? One possible topic is the need for a F-2-F meeting in Monterey, but that can be handled by email. Opinions? -Paul From: ofiwg-boun...@lists.openfabrics.org [mailto:ofiwg-boun...@lists.openfabrics.org] O

Re: [ofiwg] OFIWG - Call for Agenda Topics for tomorrow (2/9/16) (EOM)

2016-02-09 Thread Hefty, Sean
I would like to discuss the utility library/provider framework that is being added to libfabric. ___ ofiwg mailing list ofiwg@lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/ofiwg

Re: [ofiwg] OFIWG - Call for Agenda Topics for tomorrow (2/9/16) (EOM)

2016-02-09 Thread Paul Grun
Okay, then let's plan to meet as scheduled. Agenda - short update on OFIWG sessions at the Workshop - F-2-F meeting in Monterey in April - yes or no? - utility/provider framework -Original Message- From: Hefty, Sean [mailto:sean.he...@intel.com] Sent: Tuesday, February 09, 2016 8:40 AM T

[ofiwg] reminder of new libfabrics-users mail list

2016-02-09 Thread Hefty, Sean
Do you like libfabrics? Do you like to help people? Do you need more email? Then the libfabrics-users email list is for you! This is a reminder (at least I hope it's a reminder), that there is a user focused email list for libfabrics. You can sign up for the mailing list here: http://lists.

[ofiwg] input on intra-node implementation

2016-02-09 Thread Hefty, Sean
I want to provide an intra-node communication (i.e. loopback) utility to libfabric. The loopback utility could be part of a stand-alone provider, or incorporated into other providers. For this, I'm looking at selecting a single, easily maintained implementation. These are my choices so far:

Re: [ofiwg] input on intra-node implementation

2016-02-09 Thread Atchley, Scott
> On Feb 9, 2016, at 3:54 PM, Hefty, Sean wrote: > > I want to provide an intra-node communication (i.e. loopback) utility to > libfabric. The loopback utility could be part of a stand-alone provider, or > incorporated into other providers. For this, I'm looking at selecting a > single, easi