Commit 46799a41 authored by Linu Cherian's avatar Linu Cherian Committed by Jakub Kicinski
Browse files

devlink: Add documentation for OcteonTx2 AF 



Add documentation for the following devlink params
- npc_mcam_high_zone_percent
- npc_def_rule_cntr
- nix_maxlf

Signed-off-by: default avatarLinu Cherian <lcherian@marvell.com>
Link: https://patch.msgid.link/20241105125620.2114301-4-lcherian@marvell.com


Signed-off-by: default avatarJakub Kicinski <kuba@kernel.org>
parent 70a7434b

Documentation/networking/devlink/octeontx2.rst

+21 −0
Original line number Diff line number Diff line
@@ -40,6 +40,27 @@ The ``octeontx2 AF`` driver implements the following driver-specific parameters. 
     - runtime

     - Use to set the quantum which hardware uses for scheduling among transmit queues.

       Hardware uses weighted DWRR algorithm to schedule among all transmit queues.

   * - ``npc_mcam_high_zone_percent``

     - u8

     - runtime

     - Use to set the number of high priority zone entries in NPC MCAM that can be allocated

       by a user, out of the three priority zone categories high, mid and low.

   * - ``npc_def_rule_cntr``

     - bool

     - runtime

     - Use to enable or disable hit counters for the default rules in NPC MCAM.

       Its not guaranteed that counters gets enabled and mapped to all the default rules,

       since the counters are scarce and driver follows a best effort approach.

       The default rule serves as the primary packet steering rule for a specific PF or VF,

       based on its DMAC address which is installed by AF driver as part of its initialization.

       Sample command to read hit counters for default rule from debugfs is as follows,

       cat /sys/kernel/debug/cn10k/npc/mcam_rules

   * - ``nix_maxlf``

     - u16

     - runtime

     - Use to set the maximum number of LFs in NIX hardware block. This would be useful

       to increase the availability of default resources allocated to enabled LFs like

       MCAM entries for example.



The ``octeontx2 PF`` driver implements the following driver-specific parameters.