Searched hist:"71844 fac1ed459024dd2a448d63d5b28b8c87daa" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/drivers/net/ethernet/netronome/nfp/abm/ |
| H A D | main.c | diff 71844fac1ed459024dd2a448d63d5b28b8c87daa Wed Nov 28 00:24:55 CST 2018 Jakub Kicinski <jakub.kicinski@netronome.com> nfp: add locking around representor changes
Up until now we never needed to keep a networking locks around
representors accesses, we only accessed them when device was
reconfigured (under nfp pf->lock) or on fast path (under RCU).
Now we want to be able to iterate over all representors during
notifications, so make sure representor assignment is done
under RTNL lock.
Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: John Hurley <john.hurley@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/drivers/net/ethernet/netronome/nfp/ |
| H A D | nfp_app.c | diff 71844fac1ed459024dd2a448d63d5b28b8c87daa Wed Nov 28 00:24:55 CST 2018 Jakub Kicinski <jakub.kicinski@netronome.com> nfp: add locking around representor changes
Up until now we never needed to keep a networking locks around
representors accesses, we only accessed them when device was
reconfigured (under nfp pf->lock) or on fast path (under RCU).
Now we want to be able to iterate over all representors during
notifications, so make sure representor assignment is done
under RTNL lock.
Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: John Hurley <john.hurley@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | nfp_net_repr.c | diff 71844fac1ed459024dd2a448d63d5b28b8c87daa Wed Nov 28 00:24:55 CST 2018 Jakub Kicinski <jakub.kicinski@netronome.com> nfp: add locking around representor changes
Up until now we never needed to keep a networking locks around
representors accesses, we only accessed them when device was
reconfigured (under nfp pf->lock) or on fast path (under RCU).
Now we want to be able to iterate over all representors during
notifications, so make sure representor assignment is done
under RTNL lock.
Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: John Hurley <john.hurley@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|