OpenFabrics Developer Summit at SC06, Tampa Nov. 16,17

1. OpenFabrics Developer Summit at SC06, Tampa Nov. 16,17 Bill Boas, Sujal Das, Matt Leininger, Hal Rosenstock, Tom Tucker, Johann George, Bob Woodruff, Pramod Srivatsa

2. Strawman Agenda Strawman Agenda Thursday Nov 16 Room 17 see attached Tampa Convention Center layout 13.30 Introductions of Attendees and Roles, Process, Agenda, Goals, timelines, etc… 14.00 Share OFED ( Linux and Windows) experience from customers, IB vendors, OEMs 14.45 Break 15.00 Overview feature list and developers for OF-Linux Rel. 2.O – IB and iWARP together 17.00 Overview feature list and developers for OF-Windows Rel. 2.0 18.00 Processes for development, engineering test, bug fix and commit to OF trunk 18.30 Working Supper 19.30 – 21.00 Component by component review of features, task sizing, time requirements along with prioritization and strawman assignment to developers so as to produce an ordered list of features and an assessment/estimate of commitment for the items that are candidates to be included in Release 2.0 development for both Linux and Windows. Friday November 17 Room13 Tampa Convention Center, 08.00 Breakfast 08.30 Continue Component Review as described above until 10.00 Break 10.30-12.00 Complete the ordered list, “draw the line”, finalize developer assignments. 12.00-13.00 Working Lunch 13.00-13.30 Development, engineering test, bug fix, commit and documentation for Rel 2.0 13.30-14.30 OF-OFED handoff and OFED-EWG testing processes review and update etc. 14.30-15.00 OFED 1.x feature road map till OFED 2.0 15.00-15.15 Break 15.15-16.00 Customer, IB Vendor and OEM feedback and contribution discussion 16.00-16.30 Outstanding Issues and follow up activities, wrap-up.

3. Purposes of Meeting • Identify the possible list of features that are candidate items for development for Release 2.0 of the OpenFabrics Stack (note this is not an OFED candidate list); • Identify the developers/contributors/maintainers that are candidates to participate in the development team and their prerequisites before commitment to participate can be assured; • Recognize these developers as the “OF Release 2.0 Developers Working Group” (OF 2.0 DWG) • Allocate developer candidates to items agreed for development and “swag” timelines, engineering test procedures and other resources; • Identify Alliance member product managers and customers who will participate in the item prioritization and inclusion process (which also needs to be agreed) • Discuss and reach consensus on the agreed development item list, confirm responsible contributor/developer swagged timelines, level of engineering test and trunk commitment process • Discuss and agree with the Enterprise Working Group (who are responsible for OFED 1.x and 2.x) the OFED candidate deposition and SVN branching process for OFED 2.0 • Review and agree bug identification, logging in Bugzilla, assigning to developer and bug resolution for both DWG and EWG

4. Attendance Criteria & Company Commitment • Meeting attendance is encouraged from OpenFabrics members and selected individuals that can contribute to the negotiation of and commitment to: 1) - the features and components of Release 2.0; 2) - the engineering processes and resources necessary to ensure that Release 2.0 is developed for hand-off to the EWG for OFED quality assurance; 3) – improving the OFED processes to assure that OFED 2.0 meets Enterprise quality and robustness criteria as well as HPC performance and feature requirements; 4) readiness for Interoperability testing. • Companies and members participating need to send developers and product managers that can commit (at the meeting) company resources, developer’s time and effort and regression test suites and systems that can engineering test OF 2.0 so that every company believes meet its customers needs with 2.0 after the EWG has put it thru OFED and drop their proprietary competing software stacks. • The paragraph above implies that companies must plan their participation and commitment in advance as well as interact with collaborating member companies to workout in advance a strawman division of feature commitment, responsibilities and resources. • Linux distros, ISVs Tier 1 and 2 OEMs and Customers who are invited to participate should also understand that they will be expected to participate in detailed technical implementation discussion and prioritization of features. Participation in this meeting is also an indication by the customer that significant testing will be done by qualified customer personnel utilizing significant customer resources sufficient to contribute to the enterprise readiness of OFED 2.0 when it is released

5. Suggested Attendees • Current Developers/Contributors/Maintainers • Additional Developers and Contributors particularly from iWARP and Storage communities • Engineering and Product Managers from Member companies as well as VPs • Make effort to get planning participation from Dell, HP, IBM, Sun, Appro, Linux Networx, PANTA, Rackable, Tyan, LSI Logic, DDN, Novell, Redhat, Oracle, NetApp • Designated representatives from XWG, IPWG, EWG, IWG and HSIR (add Oil and Gas, Mfg, EDA, ISVs,etc. to Wall St.) • Special Effort to invite participation by qualified European and Asian attendees at SC, e.g. IBM Germany, CEA, HLRS, Bull, CERN, Fujitsu, NEC, Hitachi

6. OpenFabrics Software Stack IP Based App Access Sockets BasedAccess Various MPIs Block Storage Access Clustered DB Access Access to File Systems Application Level Diag Tools Open SM User Level MAD API UDAPL User APIs InfiniBand OpenFabrics User Level Verbs / API iWARP R-NIC User Space SDP Lib Kernel Space Upper Layer Protocol IPoIB SDP SRP iSER RDS NFS-RDMA RPC Cluster File Sys Connection Manager Abstraction (CMA) Mid-Layer SA Client MAD SMA Connection Manager ConnectionManager Kernel bypass Kernel bypass InfiniBand OpenFabrics Kernel Level Verbs / API iWARP R-NIC Provider Hardware Specific Driver Hardware Specific Driver Key Common Apps & AccessMethodsfor usingOF Stack InfiniBand Hardware InfiniBand HCA iWARP R-NIC iWARP

7. Linux Components and Maintainers (and Most Active Participant)

8. Linux Components and Maintainers (and Most Active Participant)

9. MPI2* Winsock Socket Switch Applications WinSock Provider SDP SPI** Windows Access Layer Library OF Windows Verbs Provider Library Hardware TCP/UDP/ICMP IP StorPort SDP** * Windows Compute Cluster Server 2003 ** Will be available in the future Kernel Bypass NDIS SRP Miniport IPoIB Access Layer HCA Hardware Verbs Provider Driver Windows Architecture Applications User WSD SAN Provider Management Tools VNIC** Kernel

10. Windows Components & Maintainers * Not available on Windows XP ** Not available on Windows XP 32 bits *** Will be available in the future

11. Candidate Component and Feature Description • iWARP integration • Windows interoperability • IPoIB • Connected mode • Bonding • NAPI • SDP • zcopy • netstat • AIO • uDAPL 2.0 provider for OpenFabrics (Note these are placeholders to get the real list started by contribution from the attendees before the meeting)

12. Candidate Component and Feature Description • Node Description changed trap support • Event subscriptions and event handling support • Performance Manager • Quality of Service • Other HA, performance, and scalability enhancements • Additional IBA 1.2 verb support • Some IB routing support (enablement) • Asynchronous get_user_pages ? • Tools • Other PathForward stage 3 items ? (Note these are placeholders to get the real list started by contribution from the attendees before the meeting)