Lines Matching refs:traffic

153 different traffic flows received by one interface to be processed by different
156 The driver has support for multiple prioritized Tx traffic classes. Priorities
158 strict priority levels. Each traffic class contains NR_CPU TX queues. By
159 default, only one traffic class is enabled and the lowest priority Tx queues
160 are used. Higher priority traffic classes can be enabled with the mqprio
161 qdisc. For example, all four traffic classes are enabled on an interface with
162 the following command. Furthermore, skb priority levels are mapped to traffic
165 	* priorities 0 to 3 - traffic class 0 (low priority)
166 	* priorities 4 to 7 - traffic class 1 (medium-low priority)
167 	* priorities 8 to 11 - traffic class 2 (medium-high priority)
168 	* priorities 12 to 15 - traffic class 3 (high priority)
177 queues is seen by the CPU as ingress traffic on a certain portal.
182 DPAA FMan Parser and Keygen blocks to distribute traffic on 128
185 When RSS is disabled, all traffic received by a certain interface is
187 queues are configured to put the received traffic into a pool channel
188 that allows any available CPU portal to dequeue the ingress traffic.
190 traffic bursts from a certain queue are serviced by the same CPU.
192 is that only one CPU at a time can service the traffic received by a
198 hardcoded, there is no indirection table to move traffic for a certain
199 FQ (hash result) to another CPU. The ingress traffic arriving on one
202 and workload distribution for multiple traffic flows.
216 Besides using the FMan Keygen computed hash for spreading traffic on the