[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <55AFDA89.1080304@cumulusnetworks.com>
Date: Wed, 22 Jul 2015 20:01:45 +0200
From: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
To: Cong Wang <cwang@...pensource.com>
Cc: netdev <netdev@...r.kernel.org>,
"bridge@...ts.linux-foundation.org"
<bridge@...ts.linux-foundation.org>,
David Miller <davem@...emloft.net>,
Stephen Hemminger <stephen@...workplumber.org>,
Satish Ashok <sashok@...ulusnetworks.com>
Subject: Re: [PATCH net-next] bridge: mcast: when multicast is disabled flush
the groups
On 07/22/2015 07:03 PM, Cong Wang wrote:
> On Wed, Jul 22, 2015 at 3:28 AM, Nikolay Aleksandrov
> <nikolay@...ulusnetworks.com> wrote:
>> From: Satish Ashok <sashok@...ulusnetworks.com>
>>
>> Once multicast gets disabled we should flush the groups.
>> Example:
>> # bridge mdb add dev br0 port eth3 grp 239.0.0.1
>> # bridge mdb
>> dev br0 port eth3 grp 239.0.0.1 temp
>> # echo 0 > multicast_snooping
>> # bridge mdb
>
> Why? Why we can't save the mdb config for a mcast snooping flip?
>
Right, I've discussed this with my colleagues and we think this doesn't have any
value for upstream and shouldn't have been sent which is bad judgment on my side.
It actually makes things worse because it removes the user's permanent entries on
snooping disable and it may happen automatically by hash exhaustion.
Anyway, please drop this patch and sorry for the noise, I should've given this
change more thought.
Thanks,
Nik
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists