From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f49.google.com (mail-qg0-f49.google.com [209.85.192.49]) by dpdk.org (Postfix) with ESMTP id 6AFEF2C0C for ; Mon, 28 Mar 2016 03:02:16 +0200 (CEST) Received: by mail-qg0-f49.google.com with SMTP id c67so64586008qgc.1 for ; Sun, 27 Mar 2016 18:02:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=purestorage.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=KwqQ2c+ZjyiHz0Th5fywl7xqpJS+VRPRPHKSBTO3eUw=; b=M4f159DlWDnFqCy1ga/kLn5N42rvuAaR+4JeZXC8hi11EJ2dLF97Y7WIfYpx4PSBGf 0L3ai7xGj76TXvv/uOkeuYYSR1WBfaAhUfNsvoJaQycmt/pYZevrtmxmV1dmO+9Ujvz/ THlug4Lb86uO55XjVMpNqInGEUi3cv0WgXKD8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=KwqQ2c+ZjyiHz0Th5fywl7xqpJS+VRPRPHKSBTO3eUw=; b=QoO17awgn/VYHUItB0UNb62yZQMXO8BRH99hT/D8dNn9J9IdT1W/Mo+r8GwRRHWUYm iUJ1G+k7K08Rko5F/DGpax6V/YnGntDCxIkhok413VX1nZmbOCgzwbQuc8b5px2kOLVU a93EwoRRaMf3Ih9h+vx8Cc4iZfQw3Avnt+tZjxvenNRS+Uzv0h7xwFxyY+BMEjzbHJuj NexoEGdDl882Sm+mOVmzEZq909ZrO92O+P6uMTU6EuHy63iACLRkc+08ZeY4ySUwljPT 8ZFADosSji3jI7ICvr5cMMzdnXs6UaaTwN89rgzLPB4JVjzI/zPF799oN3UdxXxwm0co +qgw== X-Gm-Message-State: AD7BkJKd/VJWfryjIW7SClloNoTz+DG7ZndbYZqmsPe0pLJzF+x1pnMdVzuPu0lS7OFygyObUcyFPw8frwZSaMKM MIME-Version: 1.0 X-Received: by 10.140.97.9 with SMTP id l9mr31762660qge.106.1459126935900; Sun, 27 Mar 2016 18:02:15 -0700 (PDT) Received: by 10.140.98.7 with HTTP; Sun, 27 Mar 2016 18:02:15 -0700 (PDT) In-Reply-To: References: Date: Sun, 27 Mar 2016 18:02:15 -0700 Message-ID: From: John Boyle To: Jesper Wramberg Cc: Toby DiPasquale , users@dpdk.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] pkts not transmitting with DPDK 2.2.0 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2016 01:02:16 -0000 Look at the output of "dmesg", specifically for messages printed by ixgbe. I've encountered two problems of the sort "DPDK thinks packets were successfully sent, but the packets never left the NIC", and both would manifest as some errors in dmesg. One particularly common failure mode was due to the spoof checking Jesper mentions, where the NIC will drop packets where the source MAC doesn't match the VF's MAC. In that case, "dmesg" will print lines like this: [92990.018296] ixgbe 0000:01:00.1 p5p2: 2 Spoofed packets detected -- John Boyle *Science is what we understand well enough to explain to a computer. Art is everything else we do.* --Knuth On Sun, Mar 27, 2016 at 1:19 PM, Jesper Wramberg wrote: > Hi, > > I may have been a bit unclear in my previous mail. Are you using EC2 or > some kind of virtual server without access to the hypervisor ? The NIC you > are using seems to be a virtual PCI function (SR-IOV). I was assuming you > had access to the physical function (i.e. the actual NIC interface and not > the virtualized/limited one). > > If you don't have access to any information or controls on the hypervisor I > guess we can only check xstats for errors through DPDK. But since the PMD > does not report any errors in your application my best guess is that the > physical function (the physical NIC) receives your packets from the > virtualized interface but discards them for some reason. > > From my (limited) experience, my guess is that your packets are dropped due > to MAC spoofcheck or some kind of IP anti-spoofing. I don't know anything > about EC2 but how do you obtain an IP for your network interface(s) in > Linux ? Can you use static IPs in Linux ? Also, what is the destination IP > of the packets you are receiving ? From my quick glance at your source it > seems you use the dest. IP as source IP when TXing. Since you set the port > in promisc. mode you could be using others IPs (although I don't think > promisc. does much in this particular case since you are using a virtual > function). > > Maybe a simpler application could be used to isolate the error. You could > always try sending a DHCP discover or something that doesn't require an IP > (and use the source MAC reported by the rte_ethdev_macaddr_get() function.) > > Hope it helps > > 2016-03-27 20:17 GMT+02:00 Toby DiPasquale : > > > Hi Jesper, > > > > Neither ethtool nor ip return for this NIC: > > > > # ethtool -S eth1 > > Cannot get stats strings information: No such device > > # ip link show eth1 > > Device "eth1" does not exist. > > > > The NIC has been disconnected from the OS via dpdk_nic_bind.py. The > > MAC addresses do match, also. If the NIC is not visible to the OS, and > > I'm not turning spoof checking on in the DPDK app, would the setting > > while it is attached to the kernel make a difference? > > > > > > On Sun, Mar 27, 2016 at 4:57 AM, Jesper Wramberg > > wrote: > > > Hey Toby, > > > > > > It seems you are using a VF yes ? I did some testing of SR-IOV a while > > ago > > > on an Intel NIC. I remember having to fiddle with it to get it working, > > so > > > here are a new notes/questions you might find useful (or maybe not > :-)). > > > > > > Are there any errors in the stats on the physical function (ethtool -S > > > ) ? > > > Since you are receiving packets the MAC is probably correct. But > anyway: > > > Did you check the MAC addresses of the VF using "ip link show > > interface>" - do they match what DPDK uses ? > > > Is spoof checking enabled on the PF ? > > > > > > My tests were with an XL710 only using Linux (no DPDK). To be able to > TX > > > from the VF after changing stuff with "ip link set..." I think I may > have > > > had to reset the VF or PF using "ip link set .. down/up". > > > > > > I know I'm not exactly providing any answers here - and my memory isn't > > > helping - but maybe something can point you in the right direction. > > > > > > Regards, > > > Jesper > > > > > > > > > 2016-03-26 20:24 GMT+01:00 Toby DiPasquale : > > >> > > >> Hi all, > > >> > > >> I'm having an issue getting packets to actually transmit out of the > > >> NIC with DPDK 2.2.0. I've built a simple UDP echo server here: > > >> https://github.com/codeslinger/udpecho > > >> > > >> Packets are received just fine, and they appear to say they are > > >> transmitted, as well, but they never actually leave the NIC. Here is > > >> some sample output with the details of how I'm running this: > > >> https://gist.github.com/codeslinger/d2e59b00bdc1208f4369 > > >> > > >> I'm kinda stumped. I had a local person with DPDK experience look at > > >> this code and he was similarly confused as to why it wasn't working. > > >> Anyone have any ideas on this one? Thanks in advance! > > >> > > >> -- > > >> Toby DiPasquale > > > > > > > > > > > > > > -- > > Toby DiPasquale > > >