Re: [PATCH net-next v5 0/2] Multicast group join/leave at ip level

[Madhu Challa <challa@noironetworks.com>]

On Fri, Feb 27, 2015 at 1:26 PM, David Miller <davem@davemloft.net> wrote:
> From: Madhu Challa <challa@noironetworks.com>
> Date: Wed, 25 Feb 2015 09:58:33 -0800
>
>> This series enables configuring multicast group join/leave at ip level
>> by extending the "ip address" command.
>>
>> It adds a new control socket mc_autojoin_sock and ifa_flag IFA_F_MCAUTOJOIN
>> to invoke the corresponding igmp group join/leave api.
>>
>> Since the igmp group join/leave api takes the rtnl_lock the code had to
>> be refactored by adding a shim layer prefixed by __ that can be invoked
>> by code that already has the rtnl_lock. This way we avoid proliferation of
>> work queues.
>>
>> The first patch in this series does the refactoring for igmp v6.
>> Its based on igmp v4 changes that were added by Eric Dumazet.
>>
>> The second patch in this series does the group join/leave based on the
>> setting of the IFA_F_MCAUTOJOIN flag.
>
> Applied, but I'm wondering how many hacks we are going to add to the
> tree simply because openvswitch does all of it's stuff with non-native
> tunneling devices...

Thanks David. I will look into what Thomas suggested so we can avoid
these workarounds.

Thanks.