Thanks Scott,<br><br>I'm eager to try Open-MX. I'm using Netgear GSM7224 switch which supports flow control ( IEEE 802.3x Flow Control) and jumbo frame. I don't understand the interoperability. I assume it doesn't require at the moment. <br>
<br>Hee Il<br><br><div><span class="gmail_quote">2008/3/31, Scott Atchley <<a href="mailto:atchley@myri.com">atchley@myri.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mar 28, 2008, at 1:50 AM, Hee Il Kim wrote:<br> <br> > - If the gigabit network was the cause, could it be improved with<br> > Open-MX?<br> <br> <br>Hi Kim,<br> <br> Depending on your Ethernet switch, Open-MX should be able to lower<br>
your latency and reduce your CPU usage. I see about 10.5 us<br> internally using the e1000 driver with interrupt coalescing turned<br> off, others report that they have seen as low as 6.5 us (I do not<br> know what NICs they used or if it the machines were switched or back-<br>
to-back).<br> <br> To use Open-MX, your switch must support flow control for send and<br> receive (some don't) and jumbo frames. If you need interoperability<br> with native MX over Ethernet (some hosts with Myri-10G NICs connected<br>
to an Ethernet switch, some hosts with non-Myricom NICs), then your<br> switch must handle at least 4 KB frames. If you do not need<br> interoperability, then you can use 8 or 9 KB frames and possibly see<br> slightly better performance (fewer interrupts).<br>
<br> Brice released version 0.4.0 which has working interoperability with<br> native MX and is nearly feature complete. See <a href="http://www.open-mx.org">http://www.open-mx.org</a><br> for the status and source code.<br>
<br><br> Scott<br> <br> </blockquote></div><br>