[openib-general] [RFC] [PATCH 2/7] ib_multicast 2.6.20: add ib_multicast module to track join requests from the same port

Eitan Zahavi eitan at mellanox.co.il
Wed Oct 11 09:20:31 PDT 2006


The point is not the fact you need to layer. But you can not enforce ref 
counting by adding a top layer everybody can bypass.
It simply breaks on the first client that goes directly to the lower level.
Do you have a solution for this problem?
The layer you need to add is BELOW the current interface not ABOVE it.

EZ

Sean Hefty wrote:
> Eitan Zahavi wrote:
>   
>> Maybe I did not explain myself right.
>> The idea is not to implement it in the mad.c code but rather to 
>> implement it at the lowest level:
>> The problem with a new API is that a single ULP/applications which does 
>> direct umad or QP1 access will break the reference count.
>>
>> Implementing at the lowest level - I.e. by sniffing QP1 packets - would 
>> be enforced for all applications/ULPs.
>>     
>
> Implementing this in the MAD layer is not the right solution.  Something, 
> somewhere must send MADs and control access to QP0/1.  Something, somewhere must 
> send MADs to the SA, and must be layered over the previous something. 
> Something, somewhere needs to perform reference counting on multicast groups and 
> request join/leave requests to the SA, and must be layered over the previous 
> something.
>
> Pushing all of this functionality down into a single module does not remove the 
> need for the different layers of functionality.  It just produces an overly 
> complex module.
>
> - Sean
>
> _______________________________________________
> openib-general mailing list
> openib-general at openib.org
> http://openib.org/mailman/listinfo/openib-general
>
> To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
>   





More information about the general mailing list