From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by dpdk.org (Postfix) with ESMTP id 88D3E8D97 for ; Mon, 18 Jan 2016 21:06:22 +0100 (CET) Received: by mail-pa0-f54.google.com with SMTP id ho8so177832031pac.2 for ; Mon, 18 Jan 2016 12:06:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=/1+RVrXqSkWXDjOCY7stqwhCFJSxuBuaNIkD1PP0V9s=; b=P66iwrO0cZvUD4p2W1y3OcAA4OkkntcBgwYeF0Nt5F82jFtwrnVXNXMykLNw4/caDO mcBzwIFEBPQV//pgz29lKN1D0lF9FVLO8EhYPe+kttidOJ5vPBFeHReNw+boexNTsaOX 2i1WxEzlWgT8kwep+pAFwtX5Ao37AeMDIauXC0OrChAG5WiuxaiG5j1+rh9DxfzD8Ob2 aeCiYlCNSzhUecIkhvCCRZsfa6LI+H2g4RY7IgVKjGO/thuxLgNI8fDvwopCmCbsdGe5 QKtLioIYfSIm0qlAkCsWIk4yO4p1hHfFxfkGDLJ32UFHXv8biWJgXNJd1CCKifg4KSOB 6mvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=/1+RVrXqSkWXDjOCY7stqwhCFJSxuBuaNIkD1PP0V9s=; b=iM8LlB10ueda7T6NGhPMoBaeqrYbkSAcmTQl/adjVpCgrLFd8tUsk5VAWjGoW6cMRJ qd8oUXy8uXCssWqf3LnlzgDfgdQiyri+90X8gF99A72GFfClfOG/ieHfxy/qOnjuDqtW bi6Apl6WK7Mj4LagLQ+4vSkDFFxxrpz7QDHzzN4FhQdmdqCPHeubFXrxZX7BlAV6DeXZ hDP/ubwY4WdnNiGwe1rccAvfD1ATjqvEYM8pJstLe6eMRUKkLoc6hu/4LgTd5z3eMmmb lr5L77A2X2i8666WL6Xto0z5HzTocOUGTi3pEDfBsgUIbqsr86mZPiOSAfq/0VSuoj9N ev0Q== X-Gm-Message-State: ALoCoQnaXfNJ75leTprAYyo75NNglsIzA4QkRZxLR4jqZLiReifS9mmIGb+7PC7a65NSE1HyZUn6qjW1dhd+Ftr2PfqmeQ/qNg== X-Received: by 10.66.216.69 with SMTP id oo5mr38173096pac.126.1453147581615; Mon, 18 Jan 2016 12:06:21 -0800 (PST) Received: from xeon-e3 (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by smtp.gmail.com with ESMTPSA id ze5sm36037145pac.32.2016.01.18.12.06.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jan 2016 12:06:21 -0800 (PST) Date: Mon, 18 Jan 2016 12:06:29 -0800 From: Stephen Hemminger To: Zhihong Wang Message-ID: <20160118120629.5ed7bcd9@xeon-e3> In-Reply-To: <1453086314-30158-1-git-send-email-zhihong.wang@intel.com> References: <1452752002-107586-1-git-send-email-zhihong.wang@intel.com> <1453086314-30158-1-git-send-email-zhihong.wang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2 0/5] Optimize memcpy for AVX512 platforms X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2016 20:06:22 -0000 On Sun, 17 Jan 2016 22:05:09 -0500 Zhihong Wang wrote: > This patch set optimizes DPDK memcpy for AVX512 platforms, to make full > utilization of hardware resources and deliver high performance. > > In current DPDK, memcpy holds a large proportion of execution time in > libs like Vhost, especially for large packets, and this patch can bring > considerable benefits. > > The implementation is based on the current DPDK memcpy framework, some > background introduction can be found in these threads: > http://dpdk.org/ml/archives/dev/2014-November/008158.html > http://dpdk.org/ml/archives/dev/2015-January/011800.html > > Code changes are: > > 1. Read CPUID to check if AVX512 is supported by CPU > > 2. Predefine AVX512 macro if AVX512 is enabled by compiler > > 3. Implement AVX512 memcpy and choose the right implementation based on > predefined macros > > 4. Decide alignment unit for memcpy perf test based on predefined macros Cool, I like it. How much impact does this have on VHOST?