Lines Matching full:and

20 resources from the network, crypto and other functional blocks into
21 PCI-compatible physical and virtual functions. Each functional block
23 RVU supports multiple PCIe SRIOV physical functions (PFs) and virtual
25 and has privileges to provision RVU functional block's LFs to each of the
39    Used for both networking and non networking usecases
51  - Also assigns MSIX vectors to each of PF and VFs.
57 Linux kernel will have multiple drivers registering to different PF and VFs
64 supports resource provisioning and configuration of functional blocks.
66 funcionality is achieved via configuration requests from PFs and VFs.
69 receiving requests AF does resource provisioning and other HW configuration.
70 AF is always attached to host kernel, but PFs and their VFs may be used by host
78  - Retrieve PHY EEPROM and stats.
84  - Attach NIX and NPA block LFs to RVU PF/VF which provide buffer pools, RQs, SQs
88  - NPC parser profile config, basically how to parse pkt and what info to extract.
90  - Manage NPC MCAM entries, upon request can frame and install requested packet forwarding rules.
93  - VLAN stripping, capture and insertion config.
94  - SSO and TIM blocks config which provide packet scheduling support.
96    NPA pools, NIX RQ, SQ and CQs, various stats etc which helps in debugging issues.
97  - And many more.
102 This RVU PF handles IO, is mapped to a physical ethernet link and this
105 links this driver talks to AF and AF gets that info from firmware and responds
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
127  - RVU PF0 ie admin function creates these VFs and maps them to loopback block's channels.
129    VF0 will be received by VF1 and viceversa.
135 Except for the IO channels or links used for packet reception and transmission there is
147 3. Then submitted to NPC block for parsing and then MCAM lookup to get the destination RVU device.
150 6. Packet is DMA'ed and driver is notified.
155 1. Driver prepares a send descriptor and submits to SQ for transmission.