From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f178.google.com (mail-qc0-f178.google.com [209.85.216.178]) by dpdk.org (Postfix) with ESMTP id 8E77D2A7 for ; Tue, 17 Jun 2014 14:55:17 +0200 (CEST) Received: by mail-qc0-f178.google.com with SMTP id c9so9758561qcz.23 for ; Tue, 17 Jun 2014 05:55:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=SoAdvBpi0LM/bLG67HRZvG1fjLPn79HYQQBrxtCfF1M=; b=WuK048kygDuMzZ5jSkQEhAcT3OZadXSbYDuu0YyAP3hvdvQA2EitcX3K6219xGWSPO YtiARsPSeqQFEHDe6OS8joSpqhYjoQxMmHqianaCjEXD9Y6+6XY9RyKiKhAEm2nDA+LH ONWDlYR1N7F2VT4alUMn26g3oqZYy0xVtJfNLaGLRJYUCACeZZU0b4BzOO0zpHCVC/X9 w1DO3Npf0mBoyPb6d79Z05Uv7s9SZe42sLfaA44ylPquj7i/aO/v96bSyHQ8ZJh/qNIm wPTpYTGUassaGuYm14rUWAmWdu+kyU3kJvNlgA53IH3s/tElvEFbxQUkVYBQmptMXQ/y aP6w== X-Received: by 10.224.72.13 with SMTP id k13mr35675739qaj.54.1403009733669; Tue, 17 Jun 2014 05:55:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.99.36 with HTTP; Tue, 17 Jun 2014 05:55:03 -0700 (PDT) From: Tomasz K Date: Tue, 17 Jun 2014 14:55:03 +0200 Message-ID: To: dev Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Unable to send Response packets to the same port X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 12:55:17 -0000 Hello We're currently testing an application based on L2FWD example. 1. The application is located on VM which has 2 VFs from 2 different PFs 2. One core simply polls both RX queues from VFs, makes simple message processing and forwards the messages to appropriate TX queue of different VF (so there is no multiple access to the same port) 3. However sometimes when message is being processed, it results with failure and code needs to send back Failure notification to the port from which the message was received. The issue is that sometimes we see that packets are not being sent back (even though rte_eth_tx_burst() is succesfull... checked with tcpdump on peer ). Instead the core receives next packets and tries to send Failure Indications again until it runs out of memory in mempool. One thing to notice is that our app priority is latency over throughput so it always invokes rte_eth_tx_burst with only 1 packet to send. (we are suspecting this might be an issue here) Has anyone encountered such issue before.? Host Setup: DL380p Gen8 Server Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz Ubuntu 14.04: 3.13.0-24-generic Intel 82599 VM Setup: Ubuntu 14.04: 3.13.0-24-generic 2 VFs (each one from different PF)