Lines Matching refs:RPS

14   RPS: Receive Packet Steering
99 RPS: Receive Packet Steering
102 Receive Packet Steering (RPS) is logically a software implementation of
105 interrupt handler, RPS selects the CPU to perform protocol processing
108 RPS has some advantages over RSS: 1) it can be used with any NIC,
113 RPS is called during bottom half of the receive interrupt handler, when
118 The first step in determining the target CPU for RPS is to calculate a
129 RPS may enqueue packets for processing. For each received packet,
138 ==== RPS Configuration
140 RPS requires a kernel compiled with the CONFIG_RPS kconfig symbol (on
141 by default for SMP). Even when compiled in, RPS remains disabled until
142 explicitly configured. The list of CPUs to which RPS may forward traffic
147 This file implements a bitmap of CPUs. RPS is disabled when it is zero
154 For a single queue device, a typical RPS configuration would be to set
161 receive queue is mapped to each CPU, then RPS is probably redundant
163 RPS might be beneficial if the rps_cpus for each queue are the ones that
166 ==== RPS Flow Limit
168 RPS scales kernel receive processing across CPUs without introducing
176 Flow Limit is an optional RPS feature that prioritizes small flows
178 ahead of those from small flows. It is active only when an RPS or RFS
202 the same that selects a CPU in RPS, but as the number of buckets can
228 While RPS steers packets solely based on hash, and thus generally
233 consuming the packet is running. RFS relies on the same RPS mechanisms
240 (see RPS section above) is used to calculate the index into this table.
243 are steered using plain RPS. Multiple table entries may point to the
327 Accelerated RFS is to RFS what RSS is to RPS: a hardware-accelerated load
436 RPS and RFS were introduced in kernel 2.6.35. XPS was incorporated into