Lines Matching +full:multi +full:- +full:functional
1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 - Validation
18 * - ``enable_roce``
19 - driverinit
20 - Type: Boolean
26 * - ``io_eq_size``
27 - driverinit
28 - The range is between 64 and 4096.
29 * - ``event_eq_size``
30 - driverinit
31 - The range is between 64 and 4096.
32 * - ``max_macs``
33 - driverinit
34 - The range is between 1 and 2^31. Only power of 2 values are supported.
36 The ``mlx5`` driver also implements the following driver-specific
39 .. list-table:: Driver-specific parameters implemented
42 * - Name
43 - Type
44 - Mode
45 - Description
46 * - ``flow_steering_mode``
47 - string
48 - runtime
49 - Controls the flow steering mode of the driver
62 * - ``fdb_large_groups``
63 - u32
64 - driverinit
65 - Control the number of large groups (size > 1) in the FDB table.
68 * - ``esw_multiport``
69 - Boolean
70 - runtime
71 - Control MultiPort E-Switch shared fdb mode.
73 An experimental mode where a single E-Switch is used and all the vports
79 Note: Future devices, ConnectX-8 and onward, will eventually have this
81 E-switch environment and the dual E-switch mode will likely get
85 * - ``esw_port_metadata``
86 - Boolean
87 - runtime
88 - When applicable, disabling eswitch metadata can increase packet rate up
92 with metadata. Metadata tagging must be enabled for multi-port RoCE,
94 enabled on the supported devices in E-switch. Metadata is applicable only
95 for E-switch in switchdev mode and users may disable it when NONE of the
97 1. HCA is in Dual/multi-port RoCE mode.
107 * - ``hairpin_num_queues``
108 - u32
109 - driverinit
110 - We refer to a TC NIC rule that involves forwarding as "hairpin".
115 * - ``hairpin_queue_size``
116 - u32
117 - driverinit
118 - Control the size (in packets) of the hairpin queues.
127 .. list-table:: devlink info versions implemented
130 * - Name
131 - Type
132 - Description
133 * - ``fw.psid``
134 - fixed
135 - Used to represent the board id of the device.
136 * - ``fw.version``
137 - stored, running
138 - Three digit major.minor.subminor firmware version number.
144 -----------
147 - tx timeout
150 - tx error completion
153 - tx PTP port timestamping CQ unhealthy
155 Recover by flushing and re-creating all PTP channels.
162 - Diagnose send queues status::
169 - Show number of tx errors indicated, number of recover flows ended successfully,
175 -----------
178 - rx queues' initialization (population) timeout
183 - rx completions with errors (reported by HW on interrupt context)
190 - Diagnose rx queues' status and corresponding completion queue::
197 - Show number of rx errors indicated, number of recover flows ended successfully,
203 -----------
212 - Check fw heath status::
216 - Read FW core dump if already stored or trigger new one::
225 -----------------
227 It follows fatal errors indications by CR-space dump and recover flow.
228 The CR-space dump uses vsc interface which is valid even if the FW command
229 interface is not functional, which is the case in most FW fatal errors.
237 - Run fw recover flow manually::
241 - Read FW CR-space dump if already stored or trigger new one::
249 -------------
256 - total_error_queues
259 - send_queue_priority_update_flow
261 - cq_overrun
263 - async_eq_overrun
265 - comp_eq_overrun
268 - quota_exceeded_command
270 - invalid_command
273 - nic_receive_steering_discard
276 - generated_pkt_steering_fail
279 - handled_pkt_steering_fail
286 - Diagnose PF/VF vnic counters::
290 - Diagnose representor vnic counters (performed by supplying devlink port of the