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