<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>Re: [openfabrics-ewg] Re: How to generate IBED releases using 1.0 branch</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Communicating to open fabrics general - the proposal was for the nominated chair, Shawn, to do so.</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Bryan O'Sullivan</FONT>
<BR><FONT SIZE=2>To: Tziporet Koren</FONT>
<BR><FONT SIZE=2>CC: Michael S. Tsirkin; Openfabrics-ewg@openib.org</FONT>
<BR><FONT SIZE=2>Sent: Wed Mar 29 08:00:45 2006</FONT>
<BR><FONT SIZE=2>Subject: [openfabrics-ewg] Re: How to generate IBED releases using 1.0 branch</FONT>
</P>
<P><FONT SIZE=2>On Wed, 2006-03-29 at 16:54 +0200, Tziporet Koren wrote:</FONT>
</P>
<P><FONT SIZE=2>> 1. Any module that is already in the kernel will be taken from</FONT>
<BR><FONT SIZE=2>> the git tree that is targeted for 2.6.17</FONT>
<BR><FONT SIZE=2>> (<A HREF="http://www.kernel.org/git/?p=linux/kernel/git/roland/infiniband.git;a=summary" TARGET="_blank">http://www.kernel.org/git/?p=linux/kernel/git/roland/infiniband.git;a=summary</A>)</FONT>
<BR><FONT SIZE=2>> This include the following: mthca, ipath (if I understand it</FONT>
<BR><FONT SIZE=2>> should be in soon), core (all modules), ipoib, srp</FONT>
<BR><FONT SIZE=2>> 2. Kernel modules that are not in Linux kernel will be taken from</FONT>
<BR><FONT SIZE=2>> these directories:</FONT>
<BR><FONT SIZE=2>> iSER, SDP – from the trunk</FONT>
<BR><FONT SIZE=2>> RDS: from SilverStorm contrib directory (till they move it to</FONT>
<BR><FONT SIZE=2>> the trunk)</FONT>
</P>
<P><FONT SIZE=2>Sounds good to me.</FONT>
</P>
<P><FONT SIZE=2>> 1. All user space code will be taken from the 1.0 branch. I will</FONT>
<BR><FONT SIZE=2>> send all user space patches that are important for this</FONT>
<BR><FONT SIZE=2>> release. If it’s OK I can also check them in, or ask the</FONT>
<BR><FONT SIZE=2>> maintainers as agreed to do so.</FONT>
</P>
<P><FONT SIZE=2>I think the best thing to do is send patches, then commit to svn after</FONT>
<BR><FONT SIZE=2>say a day's delay in case anyone objects.</FONT>
</P>
<P><FONT SIZE=2>> 1. MPI:</FONT>
<BR><FONT SIZE=2>> MVAPICH – tarball is provided by Mellanox</FONT>
</P>
<P><FONT SIZE=2>Why would we not want to build MVAPICH from SVN?</FONT>
</P>
<P><FONT SIZE=2>> Open MPI – tarball is provided by Cisco</FONT>
</P>
<P><FONT SIZE=2>I'm reluctant to just use a tarball without any visibility into what's</FONT>
<BR><FONT SIZE=2>happening in its development. Can we at least have a pointer to where</FONT>
<BR><FONT SIZE=2>the Open MPI development tree is, be it SVN or CVS or whatever?</FONT>
</P>
<P><FONT SIZE=2>> I think this module can help us to progress both OpenFabrics and IBED</FONT>
<BR><FONT SIZE=2>> releases very well and also contribute for the stability of code that</FONT>
<BR><FONT SIZE=2>> is going to Linux kernel.</FONT>
</P>
<P><FONT SIZE=2>Yep.</FONT>
</P>
<P><FONT SIZE=2>> BTW – when do we go public to OpenFabrics general list?</FONT>
</P>
<P><FONT SIZE=2>This should really have happened by now. I'd like someone to put</FONT>
<BR><FONT SIZE=2>together a draft announcement, circulate it here, and then send it to</FONT>
<BR><FONT SIZE=2>openib-general once it's been whipped into shape.</FONT>
</P>
<P> <FONT SIZE=2><b</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>openfabrics-ewg mailing list</FONT>
<BR><FONT SIZE=2>openfabrics-ewg@openib.org</FONT>
<BR><FONT SIZE=2><A HREF="http://openib.org/mailman/listinfo/openfabrics-ewg" TARGET="_blank">http://openib.org/mailman/listinfo/openfabrics-ewg</A></FONT>
</P>
</BODY>
</HTML>