[Openframeworkwg] revisiting the OFWG name

[Hefty, Sean]

Given the choice between 'device direct' versus 'process direct IO', I would lean toward the latter.  We're defining the APIs around the application requirement, versus trying to expose what each device does.

Additionally, I believe we'll eventually want to expose capabilities that are best thought of as being part of the network itself (e.g. collective operations, topology details).


> -----Original Message-----
> From: openframeworkwg-bounces at lists.openfabrics.org
> [mailto:openframeworkwg-bounces at lists.openfabrics.org] On Behalf Of Bernard
> Metzler
> Sent: Wednesday, March 05, 2014 8:55 AM
> To: Jeff Squyres (jsquyres)
> Cc: Open Frameworks Working Group; openframeworkwg-
> bounces at lists.openfabrics.org
> Subject: Re: [Openframeworkwg] revisiting the OFWG name
> 
> well some of us even think about accessing local pci attached SCM via
> openfabrics interface (RDMA Read/Write etc.). So to me a generalization
> for all devices which allow for (restrict that to byte granular ?) direct
> memory access makes sense.  I am not sure about further generalization
> than memory though. But in the end, any addressable device resource can be
> read/written that way. With that, I would end up in Christoph's camp.
> 
> Best
> Bernard.
> 
> 
> openframeworkwg-bounces at lists.openfabrics.org wrote on 03/05/2014 05:41:07
> PM:
> 
> > From: "Jeff Squyres (jsquyres)" <jsquyres at cisco.com>
> > To: Christoph Lameter <christoph at lameter.com>
> > Cc: Open Frameworks Working Group <openframeworkwg at lists.openfabrics.org>
> > Date: 03/05/2014 05:41 PM
> > Subject: Re: [Openframeworkwg] revisiting the OFWG name
> > Sent by: openframeworkwg-bounces at lists.openfabrics.org
> >
> > I wasn't aware that we were targeting non-network devices.
> >
> > For full-access PCI device OS bypass, there's already VFIO, right?
> >
> >
> > On Mar 5, 2014, at 7:44 AM, Christoph Lameter <christoph at lameter.com>
> wrote:
> >
> > > Well I think not so much about a fabric but of general direct
> > hardware device access from userspace for multiple purposes.  NVram,
> > SSDs, Coprocessors etc come to mind.
> > >
> > > So
> > >
> > > "Device Direct"
> > >
> > > ?
> > >
> > > Can do more than Network Direct.
> > >
> > >
> > > On Wed, Mar 5, 2014 at 9:36 AM, Jeff Squyres (jsquyres)
> > <jsquyres at cisco.com> wrote:
> > > How about "The Libfabric Working Group"?  libfabric has the
> > advantage of being nicely google-able -- i.e., all the results are
> > directly related to this effort.
> > >
> > > "PDIO" does have a nice ring to it, but I agree it is close to
> > "Network Direct", and seems to bring up lots of other sites via googling.
> > >
> > >
> > > On Mar 4, 2014, at 6:09 PM, "Hefty, Sean" <sean.hefty at intel.com> wrote:
> > >
> > > > In today's meeting we revisited trying to come up with a name
> > for this workgroup and the work that it is doing.  To that end, I
> > went back through the email archives in hope that we can narrow down
> > and select some option by the next meeting.
> > > >
> > > > These are the basic options that have been thrown out so far:
> > > >
> > > > Keep current name - OpenFrameworks
> > > > OpenFabricFrameworks
> > > > FabricFrameworks
> > > > OFA Agnostic Process Direct IO API Working Group
> > > >
> > > > To this end, I've been using the terms libfabric and fabric
> > interfaces, without hearing any objections (so far), so I will also
> > propose something simple:
> > > >
> > > > Open Fabrics Interfaces (Working Group)
> > > >
> > > > I do like the term PDIO that Doug came up with, but it
> > immediately makes me think of Network Direct by Microsoft.
> > > >
> > > > Please provide comments, support, alternatives, etc.
> > > >
> > > > Thanks,
> > > > Sean
> > > > _______________________________________________
> > > > Openframeworkwg mailing list
> > > > Openframeworkwg at lists.openfabrics.org
> > > > http://lists.openfabrics.org/cgi-bin/mailman/listinfo/openframeworkwg
> > >
> > >
> > > --
> > > Jeff Squyres
> > > jsquyres at cisco.com
> > > For corporate legal information go to: http://www.cisco.com/web/
> > about/doing_business/legal/cri/
> > >
> > > _______________________________________________
> > > Openframeworkwg mailing list
> > > Openframeworkwg at lists.openfabrics.org
> > > http://lists.openfabrics.org/cgi-bin/mailman/listinfo/openframeworkwg
> > >
> >
> >
> > --
> > Jeff Squyres
> > jsquyres at cisco.com
> > For corporate legal information go to: http://www.cisco.com/web/
> > about/doing_business/legal/cri/
> >
> > _______________________________________________
> > Openframeworkwg mailing list
> > Openframeworkwg at lists.openfabrics.org
> > http://lists.openfabrics.org/cgi-bin/mailman/listinfo/openframeworkwg
> >
> 
> _______________________________________________
> Openframeworkwg mailing list
> Openframeworkwg at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/openframeworkwg