Lines Matching full:nic
47 # 7. Some OS Drivers will manage different ports and functions (NIC,
48 # storage, etc.) on different Physical Functions. For example, NIC
61 # 3 application functions (NIC, FCoE, iSCSI) per port *
70 # true for the NIC application functionality. (Note that there is
72 # Functions so this is in fact solely limited to NIC.)
173 # 4 ports, 3 functions (NIC, FCoE and iSCSI), scaling up to 8 "CPU Queue Sets"
182 # NFUNCS = 3 # functions per port (NIC, FCoE, iSCSI)
194 # NVI_NIC = 4 # NIC access to NPORTS
195 # NFLIQ_NIC = 32 # NIC Ingress Queues with Free Lists
196 # NETHCTRL_NIC = 32 # NIC Ethernet Control/TX Queues
197 # NEQ_NIC = 64 # NIC Egress Queues (FL, ETHCTRL/TX)
198 # NMPSTCAM_NIC = 16 # NIC MPS TCAM Entries (NPORTS*4)
199 # NMSIX_NIC = 32 # NIC MSI-X Interrupt Vectors (FLIQ)
201 # NVI_OFLD = 0 # Offload uses NIC function to access ports
205 # NMPSTCAM_OFLD = 0 # Offload MPS TCAM Entries (uses NIC's)
208 # NVI_RDMA = 0 # RDMA uses NIC function to access ports
212 # NMPSTCAM_RDMA = 0 # RDMA MPS TCAM Entries (uses NIC's)
252 # Adding all of the above Unified PF resource needs together: (NIC + OFLD +
281 # For PF0-3 we assign 8 vectors each for NIC Ingress Queues of the associated
319 # only enough resources to support a single port's NIC application functions
320 # on PF0-3. The below assumes that we're only doing NIC with NCPUS "Queue
390 # For Virtual functions, we only allow NIC functionality and we only allow