[dpdk-dev] [PATCH v7 0/6] Fail-safe\ethdev: fix removal handling lack

[Ferruh Yigit]

On 1/20/2018 9:12 PM, Matan Azrad wrote:
> 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, adjust ethdev APIs to return -EIO in case of removal 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.
> 
> V3:
> Adjust ethdev APIs removal error report.
> Change failsafe check to check eth_dev* return values.
> Remove backporting of fail-safe patch.
> 
> V4:
> Improve fail-safe internal API to adjust the actual error value as discussed.
> Remove "Fixes" lines from fail-safe patch.
> No changes in ethdev\mlx patches.
> 
> V5:
> Rebase on top of master-net-mlx. 
> 
> V6:
> Move ethdev new API to be EXPERIMENTAL.
> 
> V7:
> Fix API return value description.
> Swap checks in the new API as Konstantin suggested.
> Add comment in the API as Ferruh suggested.
> 
> Matan Azrad (6):
>   ethdev: add devop to check removal status
>   net/mlx4: support a device removal check operation
>   net/mlx5: support a device removal check operation
>   ethdev: adjust APIs removal error report
>   ethdev: adjust flow APIs removal error report
>   net/failsafe: fix removed device handling

Series applied to dpdk-next-net/master, thanks.