diff options
author | Maxim Mikityanskiy <maximmi@mellanox.com> | 2019-09-16 14:54:20 +0300 |
---|---|---|
committer | Saeed Mahameed <saeedm@mellanox.com> | 2019-10-30 02:27:19 +0300 |
commit | 9df86bdb6746d7fcfc2fda715f7a7c3d0ddb2654 (patch) | |
tree | 4c2f65e512991a8f987027fb150074301d0b4251 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 2a4b6526236791a1bb8092079ad87a1629e78db5 (diff) | |
download | linux-9df86bdb6746d7fcfc2fda715f7a7c3d0ddb2654.tar.xz |
net/mlx5e: Fix handling of compressed CQEs in case of low NAPI budget
When CQE compression is enabled, compressed CQEs use the following
structure: a title is followed by one or many blocks, each containing 8
mini CQEs (except the last, which may contain fewer mini CQEs).
Due to NAPI budget restriction, a complete structure is not always
parsed in one NAPI run, and some blocks with mini CQEs may be deferred
to the next NAPI poll call - we have the mlx5e_decompress_cqes_cont call
in the beginning of mlx5e_poll_rx_cq. However, if the budget is
extremely low, some blocks may be left even after that, but the code
that follows the mlx5e_decompress_cqes_cont call doesn't check it and
assumes that a new CQE begins, which may not be the case. In such cases,
random memory corruptions occur.
An extremely low NAPI budget of 8 is used when busy_poll or busy_read is
active.
This commit adds a check to make sure that the previous compressed CQE
has been completely parsed after mlx5e_decompress_cqes_cont, otherwise
it prevents a new CQE from being fetched in the middle of a compressed
CQE.
This commit fixes random crashes in __build_skb, __page_pool_put_page
and other not-related-directly places, that used to happen when both CQE
compression and busy_poll/busy_read were enabled.
Fixes: 7219ab34f184 ("net/mlx5e: CQE compression")
Signed-off-by: Maxim Mikityanskiy <maximmi@mellanox.com>
Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions