From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: [PATCH 0/4] eal/common: introduce rte_memset and related test Date: Wed, 7 Dec 2016 17:37:42 +0800 Message-ID: <20161207093742.GF31182@yliu-dev.sh.intel.com> References: <1480926387-63838-1-git-send-email-zhiyong.yang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Maxime Coquelin , "dev@dpdk.org" , "Richardson, Bruce" , "Ananyev, Konstantin" , "Pierre Pfister (ppfister)" To: "Yang, Zhiyong" Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 5E0332B8F for ; Wed, 7 Dec 2016 10:36:59 +0100 (CET) Content-Disposition: inline In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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. > You know, memset(hdr, 0, head_size); only consumes fewer cycles for virtio pmd. > head_size only 10 or 12 bytes. > I optimize rte_memset perf further for N=8~15 bytes. > The main purpose of Introducing rte_memset is that we can use it > to avoid perf drop issue instead of glibc memset on some platform, I think. For this case (as well as the 4th patch), it's more about making sure rte_memset is inlined. --yliu