networking/devlink/devlink-dpipe.rst

1 .. SPDX-License-Identifier: GPL-2.0
12 ``devlink-dpipe`` provides a standardized way to provide visibility into the
34 Level Path Compression trie (LPC-trie) in hardware.
36 In many situations trying to analyze systems failure solely based on the
45 The ``devlink-dpipe`` interface closes this gap. The hardware's pipeline is
50 configuration, but the ``devlink-dpipe`` interface uses it for visibility
52 ``devlink-dpipe`` should change according to the changes done by the
56 using Ternary Content Addressable Memory (TCAM). The TCAM memory can be
57 divided into TCAM regions. Complex TC filters can have multiple rules with
59 TCAM regions have a predefined lookup key. Offloading the TC filter rules
60 using TCAM engine can result in multiple TCAM regions being interconnected
82 blocks like TCAM regions which can be allocated and freed dynamically.
84 ``devlink-dpipe`` generally is not intended for configuration. The exception
96 -----
107 ------------
113 and should be defined in the driver. Additionally, each driver-specific
114 devlink documentation file should document the driver-specific ``dpipe``
124 -----
140 ------
151 -----
167 ---
176 host table for directly connected routes, or adjacency table for next-hops.
195 ----------
213 ---------
217 Concurrently a hash of the packet is generated. Based on the ECMP group size
234 ----
239 updated based on the packet's type (broadcast, unicast, multicast).