[ewg] [RFC] – Proposal for new process for OFED releases

Hefty, Sean sean.hefty at intel.com
Thu Dec 1 16:04:36 PST 2011


> We propose a new process for the OFED releases starting from next OFED
> release:
> - OFED content will be the relevant kernel.org modules and user space released
> packages
> - OFED will offer only backports to the distros  (no fixes)

I think this point needs to be clarified - at least to me anyway. :)

> - OFED package will be used for easy installation of all packages in a
> friendly manner
> 
> The main goals of this change:
> 1. Ensure OFED and the upstream kernel are the same
> 2. Provide customers a way to use the new features in latest kernels on
> existing distros
> 3. OFED qualification will contribute to the stability of the upstream code

I like this approach.
 
> We think that at this point of the RDMA technology maturity this is the right
> way to go.
> In this way OFED is not conflicting with the kernel or the distros, and still
> provide a valuable value for early adopters of new features.
> 
> Versions:
> We suggest that the OFED version will be the same as kernel.org
> For example, for kernel 3.2 the OFED release would be OFED-3.2.
> This would make it easy for people to associate the OFED code with the
> corresponding kernel.org code.
> 
> Some open questions that we should consider:
> - How to handle experimental features?
> - Need to follow up kernel stable releases if bug fixes are relevant to OFA
> modules
> - Should we have a release for every kernel release (I think yes)

This would help test upstream submissions, which would be good.  It may be desirable to have stable versions of previous releases, so that customers can get bug fixes without pulling in a bunch of new features.  E.g. OFED-3.2.1, OFED-3.2.2, etc.  If maintaining stable releases of every version is too expensive, maybe mark specific versions (i.e. 3.2) as stable, with intermediate releases (i.e. 3.3, 3.4) as experimental.  Just some ideas.

> - What should we do with modules like SDP that are not in kernel?

Either remove them or carry them forward as experimental features.

- Sean



More information about the ewg mailing list