Lines Matching refs:packet

26 applying a filter to each packet that assigns it to one of a small number
36 IP addresses and TCP ports of a packet. The most common hardware
38 stores a queue number. The receive queue for a packet is determined
40 packet (usually a Toeplitz hash), taking this number as a key into the
73 an IRQ may be handled on any CPU. Because a non-negligible part of packet
106 above the interrupt handler. This is accomplished by placing the packet
114 a driver sends a packet up the network stack with netif_rx() or
116 selects the queue that should process a packet.
119 flow hash over the packet’s addresses or ports (2-tuple or 4-tuple hash
121 associated flow of the packet. The hash is either provided by hardware
123 the receive descriptor for the packet; this would usually be the same
126 packet’s flow.
129 RPS may enqueue packets for processing. For each received packet,
131 of the list. The indexed CPU is the target for processing the packet,
132 and the packet is queued to the tail of that CPU’s backlog queue. At
170 to the same CPU is CPU load imbalance if flows vary in packet rate.
179 destination CPU approaches saturation.  Once a CPU's input packet
181 net.core.netdev_max_backlog), the kernel starts a per-flow packet
183 default, half) of these packets when a new packet arrives, then the
184 new packet is dropped. Packets from other flows are still only
185 dropped once the input packet queue reaches netdev_max_backlog.
186 No packets are dropped when the input packet queue length is below
200 Per-flow rate is calculated by hashing each packet into a hashtable
219 The feature depends on the input packet queue length to exceed
233 consuming the packet is running. RFS relies on the same RPS mechanisms
266 CPU's backlog when a packet in this flow was last enqueued. Each backlog
275 CPU for packet processing (from get_rps_cpu()) the rps_sock_flow table
276 and the rps_dev_flow table of the queue that the packet was received on
279 table), the packet is enqueued onto that CPU’s backlog. If they differ,
288 After this check, the packet is sent to the (possibly updated) current
368 which transmit queue to use when transmitting a packet on a multi-queue
383 When transmitting the first packet in a flow, the function
396 skb->ooo_okay is set for a packet in the flow. This flag indicates that