Lines Matching refs:hardware
10 While performing the hardware offloading process, much of the hardware
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.
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
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
85 is hardware counting for a specific table.
103 * ``counters_set_update``: Synchronize hardware with counters enabled or
126 Matches are kept primitive and close to hardware operation. Match types like
142 Similar to match, the actions are kept primitive and close to hardware
164 hardware sizes and are provided for demonstration purposes.
171 /32, and in case of a miss the hardware will continue to the next hash