From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrien Mazarguil Subject: [PATCH 0/7] Fix Rx interrupt support in mlx4 and mlx5 Date: Wed, 14 Jun 2017 13:49:10 +0200 Message-ID: To: dev@dpdk.org Return-path: Received: from mail-wr0-f169.google.com (mail-wr0-f169.google.com [209.85.128.169]) by dpdk.org (Postfix) with ESMTP id E43A07CEF for ; Wed, 14 Jun 2017 13:49:30 +0200 (CEST) Received: by mail-wr0-f169.google.com with SMTP id v104so174200807wrb.0 for ; Wed, 14 Jun 2017 04:49:30 -0700 (PDT) Received: from 6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id p8sm853414wrd.57.2017.06.14.04.49.27 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Wed, 14 Jun 2017 04:49:28 -0700 (PDT) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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(-) -- 2.1.4