From patchwork Tue Aug 22 10:41:26 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alejandro Lucero X-Patchwork-Id: 27713 X-Patchwork-Delegate: ferruh.yigit@amd.com Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 4702E7D5B; Tue, 22 Aug 2017 12:41:38 +0200 (CEST) Received: from netronome.com (host-79-78-33-110.static.as9105.net [79.78.33.110]) by dpdk.org (Postfix) with ESMTP id 720787D5A for ; Tue, 22 Aug 2017 12:41:36 +0200 (CEST) Received: from netronome.com (localhost [127.0.0.1]) by netronome.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v7MAfQRg001983; Tue, 22 Aug 2017 11:41:26 +0100 Received: (from alucero@localhost) by netronome.com (8.14.4/8.14.4/Submit) id v7MAfQtn001982; Tue, 22 Aug 2017 11:41:26 +0100 From: Alejandro Lucero To: dev@dpdk.org Cc: ferruh.yigit@intel.com Date: Tue, 22 Aug 2017 11:41:26 +0100 Message-Id: <1503398486-1944-1-git-send-email-alejandro.lucero@netronome.com> X-Mailer: git-send-email 1.9.1 Subject: [dpdk-dev] [PATCH v2] nfp: handle packets with length 0 as usual ones X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" A DPDK app could, whatever the reason, send packets with size 0. The PMD is not sending those packets, which does make sense, but the problem is the mbuf is not released either. That leads to mbufs not being available, because the app trusts the PMD will do it. Although this is a problem related to app wrong behaviour, we should harden the PMD in this regard. Not sending a packet with size 0 could be problematic, needing special handling inside the PMD xmit function. It could be a burst of those packets, which can be easily handled, but it could also be a single packet in a burst, what is harder to handle. It would be simpler to just send that kind of packets, which will likely be dropped by the hw at some point. The main problem is how the fw/hw handles the DMA, because a dma read to a hypothetical 0x0 address could trigger an IOMMU error. It turns out, it is safe to send a descriptor with packet size 0 to the hardware: the DMA never happens, from the PCIe point of view. v2: remove code for handling zero-length mbuf chained. Signed-off-by: Alejandro Lucero --- drivers/net/nfp/nfp_net.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/net/nfp/nfp_net.c b/drivers/net/nfp/nfp_net.c index 92b03c4..6f1800c 100644 --- a/drivers/net/nfp/nfp_net.c +++ b/drivers/net/nfp/nfp_net.c @@ -2094,7 +2094,7 @@ uint32_t nfp_net_txq_full(struct nfp_net_txq *txq) */ pkt_size = pkt->pkt_len; - while (pkt_size) { + while (pkt) { /* Copying TSO, VLAN and cksum info */ *txds = txd; @@ -2126,13 +2126,13 @@ uint32_t nfp_net_txq_full(struct nfp_net_txq *txq) txq->wr_p = 0; pkt_size -= dma_size; - if (!pkt_size) { + if (!pkt_size) /* End of packet */ txds->offset_eop |= PCIE_DESC_TX_EOP; - } else { + else txds->offset_eop &= PCIE_DESC_TX_OFFSET_MASK; - pkt = pkt->next; - } + + pkt = pkt->next; /* Referencing next free TX descriptor */ txds = &txq->txds[txq->wr_p]; lmbuf = &txq->txbufs[txq->wr_p].mbuf;