Searched hist:dc002875 (Results 1 – 4 of 4) sorted by relevance
/openbmc/linux/net/bridge/ |
H A D | br_vlan_options.c | dc002875 Tue Aug 10 10:29:33 CDT 2021 Nikolay Aleksandrov <nikolay@nvidia.com> net: bridge: vlan: use br_rports_fill_info() to export mcast router ports
Embed the standard multicast router port export by br_rports_fill_info() into a new global vlan attribute BRIDGE_VLANDB_GOPTS_MCAST_ROUTER_PORTS. In order to have the same format for the global bridge mcast context and the per-vlan mcast context we need a double-nesting: - BRIDGE_VLANDB_GOPTS_MCAST_ROUTER_PORTS - MDBA_ROUTER
Currently we don't compare router lists, if any router port exists in the bridge mcast contexts we consider their option sets as different and export them separately.
In addition we export the router port vlan id when dumping similar to the router port notification format.
Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | br_mdb.c | dc002875 Tue Aug 10 10:29:33 CDT 2021 Nikolay Aleksandrov <nikolay@nvidia.com> net: bridge: vlan: use br_rports_fill_info() to export mcast router ports
Embed the standard multicast router port export by br_rports_fill_info() into a new global vlan attribute BRIDGE_VLANDB_GOPTS_MCAST_ROUTER_PORTS. In order to have the same format for the global bridge mcast context and the per-vlan mcast context we need a double-nesting: - BRIDGE_VLANDB_GOPTS_MCAST_ROUTER_PORTS - MDBA_ROUTER
Currently we don't compare router lists, if any router port exists in the bridge mcast contexts we consider their option sets as different and export them separately.
In addition we export the router port vlan id when dumping similar to the router port notification format.
Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | br_private.h | dc002875 Tue Aug 10 10:29:33 CDT 2021 Nikolay Aleksandrov <nikolay@nvidia.com> net: bridge: vlan: use br_rports_fill_info() to export mcast router ports
Embed the standard multicast router port export by br_rports_fill_info() into a new global vlan attribute BRIDGE_VLANDB_GOPTS_MCAST_ROUTER_PORTS. In order to have the same format for the global bridge mcast context and the per-vlan mcast context we need a double-nesting: - BRIDGE_VLANDB_GOPTS_MCAST_ROUTER_PORTS - MDBA_ROUTER
Currently we don't compare router lists, if any router port exists in the bridge mcast contexts we consider their option sets as different and export them separately.
In addition we export the router port vlan id when dumping similar to the router port notification format.
Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/include/uapi/linux/ |
H A D | if_bridge.h | dc002875 Tue Aug 10 10:29:33 CDT 2021 Nikolay Aleksandrov <nikolay@nvidia.com> net: bridge: vlan: use br_rports_fill_info() to export mcast router ports
Embed the standard multicast router port export by br_rports_fill_info() into a new global vlan attribute BRIDGE_VLANDB_GOPTS_MCAST_ROUTER_PORTS. In order to have the same format for the global bridge mcast context and the per-vlan mcast context we need a double-nesting: - BRIDGE_VLANDB_GOPTS_MCAST_ROUTER_PORTS - MDBA_ROUTER
Currently we don't compare router lists, if any router port exists in the bridge mcast contexts we consider their option sets as different and export them separately.
In addition we export the router port vlan id when dumping similar to the router port notification format.
Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|