On 6/14/2017 12:49 PM, Adrien Mazarguil wrote: > Several issues mainly related to error handling were found in both > implementations as they share most of their Rx interrupts handling code. > > Another problem with the mlx4 implementation is that it does not work > properly with multiple ports adapters that share a common PCI device. > > Adrien Mazarguil (7): > net/mlx4: fix typos from prior commit > net/mlx4: fix Rx interrupts with multiple ports > net/mlx4: fix Rx interrupts management > net/mlx5: fix misplaced Rx interrupts functions > net/mlx5: fix Rx interrupts support checks > net/mlx5: fix return value in Rx interrupts code > net/mlx5: fix Rx interrupts management > > drivers/net/mlx4/mlx4.c | 179 ++++++++++++++++------------------- > drivers/net/mlx4/mlx4.h | 1 + > drivers/net/mlx5/mlx5.c | 2 + > drivers/net/mlx5/mlx5_rxq.c | 142 ++++++++++++++++++--------- > drivers/net/mlx5/mlx5_rxtx.c | 73 -------------- > drivers/net/mlx5/mlx5_rxtx.h | 12 +-- > drivers/net/mlx5/mlx5_trigger.c | 16 ++-- > 7 files changed, 194 insertions(+), 231 deletions(-)
Series applied to dpdk-next-net/master, thanks.
