Re: [Bridge] [PATCH net-next v2] bridge: Synchronize unicast filtering with FDB

[Toshiaki Makita]

On 16/06/13 (月) 20:23, Nikolay Aleksandrov wrote:

On 13/06/16 13:13, Toshiaki Makita wrote:

On 2016/06/12 15:35, Toshiaki Makita wrote:

On 16/06/12 (日) 1:17, Nikolay Aleksandrov via Bridge wrote:

On 06/11/2016 07:35 AM, David Miller wrote:

From: Toshiaki Makita 
Date: Mon,  6 Jun 2016 21:20:13 +0900


Patrick Schaaf reported that flooding due to a missing fdb entry of
the address of macvlan on the bridge device caused high CPU
consumption of an openvpn process behind a tap bridge port.
Adding an fdb entry of the macvlan address can suppress flooding
and avoid this problem.

This change makes bridge able to synchronize unicast filtering with
fdb automatically so admin do not need to manually add an fdb entry.
This effectively supports IFF_UNICAST_FLT in bridge, thus adding an
macvlan device would not place bridge into promiscuous mode as well.

v2:
- Test vlan with br_vlan_should_use() in br_fdb_sync_uc() as per
Nikolay Aleksandrov.

Reported-by: Patrick Schaaf 
Signed-off-by: Toshiaki Makita 


I really need bridging experts to review and ACK/NACK this.

Thanks.



Oops, I almost missed the v2, sorry about that. So, technically it
looks correct, but
I only fear the scalability impact of the change. If there're a large
number of vlans
adding a macvlan (or any device that syncs uc addr) might become very
slow and every
flag change will become very slow too without an option to revert to
the original
behaviour so we'll have to wait for the entries to be added in order
to delete them.
Another common scenario is having 8021q interfaces on top of the
bridge with different
mac addresses for some of the configured vlans (or with macvlans on
top of them for VRR),
that use case would suffer as well because their macs need to be local
only for those vlans,
and not the 2000+ other vlans that might exist.
On every sync_uc() call all the fdb entries get deleted and added
again, so even after deleting
some manually they can come back unexpectedly after some operation and
also the message storm from
all the deletes and adds could be problematic as well.

E.g. 2000 br0 vlans, 25 macvlans on br0 (adding them took more than 5
minutes, 53k fdb entries):
$ bridge fdb del de:8e:9f:16:c5:71 dev br0 vlan 289
$ ip l set br0 multicast on
$ bridge fdb | grep 289 | grep de:8e:9f:16:c5:71
de:8e:9f:16:c5:71 dev br0 vlan 1289 master br0 permanent
de:8e:9f:16:c5:71 dev br0 vlan 289 master br0 permanent

In fact you can't escape the slow performance even if you delete all
entries because on the
next flag change or interface add, they will be added back.


I still think this auto-sync should be done, otherwise macvlan imposes
promiscuous mode on bridge even if you manually add such fdb entries.
I believe most of your concern would disappear by making use of
__dev_uc_sync() instead.
Indeed it seems that there is no easy way to propagate the combination
of uc addr and vlan from upper device, so local entries for unneeded
vlan can still be created even if using __dev_uc_sync(). In case you
worry about those unneeded entries, I can add a knob to disable this
feature.
Are you comfortable with this change?


Tested performance using __dev_uc_sync() and got expected results.
(Add 3000 br0 vlans, 50 macvlans on br0)

* Without patch
  1.8s

* Patch v2
  2m42s

Your machine is much faster apparently. :-) It took me ~5 minutes for 25
macvlans
in my VM.



* Patch using __dev_uc_sync()
  3.5s
  Also, a manually deleted entry is not restored by flag change.


Nikolay, David, I'd like to hear your feedback.
I'm thinking the performance implication now looks reasonable.
If you don't have objection, I'll work on v3 (using __dev_uc_sync() and
knob to disable the feature).

Thanks,
Toshiaki Makita



The numbers sound okay, but I'd have to see the patch to be able to comment
further.


Sure.

> I wonder why the push for this change when this can be currently

