Lines Matching refs:RPS

18 - RPS: Receive Packet Steering
109 RPS: Receive Packet Steering
112 Receive Packet Steering (RPS) is logically a software implementation of
115 interrupt handler, RPS selects the CPU to perform protocol processing
118 RPS has some advantages over RSS:
125 RPS is called during bottom half of the receive interrupt handler, when
130 The first step in determining the target CPU for RPS is to calculate a
141 RPS may enqueue packets for processing. For each received packet,
151 RPS Configuration
154 RPS requires a kernel compiled with the CONFIG_RPS kconfig symbol (on
155 by default for SMP). Even when compiled in, RPS remains disabled until
156 explicitly configured. The list of CPUs to which RPS may forward traffic
161 This file implements a bitmap of CPUs. RPS is disabled when it is zero
170 For a single queue device, a typical RPS configuration would be to set
177 receive queue is mapped to each CPU, then RPS is probably redundant
179 RPS might be beneficial if the rps_cpus for each queue are the ones that
183 RPS Flow Limit
186 RPS scales kernel receive processing across CPUs without introducing
194 Flow Limit is an optional RPS feature that prioritizes small flows
196 ahead of those from small flows. It is active only when an RPS or RFS
222 the same that selects a CPU in RPS, but as the number of buckets can
250 While RPS steers packets solely based on hash, and thus generally
255 consuming the packet is running. RFS relies on the same RPS mechanisms
262 (see RPS section above) is used to calculate the index into this table.
265 are steered using plain RPS. Multiple table entries may point to the
353 Accelerated RFS is to RFS what RSS is to RPS: a hardware-accelerated load
513 RPS and RFS were introduced in kernel 2.6.35. XPS was incorporated into