[openib-general] [PATCH v2 0/11] [RFC] Support for QLogic Virtual Ethernet I/O Controller (VEx)

Roland Dreier rdreier at cisco.com
Thu Nov 16 10:02:42 PST 2006


 > Would the branch that you create be in sync with the for-2.6.20 branch ?
 > That way I can keep the code in sync with the latest changes.
 > Also is the branch already created ? I tried to update my copy of the tree
 > but could not see a vex branch.

I have not created the branch yet.  I will probably be able to do it
today.  The way I will do it is to make a branch from the "master"
branch so that your patches should just be on top of Linus's tree.

 > Please note that this driver is a device driver for a remote device and
 > the communication between the driver and the device is like any other
 > device driver, its just that this driver uses IB as its bus where
 > as others use PCI etc. 

OK...

 > Each virtual NIC has a netpath, which is an abstraction of a connection to
 > the VEx. Each netpath has a viport, the virtual port, which is an abstraction
 > of the control and data IB connections through which control and data messages
 > are exchanged.

...but this seems like over-abstraction that makes the code harder to understand.

 - R.




More information about the general mailing list