"fixed" by adding the macs manually as local (pointing to the bridge) ?


Well, there are two problems.
One is what Patrick Schaaf reported and can be solved by manually adding 
local entries as well.
The other is that macvlans force the bridge to be promiscuous. That 
means bridge ports cannot be non-promiscuous if any macvlan exists. This 
is because bridge's non-promiscuous feature requires all necessary fdb 
entries to be configured in order to sync them to brport's uc list. 
Without sync_uc of the bridge device, bridge cannot know what addresses 
are needed for brport's uc filter so we cannot get around promiscuous 
mode with macvlans. This is what I feel is worth fixing with this patch. 
I'm thinking this auto non-promiscuous should be transparently done with 
macvlans...

Sorry about the lack of explanation.

Thanks,
Toshiaki Makita

Re: [Bridge] [PATCH net-next v2] bridge: Synchronize unicast filtering with FDB

[Nikolay Aleksandrov]

On 13/06/16 13:13, Toshiaki Makita wrote:

On 2016/06/12 15:35, Toshiaki Makita wrote:

On 16/06/12 (日) 1:17, Nikolay Aleksandrov via Bridge wrote:

On 06/11/2016 07:35 AM, David Miller wrote:

From: Toshiaki Makita 
Date: Mon,  6 Jun 2016 21:20:13 +0900


Patrick Schaaf reported that flooding due to a missing fdb entry of
the address of macvlan on the bridge device caused high CPU
consumption of an openvpn process behind a tap bridge port.
Adding an fdb entry of the macvlan address can suppress flooding
and avoid this problem.

This change makes bridge able to synchronize unicast filtering with
fdb automatically so admin do not need to manually add an fdb entry.
This effectively supports IFF_UNICAST_FLT in bridge, thus adding an
macvlan device would not place bridge into promiscuous mode as well.

v2:
- Test vlan with br_vlan_should_use() in br_fdb_sync_uc() as per
Nikolay Aleksandrov.

Reported-by: Patrick Schaaf 
Signed-off-by: Toshiaki Makita 


I really need bridging experts to review and ACK/NACK this.

Thanks.



Oops, I almost missed the v2, sorry about that. So, technically it
looks correct, but
I only fear the scalability impact of the change. If there're a large
number of vlans
adding a macvlan (or any device that syncs uc addr) might become very
slow and every
flag change will become very slow too without an option to revert to
the original
behaviour so we'll have to wait for the entries to be added in order
to delete them.
Another common scenario is having 8021q interfaces on top of the
bridge with different
mac addresses for some of the configured vlans (or with macvlans on
top of them for VRR),
that use case would suffer as well because their macs need to be local
only for those vlans,
and not the 2000+ other vlans that might exist.
On every sync_uc() call all the fdb entries get deleted and added
again, so even after deleting
some manually they can come back unexpectedly after some operation and
also the message storm from
all the deletes and adds could be problematic as well.

E.g. 2000 br0 vlans, 25 macvlans on br0 (adding them took more than 5
minutes, 53k fdb entries):
$ bridge fdb del de:8e:9f:16:c5:71 dev br0 vlan 289
$ ip l set br0 multicast on
$ bridge fdb | grep 289 | grep de:8e:9f:16:c5:71
de:8e:9f:16:c5:71 dev br0 vlan 1289 master br0 permanent
de:8e:9f:16:c5:71 dev br0 vlan 289 master br0 permanent

In fact you can't escape the slow performance even if you delete all
entries because on the
next flag change or interface add, they will be added back.


I still think this auto-sync should be done, otherwise macvlan imposes
promiscuous mode on bridge even if you manually add such fdb entries.
I believe most of your concern would disappear by making use of
__dev_uc_sync() instead.
Indeed it seems that there is no easy way to propagate the combination
of uc addr and vlan from upper device, so local entries for unneeded
vlan can still be created even if using __dev_uc_sync(). In case you
worry about those unneeded entries, I can add a knob to disable this
feature.
Are you comfortable with this change?


