diff options
author | Saeed Mahameed <saeedm@mellanox.com> | 2016-08-29 01:13:42 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-08-28 23:24:15 -0400 |
commit | fe4c988bdd1cc60402a4e3ca3976a686ea991b5a (patch) | |
tree | d003855813fc889c189d2e44f13db431afbec16b /tools/perf/scripts/python/net_dropmonitor.py | |
parent | 9dbeea7f08f3784b152d9fb3b86beb34aad77c72 (diff) |
net/mlx5e: Limit UMR length to the device's limitation
ConnectX-4 UMR (User Memory Region) MTT translation table offset in WQE
is limited to U16_MAX, before this patch we ignored that limitation and
requested the maximum possible UMR translation length that the netdev
might need (MAX channels * MAX pages per channel).
In case of a system with #cores > 32 and when linear WQE allocation fails,
falling back to using UMR WQEs will cause the RQ (Receive Queue) to get
stuck.
Here we limit UMR length to min(U16_MAX, max required pages) (while
considering the required alignments) on driver load, by default U16_MAX is
sufficient since the default RX rings value guarantees that we are in
range, dynamically (on set_ringparam/set_channels) we will check if the
new required UMR length (num mtts) is still in range, if not, fail the
request.
Fixes: bc77b240b3c5 ('net/mlx5e: Add fragmented memory support for RX multi packet WQE')
Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions