Searched refs:VF (Results 1 – 25 of 33) sorted by relevance
12
170 PCI devices, but the BARs in VF config space headers are unusual. For171 a non-VF device, software uses BARs in the config space header to172 discover the BAR sizes and assign addresses for them. For VF devices,173 software uses VF BAR registers in the *PF* SR-IOV Capability to174 discover sizes and assign addresses. The BARs in the VF's config space177 When a VF BAR in the PF SR-IOV Capability is programmed, it sets the178 base address for all the corresponding VF(n) BARs. For example, if the180 1MB VF BAR0, the address in that VF BAR sets the base of an 8MB region.182 is a BAR0 for one of the VFs. Note that even though the VF BAR183 describes an 8MB region, the alignment requirement is for a single VF,[all …]
21 Available for PF and VF in host. VF in guest currently only44 Available for both PF and VF, and take no other effect on SEC.50 Available for both PF and VF, and take no other effect on SEC.56 Available for both PF and VF, and take no other effect on SEC.62 Available for both PF and VF, and take no other effect on SEC.68 Available for both PF and VF, and take no other effect on SEC.75 Available for both PF and VF, and take no other effect on SEC.81 Available for both PF and VF, and take no other effect on SEC.87 Available for both PF and VF, and take no other effect on SEC.93 Available for both PF and VF, and take no other effect on SEC.[all …]
40 Available for PF and VF in host. VF in guest currently only64 Available for both PF and VF, and take no other effect on HPRE.70 Available for both PF and VF, and take no other effect on HPRE.76 Available for both PF and VF, and take no other effect on HPRE.82 Available for both PF and VF, and take no other effect on HPRE.88 Available for both PF and VF, and take no other effect on HPRE.95 Available for both PF and VF, and take no other effect on HPRE.101 Available for both PF and VF, and take no other effect on HPRE.107 Available for both PF and VF, and take no other effect on HPRE.114 Available for both PF and VF, and take no other effect on HPRE.[all …]
33 Available for PF and VF in host. VF in guest currently only57 Available for both PF and VF, and take no other effect on ZIP.63 Available for both PF and VF, and take no other effect on ZIP.69 Available for both PF and VF, and take no other effect on ZIP.75 Available for both PF and VF, and take no other effect on ZIP.81 Available for both PF and VF, and take no other effect on ZIP.88 Available for both PF and VF, and take no other effect on ZIP.94 Available for both PF and VF, and take no other effect on ZIP.100 Available for both PF and VF, and take no other effect on ZIP.107 Available for both PF and VF, and take no other effect on ZIP.[all …]
70 Description: Default VF timeout 250ms. Testing might require 1000ms.
73 packets with VLAN tags, you can disable VLAN tag stripping for the VF. The74 Physical Function (PF) processes requests issued from the VF to enable or75 disable VLAN tag stripping. Note that if the PF has assigned a VLAN to a VF,76 then requests from that VF to set VLAN tag stripping will be ignored.78 To enable/disable VLAN tag stripping for a VF, issue the following command79 from inside the VM in which you are running the VF::89 Adaptive Virtual Function (AVF) allows the virtual function driver, or VF, to106 - 1 Virtual Station Interface (VSI) per VF110 - 1 unicast MAC address reserved per VF111 - 16 MAC address filters for each VF[all …]
70 For example, the following instructions will configure PF eth0 and the first VF78 virtual function (VF). Further, this feature allows you to designate a79 particular VF as trusted, and allows that trusted VF to request selective82 To set a VF as trusted or untrusted, enter the following command in the87 Once the VF is designated as trusted, use the following commands in the VM to88 set the VF to promiscuous mode.94 Where eth2 is a VF interface in the VM98 Where eth2 is a VF interface in the VM101 "off",meaning that promiscuous mode for the VF will be limited. To set the102 promiscuous mode for the VF to true promiscuous and allow the VF to see all[all …]
80 ip link set eth0 vf 0 vlan 100 // set vlan 100 for VF 082 ip link set eth0 vf 0 vlan 200 // set a new vlan 200 for VF 0170 Spoof event(s) detected on VF(n), where n = the VF that attempted to do the176 You can set a MAC address of a Virtual Function (VF), a default VLAN and the
225 ip link set eth0 vf 0 vlan 100 // set VLAN 100 for VF 0227 ip link set eth0 vf 0 vlan 200 // set a new VLAN 200 for VF 0242 Physical Function (PF) and each Virtual Function (VF) is allocated a pool of250 each enabled VF is as follows:399 bits represents the queue number, while the next 8 bits represent which VF.400 Note that 0 is the PF, so the VF identifier is offset by 1. For example::405 that VF.440 a virtual function (VF), jumbo frames must first be enabled in the physical441 function (PF). The VF MTU setting cannot be larger than the PF MTU.501 NOTE: This feature can be disabled for a specific Virtual Function (VF)::[all …]
52 ip link set eth0 vf 0 vlan 100 // set vlan 100 for VF 054 ip link set eth0 vf 0 vlan 200 // set a new vlan 200 for VF 0
21 while the virtual devices are referred to as Virtual Functions (VF).22 Allocation of the VF can be dynamically controlled by the PF via25 turned on, each VF's PCI configuration space can be accessed by its own26 Bus, Device and Function Number (Routing ID). And each VF also has PCI27 Memory Space, which is used to map its register set. VF device driver45 enables per-PF, VF enable/disable values versus the first method,51 The second method is the recommended method for new/future VF devices.56 The VF is treated as hot-plugged PCI devices in the kernel, so they57 should be able to work in the same way as real PCI devices. The VF
71 Virtual Function (VF) device is passed to the guest as a PCI72 device. In this case, both a synthetic (netvsc) and VF device are75 The VF is enslaved by netvsc device. The netvsc driver will transparently76 switch the data path to the VF when it is available and up.81 VF slave device.104 program on the associated VF NIC as well.107 VF NIC automatically. Setting / unsetting XDP program on VF NIC directly
25 direct attached VF by failing over to the paravirtual datapath when the VF36 virtio-net and VF interfaces.76 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode80 with VMs that have direct attached SR-IOV VF devices by automatic failover to81 the paravirtual datapath when the VF is unplugged.
16 This enables paravirtual drivers to use a VF as an accelerated low latency18 failing over to the paravirtual datapath when the VF is unplugged.
26 PF/VF.42 - A PF/VF with NIX-LF & NPA-LF resources works as a pure network device43 - A PF/VF with CPT-LF resource works as a pure crypto offload device.84 - Attach NIX and NPA block LFs to RVU PF/VF which provide buffer pools, RQs, SQs121 the reply to VF.122 - From functionality point of view there is no difference between PF and VF as same type136 no other difference between these VF types. AF driver takes care of IO channel mapping,137 hence same VF driver works for both types of devices.
24 tristate "Intel IFC VF vDPA driver"28 This kernel module can drive Intel IFC VF NIC to offload
264 | PF | | VF |285 through virtual function (VF) devices via PCIe SRIOV. Each VF only contains310 | PCI PF Device | | | PCI VF Device |313 FPGA PCIe device driver is always loaded first once a FPGA PCIe PF or VF device316 * Finishes enumeration on both FPGA PCIe PF and VF device using common322 a port from PF, then it's safe to expose this port through a VF via PCIe SRIOV326 respective AFU's port needs to be assigned to a VF using the following steps:329 reassigned to a VF must first be released through the333 to enable SRIOV and VFs. Each VF owns only one Port with AFU.341 #. The AFU under VF is accessible from applications in VM (using the[all …]
17 tristate "ENETC VF driver"24 virtual function (VF) devices enabled by the ENETC PF driver.
14 #define MDP_COLORFMT_PACK(VIDEO, PLANE, COPLANE, HF, VF, BITS, GROUP, SWAP, ID)\ argument16 ((HF) << 20) | ((VF) << 18) | ((BITS) << 8) | ((GROUP) << 6) |\
21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
235 ifeq ($(VF),1)
92 tristate "Cavium LiquidIO VF support"
387 Enabling QP0 on VFs for selected VF/port. By default, no VFs are392 for the indicated VF/port396 indicated VF/port. 0 = disable, 1 = enable.399 The requested enablement will occur at the next reset of the VF400 (e.g. driver restart on the VM which owns the VF).
124 This selects the HNS3 VF drivers network acceleration engine & its hardware
49 (just like a normal non-NPIV adapter). Using the Virtual Fabric (VF)54 used together with VF so that the port can obtain multiple N_Port_IDs73 vports. However, consideration was given to VF-based vports and it
