<!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>RE: [Openib-windows] [BUG] Errors with multiple HCAs in a single system</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>the new driver is expected to replace the current one.</FONT>
<BR><FONT SIZE=2>it will support all Mellanox HCA chips.</FONT>
</P>
<P><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Fab Tillier [<A HREF="mailto:ftillier@silverstorm.com">mailto:ftillier@silverstorm.com</A>]</FONT>
<BR><FONT SIZE=2>> Sent: Wednesday, October 19, 2005 7:56 PM</FONT>
<BR><FONT SIZE=2>> To: 'Leonid Keller'; openib-windows@openib.org</FONT>
<BR><FONT SIZE=2>> Subject: RE: [Openib-windows] [BUG] Errors with multiple HCAs in a</FONT>
<BR><FONT SIZE=2>> single system</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Hi Leonid,</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> > > From: Fab Tillier [<A HREF="mailto:ftillier@silverstorm.com">mailto:ftillier@silverstorm.com</A>]</FONT>
<BR><FONT SIZE=2>> > > Sent: Monday, October 17, 2005 9:16 PM</FONT>
<BR><FONT SIZE=2>> > ></FONT>
<BR><FONT SIZE=2>> > > I am trying to run both a PCI-X and PCI-Express HCA in a</FONT>
<BR><FONT SIZE=2>> > > single server</FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> > I guess, you are the first one, that's trying that ... :(</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Perhaps, though this would also happen when running more than one HCA,</FONT>
<BR><FONT SIZE=2>> regardless of the model of the HCA.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> > > to</FONT>
<BR><FONT SIZE=2>> > > compare performance, and cannot enable both devices</FONT>
<BR><FONT SIZE=2>> > > simultaneously. Which ever</FONT>
<BR><FONT SIZE=2>> > > HCA is starts second fails with the following output to </FONT>
<BR><FONT SIZE=2>> the debugger:</FONT>
<BR><FONT SIZE=2>> > ></FONT>
<BR><FONT SIZE=2>> > > <1> MDT(1): prepare_intr_resources: Failed to MOSAL_ISR_set</FONT>
<BR><FONT SIZE=2>> > > MOSAL ret=-1</FONT>
<BR><FONT SIZE=2>> > > <1> MDT(4): THH_eventp_create: Cannot set interrupt resources.</FONT>
<BR><FONT SIZE=2>> > > <1> MDT(1): THH_hob_open_hca: could not create eventp (-255)</FONT>
<BR><FONT SIZE=2>> > > <1> MDT(1): THH_hob_close_hca: Device already closed</FONT>
<BR><FONT SIZE=2>> > ></FONT>
<BR><FONT SIZE=2>> > > It looks like the device lookup in MOSAL_ISR_set uses a </FONT>
<BR><FONT SIZE=2>> generic name</FONT>
<BR><FONT SIZE=2>> > > "InfiniHost" and thus matches the first entry in the table.</FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> > Yes, a bug in prepare_intr_resources(), which calls </FONT>
<BR><FONT SIZE=2>> MOSAL_ISR_set() with</FONT>
<BR><FONT SIZE=2>> > "InfiniHost" built_in parameter instead of real name. Try </FONT>
<BR><FONT SIZE=2>> to change it by</FONT>
<BR><FONT SIZE=2>> > eventp->hob.dev_name.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Will you be working a fix for this driver, or is the MTHCA </FONT>
<BR><FONT SIZE=2>> driver expected to</FONT>
<BR><FONT SIZE=2>> replace the existing driver?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> > > Why is this doing a lookup? Doesn't the code know exactly</FONT>
<BR><FONT SIZE=2>> > > which device is being</FONT>
<BR><FONT SIZE=2>> > > initialized? Why put the device in the MOSAL_dev_db and then</FONT>
<BR><FONT SIZE=2>> > > search for it?</FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> > MOSAL was born in Linux as a separate module, that performs all</FONT>
<BR><FONT SIZE=2>> > OS-dependent things.</FONT>
<BR><FONT SIZE=2>> > It is to do that on base of the function parameters.</FONT>
<BR><FONT SIZE=2>> > When i start to port MOSAL to Windows, i saw that in some cases</FONT>
<BR><FONT SIZE=2>> > (like with MOSAL_ISR_set()) MOSAL can't do that, because it needs</FONT>
<BR><FONT SIZE=2>> > some information, found only in the posession of the driver.</FONT>
<BR><FONT SIZE=2>> > That's why i added MOSAL DB, which duplicates some Driver device</FONT>
<BR><FONT SIZE=2>> > information.</FONT>
<BR><FONT SIZE=2>> > There is no MOSAL in new driver, so there will be no that </FONT>
<BR><FONT SIZE=2>> problem ...</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Ok, thanks for the explanation. Will the new driver support </FONT>
<BR><FONT SIZE=2>> Tavor too, or is it</FONT>
<BR><FONT SIZE=2>> just a memfree/native arbel driver?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> - Fab</FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
</BODY>
</HTML>