Searched hist:"5 d8b3e69fc5e5ccafc9db1251bb7c78a8622fddd" (Results 1 – 2 of 2) sorted by relevance
| /linux/include/linux/ |
| H A D | mroute.h | diff 5d8b3e69fc5e5ccafc9db1251bb7c78a8622fddd Tue Oct 03 09:58:07 CEST 2017 Yotam Gigi <yotamg@mellanox.com> ipv4: ipmr: Add the parent ID field to VIF struct
In order to allow the ipmr module to do partial multicast forwarding
according to the device parent ID, add the device parent ID field to the
VIF struct. This way, the forwarding path can use the parent ID field
without invoking switchdev calls, which requires the RTNL lock.
When a new VIF is added, set the device parent ID field in it by invoking
the switchdev_port_attr_get call.
Signed-off-by: Yotam Gigi <yotamg@mellanox.com>
Reviewed-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /linux/net/ipv4/ |
| H A D | ipmr.c | diff 5d8b3e69fc5e5ccafc9db1251bb7c78a8622fddd Tue Oct 03 09:58:07 CEST 2017 Yotam Gigi <yotamg@mellanox.com> ipv4: ipmr: Add the parent ID field to VIF struct
In order to allow the ipmr module to do partial multicast forwarding
according to the device parent ID, add the device parent ID field to the
VIF struct. This way, the forwarding path can use the parent ID field
without invoking switchdev calls, which requires the RTNL lock.
When a new VIF is added, set the device parent ID field in it by invoking
the switchdev_port_attr_get call.
Signed-off-by: Yotam Gigi <yotamg@mellanox.com>
Reviewed-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|