Lines Matching refs:PF
28 PF/VF.
44 - A PF/VF with NIX-LF & NPA-LF resources works as a pure network device
45 - A PF/VF with CPT-LF resource works as a pure crypto offload device.
51 - Number of VFs per PF are either static or configurable at compile time.
53 - Also assigns MSIX vectors to each of PF and VFs.
59 Linux kernel will have multiple drivers registering to different PF and VFs
70 PF/VFs communicates with AF via a shared memory region (mailbox). Upon
85 - Map a physical link to a RVU PF to which a netdev is registered.
86 - Attach NIX and NPA block LFs to RVU PF/VF which provide buffer pools, RQs, SQs
104 This RVU PF handles IO, is mapped to a physical ethernet link and this
117 SR-IOV PF and the VFs which work in pairs using internal HW loopback channels (LBK).
120 - These VFs and their parent PF share a physical link and used for outside communication.
121 - VFs cannot communicate with AF directly, they send mbox message to PF and PF
122 forwards that to AF. AF after processing, responds back to PF and PF forwards
124 - From functionality point of view there is no difference between PF and VF as same type
126 from PF as PF is treated as owner/admin of the link.
172 - Error due to operation of unmapped PF.
236 - Receive packet on an unmapped PF.