Lines Matching +full:1 +full:- +full:of +full:- +full:4
1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
16 * - Name
17 - Mode
18 - Notes
19 * - ``enable_roce``
20 - runtime
21 - mutually exclusive with ``enable_iwarp``
22 * - ``enable_iwarp``
23 - runtime
24 - mutually exclusive with ``enable_roce``
25 * - ``tx_scheduling_layers``
26 - permanent
27 - The ice hardware uses hierarchical scheduling for Tx with a fixed
28 number of layers in the scheduling tree. Each of them are decision
30 the queues. This way of configuring the Tx scheduler allows features
31 like DCB or devlink-rate (documented below) to configure how much
32 bandwidth is given to any given queue or group of queues, enabling
33 fine-grained control because scheduling parameters can be configured
34 at any given layer of the tree.
36 The default 9-layer tree topology was deemed best for most workloads,
37 as it gives an optimal ratio of performance to configurability. However,
38 for some specific cases, this 9-layer topology might not be desired.
40 of 8. Because the maximum radix is limited to 8 in 9-layer topology,
55 To address this need, you can switch to a 5-layer topology, which
58 to the same parent in the tree. The obvious drawback of this solution
59 is a lower configuration depth of the tree.
62 to change the transmit scheduler topology. To use 5-layer topology,
63 use a value of 5. For example:
66 Use a value of 9 to set it back to the default value.
72 .. list-table:: Driver specific parameters implemented
75 * - Name
76 - Mode
77 - Description
78 * - ``local_forwarding``
79 - runtime
80 - Controls loopback behavior by tuning scheduler bandwidth.
81 It impacts all kinds of functions: physical, virtual and
85 ``enabled`` - loopback traffic is allowed on port
87 ``disabled`` - loopback traffic is not allowed on this port
89 ``prioritized`` - loopback traffic is prioritized on this port
91 Default value of ``local_forwarding`` parameter is ``enabled``.
93 one port capacity at cost of the another. User needs to disable
94 local forwarding on one of the ports in order have increased capacity
102 .. list-table:: devlink info versions implemented
105 * - Name
106 - Type
107 - Example
108 - Description
109 * - ``board.id``
110 - fixed
111 - K65390-000
112 - The Product Board Assembly (PBA) identifier of the board.
113 * - ``cgu.id``
114 - fixed
115 - 36
116 - The Clock Generation Unit (CGU) hardware revision identifier.
117 * - ``fw.mgmt``
118 - running
119 - 2.1.7
120 - 3-digit version number of the management firmware running on the
121 Embedded Management Processor of the device. It controls the PHY,
124 * - ``fw.mgmt.api``
125 - running
126 - 1.5.1
127 - 3-digit version number (major.minor.patch) of the API exported over
129 identify what commands are supported. Historical versions of the
130 kernel only displayed a 2-digit version number (major.minor).
131 * - ``fw.mgmt.build``
132 - running
133 - 0x305d955f
134 - Unique identifier of the source for the management firmware.
135 * - ``fw.undi``
136 - running
137 - 1.2581.0
138 - Version of the Option ROM containing the UEFI driver. The version is
142 non-breaking changes and reset to 1 when the major version is
145 * - ``fw.psid.api``
146 - running
147 - 0.80
148 - Version defining the format of the flash contents.
149 * - ``fw.bundle_id``
150 - running
151 - 0x80002ec0
152 - Unique identifier of the firmware image file that was loaded onto
153 the device. Also referred to as the EETRACK identifier of the NVM.
154 * - ``fw.app.name``
155 - running
156 - ICE OS Default Package
157 - The name of the DDP package that is active in the device. The DDP
159 variation of the DDP package has a unique name.
160 * - ``fw.app``
161 - running
162 - 1.3.1.0
163 - The version of the DDP package that is active in the device. Note
166 * - ``fw.app.bundle_id``
167 - running
168 - 0xc0000001
169 - Unique identifier for the DDP package loaded in the device. Also
172 * - ``fw.netlist``
173 - running
174 - 1.1.2000-6.7.0
175 - The version of the netlist module. This module defines the device's
177 management firmware as part of managing link and device
179 * - ``fw.netlist.build``
180 - running
181 - 0xee16ced7
182 - The first 4 bytes of the hash of the netlist module contents.
183 * - ``fw.cgu``
184 - running
185 - 8032.16973825.6021
186 - The version of Clock Generation Unit (CGU). Format:
193 ``devlink-flash`` interface. It supports updating the device flash using a
197 .. list-table:: List of supported overwrite modes
200 * - Bits
201 - Behavior
202 * - ``DEVLINK_FLASH_OVERWRITE_SETTINGS``
203 - Do not preserve settings stored in the flash components being
205 determines the number of physical functions the device will
207 * - ``DEVLINK_FLASH_OVERWRITE_SETTINGS`` and ``DEVLINK_FLASH_OVERWRITE_IDENTIFIERS``
208 - Do not preserve either settings or identifiers. Overwrite everything
242 a predefined set of available port split options for the whole device.
246 The following command will select the port split option with 4 ports:
250 $ devlink port split pci/0000:16:00.0/0 count 4
252 The list of all available port options will be printed to dynamic debug after
258 ice 0000:16:00.0: Status Split Quad 0 Quad 1
260 ice 0000:16:00.0: Active 2 100 - - - 100 - - -
261 ice 0000:16:00.0: 2 50 - 50 - - - - -
262 ice 0000:16:00.0: Pending 4 25 25 25 25 - - - -
263 ice 0000:16:00.0: 4 25 25 - - 25 25 - -
265 ice 0000:16:00.0: 1 100 - - - - - - -
271 ``devlink port unsplit`` will select the option with a split count of 1. If
272 there is no FW option available with split count 1, you will receive an error.
280 .. list-table:: regions implemented
283 * - Name
284 - Description
285 * - ``nvm-flash``
286 - The contents of the entire flash chip, sometimes referred to as
288 * - ``shadow-ram``
289 - The contents of the Shadow RAM, which is loaded from the beginning
290 of the flash. Although the contents are primarily from the flash,
293 * - ``device-caps``
294 - The contents of the device firmware's capabilities buffer. Useful to
295 determine the current state and configuration of the device.
297 Both the ``nvm-flash`` and ``shadow-ram`` regions can be accessed without a
298 snapshot. The ``device-caps`` region requires a snapshot as the contents are
301 Users can request an immediate capture of a snapshot for all three regions
307 pci/0000:01:00.0/nvm-flash: size 10485760 snapshot [] max 1
308 pci/0000:01:00.0/device-caps: size 4096 snapshot [] max 10
310 $ devlink region new pci/0000:01:00.0/nvm-flash snapshot 1
311 $ devlink region dump pci/0000:01:00.0/nvm-flash snapshot 1
313 $ devlink region dump pci/0000:01:00.0/nvm-flash snapshot 1
319 $ devlink region read pci/0000:01:00.0/nvm-flash snapshot 1 address 0 length 16
322 $ devlink region delete pci/0000:01:00.0/nvm-flash snapshot 1
324 $ devlink region new pci/0000:01:00.0/device-caps snapshot 1
325 $ devlink region dump pci/0000:01:00.0/device-caps snapshot 1
361 $ devlink region delete pci/0000:01:00.0/device-caps snapshot 1
366 The ``ice`` driver implements devlink-rate API. It allows for offload of
375 for example creation of the new traffic class. The driver will prevent DCB
377 devlink-rate API. To configure those features a driver reload is necessary.
384 It's required because devlink-rate requires devlink-port objects to be
388 hierarchy the moment VF's are created. Root of the tree is always
392 .. list-table:: Attributes supported
395 * - Name
396 - Description
397 * - ``tx_max``
398 - maximum bandwidth to be consumed by the tree Node. Rate Limit is
399 an absolute number specifying a maximum amount of bytes a Node may
400 consume during the course of one second. Rate limit guarantees
404 * - ``tx_share``
405 - minimum bandwidth allocated to a tree node when it is not blocked.
409 * - ``tx_priority``
410 - allows for usage of strict priority arbiter among siblings. This
413 Range 0-7. Nodes with priority 7 have the highest priority and are
416 * - ``tx_weight``
417 - allows for usage of Weighted Fair Queuing arbitration scheme among
419 the strict priority. Range 1-200. Only relative values matter for
429 $ devlink dev eswitch set pci/0000:4b:00.0 mode switchdev
435 pci/0000:4b:00.0/node_25: type node parent node_24
436 pci/0000:4b:00.0/node_24: type node parent node_0
437 pci/0000:4b:00.0/node_32: type node parent node_31
438 pci/0000:4b:00.0/node_31: type node parent node_30
439 pci/0000:4b:00.0/node_30: type node parent node_16
440 pci/0000:4b:00.0/node_19: type node parent node_18
441 pci/0000:4b:00.0/node_18: type node parent node_17
442 pci/0000:4b:00.0/node_17: type node parent node_16
443 pci/0000:4b:00.0/node_14: type node parent node_5
444 pci/0000:4b:00.0/node_5: type node parent node_3
445 pci/0000:4b:00.0/node_13: type node parent node_4
446 pci/0000:4b:00.0/node_12: type node parent node_4
447 pci/0000:4b:00.0/node_11: type node parent node_4
448 pci/0000:4b:00.0/node_10: type node parent node_4
449 pci/0000:4b:00.0/node_9: type node parent node_4
450 pci/0000:4b:00.0/node_8: type node parent node_4
451 pci/0000:4b:00.0/node_7: type node parent node_4
452 pci/0000:4b:00.0/node_6: type node parent node_4
453 pci/0000:4b:00.0/node_4: type node parent node_3
454 pci/0000:4b:00.0/node_3: type node parent node_16
455 pci/0000:4b:00.0/node_16: type node parent node_15
456 pci/0000:4b:00.0/node_15: type node parent node_0
457 pci/0000:4b:00.0/node_2: type node parent node_1
458 pci/0000:4b:00.0/node_1: type node parent node_0
459 pci/0000:4b:00.0/node_0: type node
460 pci/0000:4b:00.0/1: type leaf parent node_25
461 pci/0000:4b:00.0/2: type leaf parent node_25
464 $ devlink port function rate add pci/0000:4b:00.0/node_custom parent node_0
467 $ devlink port function rate add pci/0000:4b:00.0/node_custom_1 parent node_custom
470 $ devlink port function rate set pci/0000:4b:00.0/2 parent node_custom_1
473 $ devlink port function rate set pci/0000:4b:00.0/2 tx_weight 5
476 $ devlink port function rate set pci/0000:4b:00.0/2 tx_share 500Mbps