Lines Matching refs:receive

23 Contemporary NICs support multiple receive and transmit descriptor queues
27 of logical flows. Packets for each flow are steered to a separate receive
38 stores a queue number. The receive queue for a packet is determined
45 can be directed to their own receive queue. Such “n-tuple” filters can
53 num_queues. A typical RSS configuration would be to have one receive queue
68 Each receive queue has a separate IRQ associated with it. The NIC triggers
74 processing takes place in receive interrupt handling, it is advantageous
75 to spread receive interrupts between CPUs. To manually adjust the IRQ
82 RSS should be enabled when latency is a concern or whenever receive
87 is likely the one with the smallest number of receive queues where no
88 receive queue overflows due to a saturated CPU, because in default
113 RPS is called during bottom half of the receive interrupt handler, when
123 the receive descriptor for the packet; this would usually be the same
128 Each receive hardware queue has an associated list of CPUs to which
143 can be configured for each receive queue using a sysfs file entry:
161 receive queue is mapped to each CPU, then RPS is probably redundant
196 receive packets on the old CPU, packets may arrive out of order. To
199 receive queue of each device. Each table value stores a CPU index and a
250 Both of these need to be set before RFS is enabled for a receive queue.
262 are 16 configured receive queues, rps_flow_cnt for each queue might be
298 configured for each receive queue by the driver, so no additional