Documentation: Add description of packet trap policers
Extend devlink-trap documentation with information about packet trap policers. Signed-off-by: Ido Schimmel <idosch@mellanox.com> Reviewed-by: Jiri Pirko <jiri@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
1e8c661989
commit
ef7d5c7d43
@ -287,6 +287,32 @@ narrow. The description of these groups must be added to the following table:
|
||||
- Contains packet traps for packets that were dropped by the device during
|
||||
ACL processing
|
||||
|
||||
Packet Trap Policers
|
||||
====================
|
||||
|
||||
As previously explained, the underlying device can trap certain packets to the
|
||||
CPU for processing. In most cases, the underlying device is capable of handling
|
||||
packet rates that are several orders of magnitude higher compared to those that
|
||||
can be handled by the CPU.
|
||||
|
||||
Therefore, in order to prevent the underlying device from overwhelming the CPU,
|
||||
devices usually include packet trap policers that are able to police the
|
||||
trapped packets to rates that can be handled by the CPU.
|
||||
|
||||
The ``devlink-trap`` mechanism allows capable device drivers to register their
|
||||
supported packet trap policers with ``devlink``. The device driver can choose
|
||||
to associate these policers with supported packet trap groups (see
|
||||
:ref:`Generic-Packet-Trap-Groups`) during its initialization, thereby exposing
|
||||
its default control plane policy to user space.
|
||||
|
||||
Device drivers should allow user space to change the parameters of the policers
|
||||
(e.g., rate, burst size) as well as the association between the policers and
|
||||
trap groups by implementing the relevant callbacks.
|
||||
|
||||
If possible, device drivers should implement a callback that allows user space
|
||||
to retrieve the number of packets that were dropped by the policer because its
|
||||
configured policy was violated.
|
||||
|
||||
Testing
|
||||
=======
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user