Lines Matching refs:trap
31 The ``devlink-trap`` mechanism allows capable device drivers to register their
35 Upon receiving trapped packets, ``devlink`` will perform a per-trap packets and
37 event along with all the provided metadata (e.g., trap reason, timestamp, input
42 The following diagram provides a general overview of ``devlink-trap``::
89 The ``devlink-trap`` mechanism supports the following packet trap types:
93 The trap action (see :ref:`Trap-Actions`) can be changed.
112 The ``devlink-trap`` mechanism supports the following packet trap actions:
114 * ``trap``: The sole copy of the packet is sent to the CPU.
123 Generic packet traps are used to describe traps that trap well-defined packets
361 IP address with a link-local scope (i.e., fe80::/10). The trap allows
406 - Traps packets logged during processing of flow action trap (e.g., via
407 tc's trap action)
439 This packet trap could include packets which do not pass an IP checksum
447 error checking is performed here as for the ip_1_parsing trap
454 This packet trap could include checksum errorrs, an improper UDP
507 Generic packet trap groups are used to aggregate logically related packet
508 traps. These groups allow the user to batch operations such as setting the trap
509 action of all member traps. In addition, ``devlink-trap`` can report aggregated
510 per-group packets and bytes statistics, in case per-trap statistics are too
561 - Contains a packet trap for unicast loopback packets (i.e.,
562 ``uc_loopback``). This trap is singled-out because in cases such as
564 the CPU usage, a packet trap policer with a low rate can be bound to the
596 As previously explained, the underlying device can trap certain packets to the
602 devices usually include packet trap policers that are able to police the
605 The ``devlink-trap`` mechanism allows capable device drivers to register their
606 supported packet trap policers with ``devlink``. The device driver can choose
607 to associate these policers with supported packet trap groups (see
613 trap groups by implementing the relevant callbacks.