summaryrefslogtreecommitdiffstats
path: root/net/ipv4
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2019-12-06 20:45:09 -0800
committerDavid S. Miller <davem@davemloft.net>2019-12-06 20:45:09 -0800
commit9a74542eee86313ab7b31ae28b45c59d244e3a85 (patch)
treebabfe8574b84081e05e01343889868507159fc73 /net/ipv4
parente0b60903b434a7ee21ba8d8659f207ed84101e89 (diff)
parent25a443f74bcff2c4d506a39eae62fc15ad7c618a (diff)
downloadlinux-9a74542eee86313ab7b31ae28b45c59d244e3a85.tar.gz
linux-9a74542eee86313ab7b31ae28b45c59d244e3a85.tar.bz2
linux-9a74542eee86313ab7b31ae28b45c59d244e3a85.zip
Merge branch 'net-tc-indirect-block-relay'
John Hurley says: ==================== Ensure egress un/bind are relayed with indirect blocks On register and unregister for indirect blocks, a command is called that sends a bind/unbind event to the registering driver. This command assumes that the bind to indirect block will be on ingress. However, drivers such as NFP have allowed binding to clsact qdiscs as well as ingress qdiscs from mainline Linux 5.2. A clsact qdisc binds to an ingress and an egress block. Rather than assuming that an indirect bind is always ingress, modify the function names to remove the ingress tag (patch 1). In cls_api, which is used by NFP to offload TC flower, generate bind/unbind message for both ingress and egress blocks on the event of indirectly registering/unregistering from that block. Doing so mimics the behaviour of both ingress and clsact qdiscs on initialise and destroy. This now ensures that drivers such as NFP receive the correct binder type for the indirect block registration. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4')
0 files changed, 0 insertions, 0 deletions