Tested performance using __dev_uc_sync() and got expected results.
(Add 3000 br0 vlans, 50 macvlans on br0)

* Without patch
  1.8s

* Patch v2
  2m42s

Your machine is much faster apparently. :-) It took me ~5 minutes for 25 
macvlans
in my VM.



* Patch using __dev_uc_sync()
  3.5s
  Also, a manually deleted entry is not restored by flag change.


Nikolay, David, I'd like to hear your feedback.
I'm thinking the performance implication now looks reasonable.
If you don't have objection, I'll work on v3 (using __dev_uc_sync() and
knob to disable the feature).

Thanks,
Toshiaki Makita



The numbers sound okay, but I'd have to see the patch to be able to comment
further. I wonder why the push for this change when this can be currently
"fixed" by adding the macs manually as local (pointing to the bridge) ?
Anyway I don't mind having it automated if the change doesn't break anything
or introduce any performance regressions.

Cheers,
 Nik

Re: [Bridge] [PATCH net-next v2] bridge: Synchronize unicast filtering with FDB

[Toshiaki Makita]

On 2016/06/12 15:35, Toshiaki Makita wrote:
> On 16/06/12 (日) 1:17, Nikolay Aleksandrov via Bridge wrote:
>> On 06/11/2016 07:35 AM, David Miller wrote:
>>> From: Toshiaki Makita 
>>> Date: Mon,  6 Jun 2016 21:20:13 +0900
>>>
 Patrick Schaaf reported that flooding due to a missing fdb entry of
 the address of macvlan on the bridge device caused high CPU
 consumption of an openvpn process behind a tap bridge port.
 Adding an fdb entry of the macvlan address can suppress flooding
 and avoid this problem.

 This change makes bridge able to synchronize unicast filtering with
 fdb automatically so admin do not need to manually add an fdb entry.
 This effectively supports IFF_UNICAST_FLT in bridge, thus adding an
 macvlan device would not place bridge into promiscuous mode as well.

 v2:
 - Test vlan with br_vlan_should_use() in br_fdb_sync_uc() as per
Nikolay Aleksandrov.

 Reported-by: Patrick Schaaf 
 Signed-off-by: Toshiaki Makita 
>>>
>>> I really need bridging experts to review and ACK/NACK this.
>>>
>>> Thanks.
>>>
>>
>> Oops, I almost missed the v2, sorry about that. So, technically it
>> looks correct, but
>> I only fear the scalability impact of the change. If there're a large
>> number of vlans
>> adding a macvlan (or any device that syncs uc addr) might become very
>> slow and every
>> flag change will become very slow too without an option to revert to
>> the original
>> behaviour so we'll have to wait for the entries to be added in order
>> to delete them.
>> Another common scenario is having 8021q interfaces on top of the
>> bridge with different
>> mac addresses for some of the configured vlans (or with macvlans on
>> top of them for VRR),
>> that use case would suffer as well because their macs need to be local
>> only for those vlans,
>> and not the 2000+ other vlans that might exist.
>> On every sync_uc() call all the fdb entries get deleted and added
>> again, so even after deleting
>> some manually they can come back unexpectedly after some operation and
>> also the message storm from
>> all the deletes and adds could be problematic as well.
>>
>> E.g. 2000 br0 vlans, 25 macvlans on br0 (adding them took more than 5
>> minutes, 53k fdb entries):
>> $ bridge fdb del de:8e:9f:16:c5:71 dev br0 vlan 289
>> $ ip l set br0 multicast on
>> $ bridge fdb | grep 289 | grep de:8e:9f:16:c5:71
>> de:8e:9f:16:c5:71 dev br0 vlan 1289 master br0 permanent
>> de:8e:9f:16:c5:71 dev br0 vlan 289 master br0 permanent
>>
>> In fact you can't escape the slow performance even if you delete all
>> entries because on the
>> next flag change or interface add, they will be added back.
> 
> I still think this auto-sync should be done, otherwise macvlan imposes
> promiscuous mode on bridge even if you manually add such fdb entries.
> I believe most of your concern would disappear by making use of
> __dev_uc_sync() instead.
> Indeed it seems that there is no easy way to propagate the combination
> of uc addr and vlan from upper device, so local entries for unneeded
> vlan can still be created even if using __dev_uc_sync(). In case you
> worry about those unneeded entries, I can add a knob to disable this
> feature.
> Are you comfortable with this change?

