This email was generated automatically, please do not reply
git_url: git://git.openfabrics.org/ofed_1_5/linux-2.6.git
git_branch: ofed_kernel_1_5
Common build parameters: --with-ipoib-mod --with-sdp-mod --with-user_mad-mod
--with-user_access-mod --with-mthca-mod --with-mlx4-mod
Hi,
OFED 1.5.4-rc5 is available.
The tarball is available on:
http://www.openfabrics.org/downloads/OFED/ofed-1.5.4/OFED-1.5.4-rc5.tgz
To get BUILD_ID run ofed_info
Please report any issues in bugzilla https://bugs.openfabrics.org/ for OFED
1.5.4
Regards,
Vladimir
Main changes from RC4:
HI,
Thanks for coming back to me. The problem here is openvz is a complete kernel,
however
based of RHEL6 2.6.32, so patches for the standard el6 kernel may not work, but
then again
compiling as if it was a vanilla kernel may not work either being RHEL6 based
I did manage to find the below:
Hi Vlad. I have yet to use rnfs-utils in any of my testing. Modern
versions of mount (at least the one that comes with SLES11SP1 and
RHEL6.1) support NFSRDMA, so I don't think rnfs-utils is needed anymore
(it provided an upstream version of mount for older OFED versions).
Maybe we should at least
Meeting minutes for EWG/OFED meeting for Nov 29, 2011:
1. OFED 1.5.4:
We have decide that all issues are not critical except for the compilation issue
Rc5 - Thu Dec 1 - was released by Vlad
GA - next Mon - Dec 5
2. Next
Hi Tziporet
On 12/01/11 09:42, Tziporet Koren wrote:
Meeting minutes for EWG/OFED meeting for Nov 29, 2011:
1. OFED 1.5.4:
We have decide that all issues are not critical except for the compilation
issue
Rc5 - Thu
Are these items absolutely required for OFED-1.5.4 ? Personally, I
have some people that really need to have this release out ASAP and do not
want to hold it up anymore if possible. The release has already slipped
a lot from our original plan.
woody
-Original Message-
From:
Hi Woody
On 12/01/11 11:20, Woodruff, Robert J wrote:
Are these items absolutely required for OFED-1.5.4 ? Personally, I
have some people that really need to have this release out ASAP and do not
want to hold it up anymore if possible. The release has already slipped
a lot from our original
I agree with Woody
We do not wish to postpone the release any more.
Tziporet
- Original Message -
From: Woodruff, Robert J [mailto:robert.j.woodr...@intel.com]
Sent: Thursday, December 01, 2011 09:20 PM
To: Jeff Becker jeffrey.c.bec...@nasa.gov; Tziporet Koren
Cc:
Well, we all agreed in the last EWG meeting that RC5 was to
be the last RC, so if those backports are not in RC5, they will have to
wait for the next release.
-Original Message-
From: Jeff Becker [mailto:jeffrey.c.bec...@nasa.gov]
Sent: Thursday, December 01, 2011 11:27 AM
To:
On 12/01/11 11:30, Woodruff, Robert J wrote:
Well, we all agreed in the last EWG meeting that RC5 was to
be the last RC, so if those backports are not in RC5, they will have to
wait for the next release.
OK. I will work on the performance issue then. When I fix the release
notes I'll mention
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
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
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
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
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 included
On Fri, Dec 2, 2011 at 1:04 AM, Hefty, Sean sean.he...@intel.com 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
17 matches
Mail list logo
