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 at 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 at dpdk.org] On Behalf Of Sambath Kumar > Balasubramanian > Sent: Sunday, November 03, 2013 4:26 AM > To: dev at 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 at 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. > > =============================================================================== >
