octeontx2 devlink support¶
This document describes the devlink features implemented by the octeontx2 AF, PF and VF
device drivers.
Parameters¶
The octeontx2 PF and VF
drivers implement the following driver-specific parameters.
Name |
Type |
Mode |
Description |
|
u16 |
runtime |
Select number of match CAM entries to be allocated for an interface. The same is used for ntuple filters of the interface. Supported by PF and VF drivers. |
The octeontx2 AF
driver implements the following driver-specific parameters.
Name |
Type |
Mode |
Description |
|
u32 |
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. |
|
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. |
|
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 |
|
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.
Name |
Type |
Mode |
Description |
|
u8 |
runtime |
Set the maximum number of unicast filters that can be programmed for the device. This can be used to achieve better device resource utilization, avoiding over consumption of unused MCAM table entries. |