<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>[ANNOUNCE]OFA Component Early Integration Test Tree</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Courier New">At SC'06 developer's summit in Tampa, we had some discussion of having an</FONT>
<BR><FONT SIZE=2 FACE="Courier New">early integration-test tree (kind of like the MM tree) for early testing of</FONT>
<BR><FONT SIZE=2 FACE="Courier New">new infiniband components. I have started to look at putting together such a tree</FONT>
<BR><FONT SIZE=2 FACE="Courier New">that contains Sean's latest uCMA, local sa cache, multicast code, and the</FONT>
<BR><FONT SIZE=2 FACE="Courier New">IPoIB_CM code, at least for my own testing. If others are interested in</FONT>
<BR><FONT SIZE=2 FACE="Courier New">trying this stuff out before it gets into OFED or the kernel.org tree,</FONT>
<BR><FONT SIZE=2 FACE="Courier New">they can clone my ofa_integration tree at,</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">~woody/scm/ofa-integration</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">The merged code is in the integration-test branch.</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">My merge script also creates a single patch from the integration-test </FONT>
<BR><FONT SIZE=2 FACE="Courier New">branch using</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">git-diff linux-2.6.19 integration-test > ./infiniband-ofa-mmddyy-for-linux-2.6.19.patch</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">that people could take and just apply against a </FONT>
<BR><FONT SIZE=2 FACE="Courier New">stock 2.6.19 kernel. These are in my top level directory,</FONT>
<BR><FONT SIZE=2 FACE="Courier New">~woody</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">Not sure if these patches would be useful to anyone else, but if they </FONT>
<BR><FONT SIZE=2 FACE="Courier New">are, we could figure out a way to publish them for use by the</FONT>
<BR><FONT SIZE=2 FACE="Courier New">greater community, or people could always just generate the patch</FONT>
<BR><FONT SIZE=2 FACE="Courier New">themselves using git-diff. </FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">So far I have tested the </FONT>
<BR><FONT SIZE=2 FACE="Courier New">~woody/infiniband-ofa-1207006-for-linux-2.6.19.patch </FONT>
<BR><FONT SIZE=2 FACE="Courier New">which contains Sean's local_sa cache, uCMA, and the IPoIB_CM code.</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">The ~woody/infiniband-ofa-1211006-for-linux-2.6.19.patch has the loca_sa cache,</FONT>
<BR><FONT SIZE=2 FACE="Courier New">uCMA, IPoIB_CM, and Sean Multicast code. I just created this one, the merge </FONT>
<BR><FONT SIZE=2 FACE="Courier New">went ok, but I have yet to test it.</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">If other people would like to add some new kernel code to this tree to test</FONT>
<BR><FONT SIZE=2 FACE="Courier New">with other components that are under development, I can add your code.</FONT>
<BR><FONT SIZE=2 FACE="Courier New">What I need to do this is for you to publish a git tree based on 2.6.19 (the release kernel)</FONT>
<BR><FONT SIZE=2 FACE="Courier New">that has your code (and only your code) in a branch, such that one could</FONT>
<BR><FONT SIZE=2 FACE="Courier New">create a self contained patch that would apply to a stock 2.6.19 kernel using</FONT>
<BR><FONT SIZE=2 FACE="Courier New">git-diff. e.g.,</FONT>
<BR><FONT SIZE=2 FACE="Courier New">git-diff linux-2.6.19 mybranch </FONT>
<BR><FONT SIZE=2 FACE="Courier New">would create a self contained patch of your code. </FONT>
<BR><FONT SIZE=2 FACE="Courier New">This should allow me to easily merge the code into my tree. </FONT>
<BR><FONT SIZE=2 FACE="Courier New">If your git tree contains changes to other core infiniband code or is based</FONT>
<BR><FONT SIZE=2 FACE="Courier New">on something other than the release 2.6.19 kernel.org kernel, I cannot use it,</FONT>
<BR><FONT SIZE=2 FACE="Courier New">since I cannot easily merge it with the other experimental components that </FONT>
<BR><FONT SIZE=2 FACE="Courier New">are based on 2.6.19.</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">If people think that this would be of value to the wider community,</FONT>
<BR><FONT SIZE=2 FACE="Courier New">I will add something to the wiki to explain how to get the tree and the</FONT>
<BR><FONT SIZE=2 FACE="Courier New">userspace code that matches this kernel code.</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">woody</FONT>
</P>
</BODY>
</HTML>