[ofw] help deciphering mlx4 driver

Leonid Keller leonid at mellanox.co.il
Tue Aug 12 11:35:53 PDT 2008


I've fixed async event notification mechanism in rev.1480. 

> -----Original Message-----
> From: Hefty, Sean [mailto:sean.hefty at intel.com] 
> Sent: Monday, August 11, 2008 8:13 AM
> To: Leonid Keller; ofw at lists.openfabrics.org
> Subject: RE: [ofw] help deciphering mlx4 driver
> 
> >ca_event_handler is never invoked.
> >My oversight, thank you.
> >But do you really need it ?
> >MTHCA *does* call ca_event_handler, but it is not used by IBAL.
> 
> I'm trying to have the mlx4 driver report asynchronous events 
> to anyone that subscribes for them.  Basically, this allows 
> the HCA driver to support multiple consumers of asynchronous 
> events, i.e. both IBAL and Winverbs, and allows the 
> eventually elimination of the overhead of using an 
> intermediate driver to invoke callbacks.
> 
> If you can point me to where the IBAL async callback is 
> invoked, I can modify the code there instead.
> 
> - Sean
> 



More information about the ofw mailing list