Lines Matching full:flows

31 of logical flows. Packets for each flow are steered to a separate receive
50 applications that monitor TCP/IP flows (IDS, firewalls, ...etc) and need
245 to the same CPU is CPU load imbalance if flows vary in packet rate.
251 Flow Limit is an optional RPS feature that prioritizes small flows
252 during CPU contention by dropping packets from large flows slightly
253 ahead of those from small flows. It is active only when an RPS or RFS
259 new packet is dropped. Packets from other flows are still only
263 even large flows maintain connectivity.
281 identification of large flows and fewer false positives. The default
318 flows to the CPUs where those flows are being processed. The flow hash
323 same CPU. Indeed, with many flows and few CPUs, it is very likely that
324 a single application thread handles flows with many different flow hashes.
327 for flows: the CPU that is currently processing the flow in userspace.
350 entry i is actually selected by hash and multiple flows may hash to the
411 balancing mechanism that uses soft state to steer flows based on where