From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id CF849370 for ; Wed, 7 Dec 2016 10:47:36 +0100 (CET) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga105.fm.intel.com with ESMTP; 07 Dec 2016 01:47:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,310,1477983600"; d="scan'208";a="39932844" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by fmsmga006.fm.intel.com with ESMTP; 07 Dec 2016 01:47:34 -0800 Date: Wed, 7 Dec 2016 17:48:20 +0800 From: Yuanhan Liu To: "Yang, Zhiyong" Cc: Maxime Coquelin , "dev@dpdk.org" , "Richardson, Bruce" , "Ananyev, Konstantin" , "Pierre Pfister (ppfister)" Message-ID: <20161207094820.GI31182@yliu-dev.sh.intel.com> References: <1480926387-63838-1-git-send-email-zhiyong.yang@intel.com> <20161207093742.GF31182@yliu-dev.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH 0/4] eal/common: introduce rte_memset and related test 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: Wed, 07 Dec 2016 09:47:37 -0000 On Wed, Dec 07, 2016 at 09:43:06AM +0000, Yang, Zhiyong wrote: > > On Wed, Dec 07, 2016 at 09:28:17AM +0000, Yang, Zhiyong wrote: > > > > >> Wouldn't be worth to also use rte_memset in Virtio PMD (not > > > > >> compiled/tested)? : > > > > >> > > > > > > > > > > I think rte_memset maybe can bring some benefit here, but , I'm > > > > > not clear how to enter the branch and test it. :) > > > > > > > > Indeed, you will need Pierre's patch: > > > > [dpdk-dev] [PATCH] virtio: tx with can_push when VERSION_1 is set > > > > I will apply it shortly. > > > > > > Thanks, > > > > Maxime > > > > > > > > Thank you Maxime. > > > I can see a little, but not obviously performance improvement here. > > > > Are you you have run into that code piece? FYI, you have to enable virtio 1.0 > > explicitly, which is disabled by deafault. > > Yes. I use the patch from Pierre and set offload = 0 ; I meant virtio 1.0. Have you added following options for the QEMU virtio-net device? disable-modern=false --yliu