aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/dsa/mv88e6xxx
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2019-05-05 21:49:24 -0700
committerDavid S. Miller <davem@davemloft.net>2019-05-05 21:49:24 -0700
commit7e6a95d31b191d81639b089b6ff7a7995bcb4ac3 (patch)
tree4219c7cb2a12e4dcb82f7269483a68380e87198c /drivers/net/dsa/mv88e6xxx
parentMerge branch 'of_net-Add-NVMEM-support-to-of_get_mac_address' (diff)
parentnfp: flower: add qos offload stats request and reply (diff)
downloadlinux-dev-7e6a95d31b191d81639b089b6ff7a7995bcb4ac3.tar.xz
linux-dev-7e6a95d31b191d81639b089b6ff7a7995bcb4ac3.zip
Merge branch 'net-act_police-offload-support'
Jakub Kicinski says: =================== net: act_police offload support this set starts by converting cls_matchall to the new flow offload infrastructure. It so happens that all drivers implementing cls_matchall offload today also offload cls_flower, so its a little easier for them to handle the actions in unified flow_rule format, even though in cls_matchall there is no flow to speak of. If a driver ever appears which would prefer the old, direct access to TC exts, we can add the pointer in the offload structure back and support both. Next the act_police is added to actions supported by flow offload API. NFP support for act_police offload is added as the final step. The flower firmware is configured to perform TX rate limiting in a way which matches act_police's behaviour. It does not use DMA.IN back pressure, and instead drops packets after they had been already DMAed into the NIC. IOW it uses our standard traffic policing implementation, future patches will extend it to other ports and traffic directions. =================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/dsa/mv88e6xxx')
0 files changed, 0 insertions, 0 deletions