OSDN Git Service

net/mlx5e: Trigger NAPI after activating an SQ
authorMaxim Mikityanskiy <maximmi@nvidia.com>
Tue, 30 Aug 2022 16:39:49 +0000 (19:39 +0300)
committerSaeed Mahameed <saeedm@nvidia.com>
Sat, 4 Feb 2023 10:07:04 +0000 (02:07 -0800)
commit79efecb41f58430454cbb5809fa7b3135150da6d
treea60293809269637257a979cd171194656e81183e
parenta7385187a386d0fc4721727e2cbe4a70a9cff6f7
net/mlx5e: Trigger NAPI after activating an SQ

If an SQ is deactivated and reactivated again, some packets could be
sent after MLX5E_SQ_STATE_ENABLED is cleared, but before
netif_tx_stop_queue, meaning that NAPI might miss some completions. In
order to handle them, make sure to trigger NAPI after SQ activation in
all cases where it can be relevant. Regular SQs, XDP SQs and XSK SQs are
good. Missing cases added: after recovery, after activating HTB SQs and
after activating PTP SQs.

Signed-off-by: Maxim Mikityanskiy <maximmi@nvidia.com>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
drivers/net/ethernet/mellanox/mlx5/core/en.h
drivers/net/ethernet/mellanox/mlx5/core/en/ptp.c
drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c
drivers/net/ethernet/mellanox/mlx5/core/en_main.c