[Openib-windows] [BUG] Errors with multiple HCAs in a single system

[Leonid Keller]

the new driver is expected to replace the current one.
it will support all Mellanox HCA chips.

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