Lines Matching refs:traffic

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