From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <nhorman@tuxdriver.com>
Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58])
 by dpdk.org (Postfix) with ESMTP id BB674B53A
 for <dev@dpdk.org>; Thu, 19 Feb 2015 13:43:26 +0100 (CET)
Received: from hmsreliant.think-freely.org
 ([2001:470:8:a08:7aac:c0ff:fec2:933b] helo=localhost)
 by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63)
 (envelope-from <nhorman@tuxdriver.com>)
 id 1YOQRv-0002zb-C7; Thu, 19 Feb 2015 07:43:25 -0500
Date: Thu, 19 Feb 2015 07:43:22 -0500
From: Neil Horman <nhorman@tuxdriver.com>
To: Vithal S Mohare <vmohare@arubanetworks.com>
Message-ID: <20150219124322.GA24069@hmsreliant.think-freely.org>
References: <98DB008FA2AC6644B40AD8C766FAB271020CA67F5E@BOREAL.arubanetworks.com>
 <20150217130131.GA2729@neilslaptop.think-freely.org>
 <98DB008FA2AC6644B40AD8C766FAB271020CA68463@BOREAL.arubanetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <98DB008FA2AC6644B40AD8C766FAB271020CA68463@BOREAL.arubanetworks.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Score: -2.9 (--)
X-Spam-Status: No
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_memcpy optimization patch to dpdk ver 1.7
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2015 12:43:27 -0000

On Wed, Feb 18, 2015 at 04:09:25AM +0000, Vithal S Mohare wrote:
> Ok, crash, as expected.   So, now dpdk mandates either AVX2 or SSSE2 supported CPUs.   OR applications needs to handle it run-time.
> 
No, sse3 is the minimum, but I think thats been the case for quite some time
now, I think.

Neil

> Thanks,
> -Vithal
> 
> -----Original Message-----
> From: Neil Horman [mailto:nhorman@tuxdriver.com] 
> Sent: Tuesday, February 17, 2015 6:32 PM
> To: Vithal S Mohare
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] rte_memcpy optimization patch to dpdk ver 1.7
> 
> On Tue, Feb 17, 2015 at 08:39:22AM +0000, Vithal S Mohare wrote:
> > Hi,
> > 
> > I am trying to use rte_memcpy optimization patch along with dpdk version 1.7.  With the patch, while dpdk itself is compiled, applications failed with below error:
> > -------------------------------
> > include/rte_memcpy.h:629:2: error: implicit declaration of function 
> > '_mm_alignr_epi8' [-Werror=implicit-function-declaration]
> > /home/vithals/adu_src/build/x-men_dev/Default/shumway/infra/dpdk/shumway_obj/lib/../include/rte_memcpy.h:629:2: error: incompatible type for argument 2 of '_mm_storeu_si128'
> > -------------------------------
> > 
> > After including -mssse3 flags, compilation (cross compiled for a x86 linux based platform) went through.  Now the question is, when this binary is loaded on system that doesn't support SSSE3 instruction set (but just sse2 etc), what would be the behavior?
> > 
> A crash.  You'll attempt to send an unknown binary instruction into the execution pipeline and the processor will fault.
> 
> Neil
> 
> 
>