Lines Matching full:same
49 are swapped, the computed hash is the same. This is beneficial in some
51 both directions of the flow to land on the same Rx queue (and CPU). The
140 modified using the same APIs as the default context::
192 the receive descriptor for the packet; this would usually be the same
228 the rps_cpus to the CPUs in the same memory domain of the interrupting
237 share the same memory domain as the interrupting CPU for that queue.
244 reordering. The trade-off to sending all packets from the same flow
245 to the same CPU is CPU load imbalance if flows vary in packet rate.
272 in sysctl net.core.flow_limit_cpu_bitmap. It exposes the same CPU
279 the same that selects a CPU in RPS, but as the number of buckets can
312 consuming the packet is running. RFS relies on the same RPS mechanisms
323 same CPU. Indeed, with many flows and few CPUs, it is very likely that
339 and userspace processing occur on the same CPU, and hence the CPU index
351 same entry i).
399 would normally be configured to the same value as rps_sock_flow_entries.
415 will either be the same CPU where the application runs, or at least a CPU
467 significantly reduced since fewer CPUs contend for the same queue
479 on the same queue associations for transmit and receive. This is useful for
484 socket for the connection. In this model, sending the packets on the same
487 the same queue-association that a given application is polling on. This
490 may be processed along with it in the same thread context and so result in