[ofw] [owf][patch] user multicast offload support

[Yiftah Shahar]

Hi Sean,

 

> The communication of this policy needs to be between ipoib and the
application that doesn't want it to attach.

How the application can communicate directly with IPoIB?

Are you thinking about some interface that will be exposed by IPoIB to
applications/IBAL (like by the join API) ?

 

I think that a limitation of "use user space MC only" or "use IPoIB
only" per specific MC group is acceptable by our customers at list for
first version...

 

Yiftah

 

 

________________________________

From: ofw-bounces at lists.openfabrics.org
[mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Sean Hefty
Sent: Wednesday, July 02, 2008 18:38
To: Slava Strebkov; Fab Tillier; ofw at lists.openfabrics.org
Subject: RE: [ofw] [owf][patch] user multicast offload support

 

>This leads me back to my original suggestion of simply having a

>parameter on the join multicast group that indicates if the QP should
be

>attached.  This is way simpler and moves the complexity of determining

>when to attach to the ULP, where it belongs.

Multicast group opened from user mode is always attached. Attachment of
groups from IPoIB depends on whether same group was attached previously
from user mode. IPoIB does not know this.

 

There's something fundamentally wrong with this approach.  You're moving
policy into the verb layer to determine if a request from a kernel
client should or should not attach its QP to the multicast group.  The
communication of this policy needs to be between ipoib and the
application that doesn't want it to attach.

 

- Sean

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20080708/13890c86/attachment.html>