net/mlx5e: RX, Fix flush and close release flow of regular rq for legacy rq

Browse source

[ Upstream commit 2e2d196579 ]

Regular (non-XSK) RQs get flushed on XSK setup and re-activated on XSK
close. If the same regular RQ is closed (a config change for example)
soon after the XSK close, a double release occurs because the missing
wqes get released a second time.

Fixes: 3f93f82988 ("net/mlx5e: RX, Defer page release in legacy rq for better recycling")
Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>

...

This commit is contained in:

Dragos Tatulea 2023-05-22 21:18:53 +03:00 • committed by Greg Kroah-Hartman

parent 7035e3ae60

commit bfc6d6dfd0

1 changed files with 10 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

12

drivers/net/ethernet/mellanox/mlx5/core/en_rx.c

View file