Lines Matching full:nic
32 # 7. Some OS Drivers will manage different ports and functions (NIC,
33 # storage, etc.) on different Physical Functions. For example, NIC
46 # 3 application functions (NIC, FCoE, iSCSI) per port *
54 # and "PCI Device Passthrough" -- this is especially true for the NIC
208 # 4 ports, 3 functions (NIC, FCoE and iSCSI), scaling up to 8 "CPU Queue Sets"
217 # NFUNCS = 3 # functions per port (NIC, FCoE, iSCSI)
229 # NVI_NIC = 4 # NIC access to NPORTS
230 # NFLIQ_NIC = 32 # NIC Ingress Queues with Free Lists
231 # NETHCTRL_NIC = 32 # NIC Ethernet Control/TX Queues
232 # NEQ_NIC = 64 # NIC Egress Queues (FL, ETHCTRL/TX)
233 # NMPSTCAM_NIC = 16 # NIC MPS TCAM Entries (NPORTS*4)
234 # NMSIX_NIC = 32 # NIC MSI-X Interrupt Vectors (FLIQ)
236 # NVI_OFLD = 0 # Offload uses NIC function to access ports
240 # NMPSTCAM_OFLD = 0 # Offload MPS TCAM Entries (uses NIC's)
243 # NVI_RDMA = 0 # RDMA uses NIC function to access ports
247 # NMPSTCAM_RDMA = 0 # RDMA MPS TCAM Entries (uses NIC's)
287 # Adding all of the above Unified PF resource needs together: (NIC + OFLD +
316 # For PF0-3 we assign 8 vectors each for NIC Ingress Queues of the associated
353 # only enough resources to support a single port's NIC application functions
354 # on PF0-3. The below assumes that we're only doing NIC with NCPUS "Queue
505 # For Virtual functions, we only allow NIC functionality and we only allow