Lines Matching +full:hardware +full:- +full:based

1 .. SPDX-License-Identifier: GPL-2.0
10 While performing the hardware offloading process, much of the hardware
12 ``devlink-dpipe`` provides a standardized way to provide visibility into the
16 Linux kernel may differ from the hardware implementation. The pipeline debug
20 The hardware offload process is expected to be done in a way that the user
21 should not be able to distinguish between the hardware vs. software
22 implementation. In this process, hardware specifics are neglected. In
28 differences in the hardware and software models some processes cannot be
32 greatly to the hardware implementation. The configuration API is the same,
34 Level Path Compression trie (LPC-trie) in hardware.
36 In many situations trying to analyze systems failure solely based on the
38 information about the underlying hardware, this debugging can be made
45 The ``devlink-dpipe`` interface closes this gap. The hardware's pipeline is
47 hardware block. This model is not new, first being used by the P4 language.
49 Traditionally it has been used as an alternative model for hardware
50 configuration, but the ``devlink-dpipe`` interface uses it for visibility
52 ``devlink-dpipe`` should change according to the changes done by the
58 different priorities and different lookup keys. On the other hand hardware
74 the packet. A ``table`` describes hardware blocks. An ``entry`` describes
77 The hardware pipeline is not port specific, but rather describes the whole
81 dynamic behavior. This dynamic behavior is mandatory for describing hardware
84 ``devlink-dpipe`` generally is not intended for configuration. The exception
85 is hardware counting for a specific table.
96 -----
103   * ``counters_set_update``: Synchronize hardware with counters enabled or
107 ------------
113 and should be defined in the driver. Additionally, each driver-specific
114 devlink documentation file should document the driver-specific ``dpipe``
124 -----
126 Matches are kept primitive and close to hardware operation. Match types like
140 ------
142 Similar to match, the actions are kept primitive and close to hardware
151 -----
164 hardware sizes and are provided for demonstration purposes.
167 ---
171 /32, and in case of a miss the hardware will continue to the next hash
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).