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 0EC33A0679 for ; Fri, 5 Apr 2019 08:42:06 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 031741B445; Fri, 5 Apr 2019 08:42:05 +0200 (CEST) Received: from mail.altencalsoftlabs.com (mail.altencalsoftlabs.com [182.73.72.41]) by dpdk.org (Postfix) with ESMTP id D746D1B442 for ; Fri, 5 Apr 2019 08:42:02 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.altencalsoftlabs.com (Postfix) with ESMTP id E896C4420022; Fri, 5 Apr 2019 12:12:01 +0530 (IST) Received: from mail.altencalsoftlabs.com ([127.0.0.1]) by localhost (mail.altencalsoftlabs.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id e_C_ii4ad-Us; Fri, 5 Apr 2019 12:12:01 +0530 (IST) Received: from localhost (localhost [127.0.0.1]) by mail.altencalsoftlabs.com (Postfix) with ESMTP id 877F6442001E; Fri, 5 Apr 2019 12:12:01 +0530 (IST) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.altencalsoftlabs.com 877F6442001E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=altencalsoftlabs.com; s=selector; t=1554446521; bh=uzFr+qTH+KkhbearbqG/oK4V48MIOVOWq3NZwGYtmf0=; h=To:From:Message-ID:Date:MIME-Version; b=0hDojkYOs7T+6S+DDoXlgjSG8bBZF/xlhYtT7JryElrOz7snS3FJS0of5d4hQHdFA abJjPnkBlHal9prk17gxJ5DIKziC4dMR84lYQiBL8Z9Lc52k6CmRtpGd0dhJPr0jRX YnE2h4o4UNW8IoX4HSLZQO0+WN5PfjOaT9p/rwL8= X-Virus-Scanned: amavisd-new at altencalsoftlabs.com Received: from mail.altencalsoftlabs.com ([127.0.0.1]) by localhost (mail.altencalsoftlabs.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id pjNRwo-upEm1; Fri, 5 Apr 2019 12:12:01 +0530 (IST) Received: from [172.23.103.233] (unknown [10.1.0.4]) by mail.altencalsoftlabs.com (Postfix) with ESMTPSA id 3D9DA4420009; Fri, 5 Apr 2019 12:12:01 +0530 (IST) To: Stephen Hemminger , users@dpdk.org References: <9beaa13f-239a-5361-81ea-20d5237bf1be@altencalsoftlabs.com> <8cf0736f-29d8-1ce7-ea77-83f091cd666f@altencalsoftlabs.com> <20190404084110.76def58a@shemminger-XPS-13-9360> From: Sharon Message-ID: Date: Fri, 5 Apr 2019 12:12:00 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20190404084110.76def58a@shemminger-XPS-13-9360> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [dpdk-users] Tx burst getting failed with Virtio driver 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, Regarding pps, 6 Gbps comes around to be less than 0.6 Mpps with packet size 1300 Bytes. Also, in a GCP VM instance, virtio is able to process 10 Gbps easily with 5-6 cores. (without DPDK) Kindly advice. Thanks & Regards, Sharon T N On 04/04/19 9:11 PM, Stephen Hemminger wrote: > On Thu, 4 Apr 2019 13:01:16 +0530 > Sharon wrote: > >> Hi, >> >> With a dpdk based application inside GCP VM instance, >> it is observed that while sending UDP packets of length 1300 at around 6 >> Gbps rate, tx burst starts failing frequently. > Virtio (like all devices) can only transmit so fast. > If you transmit faster than the host can consume, the queue will get full > this shows up in DPDK when all transmit descriptors are used. > > 6Gbps is about 4.4 Mpps and the upper bound on virtio is usually about 1 to 2 Mpps > because of the overhead of host processing (vhost and linux bridge). >