summaryrefslogtreecommitdiffstats
path: root/scripts/dtc/fdtget.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2020-01-19 16:17:07 +0100
committerDavid S. Miller <davem@davemloft.net>2020-01-19 16:17:07 +0100
commit95ae2d1d114989ce07db59dcf357eb78d7357fe1 (patch)
treec553dbfc10a7f28890415cafdd2a03197b7a7224 /scripts/dtc/fdtget.c
parent0c58ac1e0155fdbefb976ff2d321d1093b92fe50 (diff)
parent278d51f24330718aefd7fe86996a6da66fd345e7 (diff)
downloadblackbird-op-linux-95ae2d1d114989ce07db59dcf357eb78d7357fe1.tar.gz
blackbird-op-linux-95ae2d1d114989ce07db59dcf357eb78d7357fe1.zip
Merge branch 'for-net-next' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux
Saeed Mahameed says: ==================== Mellanox, mlx5 E-Switch chains and prios This series has two parts, 1) A merge commit with mlx5-next branch that include updates for mlx5 HW layouts needed for this and upcoming submissions. 2) From Paul, Increase the number of chains and prios Currently the Mellanox driver supports offloading tc rules that are defined on the first 4 chains and the first 16 priorities. The restriction stems from the firmware flow level enforcement requiring a flow table of a certain level to point to a flow table of a higher level. This limitation may be ignored by setting the ignore_flow_level bit when creating flow table entries. Use unmanaged tables and ignore flow level to create more tables than declared by fs_core steering. Manually manage the connections between the tables themselves. HW table is instantiated for every tc <chain,prio> tuple. The miss rule of every table either jumps to the next <chain,prio> table, or continues to slow_fdb. This logic is realized by following this sequence: 1. Create an auto-grouped flow table for the specified priority with reserved entries Reserved entries are allocated at the end of the flow table. Flow groups are evaluated in sequence and therefore it is guaranteed that the flow group defined on the last FTEs will be the last to evaluate. Define a "match all" flow group on the reserved entries, providing the platform to add table miss actions. 2. Set the miss rule action to jump to the next <chain,prio> table or the slow_fdb. 3. Link the previous priority table to point to the new table by updating its miss rule. Please pull and let me know if there's any problem. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts/dtc/fdtget.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud