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