Lines Matching refs:queues

23 Contemporary NICs support multiple receive and transmit descriptor queues
25 queues to distribute processing among CPUs. The NIC distributes packets by
43 Some advanced NICs allow steering packets to queues based on
51 module parameter for specifying the number of hardware queues to
54 for each CPU if the device supports enough queues, or otherwise at least
60 default mapping is to distribute the queues evenly in the table, but the
63 indirection table could be done to give different queues different
72 of queues to IRQs can be determined from /proc/interrupts. By default,
85 is to allocate as many queues as there are CPUs in the system (or the
87 is likely the one with the smallest number of receive queues where no
95 initial tests, so limit the number of queues to the number of CPU cores
145  /sys/class/net/<dev>/queues/rx-<n>/rps_cpus
162 and unnecessary. If there are fewer hardware queues than CPUs, then
304  /sys/class/net/<dev>/queues/rx-<n>/rps_flow_cnt
319 queues. So for instance, if rps_sock_flow_entries is set to 32768 and there
320 are 16 configured receive queues, rps_flow_cnt for each queue might be
355 of CPU to queues is automatically deduced from the IRQ affinities
370 recorded. The goal of this mapping is usually to assign queues
372 these queues are processed on a CPU within this set. This choice
382 transmit queues, is computed and maintained for each network device.
387 queues match, one is selected by using the flow hash to compute an index
410 /sys/class/net/<dev>/queues/tx-<n>/xps_cpus
417 If there are as many queues as there are CPUs in the system, then each
419 experience no contention. If there are fewer queues than CPUs, then the
430 /sys/class/net/<dev>/queues/tx-<n>/tx_maxrate