<!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 5.5.2654.45">
<TITLE>OpenSM Work Q2 2005</TITLE>
</HEAD>
<BODY>
<P ALIGN=LEFT><FONT COLOR="#0000FF" FACE="Palatino Linotype">Hi All,</FONT></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" FACE="Palatino Linotype">For your</FONT> <FONT COLOR="#0000FF" FACE="Palatino Linotype">comments and information</FONT> <FONT COLOR="#0000FF" FACE="Palatino Linotype">Mellanox plans to work on the following new OpenSM feature and enhancements this</FONT> <FONT COLOR="#0000FF" FACE="Palatino Linotype">quarter</FONT><FONT COLOR="#0000FF" FACE="Palatino Linotype"> (and maybe next one):</FONT></P>
<UL>
<P ALIGN=LEFT><FONT COLOR="#0000FF" FACE="Palatino Linotype">1. PKey re-ordering - current implementation of PKey tables in OpenSM "re-orders" the PKeys. This breaks any installation that uses PKeys.</FONT></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" FACE="Palatino Linotype">2. Routing algorithm time - 2minutes for 1K nodes. The solution is to implement a new "tree based" router that scales to 50K nodes fat tree and also implement "loading" of pre-routes.</FONT><FONT COLOR="#0000FF" FACE="Palatino Linotype"> </FONT></P>
<P ALIGN=LEFT> <FONT COLOR="#0000FF" FACE="Palatino Linotype">NOTE: I will send a mail describing the proposed algorithms and will highly appreciate any input regarding other alternatives and</FONT> <FONT COLOR="#0000FF" FACE="Palatino Linotype">review of the provided Order of complexity.</FONT></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" FACE="Palatino Linotype">3. SL2VL support by Path Record - current implementation ignores any SL2VL mapping. If one will configure those somehow, wrong path record results will break connectivity.</FONT></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" FACE="Palatino Linotype">4</FONT><FONT COLOR="#0000FF" FACE="Palatino Linotype">. Default PKey values are not set - New hardware that does not have default known PKey (0xffff) will fail any communication as the SM is supposed to set that value for it.</FONT></P>
</UL>
<P><FONT COLOR="#0000FF" FACE="Palatino Linotype">5. </FONT> <FONT COLOR="#0000FF" FACE="Palatino Linotype">QoS - OpenSM does not implement any QoS policy. Seems like people are more interested in that too. The solution is to implement a simple uniform QoS based on SL2VL and VLArb.</FONT></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" FACE="Palatino Linotype">Your comments and ideas are</FONT> <FONT COLOR="#0000FF" FACE="Palatino Linotype">welcome</FONT><FONT COLOR="#0000FF" FACE="Palatino Linotype">.</FONT></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" FACE="Palatino Linotype">Thanks</FONT></P>
<P ALIGN=LEFT><B><I></I></B><A NAME="_MailAutoSig"><B><I><FONT COLOR="#0000FF" SIZE=6 FACE="Monotype Corsiva">Eitan Zahavi</FONT></I></B></A></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">Design Technology Director</FONT></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">Mellanox Technologies LTD</FONT></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">Tel:+972-4-9097208<BR>
Fax:+972-4-9593245</FONT></P>
<P ALIGN=LEFT><FONT COLOR="#0000FF" SIZE=2 FACE="Tahoma">P.O. Box 586 Yokneam 20692 ISRAEL</FONT></P>
<P ALIGN=LEFT></P>
</BODY>
</HTML>