diff options
author | Ioana Radulescu <ruxandra.radulescu@nxp.com> | 2020-05-31 00:08:12 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2020-06-01 12:04:32 -0700 |
commit | 3f8b826d705fc6f0f0602fcbe6ee3b646ed3316e (patch) | |
tree | a18f6ef3292f393566cf0a87f446031d51998698 /drivers/perf | |
parent | 2c8d1c8d7d62dfedab97927c22e9421f0d72de8e (diff) |
dpaa2-eth: Update FQ taildrop threshold and buffer pool count
Now that we have congestion group taildrop configured at all
times, we can afford to increase the frame queue taildrop
threshold; this will ensure a better response when receiving
bursts of large-sized frames.
Also decouple the buffer pool count from the Rx FQ taildrop
threshold, as above change would increase it too much. Instead,
keep the old count as a hardcoded value.
With the new limits, we try to ensure that:
* we allow enough leeway for large frame bursts (by buffering
enough of them in queues to avoid heavy dropping in case of
bursty traffic, but when overall ingress bandwidth is manageable)
* allow pending frames to be evenly spread between ingress FQs,
regardless of frame size
* avoid dropping frames due to the buffer pool being empty; this
is not a bad behaviour per se, but system overall response is
more linear and predictable when frames are dropped at frame
queue/group level.
Signed-off-by: Ioana Radulescu <ruxandra.radulescu@nxp.com>
Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/perf')
0 files changed, 0 insertions, 0 deletions