diff options
author | John Hurley <john.hurley@netronome.com> | 2019-12-05 17:03:34 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-12-06 20:45:09 -0800 |
commit | dbad3408896c3c5722ec9cda065468b3df16c5bf (patch) | |
tree | 2495bdc15102c3b5b3fac309d84a5659fc4fb5e4 /net/rds | |
parent | e0b60903b434a7ee21ba8d8659f207ed84101e89 (diff) |
net: core: rename indirect block ingress cb function
With indirect blocks, a driver can register for callbacks from a device
that is does not 'own', for example, a tunnel device. When registering to
or unregistering from a new device, a callback is triggered to generate
a bind/unbind event. This, in turn, allows the driver to receive any
existing rules or to properly clean up installed rules.
When first added, it was assumed that all indirect block registrations
would be for ingress offloads. However, the NFP driver can, in some
instances, support clsact qdisc binds for egress offload.
Change the name of the indirect block callback command in flow_offload to
remove the 'ingress' identifier from it. While this does not change
functionality, a follow up patch will implement a more more generic
callback than just those currently just supporting ingress offload.
Fixes: 4d12ba42787b ("nfp: flower: allow offloading of matches on 'internal' ports")
Signed-off-by: John Hurley <john.hurley@netronome.com>
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/rds')
0 files changed, 0 insertions, 0 deletions