[ofw] Functions exporting from driver module

[Leonid Keller]

Direct function call by name requires interlinkage between the different
drivers (MTHCA and IBBUS - in this case).
We don't want that.
We want the drivers to be independent, be loaded in any order and to
call each other by versioned interfaces.
 


________________________________

	From: ofw-bounces at lists.openfabrics.org
[mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Deepak Gupta
	Sent: Wednesday, January 23, 2008 11:11 AM
	To: ofw at lists.openfabrics.org
	Subject: [ofw] Functions exporting from driver module
	
	
	Hi All,
	 
	I have the following doubt
	 
	Why do we use two step mehanism for interacting HCA driver with
IBBUS.SYS.
	 
	Mechanism Used
	    First we look for the GUID_IB_CI_INTERFACE's (created by
IBBUS) arrival in HCA driver
	    Then we get the ib_register_ca ,ib_deregister_ca and other
function pointer via IRP_MN_QUERY_INTERFACE on ibbus.
	    Then we regiser HCA driver to the core(ibbus) providing
funtion pointer to the verbs implementation
	 
	    Above interaction could have achieved in just one step if
IBBUS.SYS would have exported ib_register_ca ,ib_bus_deregister_ca.
	 
	Or Mechanism used satisfy some other requirements also which I
am not able to decipher.
	 
	Cheers
	Deepak
	    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20080123/27b5c483/attachment.html>