From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-x22c.google.com (mail-vc0-x22c.google.com [IPv6:2607:f8b0:400c:c03::22c]) by dpdk.org (Postfix) with ESMTP id B3456156 for ; Sun, 3 Nov 2013 15:38:35 +0100 (CET) Received: by mail-vc0-f172.google.com with SMTP id ks9so4029368vcb.17 for ; Sun, 03 Nov 2013 06:39:28 -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=wGaLd95bjexflZT6MJ6DkRIx7ej18ozkcDuzleD+zq8=; b=S1B+9uEn2+kFFI5jfv4ODJvpMmeow2zwmk+su0L7jB45tjuVkd3FYm0arS386Flf7I s2qjA2OwJMg4mcyGFUy+GvGIwjuiAGCIuw0wsIAydeSawcQUn9JM7hABFCXta/1qwfjE 7er/0t2XYRZGbiXloKGEvBgTvTTEPW0FmzsH34DYnsH6QHg15i2fbWwLGen2ZwVIbfJc 4xT6iNnSiV4gqLF9qyT3fEKZjLi0Ei22+8hVOEAKUuqwu62PgA0bJvTFN1MNYLqUvj8p ygul04OuaOWWAjVZqKGlYPErtexsicMnVOaALbgupwZrKIeRIB1KXDPsgNzNrl/BcmPY D2ng== MIME-Version: 1.0 X-Received: by 10.52.191.162 with SMTP id gz2mr10872vdc.26.1383489568037; Sun, 03 Nov 2013 06:39:28 -0800 (PST) Received: by 10.52.177.70 with HTTP; Sun, 3 Nov 2013 06:39:27 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Nov 2013 06:39:27 -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 14:38:36 -0000 Hi Prashant, Did some research and looks like there an option in the driver disable it from 3.2 kernel. Any kernel before that looks to be a source code modification. Again Thanks for you help. Regards, Sambath On Sun, Nov 3, 2013 at 5:18 AM, Sambath Kumar Balasubramanian < sambath.balasubramanian@gmail.com> wrote: > 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. >> >> =============================================================================== >> > >