> The kernel is a large piece that keeps moving on - its made of many smaller
> pieces/components, but with very sharp and well defined dependencies and
> interactions. The rdma stack is far from being an isolated piece which you
> can pull from kernel X and plug into kernel Y - this applies all o
On 12/05/2011 01:05 AM, Or Gerlitz wrote:
To be concrete/constructive here, a per IB stack module individual has to be assigned for that backporting, which
doesn't mean "make IB code from kernel X to build under kernel Y" - lets
see if we have people to actually do that.
For example, on the i
On 12/01/2011 02:53 PM, Tziporet Koren wrote:
>
> 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)
> - OFED p
On 12/2/2011 2:04 AM, Hefty, Sean wrote:
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
On Fri, Dec 2, 2011 at 7:12 PM, Christoph Lameter wrote:
> What were the issues that prevented the merging of the SDP
> implementation?
At least AF_INET_SDP - there might have been other issues. See e.g.
http://lkml.org/lkml/2006/3/6/70.
Bart.
--
To unsubscribe from this list: send the line "uns
On Thu, 1 Dec 2011, Tziporet Koren wrote:
> 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)
> - OFED package
On Fri, 2 Dec 2011, Bart Van Assche wrote:
> On Fri, Dec 2, 2011 at 1:04 AM, Hefty, Sean wrote:
> > > - What should we do with modules like SDP that are not in kernel?
> >
> > Either remove them or carry them forward as experimental features.
>
> Wat I expect is that reworking the SDP implementat
On Fri, Dec 2, 2011 at 1:04 AM, Hefty, Sean wrote:
> > - What should we do with modules like SDP that are not in kernel?
>
> Either remove them or carry them forward as experimental features.
Wat I expect is that reworking the SDP implementation such that it can
be included upstream will take les
On Thu, Dec 01, 2011 at 04:13:41PM -0800, Woodruff, Robert J wrote:
> Sean wrote,
> >> - OFED will offer only backports to the distros (no fixes)
> > I think this point needs to be clarified - at least to me anyway. :)
>
> What this means is that the OFED code base will be identical to what
> is
Sean wrote,
>> - OFED will offer only backports to the distros (no fixes)
> I think this point needs to be clarified - at least to me anyway. :)
What this means is that the OFED code base will be identical to what
is included in the upstream kernel and libs.
OFED will provide only backports to a
> 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 an
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)
- OFED package will be used for easy installation of all packages in
12 matches
Mail list logo
