[ewg] OFED Jan 5, 2009 meeting minutes on OFED plans
OFED Jan 5, 2009 meeting minutes on future plans = Meeting minutes on the web: http://www.openfabrics.org/txt/documentation/linux/EWG_meeting_minutes Meeting Summary: == 1. OFED 1.4.1 release: We will look into it on middle of February 2. OFED 1.5: - Release target date is July 09 - Kernel base will be 2.6.29 - Features list - not closed yet Details: == 1. Conclusions from OFED 1.4 release: We got several comments from Doug (Redhat): - ammaso driver is not compiling - we should remove it from the kernel sources since its not compile - IBM ehca driver - does not compile on RHEL4 - Improvements for the build system - grep for undefined functions and report this since they will fail when trying to load the module Other conclusions: - Real feature freeze is only after we are on the right kernel base - We usually have at least 6 RCs - need to plan for this on the schedule 2. Do we wish to have OFED 1.4. 1: Pros: We can add the following features: - RDS iWARP - Steve Wise - NFS/RDMA backports - Steve Wise - Open MPI 1.3 - Jeff S. - Supporting new OSes: RHEL 5.3, SLES 11 - Fixes of fatal bugs - if found Cons: - Having 1.4.1 release will delay 1.5 schedule for one month or more. - A large QA effort. Decision: Since no fatal bugs were reported so far, we decide to revisit this in middle of Feb. Meanwhile Steve can work on RDS iWARP support and NFS/RDMA backports on the 1.4.1 branch. People that wish to work with Open MPI 1.3 can download it from its site. 3. OFED 1.5: Schedule and features. Schedule: Release is planned for July. (assuming no 1.4.1 release) Feature Freeze: 4/20/09 Alpha Release: 4/20/09 Beta Release: 5/20/09 RC1:5/05/09 RC2:5/19/09 RC3:6/02/09 RC4:6/16/09 RC5:6/30/09 RC6:7/14/09 Release:7/28/09 Features: * Kernel.org: 2.6.28 and 2.6.29 * Multiple Event Queues to support Multi-core CPUs * NFS/RDMA - GA * RDS support for iWARP * OpenMPI 1.3 * Add support/backports for RedHat EL 5.3 and EL 4.8, SLES 11 * Support for Mellanox vNIC (EoIB) and FCoIB with BridgeX device * SDP - performance improvements * Mellanox suggested to add IB over Eth - this is similar to iWARP but more like IB (e.g. including UD), and can work over ConnectX. A concern was raised by Intel (Dave Sommers) since it is not a standard transport. Decision: This request will be raised in the MWG, and they should decide if OFA can support it. More discussions on 1.5 features will be done in next meeting. Tziporet ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
[ewg] RE: OFED Jan 5, 2009 meeting minutes on OFED plans
* Mellanox suggested to add IB over Eth - this is similar to iWARP but more like IB (e.g. including UD), and can work over ConnectX. A concern was raised by Intel (Dave Sommers) since it is not a standard transport. Decision: This request will be raised in the MWG, and they should decide if OFA can support it. Just is just my opinion, but in the past, OFED has included non-standard features, like extended connected mode, that are still not part of the IBTA spec. Do we know if such a feature would be accepted into the Linux kernel? I think OFED should base their decision more on the answer to that question than IBTA approval. - Sean ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
RE: [ewg] RE: OFED Jan 5, 2009 meeting minutes on OFED plans
Sean, I think that's a good point. What it suggests to me is asking when someone proposes a non-standard feature, what process, procedures, documentation, support, etc. if any, should be made available by the entity making the proposal? It seems to me asking the same questions of all proposed features is fair and reasonable, and shouldn't represent an unreasonable barrier to progress. Thoughts? If this already exists, it's my ignorance and I will apologize in advance Thanks again, Jim -Original Message- From: ewg-boun...@lists.openfabrics.org [mailto:ewg-boun...@lists.openfabrics.org] On Behalf Of Sean Hefty Sent: Tuesday, January 06, 2009 1:54 PM To: 'Tziporet Koren'; ewg@lists.openfabrics.org Cc: gene...@lists.openfabrics.org Subject: [ewg] RE: OFED Jan 5, 2009 meeting minutes on OFED plans * Mellanox suggested to add IB over Eth - this is similar to iWARP but more like IB (e.g. including UD), and can work over ConnectX. A concern was raised by Intel (Dave Sommers) since it is not a standard transport. Decision: This request will be raised in the MWG, and they should decide if OFA can support it. Just is just my opinion, but in the past, OFED has included non-standard features, like extended connected mode, that are still not part of the IBTA spec. Do we know if such a feature would be accepted into the Linux kernel? I think OFED should base their decision more on the answer to that question than IBTA approval. - Sean ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
RE: [ewg] RE: OFED Jan 5, 2009 meeting minutes on OFED plans
We need to look on this from the right angel. This is not a feature but rather a core component that adds support for a new adapter/NIC. This is the same as the core drivers for the other adapters that are supported already. In general we need to look not only on spec related features, but also to cover features that can benefit OFED and WinOF users (such as IPoIB connected mode or WinVerbs). Gilad. -Original Message- From: ewg-boun...@lists.openfabrics.org [mailto:ewg-boun...@lists.openfabrics.org] On Behalf Of Ryan, Jim Sent: Tuesday, January 06, 2009 2:01 PM To: Hefty, Sean; Tziporet Koren; ewg@lists.openfabrics.org Cc: gene...@lists.openfabrics.org Subject: RE: [ewg] RE: OFED Jan 5, 2009 meeting minutes on OFED plans Sean, I think that's a good point. What it suggests to me is asking when someone proposes a non-standard feature, what process, procedures, documentation, support, etc. if any, should be made available by the entity making the proposal? It seems to me asking the same questions of all proposed features is fair and reasonable, and shouldn't represent an unreasonable barrier to progress. Thoughts? If this already exists, it's my ignorance and I will apologize in advance Thanks again, Jim -Original Message- From: ewg-boun...@lists.openfabrics.org [mailto:ewg-boun...@lists.openfabrics.org] On Behalf Of Sean Hefty Sent: Tuesday, January 06, 2009 1:54 PM To: 'Tziporet Koren'; ewg@lists.openfabrics.org Cc: gene...@lists.openfabrics.org Subject: [ewg] RE: OFED Jan 5, 2009 meeting minutes on OFED plans * Mellanox suggested to add IB over Eth - this is similar to iWARP but more like IB (e.g. including UD), and can work over ConnectX. A concern was raised by Intel (Dave Sommers) since it is not a standard transport. Decision: This request will be raised in the MWG, and they should decide if OFA can support it. Just is just my opinion, but in the past, OFED has included non-standard features, like extended connected mode, that are still not part of the IBTA spec. Do we know if such a feature would be accepted into the Linux kernel? I think OFED should base their decision more on the answer to that question than IBTA approval. - Sean ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
Re: [ewg] OFED Jan 5, 2009 meeting minutes on OFED plans
Given that we GA'd OFED 1.3 on Dec 10/08, I'm pretty uncomfortable with scheduling our OFED 1.4 release almost a full 8 months later. If I remember right, our goal is to have two OFED releases a year. How about a schedule as follows: Feature Freeze: 3/25/09 Alpha Release: 3/25/09 Beta Release: 4/20/09 RC1: 4/06/09 RC2: 4/20/09 RC3: 5/04/09 RC4: 5/18/09 RC5: 6/01/09 RC6: 6/15/09 Release: 6/28/09 Or, we could be somewhat more firm about what constitutes a feature freeze, make that later, and go with less RCs. But, one way or another, I think we really need to tighten up the schedule. Betsy On Tue, 2009-01-06 at 23:41 +0200, Tziporet Koren wrote: OFED Jan 5, 2009 meeting minutes on future plans = Meeting minutes on the web: http://www.openfabrics.org/txt/documentation/linux/EWG_meeting_minutes Meeting Summary: == 1. OFED 1.4.1 release: We will look into it on middle of February 2. OFED 1.5: - Release target date is July 09 - Kernel base will be 2.6.29 - Features list - not closed yet Details: == 1. Conclusions from OFED 1.4 release: We got several comments from Doug (Redhat): - ammaso driver is not compiling - we should remove it from the kernel sources since its not compile - IBM ehca driver - does not compile on RHEL4 - Improvements for the build system - grep for undefined functions and report this since they will fail when trying to load the module Other conclusions: - Real feature freeze is only after we are on the right kernel base - We usually have at least 6 RCs - need to plan for this on the schedule 2. Do we wish to have OFED 1.4. 1: Pros: We can add the following features: - RDS iWARP - Steve Wise - NFS/RDMA backports - Steve Wise - Open MPI 1.3 - Jeff S. - Supporting new OSes: RHEL 5.3, SLES 11 - Fixes of fatal bugs - if found Cons: - Having 1.4.1 release will delay 1.5 schedule for one month or more. - A large QA effort. Decision: Since no fatal bugs were reported so far, we decide to revisit this in middle of Feb. Meanwhile Steve can work on RDS iWARP support and NFS/RDMA backports on the 1.4.1 branch. People that wish to work with Open MPI 1.3 can download it from its site. 3. OFED 1.5: Schedule and features. Schedule: Release is planned for July. (assuming no 1.4.1 release) Feature Freeze: 4/20/09 Alpha Release:4/20/09 Beta Release: 5/20/09 RC1: 5/05/09 RC2: 5/19/09 RC3: 6/02/09 RC4: 6/16/09 RC5: 6/30/09 RC6: 7/14/09 Release: 7/28/09 Features: * Kernel.org: 2.6.28 and 2.6.29 * Multiple Event Queues to support Multi-core CPUs * NFS/RDMA - GA * RDS support for iWARP * OpenMPI 1.3 * Add support/backports for RedHat EL 5.3 and EL 4.8, SLES 11 * Support for Mellanox vNIC (EoIB) and FCoIB with BridgeX device * SDP - performance improvements * Mellanox suggested to add IB over Eth - this is similar to iWARP but more like IB (e.g. including UD), and can work over ConnectX. A concern was raised by Intel (Dave Sommers) since it is not a standard transport. Decision: This request will be raised in the MWG, and they should decide if OFA can support it. More discussions on 1.5 features will be done in next meeting. Tziporet ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
