From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vb0-x22b.google.com (mail-vb0-x22b.google.com [IPv6:2607:f8b0:400c:c02::22b]) by dpdk.org (Postfix) with ESMTP id 19BDB156 for ; Sun, 3 Nov 2013 14:17:23 +0100 (CET) Received: by mail-vb0-f43.google.com with SMTP id g10so771950vbg.16 for ; Sun, 03 Nov 2013 05:18:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oPRYlKEqDKRbvroeYOuGy5gNY8xxmFXBMJIzGqh+U18=; b=qooxZ66yYC9jbMz/DqN0oBZFDyKuz0iv7/6fU5EgSvSeQi5udbfe2Va1dHXDPaFgIU 0sh71nRYmqgfy6oEcO/e4klOa/h+tqX+wbkRHbfBh4P1wFNL/BcE8GorrNGAHPOsGKdt WH74zkcKwoL8shqnAc/edIuiJPWmwxAdHYxOCv2XjdqHL3vxhpxtXbyS4quEh5js6hZj +8mksu7IXel2SR5L18nGFvPxiEQn8duup1SdSnreHimwtRoWMiKy4fYlfSYa9hnVaAFf wDnjZGNIEJZvKZQq2eaXqC5kP9EoRCM5CDYu1WSsdT8oWR9DyyBAPdx5kopmYJY9mODs UEAg== MIME-Version: 1.0 X-Received: by 10.52.243.138 with SMTP id wy10mr6843625vdc.2.1383484696385; Sun, 03 Nov 2013 05:18:16 -0800 (PST) Received: by 10.52.177.70 with HTTP; Sun, 3 Nov 2013 05:18:16 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Nov 2013 05:18:16 -0800 Message-ID: From: Sambath Kumar Balasubramanian To: Prashant Upadhyaya Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Debugging igbvf_pmd 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: Sun, 03 Nov 2013 13:17:24 -0000 Thanks Prashant. You were spot on. That was the reason for the packet drop. Do you know if there is a way to disable anti-spoofing in the NIC or the driver? Thanks for the timely help. Regards, Sambath On Sun, Nov 3, 2013 at 4:48 AM, Prashant Upadhyaya < prashant.upadhyaya@aricent.com> wrote: > Hi Sambath, > > Did you follow the step of applying the mac to each of the virtual > function as per the release notes in DPDK ? > And ofcourse the src mac of your packets should be 'that' mac as set above. > > Regards > -Prashant > > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sambath Kumar > Balasubramanian > Sent: Sunday, November 03, 2013 4:26 AM > To: dev@dpdk.org > Subject: Re: [dpdk-dev] Debugging igbvf_pmd > > Sorry pressed the send button too soon. The NIC Card we are using is > > Intel Corporation 82576 Virtual Function (rev 01) > > Do we need to do now NIC/CPU low level debugging or is there some issue in > the sw that could cause the packet to be dropped below this log message. > > PMD: eth_igb_xmit_pkts(): port_id=3 queue_id=0 pktlen=60 tx_first=14 > tx_last=14 > > PMD: eth_igb_xmit_pkts(): port_id=3 queue_id=0 tx_tail=15 nb_tx=1 > > Thanks, > Sambath > > > On Sat, Nov 2, 2013 at 3:54 PM, Sambath Kumar Balasubramanian < > sambath.balasubramanian@gmail.com> wrote: > > > Hi, > > > > We are developing an App over DPDK and in one scenario with SR-IOV > > with one of the VFs mapped to a VM and DPDK running on the VM, we see > > that the packets are not coming on the wire but I get the following > > debug logs for every packet transmitted. We are getting the same > > format of packets on the wire in a different scenario so IMO the > > Virtual Function ports are set up properly. Any idea how this can be > > debugged further. The NIC card we are using is > > > > > > > > PMD: eth_igb_xmit_pkts(): port_id=3 queue_id=0 pktlen=60 tx_first=14 > > tx_last=14 > > > > PMD: eth_igb_xmit_pkts(): port_id=3 queue_id=0 tx_tail=15 nb_tx=1 > > > > Regards, > > Sambath > > > > > > > > > > =============================================================================== > Please refer to http://www.aricent.com/legal/email_disclaimer.html > for important disclosures regarding this electronic communication. > > =============================================================================== >