[dpdk-dev] [PATCH v2 0/4] Fail-safe fix removal handling lack

[Matan Azrad]

There is time between the physical removal of the device until sub-device 
PMDs get a RMV interrupt. At this time DPDK PMDs and  applications still 
don't know about the removal and may call sub-device control operation 
which should return an error.

This series adds new ethdev operation to check device removal, adds support
for it in mlx PMDs and fixes the fail-safe bug of removal error report.

V2:
Remove ENODEV definition.
Remove checks from all mlx control commands.
Add new devop - "is_removed".
Implement it in mlx4 and mlx5.
Fix failsafe bug by the new devop.

Matan Azrad (4):
  ethdev: add devop to check removal status
  net/mlx4: support a device removal check operation
  net/mlx5: support a device removal check operation
  net/failsafe: fix removed device handling

 drivers/net/failsafe/failsafe_flow.c    | 18 ++++++++++-------
 drivers/net/failsafe/failsafe_ops.c     | 34 ++++++++++++++++++++++-----------
 drivers/net/failsafe/failsafe_private.h | 10 ++++++++++
 drivers/net/mlx4/mlx4.c                 |  1 +
 drivers/net/mlx4/mlx4.h                 |  1 +
 drivers/net/mlx4/mlx4_ethdev.c          | 20 +++++++++++++++++++
 drivers/net/mlx5/mlx5.c                 |  2 ++
 drivers/net/mlx5/mlx5.h                 |  1 +
 drivers/net/mlx5/mlx5_ethdev.c          | 20 +++++++++++++++++++
 lib/librte_ether/rte_ethdev.c           | 28 ++++++++++++++++++++++++---
 lib/librte_ether/rte_ethdev.h           | 17 +++++++++++++++++
 lib/librte_ether/rte_ethdev_version.map |  7 +++++++
 12 files changed, 138 insertions(+), 21 deletions(-)

-- 
1.8.3.1