Re: [PATCH net-next] bridge: vlan: add per-vlan struct and move to rhashtables

2015-09-29 Thread David Miller
From: Nikolay Aleksandrov Date: Fri, 25 Sep 2015 19:00:11 +0200 > This patch changes the bridge vlan implementation to use rhashtables > instead of bitmaps. This seems to be taking the code in a good direction, and I'm kinda happy to see more rhashtable users in the tree as

Re: [PATCH net-next] bridge: vlan: add per-vlan struct and move to rhashtables

2015-09-25 Thread Stephen Hemminger
On Fri, 25 Sep 2015 19:00:11 +0200 Nikolay Aleksandrov wrote: > From: Nikolay Aleksandrov > > This patch changes the bridge vlan implementation to use rhashtables > instead of bitmaps. The main motivation behind this change is that we > need

Re: [PATCH net-next] bridge: vlan: add per-vlan struct and move to rhashtables

2015-09-25 Thread Nikolay Aleksandrov
On 09/25/2015 08:30 PM, Stephen Hemminger wrote: > On Fri, 25 Sep 2015 19:00:11 +0200 > Nikolay Aleksandrov wrote: > >> From: Nikolay Aleksandrov >> >> This patch changes the bridge vlan implementation to use rhashtables >> instead of bitmaps.

[PATCH net-next] bridge: vlan: add per-vlan struct and move to rhashtables

2015-09-25 Thread Nikolay Aleksandrov
From: Nikolay Aleksandrov This patch changes the bridge vlan implementation to use rhashtables instead of bitmaps. The main motivation behind this change is that we need extensible per-vlan structures (both per-port and global) so more advanced features can be