Lines Matching +full:max +full:- +full:virtual +full:- +full:functions
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
31 like DCB or devlink-rate (documented below) to configure how much
33 fine-grained control because scheduling parameters can be configured
36 The default 9-layer tree topology was deemed best for most workloads,
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
62 to change the transmit scheduler topology. To use 5-layer topology,
72 * - ``msix_vec_per_pf_max``
73 - driverinit
74 - Set the max MSI-X that can be used by the PF, rest can be utilized for
77 * - ``msix_vec_per_pf_min``
78 - driverinit
79 - Set the min MSI-X that will be used by the PF. This value inform how many
80 MSI-X will be allocated statically. The range is from 2 to value set
83 .. list-table:: Driver specific parameters implemented
86 * - Name
87 - Mode
88 - Description
89 * - ``local_forwarding``
90 - runtime
91 - Controls loopback behavior by tuning scheduler bandwidth.
92 It impacts all kinds of functions: physical, virtual and
96 ``enabled`` - loopback traffic is allowed on port
98 ``disabled`` - loopback traffic is not allowed on this port
100 ``prioritized`` - loopback traffic is prioritized on this port
113 .. list-table:: devlink info versions implemented
116 * - Name
117 - Type
118 - Example
119 - Description
120 * - ``board.id``
121 - fixed
122 - K65390-000
123 - The Product Board Assembly (PBA) identifier of the board.
124 * - ``cgu.id``
125 - fixed
126 - 36
127 - The Clock Generation Unit (CGU) hardware revision identifier.
128 * - ``fw.mgmt``
129 - running
130 - 2.1.7
131 - 3-digit version number of the management firmware running on the
135 * - ``fw.mgmt.api``
136 - running
137 - 1.5.1
138 - 3-digit version number (major.minor.patch) of the API exported over
141 kernel only displayed a 2-digit version number (major.minor).
142 * - ``fw.mgmt.build``
143 - running
144 - 0x305d955f
145 - Unique identifier of the source for the management firmware.
146 * - ``fw.undi``
147 - running
148 - 1.2581.0
149 - Version of the Option ROM containing the UEFI driver. The version is
153 non-breaking changes and reset to 1 when the major version is
156 * - ``fw.psid.api``
157 - running
158 - 0.80
159 - Version defining the format of the flash contents.
160 * - ``fw.bundle_id``
161 - running
162 - 0x80002ec0
163 - Unique identifier of the firmware image file that was loaded onto
165 * - ``fw.app.name``
166 - running
167 - ICE OS Default Package
168 - The name of the DDP package that is active in the device. The DDP
171 * - ``fw.app``
172 - running
173 - 1.3.1.0
174 - The version of the DDP package that is active in the device. Note
177 * - ``fw.app.bundle_id``
178 - running
179 - 0xc0000001
180 - Unique identifier for the DDP package loaded in the device. Also
183 * - ``fw.netlist``
184 - running
185 - 1.1.2000-6.7.0
186 - The version of the netlist module. This module defines the device's
190 * - ``fw.netlist.build``
191 - running
192 - 0xee16ced7
193 - The first 4 bytes of the hash of the netlist module contents.
194 * - ``fw.cgu``
195 - running
196 - 8032.16973825.6021
197 - The version of Clock Generation Unit (CGU). Format:
204 ``devlink-flash`` interface. It supports updating the device flash using a
208 .. list-table:: List of supported overwrite modes
211 * - Bits
212 - Behavior
213 * - ``DEVLINK_FLASH_OVERWRITE_SETTINGS``
214 - Do not preserve settings stored in the flash components being
216 determines the number of physical functions the device will
218 * - ``DEVLINK_FLASH_OVERWRITE_SETTINGS`` and ``DEVLINK_FLASH_OVERWRITE_IDENTIFIERS``
219 - Do not preserve either settings or identifiers. Overwrite everything
268 ice 0000:16:00.0: Available port split options and max port speeds (Gbps):
271 ice 0000:16:00.0: Active 2 100 - - - 100 - - -
272 ice 0000:16:00.0: 2 50 - 50 - - - - -
273 ice 0000:16:00.0: Pending 4 25 25 25 25 - - - -
274 ice 0000:16:00.0: 4 25 25 - - 25 25 - -
276 ice 0000:16:00.0: 1 100 - - - - - - -
291 .. list-table:: regions implemented
294 * - Name
295 - Description
296 * - ``nvm-flash``
297 - The contents of the entire flash chip, sometimes referred to as
299 * - ``shadow-ram``
300 - The contents of the Shadow RAM, which is loaded from the beginning
304 * - ``device-caps``
305 - The contents of the device firmware's capabilities buffer. Useful to
308 Both the ``nvm-flash`` and ``shadow-ram`` regions can be accessed without a
309 snapshot. The ``device-caps`` region requires a snapshot as the contents are
318 pci/0000:01:00.0/nvm-flash: size 10485760 snapshot [] max 1
319 pci/0000:01:00.0/device-caps: size 4096 snapshot [] max 10
321 $ devlink region new pci/0000:01:00.0/nvm-flash snapshot 1
322 $ devlink region dump pci/0000:01:00.0/nvm-flash snapshot 1
324 $ devlink region dump pci/0000:01:00.0/nvm-flash snapshot 1
330 $ devlink region read pci/0000:01:00.0/nvm-flash snapshot 1 address 0 length 16
333 $ devlink region delete pci/0000:01:00.0/nvm-flash snapshot 1
335 $ devlink region new pci/0000:01:00.0/device-caps snapshot 1
336 $ devlink region dump pci/0000:01:00.0/device-caps snapshot 1
372 $ devlink region delete pci/0000:01:00.0/device-caps snapshot 1
377 The ``ice`` driver implements devlink-rate API. It allows for offload of
378 the Hierarchical QoS to the hardware. It enables user to group Virtual
379 Functions in a tree structure and assign supported parameters: tx_share,
388 devlink-rate API. To configure those features a driver reload is necessary.
395 It's required because devlink-rate requires devlink-port objects to be
403 .. list-table:: Attributes supported
406 * - Name
407 - Description
408 * - ``tx_max``
409 - maximum bandwidth to be consumed by the tree Node. Rate Limit is
415 * - ``tx_share``
416 - minimum bandwidth allocated to a tree node when it is not blocked.
420 * - ``tx_priority``
421 - allows for usage of strict priority arbiter among siblings. This
424 Range 0-7. Nodes with priority 7 have the highest priority and are
427 * - ``tx_weight``
428 - allows for usage of Weighted Fair Queuing arbitration scheme among
430 the strict priority. Range 1-200. Only relative values matter for