[openib-general] Some Missing Features from mthca/user MADaccess

[Hal Rosenstock]

On Tue, 2005-01-11 at 12:15, Sean Hefty wrote:
> An issue with attribute filtering is that is results in an O(lg n) 
> algorithm being used to route MADs to the correct client.  Routing 
> based on class/method can be done in O(1), since the range of 
> classes/methods is substantially smaller than that of attributes.
> 
> Adding an attribute mask isn't overly difficult, it just wasn't felt 
> that it was necessary.

Right. It was a combination of the implementation inefficiency but more
significantly the lack of a compelling need but...

Do you see a way to handle the different SA client registrations for
events (InformInfo) where an incoming Report could go to multiple
clients with the current approach ? Even adding attribute ID is
insufficient as there would need to be some sense of what reports were
being registered for (perhaps by TrapNumber but one could support even
more granularity including ProducerType and other fields in the
subscription (InformInfo) request).

I know no OpenIB code is currently doing this, but shouldn't this be
supported ?

-- Hal