[ewg] OFA EWG Meeting: Monday, Mar 27, 2017, 09:00 AM US Pacific Time (12pm EST) - Meeting Cancelled

[Davis, Arlin R]

The general consensus seems to be leaning towards a move to rdma-core v13. 
Let's finalize decision during Monday's EWG con-call and get a clear path to RC2. 

> -----Original Message-----
> From: Coulter, Susan K [mailto:skc at lanl.gov]
> Sent: Thursday, April 06, 2017 11:40 AM
> To: Adit Ranadive <aditr at vmware.com>
> Cc: Davis, Arlin R <arlin.r.davis at intel.com>; ewg at lists.openfabrics.org
> Subject: Re: [ewg] OFA EWG Meeting: Monday, Mar 27, 2017, 09:00 AM US
> Pacific Time (12pm EST) - Meeting Cancelled
> 
> If this helps, it is from 3/21 … to my knowledge the most recent summary sent
> by Doug Ledford.
> 
> Updates from version 12:
> 
> 	• Minor improvements to qedr provider
> 	• Add libpvrdma provider for VMWare rdma virt devices
> 	• Improved RoCE AH creation
> 	• Packet Pacing support
> 	• Various github build system improvements
> 	• Updates to Debian and Red Hat packaging
> 	• Timestamp support in mlx4 provider
> 	• Make the libibverbs/provider interface private
> 	• Clean up headers for improved multi-arch support
> 	• Add Verbs Direct support for mlx5 provider
> 	• Implement new, more specific multi-arch barrier methods
> 	• Update all providers to the modern registration method and remove
> ibv_register_driver entirely
> 	• Switch the code to use gcc endian conversion functions
> 	• Fix an endianness issue in srp_daemon
> 	• Implement a new release mechanism that should create more distro
> friendly tarballs based on the common release tagging format
> 	• Updates to make it possible to run sparse on rdma-core
> 	• Fixes found by running sparse on rdma-core
> 	• Fixes to travis tarball upload script
> 	• Fix to broken cmake test
> 
> 
> > On Apr 6, 2017, at 12:31 PM, Adit Ranadive <aditr at vmware.com> wrote:
> >
> > On Wed, Apr 05, 2017 at 10:22:26PM +0000, Davis, Arlin R wrote:
> >> We need to finalize the changes going into RC2. Can I get some feedback
> regarding moving to rdma-core v13 or staying with v12? Moving to rdma-core
> v13 would make vmw_pvrdma inclusion easier but would require VMware to
> pull back their changes pushed into RC1.
> >>
> >> Comments?
> >>
> >
> > I'm not opposed to rolling back the RC1 changes for vmw_pvrdma. There
> > are fairly trivial. However, you would have find out the various
> > differences between rdma-core-12 and 13, f.e. bug fixes, functionality
> changes, etc.
> > and how those impact the existing providers.
> >
> > The other thing I wanted to point out was regarding the Qlogic
> > provider -
> > rdma-core-12 added them as a user space provider but there isnt a
> > kernel driver in OFED 4.8. I believe they were added as a provider in 4.9
> kernel.
> > Not sure, if that is an issue for you guys.
> >
> > Thanks,
> > Adit
> >
> >
> >
> > _______________________________________________
> > ewg mailing list
> > ewg at lists.openfabrics.org
> > http://lists.openfabrics.org/mailman/listinfo/ewg
> 
> ==================================================
> Susan Coulter / HPC-DES
> Network Capability Lead
> (505) 667-8425
> “Once in a while you get shown the light
>     In the strangest of places if you look at it right”  Robert Hunter
> ==================================================
> 
> 
> 
> 
> 
>