diff options
author | Paolo Abeni <pabeni@redhat.com> | 2023-02-14 11:00:03 +0100 |
---|---|---|
committer | Paolo Abeni <pabeni@redhat.com> | 2023-02-14 11:00:04 +0100 |
commit | 991cbd4f34b1d2d4e4cc41aed6eb4799186c3887 (patch) | |
tree | 96f4a2990f970246a9c1cc515fcfa8a0d09f2a72 /drivers/net/wwan/rpmsg_wwan_ctrl.c | |
parent | a71fad0fd893b5db8ec5a8a287ff87720b7352a6 (diff) | |
parent | 2b68d659a704abaa61fb3255776b5483bdc4eb35 (diff) | |
download | linux-991cbd4f34b1d2d4e4cc41aed6eb4799186c3887.tar.gz linux-991cbd4f34b1d2d4e4cc41aed6eb4799186c3887.tar.bz2 linux-991cbd4f34b1d2d4e4cc41aed6eb4799186c3887.zip |
Merge branch 'add-support-for-per-action-hw-stats'
Oz Shlomo says:
====================
add support for per action hw stats
There are currently two mechanisms for populating hardware stats:
1. Using flow_offload api to query the flow's statistics.
The api assumes that the same stats values apply to all
the flow's actions.
This assumption breaks when action drops or jumps over following
actions.
2. Using hw_action api to query specific action stats via a driver
callback method. This api assures the correct action stats for
the offloaded action, however, it does not apply to the rest of the
actions in the flow's actions array, as elaborated below.
The current hw_action api does not apply to the following use cases:
1. Actions that are implicitly created by filters (aka bind actions).
In the following example only one counter will apply to the rule:
tc filter add dev $DEV prio 2 protocol ip parent ffff: \
flower ip_proto tcp dst_ip $IP2 \
action police rate 1mbit burst 100k conform-exceed drop/pipe \
action mirred egress redirect dev $DEV2
2. Action preceding a hw action.
In the following example the same flow stats will apply to the sample and
mirred actions:
tc action add police rate 1mbit burst 100k conform-exceed drop / pipe
tc filter add dev $DEV prio 2 protocol ip parent ffff: \
flower ip_proto tcp dst_ip $IP2 \
action sample rate 1 group 10 trunc 60 pipe \
action police index 1 \
action mirred egress redirect dev $DEV2
3. Meter action using jump control.
In the following example the same flow stats will apply to both
mirred actions:
tc action add police rate 1mbit burst 100k conform-exceed jump 2 / pipe
tc filter add dev $DEV prio 2 protocol ip parent ffff: \
flower ip_proto tcp dst_ip $IP2 \
action police index 1 \
action mirred egress redirect dev $DEV2
action mirred egress redirect dev $DEV3
This series provides the platform to query per action stats for in_hw flows.
The first four patches are preparation patches with no functionality change.
The fifth patch re-uses the existing flow action stats api to query action
stats for both classifier and action dumps.
The rest of the patches add per action stats support to the Mellanox driver.
====================
Link: https://lore.kernel.org/r/20230212132520.12571-1-ozsh@nvidia.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'drivers/net/wwan/rpmsg_wwan_ctrl.c')
0 files changed, 0 insertions, 0 deletions