From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 19690A00E6 for ; Wed, 20 Mar 2019 10:22:28 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 01DF92956; Wed, 20 Mar 2019 10:22:28 +0100 (CET) Received: from ls405.t-com.hr (ls405.t-com.hr [195.29.150.135]) by dpdk.org (Postfix) with ESMTP id 5051811A4 for ; Wed, 20 Mar 2019 10:22:26 +0100 (CET) Received: from ls265.t-com.hr (ls265.t-com.hr [195.29.150.93]) by ls405.t-com.hr (Postfix) with ESMTP id 0282F698861 for ; Wed, 20 Mar 2019 10:22:26 +0100 (CET) Received: from ls265.t-com.hr (localhost.localdomain [127.0.0.1]) by ls265.t-com.hr (Qmlai) with ESMTP id E8B6A2110267 for ; Wed, 20 Mar 2019 10:22:25 +0100 (CET) X-Envelope-Sender: hrvoje.habjanic@zg.ht.hr Received: from habix.doma (93-136-40-251.adsl.net.t-com.hr [93.136.40.251]) by ls265.t-com.hr (Qmali) with ESMTP id 9B56D20B02A6 for ; Wed, 20 Mar 2019 10:22:25 +0100 (CET) Received: from [192.168.10.192] (habi-doma.doma [192.168.10.192]) by habix.doma (Postfix) with ESMTPSA id 89FB71C1 for ; Wed, 20 Mar 2019 10:22:25 +0100 (CET) To: users@dpdk.org From: Hrvoje Habjanic Message-ID: Date: Wed, 20 Mar 2019 10:22:24 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-TM-AS-Product-Ver: IMSS-7.1.0.1224-8.2.0.1013-24398.003 X-TM-AS-Result: No--8.586-10.0-31-1 X-imss-scan-details: No--8.586-10.0-31-1 X-TM-AS-User-Approved-Sender: No Subject: [dpdk-users] DPDK TX problems X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi. I did write an application using dpdk 17.11 (did try also with 18.11), and when doing some performance testing, i'm seeing very odd behavior. To verify that this is not because of my app, i did the same test with l2fwd example app, and i'm still confused by results. In short, i'm trying to push a lot of L2 packets through dpdk engine - packet processing is minimal. When testing, i'm starting with small number of packets-per-second, and then gradually increase it to see where is the limit. At some point, i do reach this limit - packets start to get dropped. And this is when stuff become weird. When i reach peek packet rate (at which packets start to get dropped), i would expect that reducing packet rate will remove packet drops. But, this is not the case. For example, let's assume that peek packet rate is 3.5Mpps. At this point everything works ok. Increasing pps to 4.0Mpps, makes a lot of dropped packets. When reducing pps back to 3.5Mpps, app is still broken - packets are still dropped. At this point, i need to drastically reduce pps (1.4Mpps) to make dropped packets go away. Also, app is unable to successfully forward anything beyond this 1.4M, despite the fact that in the beginning it did forward 3.5M! Only way to recover is to restart the app. Also, sometimes, the app just stops forwarding any packets - packets are received (as seen by counters), but app is unable to send anything back. As i did mention, i'm seeing the same behavior with l2fwd example app. I did test dpdk 17.11 and also dpdk 18.11 - the results are the same. My test environment is HP DL380G8, with 82599ES 10Gig (ixgbe) cards, connected with Cisco nexus 9300 sw. On the other side is ixia test appliance. Application is run in virtual machine (VM), using KVM (openstack, with sriov enabled, and numa restrictions). I did check that VM is using only cpu's from NUMA node on which network card is connected, so there is no cross-numa traffic. Openstack is Queens, Ubuntu is Bionic release. Virtual machine is also using ubuntu bionic as OS. I do not know how to debug this? Does someone else have the same observations? Regards, H.