From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com [209.85.213.46]) by dpdk.org (Postfix) with ESMTP id 2A13D1D8E for ; Mon, 4 Dec 2017 23:11:45 +0100 (CET) Received: by mail-vk0-f46.google.com with SMTP id n63so10730393vkf.2 for ; Mon, 04 Dec 2017 14:11:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=velocloud-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=/FjflMBU0I51CDrG8qe+avWvsPrPQ237s9fMP9568+s=; b=XeSBskuSP0YCPlKUB59D0lfonILGZq+EwrYbqyJrDs0CqIInRibPzjMZL/+mSLO5nX Uohvlx6DPs5GftF2QwXsqGM7u8VvDr4ADFmd7hzvRLcQ7DAZ1c0KXgy7eaWZIqXSbese 9B/SPuJJzOvwIwc1E8z9ehFzV6e+45rppx4mBPAuJvAkucUhe7p1sjWROgGlsULfchtO yzx0iqxCoVIBpcDPFFdwUStsHaf1d3JL583YCAyzuk9Kk4lQkaJkZc/L7WWo9Z8qDoze p7HSZXokYm2phwE7eMjmFoFqEm/A02pwvlOL70NWwwaQjjT2QqtVLCUnpNY/uTQjlazb 9EmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/FjflMBU0I51CDrG8qe+avWvsPrPQ237s9fMP9568+s=; b=kz5GxKkolguNJBytQk2y5BxOREWbvM/IuKSHgFrIgJRvIp3Ddqi8XtN6TQjCN3fShM C1HR3hfIMf5AiAMeITGZ1St5xkMoZQzo2UkHqG3Eb37xPVVDK8ACsDJ9OblaEtaz9zls i/bIu2mf4aPs9g94Js1RXiYjmE9FuEOnb1IDybTumthxRAFqEFH3bzCSkg2R1etSCVJn jtUlqTa2JFD/0PbXcXPs4Yh0AjE5WdbOuFXesLtgHa/aea4Irv6m8wKpVsPQBT3saPCC c563XciAHsjHsf9FdBbkuYnPsqTNys4+ui38Cspwbxn4kGqbJkzp6QpHtoqEe7NMmpYL JJtA== X-Gm-Message-State: AKGB3mIXpGUVIIpR8D+tHgg9iSeeUIUxpYwxLFvFvyl7S6vsonjdghjs OgY0CK6Un9ynzHL1Iqzd1hEtbnX1e0H1JAeeJtunMXQ= X-Google-Smtp-Source: AGs4zMa8sB9QSZkMDbYUjc9UuHTlERq0/xSVbzuiVj7hl46Z1+UzLzAl0H9h4/igq9M7clWVnefTXeZCbSidPwb86Jc= X-Received: by 10.31.204.194 with SMTP id c185mr1028280vkg.157.1512425504222; Mon, 04 Dec 2017 14:11:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.78.203 with HTTP; Mon, 4 Dec 2017 14:11:43 -0800 (PST) From: Jordan Rhody Date: Mon, 4 Dec 2017 14:11:43 -0800 Message-ID: To: dev@dpdk.org X-Mailman-Approved-At: Tue, 05 Dec 2017 09:38:32 +0100 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] DPDK Amazon AWS ENA driver problem with ping 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: , X-List-Received-Date: Mon, 04 Dec 2017 22:11:45 -0000 Hi, I have been testing the DPDK ENA driver and am hoping that someone can help in assisting an observation I have. Using the DPDK ENA driver, I can send a ping request/reply from client A to client B through an Edge device running DPDK. However, the ping request that I observe always contains a '0xffff' for the sequence id of the icmp request: Internet Control Message Protocol Type: 8 (Echo (ping) request) Code: 0 Checksum: 0xf9a1 incorrect, should be 0xfa8c [Checksum Status: Bad] <--- checksum is original and unmodified Identifier (BE): 2385 (0x0951) Identifier (LE): 20745 (0x5109) Sequence number (BE): 65535 (0xffff) <--- here Sequence number (LE): 65535 (0xffff) <--- here [No response seen] Timestamp from icmp data: Nov 21, 2017 16:41:20.000000000 PST [Timestamp from icmp data (relative): 1.042436000 seconds] Data (48 bytes) Data: 612d0f0000000000101112131415161718191a1b1c1d1e1f... [Length: 48] I have traced the packet to the entry point of eth_ena_xmit_pkts( ) and it does *not* have sequence id 0xffff. The sequence id seems sane and valid at that point. Turning off DPDK and using the Linux Amazon AWS ENA driver yields no problems at all. ping request/reply works without a problem. As an aside, this same code works for the DPDK igb, ixgbe and virtio driver. I have patched the DPDK ENA driver with all patches through DPDK 17.05 to no avail and with the same results. Question -- the basic: Could there be something 'wrong' with my AWS network interface with regard to setup, perhaps something that may be obvious to other folks more familiar with AWS? If not, has anyone else experienced problems with DPDK AWS ENA driver? Are there any possible patches out there that have not been commit to the git repo that may fix this particular issue? Thanks in advance, Jordan Rhode