On Fri, 2004-10-22 at 17:25, Roland Dreier wrote: > Hal> The registration interface will need to be extended somehow > Hal> for this. I don't think we want to add an attribute ID mask > Hal> :-) The simplest way I can think of is to add an issm bit to > Hal> the registration request structure and special case these > Hal> unsolicited receives to go to the SM if it has been > Hal> registered and to drop otherwise. > > All these special cases are starting to look pretty awkward.
What are the other special cases for registration ? > Another solution is to get rid of the snoop_mad entry point and the SMA and > PMA agents in ib_smi, and just pass every MAD to the low-level > driver. The low-level driver can decide to handle it (consume it > and/or generate a response) or not. Everything not consumed by the > low-level driver gets put through agent dispatch as usual. Wish this part of the discussion occurred 10 days ago or so :-) > This also avoids having to add another agent for BMA to ib_smi. Adding another agent is relatively trivial as evidenced by PMA. > Also it makes it pretty easy for low-level drivers to handle > vendor-specific GSI classes (of course drivers can register an agent > for every port and class they want to handle but it turns into a bit > of a pain). -- Hal _______________________________________________ openib-general mailing list [EMAIL PROTECTED] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general