Tested performance using __dev_uc_sync() and got expected results.
(Add 3000 br0 vlans, 50 macvlans on br0)

* Without patch
 1.8s

* Patch v2
 2m42s

* Patch using __dev_uc_sync()
 3.5s
 Also, a manually deleted entry is not restored by flag change.


Nikolay, David, I'd like to hear your feedback.
I'm thinking the performance implication now looks reasonable.
If you don't have objection, I'll work on v3 (using __dev_uc_sync() and
knob to disable the feature).

Thanks,
Toshiaki Makita

Re: [Bridge] [PATCH net-next v2] bridge: Synchronize unicast filtering with FDB

[Toshiaki Makita]

On 16/06/12 (日) 1:17, Nikolay Aleksandrov via Bridge wrote:

On 06/11/2016 07:35 AM, David Miller wrote:

From: Toshiaki Makita 
Date: Mon,  6 Jun 2016 21:20:13 +0900


Patrick Schaaf reported that flooding due to a missing fdb entry of
the address of macvlan on the bridge device caused high CPU
consumption of an openvpn process behind a tap bridge port.
Adding an fdb entry of the macvlan address can suppress flooding
and avoid this problem.

This change makes bridge able to synchronize unicast filtering with
fdb automatically so admin do not need to manually add an fdb entry.
This effectively supports IFF_UNICAST_FLT in bridge, thus adding an
macvlan device would not place bridge into promiscuous mode as well.

v2:
- Test vlan with br_vlan_should_use() in br_fdb_sync_uc() as per
   Nikolay Aleksandrov.

Reported-by: Patrick Schaaf 
Signed-off-by: Toshiaki Makita 


I really need bridging experts to review and ACK/NACK this.

Thanks.



Oops, I almost missed the v2, sorry about that. So, technically it looks 
correct, but
I only fear the scalability impact of the change. If there're a large number of 
vlans
adding a macvlan (or any device that syncs uc addr) might become very slow and 
every
flag change will become very slow too without an option to revert to the 
original
behaviour so we'll have to wait for the entries to be added in order to delete 
them.
Another common scenario is having 8021q interfaces on top of the bridge with 
different
mac addresses for some of the configured vlans (or with macvlans on top of them 
for VRR),
that use case would suffer as well because their macs need to be local only for 
those vlans,
and not the 2000+ other vlans that might exist.
On every sync_uc() call all the fdb entries get deleted and added again, so 
even after deleting
some manually they can come back unexpectedly after some operation and also the 
message storm from
all the deletes and adds could be problematic as well.

E.g. 2000 br0 vlans, 25 macvlans on br0 (adding them took more than 5 minutes, 
53k fdb entries):
$ bridge fdb del de:8e:9f:16:c5:71 dev br0 vlan 289
$ ip l set br0 multicast on
$ bridge fdb | grep 289 | grep de:8e:9f:16:c5:71
de:8e:9f:16:c5:71 dev br0 vlan 1289 master br0 permanent
de:8e:9f:16:c5:71 dev br0 vlan 289 master br0 permanent

In fact you can't escape the slow performance even if you delete all entries 
because on the
next flag change or interface add, they will be added back.


I still think this auto-sync should be done, otherwise macvlan imposes 
promiscuous mode on bridge even if you manually add such fdb entries.
I believe most of your concern would disappear by making use of 
__dev_uc_sync() instead.
Indeed it seems that there is no easy way to propagate the combination 
of uc addr and vlan from upper device, so local entries for unneeded 
vlan can still be created even if using __dev_uc_sync(). In case you 
worry about those unneeded entries, I can add a knob to disable this 
feature.

Are you comfortable with this change?

Toshiaki Makita