[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dpdk-dev
Subject:    [dpdk-dev] Fwd: OVS with DPDK ..Error packets
From:       kevin.traynor () intel ! com (Traynor, Kevin)
Date:       2015-07-31 8:02:18
Message-ID: BC0FEEC7D7650749874CEC11314A88F7451CB0A8 () IRSMSX104 ! ger ! corp ! intel ! com
[Download RAW message or body]


> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Srikanth Akula
> Sent: Wednesday, July 29, 2015 10:32 PM
> To: dev at dpdk.org; dev at openvswitch.org
> Subject: [dpdk-dev] Fwd: OVS with DPDK ..Error packets
> 
> (+DPDK dev team )
> 
> 
> Hello ,
> 
> I am trying to test the OVS_DPDK performance and found that lot of packets
> being treated as error packets .
> 
> ovs-vsctl get Interface dpdk0 statistics
> {collisions=0, rx_bytes=38915076374, rx_crc_err=0, rx_dropped=0,
> *rx_errors=3840287219
> <3840287219>, *rx_frame_err=0, rx_over_err=0, rx_packets=292972799,
> tx_bytes=38935883904, tx_dropped=0, tx_errors=0, tx_packets=293068162}
> 
> I am running DPDK application inside my VM .
> 
> Looks like there is a buffer issue ( 64Bytes - 10Gbps)
> 
> Could  somebody let me know if i have missed any configuration in DPDK/OVS ?

Errors can show here when you are sending traffic in at a rate higher than can
be handled, so it can be normal to see that in some cases. 

First thing I would check is that you have your PMD(s) and qemu threads doing
the fwding core affinitised to different cores so they get the max amount of
cycles they can. 

I would also check a simple phy-phy test to eliminate any test equipment/NIC
setup issues.

> 
> -Srikanth

[prev in list] [next in list] [prev in thread] [next in thread]