Lines Matching +full:configuration +full:- +full:specific

1 .. SPDX-License-Identifier: GPL-2.0
12 ``devlink-dpipe`` provides a standardized way to provide visibility into the
32 greatly to the hardware implementation. The configuration API is the same,
34 Level Path Compression trie (LPC-trie) in hardware.
45 The ``devlink-dpipe`` interface closes this gap. The hardware's pipeline is
46 modeled as a graph of match/action tables. Each table represents a specific
50 configuration, but the ``devlink-dpipe`` interface uses it for visibility
52 ``devlink-dpipe`` should change according to the changes done by the
53 standard configuration tools.
75 the actual content of a specific table.
77 The hardware pipeline is not port specific, but rather describes the whole
84 ``devlink-dpipe`` generally is not intended for configuration. The exception
85 is hardware counting for a specific table.
96 -----
107 ------------
111 and specific ASIC metadata. The protocol headers should be declared in the
112 ``devlink`` core API. On the other hand ASIC meta data is driver specific
113 and should be defined in the driver. Additionally, each driver-specific
114 devlink documentation file should document the driver-specific ``dpipe``
124 -----
130   * ``field_exact``: Exact match on a specific field.
131   * ``field_exact_mask``: Exact match on a specific field after masking.
132   * ``field_range``: Match on a specific range.
135 identify the specific field. Furthermore, the header index should be
140 ------
151 -----
153 Entries of a specific table can be dumped on demand. Each eentry is
155 match/action values and specific counter. By dumping the tables content the
167 ---
176 host table for directly connected routes, or adjacency table for next-hops.
195 ----------
213 ---------
234 ----