[dpdk-dev] checking packet drop at NIC
Hi Daniel & all, can anyone please let me know about this. Tx -SB On Thu, Jan 30, 2014 at 4:50 PM, Sharath wrote: > hi! > > are there any interrupts which are raised by DPDK, for the fifo errors. > > please let me know, where can I find the details and how to handle such > interrupts ? > > Tx > -SB > > > On Thu, Jan 30, 2014 at 2:30 PM, Sharath gmail.com>wrote: > >> Thanks Daniel ! >> Let me check it out . . . >> On Jan 29, 2014 8:54 PM, "Daniel Kaminsky" < >> daniel.kaminsky at infinitelocality.com> wrote: >> >>> Hi Sharath, >>> >>> Try rte_eth_stats_get, I think this should give you what you're looking >>> for. >>> >>> Regards, >>> Daniel >>> >>> >>> On Tue, Jan 28, 2014 at 7:29 AM, Sharath >> gmail.com>wrote: >>> hi ! can someone please tell me whether the DPDK provides any method to handle below a. account the packet drops at NIC level ? is there any interrupt raised by DPDK for the same ? b. to check fifo errors ? c. way to check rx and tx in sync Tx, -SB >>> >>> >
[dpdk-dev] checking packet drop at NIC
Hi Sharath, In DPDK interrupts are disabled to eliminate the performance overhead. Interrupts used only for link status change. So you can poll rte_eth_stats_get and check struct rte_eth_stats for errors. Regards, Vladimir 2014-01-31 Sharath > Hi Daniel & all, > > can anyone please let me know about this. > > Tx > -SB > > > On Thu, Jan 30, 2014 at 4:50 PM, Sharath >wrote: > > > hi! > > > > are there any interrupts which are raised by DPDK, for the fifo errors. > > > > please let me know, where can I find the details and how to handle such > > interrupts ? > > > > Tx > > -SB > > > > > > On Thu, Jan 30, 2014 at 2:30 PM, Sharath >wrote: > > > >> Thanks Daniel ! > >> Let me check it out . . . > >> On Jan 29, 2014 8:54 PM, "Daniel Kaminsky" < > >> daniel.kaminsky at infinitelocality.com> wrote: > >> > >>> Hi Sharath, > >>> > >>> Try rte_eth_stats_get, I think this should give you what you're looking > >>> for. > >>> > >>> Regards, > >>> Daniel > >>> > >>> > >>> On Tue, Jan 28, 2014 at 7:29 AM, Sharath < > sharathjm.bharadwaj at gmail.com>wrote: > >>> > hi ! > > can someone please tell me whether the DPDK provides any method to > handle > below > > a. account the packet drops at NIC level ? is there any interrupt > raised by > DPDK for the same ? > b. to check fifo errors ? > c. way to check rx and tx in sync > > Tx, > -SB > > >>> > >>> > > >
[dpdk-dev] checking packet drop at NIC
thank you Vladimir. On Fri, Jan 31, 2014 at 12:36 PM, Vladimir Medvedkin wrote: > Hi Sharath, > > In DPDK interrupts are disabled to eliminate the performance overhead. > Interrupts used only for link status change. So you can poll > rte_eth_stats_get and check struct rte_eth_stats for errors. > > Regards, > Vladimir > > > > 2014-01-31 Sharath > > Hi Daniel & all, >> >> can anyone please let me know about this. >> >> Tx >> -SB >> >> >> On Thu, Jan 30, 2014 at 4:50 PM, Sharath > >wrote: >> >> > hi! >> > >> > are there any interrupts which are raised by DPDK, for the fifo errors. >> > >> > please let me know, where can I find the details and how to handle such >> > interrupts ? >> > >> > Tx >> > -SB >> > >> > >> > On Thu, Jan 30, 2014 at 2:30 PM, Sharath > >wrote: >> > >> >> Thanks Daniel ! >> >> Let me check it out . . . >> >> On Jan 29, 2014 8:54 PM, "Daniel Kaminsky" < >> >> daniel.kaminsky at infinitelocality.com> wrote: >> >> >> >>> Hi Sharath, >> >>> >> >>> Try rte_eth_stats_get, I think this should give you what you're >> looking >> >>> for. >> >>> >> >>> Regards, >> >>> Daniel >> >>> >> >>> >> >>> On Tue, Jan 28, 2014 at 7:29 AM, Sharath < >> sharathjm.bharadwaj at gmail.com>wrote: >> >>> >> hi ! >> >> can someone please tell me whether the DPDK provides any method to >> handle >> below >> >> a. account the packet drops at NIC level ? is there any interrupt >> raised by >> DPDK for the same ? >> b. to check fifo errors ? >> c. way to check rx and tx in sync >> >> Tx, >> -SB >> >> >>> >> >>> >> > >> > >
[dpdk-dev] [memnic PATCH] pmd: use memory barrier function instead of asm volatile
Hi Hiroshi-san, On 01/30/2014 12:42 PM, Hiroshi Shimamoto wrote: >> Subject: [dpdk-dev] [memnic PATCH] pmd: use memory barrier function instead >> of asm volatile > > By the way, I was also asked to use rte atomic function > instead of cmpxchg asm statement. > My re-submitted version in dpdk-ovs has such a change. > What do you think? Yes I agree about this change. Regards, Olivier
[dpdk-dev] How to debug packet sends to virtual functions
I have a follow-up on this: ixgbe version 3.13.10-k ixgbevf version 2.7.12-k (These are what was provided by Ubuntu 13.10) I tried the following sequence on the host, before starting the guest: 1) sudo rmmod ixgbe 2) sudo modprobe ixgbe max_vfs=2 3) sudo ifconfig em1 up # This is the physical function 4) sudo ifconfig em1_0 192.168.2.2 # This is the virtual function 5) ping 192.168.2.1 I can see that the ping request reaches its target, and a reply is sent back. But this reply is not received by the ping shell command. Why? Regards, Mats On Wed, Jan 29, 2014 at 6:56 PM, Mats Liljegren wrote: > I'm trying to get a modified version of the l2fwd example running, and > have problems with packets being silently thrown away. I can receive > packets, and my printf's indicates that the packets are being sent to > the correct port, using correct MAC address as source address. And > still, the packets are lost. > > Since the port is a virtual function, it seems like I cannot use > tcpdump on it to see the network traffic. There is nothing coming out > of the cable (activity light not flashing, the receiving end running > tcpdump does not see any traffic). > > I'm using two X540 with two virtual functions each. The application > runs in a KVM/Qemu environmen. > > Any suggestions how to debug this? > > Regards, > Mats
