[dpdk-dev] [PATCH v2 0/4] net/mlx5: keep indirect actions across port restart

[Dmitry Kozlyuk <dkozlyuk@nvidia.com>]

It is unspecified what happens to indirect actions when a port
is stopped, possibly reconfigured, and started again.  MLX5 PMD,
the first one to implement indirect action API, intended to keep
them across such a sequence, but the implementation was buggy,
This patcheset fixes it. There is no consensus yet what behavior
should be specified for all drivers, so current behavior is described
in PMD docs.

Dmitry Kozlyuk (3):
  net/mlx5: discover max flow priority using DevX
  net/mlx5: create drop queue using DevX
  net/mlx5: preserve indirect actions across port restart

 doc/guides/nics/mlx5.rst           |   8 +
 drivers/net/mlx5/linux/mlx5_os.c   |   5 -
 drivers/net/mlx5/mlx5_devx.c       | 204 +++++++++++++++++---
 drivers/net/mlx5/mlx5_flow.c       | 292 ++++++++++++++++++++++++++---
 drivers/net/mlx5/mlx5_flow.h       |   6 +
 drivers/net/mlx5/mlx5_flow_dv.c    | 103 ++++++++++
 drivers/net/mlx5/mlx5_flow_verbs.c |  77 +-------
 drivers/net/mlx5/mlx5_rx.h         |   4 +
 drivers/net/mlx5/mlx5_rxq.c        |  99 ++++++++--
 drivers/net/mlx5/mlx5_trigger.c    |  10 +
 10 files changed, 674 insertions(+), 134 deletions(-)

-- 
2.25.1