| /f-stack/dpdk/doc/guides/howto/ |
| H A D | vfd.rst | 8 a VF (SR-IOV Virtual Function) without direct access to the PF (SR-IOV
10 the scenario of DPDK PF with a DPDK VF. If the PF port is driven by the Linux
31 using the PF port, which can be the same as the VF application). The PF
32 application will configure the feature for the VF. Obviously, the PF
45 control should be limited to the PF.
68 the PF port to ``igb_uio``, then create the VFs based on the DPDK PF host.
74 #. Bind the PF port to ``igb_uio``, for example::
84 #. Run a DPDK application on the PF in the host::
107 Run a testpmd runtime command on the PF to set TX loopback::
134 Run a testpmd runtime command on the PF to enable/disable the MAC
[all …]
|
| H A D | lm_bond_virtio_sriov.rst | 24 backend of the Virtio device and the Physical Function (PF) device.
37 The host is running the Kernel PF driver (ixgbe or i40e).
97 The ``mac_addr`` command only works with kernel PF for Niantic
185 The ``mac_addr`` command only works with the kernel PF for Niantic.
341 The ``mac_addr`` command only works with the Kernel PF for Niantic.
442 # for the Tap device and the PF device.
443 # This enables traffic to go from the PF to the Tap to the Virtio PMD in the VM.
545 # for the Tap device and the PF device.
546 # This enables traffic to go from the PF to the Tap to the Virtio PMD in the VM.
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | nfp.rst | 18 function (PF) and the virtual functions (VFs).
34 vanilla kernel since kernel version 4.5, and support for the PF
62 Using the PF
67 the PMD with the VFs if the PF is being used by DPDK, that is, with the NFP PF
69 have a PMD able to work with the PF and VFs at the same time and with the PF
74 stopping a PF port. Since DPDK 18.05 the firmware upload happens when
79 PF looks for a firmware file in this order:
106 PF multiport support
114 However, with the NFP PF multiport there is just one PF PCI device. Supporting
135 PF multiprocess support
[all …]
|
| H A D | liquidio.rst | 8 Cavium LiquidIO® II server adapter VFs. PF management and VF creation can be
51 #. Bring up the PF ports:
58 #. Change PF MTU if required:
68 of the parent PF.
79 ip link set <PF iface> vf <VF id> mac <macaddr>
140 One VF per PF can be marked as trusted for promiscuous mode.
144 ip link set dev <PF iface> vf <VF id> trust on
153 VF MTU is limited by PF MTU. Raise PF value before configuring VF for larger packet size.
|
| H A D | ixgbe.rst | 98 PF's. If set, VF will not only check the PF's physical link status
101 trigger PF's mailbox interrupt generation. If unset, the application
102 can get the VF's link status quickly by just reading the PF's link
166 DPDK PF doesn't support MDD, but kernel PF does. We may hit problem in this
167 scenario kernel PF + DPDK VF. If user enables MDD in kernel PF, DPDK VF will
174 When using kernel PF + DPDK VF on x550, please make sure to use a kernel
175 PF driver that disables MDD or can disable MDD.
212 So when the user sets different MTUs on PF and VF ports in one physical port,
213 the real MTU for all these PF and VF ports is the largest value set.
223 There is no RTE API to add a VF's MAC address from the PF. On ixgbe, the
[all …]
|
| H A D | ipn3ke.rst | 55 - ``I40e PF name list``
57 Users need to bind FPGA LineSidePort to FVL PF. So I40e PF name list should be involved in
76 To start ``testpmd``, and add I40e PF to FPGA network port:
87 To start ``testpmd``, and add I40e PF to FPGA network port, enable FPGA HQoS and Flow Acceleration:
|
| H A D | qede.rst | 37 - SR-IOV PF and VF
96 - SR-IOV requires Linux PF driver version **8.20.x.x** or higher.
97 If the required PF driver is not available then download it from
99 For downloading PF driver, select adapter category, model and Linux distro.
193 …ce and Linux native kernel driver (qede) will function as SR-IOV PF driver. Requires PF driver to …
225 #. Bring up the PF ports:
235 of the parent PF.
248 ip link set <PF iface> vf <VF id> mac <macaddr>
|
| H A D | i40e.rst | 166 Number of queues reserved for PF.
210 representors must be specified on the creation of the PF.
260 #. Bring up the PF ports:
269 of the parent PF.
284 ip link set <PF netdev id> vf <VF id> mac <macaddr>
462 VFs created by this PF device.
539 configuration for RSS in the PF, so that different traffic classes or
621 Currently the VF's RX descriptor mode is decided by PF. There's no PF-VF
631 byte, as the PF driver.
633 The same rule for DPDK PF + DPDK VF. The PF and VF should use the same RX
[all …]
|
| H A D | intel_vf.rst | 75 interface between IAVF driver and a compliant PF driver is specified.
132 (in the case of the Linux Kernel-based Virtual Machine [KVM]) or by DPDK PMD PF driver.
144 * Using the DPDK PMD PF i40e driver:
182 (in the case of the Linux Kernel-based Virtual Machine [KVM]) or by DPDK PMD PF driver.
194 * Using the DPDK PMD PF ixgbe driver:
207 * Using the DPDK PMD PF ixgbe driver to enable VF RSS:
280 * Using DPDK PMD PF igb driver:
565 DPDK SR-IOV PMD PF/VF Driver Usage Model
588 SR-IOV (PF/VF) Approach for Inter-VM Communication
595 In this case, the DPDK PMD PF driver provides host forwarding between such VMs.
[all …]
|
| H A D | hns3.rst | 58 igb_uio and then driven by DPDK driver when PF is driven by
59 kernel mode hns3 ethdev driver, VF is not supported when PF
|
| H A D | bnxt.rst | 44 The BNXT PMD can run on PF or VF.
50 having global data in common to share with the PF and other VFs.
92 In the simplest case of flow bifurcation, a PF driver configures a NIC to
94 while the rest of the traffic is forwarded to a PF.
95 Note that the broadcast packets will be forwarded to both PF and VF.
132 Running on PF
138 can be more than one PF associated per port.
141 PFs as a master PF.
542 run on PF and vector mode needs to be disabled.
742 * rep_is_pf - true to indicate PF representor
[all …]
|
| H A D | bnx2x.rst | 35 - SR-IOV PF
156 #. Bring up the PF ports:
166 of the parent PF.
177 ip link set <PF iface> vf <VF id> mac <macaddr>
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_2_0.rst | 13 * Basic Rx/Tx functions for PF/VF
15 * Interrupt handling support for PF/VF
17 * Per queue start/stop functions for PF/VF
19 * Support Mailbox handling between PF/VF and PF/Switch Manager
21 * Receive Side Scaling (RSS) for PF/VF
23 * Scatter receive function for PF/VF
25 * Reta update/query for PF/VF
27 * VLAN filter set for PF
29 * Link status query for PF/VF
90 - 128/512 entries of 40GbE PF
|
| H A D | release_16_04.rst | 84 Please note if you want to use this promiscuous mode, you need both PF and VF
85 driver to support it. The reason is that this VF feature is configured in the PF.
86 If you use kernel PF driver and the dpdk VF driver, make sure the kernel PF driver supports
87 VF multicast promiscuous mode. If you use dpdk PF and dpdk VF ensure the PF
94 This feature is for the VF, but the settings are on the PF. It means
97 on the PF. Theoretically, the E-tag packets can be forwarded to any pool/queue
175 * **Added PF reset event reporting in i40e VF driver.**
311 driver is loaded while the PF interface is down.
312 The solution is to only set it when we get an ACK from the PF.
334 It generates a MAC address for each VFs during PF host initialization,
[all …]
|
| H A D | release_2_2.rst | 81 * **Added igb TSO support for both PF and VF.**
106 * Increased PF reset max loop limit
114 * **Added DCB support to i40e PF driver.**
128 * **Added fm10k TSO support for both PF and VF.**
339 * **igb: Fixed VF start with PF stopped.**
341 VF needs the PF interrupt support initialized even if not started.
343 * **igb: Fixed VF MAC address when using with DPDK PF.**
345 Assign a random MAC address in VF when not assigned by PF.
359 * **ixgbe: Fixed VF start with PF stopped.**
361 VF needs the PF interrupt support initialized even if not started.
[all …]
|
| /f-stack/dpdk/doc/guides/bbdevs/ |
| H A D | fpga_5gnr_fec.rst | 18 - 8 VFs per PF (physical device)
79 Bind PF UIO driver(s)
146 Configure the VFs through PF
171 - ``pf_mode_en``: identifies whether only PF is to be used, or the VFs. PF and
173 Set to 1 for PF mode enabled.
174 If PF mode is enabled all queues available in the device are assigned
175 exclusively to PF and 0 queues given to VFs.
219 /* setup FPGA PF */
222 "Failed to configure 4G FPGA PF for bbdev %s",
244 "-i", "--init-device" : Initialise PF device with default values.
[all …]
|
| H A D | fpga_lte_fec.rst | 18 - 8 VFs per PF (physical device)
78 Bind PF UIO driver(s)
145 Configure the VFs through PF
170 - ``pf_mode_en``: identifies whether only PF is to be used, or the VFs. PF and
172 Set to 1 for PF mode enabled.
173 If PF mode is enabled all queues available in the device are assigned
174 exclusively to PF and 0 queues given to VFs.
218 /* setup FPGA PF */
221 "Failed to configure 4G FPGA PF for bbdev %s",
243 "-i", "--init-device" : Initialise PF device with default values.
[all …]
|
| H A D | acc100.rst | 20 - 16 VFs per PF (physical device)
93 Bind PF UIO driver(s)
96 Install the DPDK igb_uio driver, bind it with the PF PCI device ID and use
97 ``lspci`` to confirm the PF device is under use by ``igb_uio`` DPDK UIO driver.
99 The igb_uio driver may be bound to the PF PCI device using one of two methods:
113 2. Another way to bind PF with DPDK UIO driver is by using the ``dpdk-devbind.py`` tool
123 In a similar way the ACC100 5G/4G FEC PF may be bound with vfio-pci as any PCIe device.
129 Now, it should be visible in the printouts that PCI PF is under igb_uio control
160 Configure the VFs through PF
192 "-i", "--init-device" : Initialise PF device with default values.
[all …]
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | switch_representation.rst | 304 - **A**: PF device.
320 PF:
323 - **F to A**: PF MAC as destination.
472 | PF | | VF 1 | : | PF | | VF 1 |
535 | PF | | VF 1 rep. | | VF 1 |
596 PF Pattern Item
608 PF Action
613 Same restrictions as `PF pattern item`_.
769 From outside to PF and VFs
780 From PF to outside and VFs
[all …]
|
| /f-stack/dpdk/doc/guides/cryptodevs/ |
| H A D | nitrox.rst | 42 Nitrox crypto PMD depend on Nitrox kernel PF driver being installed on the
43 platform. Nitrox PF driver is required to create VF devices which will
46 Nitrox kernel PF driver is available as part of CNN55XX-Driver SDK. The SDK
|
| H A D | octeontx.rst | 74 OCTEON TX crypto PF driver needs microcode to be available at `/lib/firmware/` directory.
83 `sriov_numvfs`, for the corresponding PF driver.
90 by using dpdk-devbind.py script. The OCTEON TX crypto PF device need to be
91 identified and the corresponding device number can be used to tune various PF
|
| H A D | octeontx2.rst | 79 crypto PF driver in linux. This driver is included in the OCTEON TX SDK.
84 List the CPT PF devices available on your OCTEON TX2 platform:
90 ``a0fd`` is the CPT PF device id. You should see output similar to:
96 Set ``sriov_numvfs`` on the CPT PF device, to create a VF:
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | sun8i-r16-nintendo-nes-classic.dts | 24 * UART0 is available on two ports: PB and PF, both are accessible.
25 * PF can also be used for the SD card so PB is preferred.
|
| /f-stack/dpdk/doc/guides/platform/ |
| H A D | octeontx.rst | 36 1. **OCTEON TX Linux kernel PF driver for Network acceleration HW blocks**
38 The OCTEON TX Linux kernel drivers (includes the required PF driver for the
44 The PF driver and the required microcode for the crypto offload block will be
74 OCTEON TX SDK 6.2.0 patch 3. In this, the PF drivers for all hardware
|
| H A D | octeontx2.rst | 74 privileges to provision RVU functional block's LFs to each of the PF/VF.
76 PF/VFs communicates with AF via a shared memory region (mailbox).Upon receiving
77 requests from PF/VF, AF does resource provisioning and other HW configuration.
79 AF is always attached to host, but PF/VFs may be used by host kernel itself,
120 single PCIe SRIOV physical function(PF) and multiple virtual functions(VF's). Users
121 can bind PF or VF to use SDP interface and it will be enumerated as ethdev ports.
201 # Enable if netdev PF driver required
206 # Enable if OCTEONTX2 DMA PF driver required
|