Lines Matching +full:00 +full:a
9 ``devlink-port`` is a port that exists on the device. It has a logically
10 separate ingress/egress point of the device. A devlink port can be any one
11 of many flavours. A devlink port flavour along with port attributes
12 describe what a port represents.
14 A device driver that intends to publish a devlink port sets the
28 - This indicates a DSA interconnect port.
30 - This indicates a CPU port applicable only to DSA.
32 - This indicates an eswitch port representing a port of PCI
35 - This indicates an eswitch port representing a port of PCI
38 - This indicates an eswitch port representing a port of PCI
41 - This indicates a virtual port for the PCI virtual function.
43 Devlink port can have a different type based on the link layer described below.
51 - Driver should set this port type when a link layer of the port is
54 - Driver should set this port type when a link layer of the port is
62 In most cases a PCI device has only one controller. A controller consists of
63 potentially multiple physical, virtual functions and subfunctions. A function
67 A PCI device connected to multiple CPUs or multiple PCI root complexes or a
68 SmartNIC, however, may have multiple controllers. For a device with multiple
69 controllers, each controller is distinguished by a unique controller number.
72 An example view of a system with two controllers::
115 before a bus specific device for the function is created. However, when
121 A user may set the hardware address of the function using
123 this means a MAC address.
153 hw_addr 00:00:00:00:00:00
157 $ devlink port function set pci/0000:06:00.0/2 hw_addr 00:11:22:33:44:55
162 hw_addr 00:11:22:33:44:55
169 hw_addr 00:00:00:00:00:00
173 $ devlink port function set pci/0000:06:00.0/32768 hw_addr 00:00:00:00:88:88
178 hw_addr 00:00:00:00:88:88
186 When user disables RoCE capability for a VF/SF, user application cannot send or
198 hw_addr 00:00:00:00:00:00 roce enable
207 hw_addr 00:00:00:00:00:00 roce disable
211 Live migration is the process of transferring a live virtual machine
218 When user enables migratable capability for a VF, and the HV binds the VF to VFIO driver
219 with migration support, the user can migrate the VM with this VF from one HV to a
223 be migrated. Thus migratable cap can impose limitations on a VF so let the user decide.
231 hw_addr 00:00:00:00:00:00 migratable disable
240 hw_addr 00:00:00:00:00:00 migratable enable
254 When user enables IPsec crypto capability for a VF, user application can offload
257 When IPsec crypto capability is disabled (default) for a VF, the XFRM state is
265 hw_addr 00:00:00:00:00:00 ipsec_crypto disabled
274 hw_addr 00:00:00:00:00:00 ipsec_crypto enabled
278 When user enables IPsec packet capability for a VF, user application can offload
282 When IPsec packet capability is disabled (default) for a VF, the XFRM state and
290 hw_addr 00:00:00:00:00:00 ipsec_packet disabled
299 hw_addr 00:00:00:00:00:00 ipsec_packet enabled
303 When user sets maximum number of IO event queues for a SF or
304 a VF, such function driver is limited to consume only enforced
320 hw_addr 00:00:00:00:00:00 ipsec_packet disabled max_io_eqs 10
329 hw_addr 00:00:00:00:00:00 ipsec_packet disabled max_io_eqs 32
334 Subfunction is a lightweight function that has a parent PCI function on which
336 SRIOV VFs, a subfunction doesn't require its own PCI virtual function.
337 A subfunction communicates with the hardware through the parent PCI function.
339 To use a subfunction, 3 steps setup sequence is followed:
341 1) create - create a subfunction;
350 A subfunction is created using a devlink port interface. A user adds the
351 subfunction by adding a devlink port of subfunction flavour. The devlink
353 it to create a subfunction devlink port. Driver then instantiates the
359 A subfunction devlink port is created but it is not active yet. That means the
361 but the subfunction device itself is not created. A user might use e-switch port
362 representor to do settings, putting it into bridge, adding TC rules, etc. A user
368 Once a subfunction is configured, user must activate it to use it. Upon
371 A subfunction device is created on the :ref:`Documentation/driver-api/auxiliary_bus.rst <auxiliary_…
372 At this point a matching subfunction driver binds to the subfunction's auxiliary device.
377 Devlink provides API to manage tx rates of single devlink port or a group.
381 Represents a single devlink port; created/destroyed by the driver. Since leaf
386 Represents a group of rate objects (leafs and/or nodes); created/deleted by
396 that parts of the parent group, if it is a part of the same group.
411 strict priority. As a node is configured with a higher rate it gets more
412 BW relative to its siblings. Values are relative like a percentage
419 ``tx_share`` is a total bandwidth distributed among children.
422 nodes with the same priority form a WFQ subgroup in the sibling group
427 #. Choose a node, or group of nodes with the highest priority that stays
428 within the BW limit and are not blocked. Use ``tx_priority`` as a
432 that subgroup. Use ``tx_weight`` as a parameter for this arbitration.
453 - A physical PCI device having one or more PCI buses consists of one or
456 - A controller consists of potentially multiple physical functions,
459 - An object to manage the function of a port.
461 - A lightweight function that has parent PCI function on which it is
464 - A bus device of the subfunction, usually on a auxiliary bus.
466 - A device driver for the subfunction auxiliary device.
468 - A PCI physical function that supports subfunction management.
470 - A device driver for PCI physical function that supports
473 - A device driver for PCI physical function that hosts subfunction