From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx01.arubanetworks.com (mx01.arubanetworks.com [104.36.248.59]) by dpdk.org (Postfix) with ESMTP id 50087ADA9 for ; Tue, 24 Feb 2015 05:25:43 +0100 (CET) X-ASG-Debug-ID: 1424751941-03d124379d143bb10001-TfluYd Received: from sjc-exch10hc-02.arubanetworks.com (sjc-exch10hc-02.arubanetworks.com [10.1.8.46]) by mx01.arubanetworks.com with ESMTP id QgQaOA61GRIDe89B (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Mon, 23 Feb 2015 20:25:41 -0800 (PST) X-Barracuda-Envelope-From: vmohare@arubanetworks.com Received: from BOREAL.arubanetworks.com ([fe80::19f0:d3af:7377:a759]) by sjc-exch10hc-02.arubanetworks.com ([fe80::88ce:11e3:e0a3:1489%16]) with mapi id 14.03.0158.001; Mon, 23 Feb 2015 20:25:41 -0800 From: Vithal S Mohare To: Neil Horman Thread-Topic: [dpdk-dev] rte_memcpy optimization patch to dpdk ver 1.7 X-ASG-Orig-Subj: RE: [dpdk-dev] rte_memcpy optimization patch to dpdk ver 1.7 Thread-Index: AdBKZLThvvzjc57ZRGSwSpbpiPzVeQAkDKeAAA3PvnAAViMxAADZMOBw Date: Tue, 24 Feb 2015 04:25:40 +0000 Message-ID: <98DB008FA2AC6644B40AD8C766FAB271020CA6A3BE@BOREAL.arubanetworks.com> References: <98DB008FA2AC6644B40AD8C766FAB271020CA67F5E@BOREAL.arubanetworks.com> <20150217130131.GA2729@neilslaptop.think-freely.org> <98DB008FA2AC6644B40AD8C766FAB271020CA68463@BOREAL.arubanetworks.com> <20150219124322.GA24069@hmsreliant.think-freely.org> In-Reply-To: <20150219124322.GA24069@hmsreliant.think-freely.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.20.22.62] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: sjc-exch10hc-02.arubanetworks.com[10.1.8.46] X-Barracuda-Start-Time: 1424751941 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-URL: https://mx01.arubanetworks.com:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at arubanetworks.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.15754 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2015 04:25:43 -0000 Hi Neil, While most of the newer CPUs supports ssse3, found a I7 not supporting it= . So, DPDK can't run these CPUs? Is this restriction acceptable? =20 -sh-3.2$ cat /proc/cpuinfo=20 processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping : 5 cpu MHz : 2660.068 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat = pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx rdtscp lm cons= tant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr popcnt lahf_lm Thanks, -Vithal -----Original Message----- From: Neil Horman [mailto:nhorman@tuxdriver.com]=20 Sent: Thursday, February 19, 2015 6:13 PM To: Vithal S Mohare Cc: dev@dpdk.org Subject: Re: [dpdk-dev] rte_memcpy optimization patch to dpdk ver 1.7 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 supp= orted CPUs. OR applications needs to handle it run-time. >=20 No, sse3 is the minimum, but I think thats been the case for quite some tim= e now, I think. Neil > Thanks, > -Vithal >=20 > -----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 >=20 > On Tue, Feb 17, 2015 at 08:39:22AM +0000, Vithal S Mohare wrote: > > Hi, > >=20 > > I am trying to use rte_memcpy optimization patch along with dpdk versio= n 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=20 > > '_mm_alignr_epi8' [-Werror=3Dimplicit-function-declaration] > > /home/vithals/adu_src/build/x-men_dev/Default/shumway/infra/dpdk/shumwa= y_obj/lib/../include/rte_memcpy.h:629:2: error: incompatible type for argum= ent 2 of '_mm_storeu_si128' > > ------------------------------- > >=20 > > After including -mssse3 flags, compilation (cross compiled for a x86 li= nux 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? > >=20 > A crash. You'll attempt to send an unknown binary instruction into the e= xecution pipeline and the processor will fault. >=20 > Neil >=20 >=20 >=20