From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 94BB71E34 for ; Thu, 21 Feb 2019 18:45:45 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id CB66830B94EA; Thu, 21 Feb 2019 17:45:44 +0000 (UTC) Received: from [10.36.112.16] (ovpn-112-16.ams2.redhat.com [10.36.112.16]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C85E16090C; Thu, 21 Feb 2019 17:45:43 +0000 (UTC) To: Tiwei Bie , zhihong.wang@intel.com, dev@dpdk.org References: <20190219105951.31046-1-tiwei.bie@intel.com> From: Maxime Coquelin Message-ID: Date: Thu, 21 Feb 2019 18:45:42 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190219105951.31046-1-tiwei.bie@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.43]); Thu, 21 Feb 2019 17:45:44 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH 0/5] Fixes and enhancements for Tx path in Virtio PMD X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2019 17:45:45 -0000 On 2/19/19 11:59 AM, Tiwei Bie wrote: > Below is a quick (unofficial) performance test (macfwd loop, 64B) > for the packed ring optimizations in this series on an Intel(R) > Xeon(R) Gold 6140 CPU @ 2.30GHz platform: > > w/o this series: > packed ring normal/in-order: ~10.4 Mpps > > w/ this series: > packed ring normal: ~10.9 Mpps > packed ring in-order: ~11.3 Mpps > > In the test, we need to make sure that the vhost side is fast enough. > So 4 forwarding cores are used in vhost side, and 1 forwarding core is > used in virtio side. > > vhost side: > > ./x86_64-native-linuxapp-gcc/app/testpmd \ > -l 13,14,15,16,17 \ > --socket-mem 1024,0 \ > --file-prefix=vhost \ > --vdev=net_vhost0,iface=/tmp/vhost0,queues=4 \ > -- \ > --forward-mode=mac \ > -i \ > --rxq=4 \ > --txq=4 \ > --nb-cores 4 > > virtio side: > > ./x86_64-native-linuxapp-gcc/app/testpmd \ > -l 8,9,10,11,12 \ > --socket-mem 1024,0 \ > --single-file-segments \ > --file-prefix=virtio-user \ > --vdev=virtio_user0,path=/tmp/vhost0,queues=4,in_order=1,packed_vq=1 \ > -- \ > --forward-mode=mac \ > -i \ > --rxq=4 \ > --txq=4 \ > --nb-cores 1 > > > Tiwei Bie (5): > net/virtio: fix Tx desc cleanup for packed ring > net/virtio: fix in-order Tx path for split ring > net/virtio: fix in-order Tx path for packed ring > net/virtio: introduce a helper for clearing net header > net/virtio: optimize xmit enqueue for packed ring > > drivers/net/virtio/virtio_ethdev.c | 4 +- > drivers/net/virtio/virtio_rxtx.c | 203 ++++++++++++++++++++--------- > 2 files changed, 146 insertions(+), 61 deletions(-) > Applied to dpdk-next-virtio/master. Thanks, Maxime