DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Vithal S Mohare <vmohare@arubanetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_memcpy optimization patch to dpdk ver 1.7
Date: Tue, 24 Feb 2015 09:49:34 +0000	[thread overview]
Message-ID: <20150224094933.GB8416@bricha3-MOBL3> (raw)
In-Reply-To: <98DB008FA2AC6644B40AD8C766FAB271020CA6A3BE@BOREAL.arubanetworks.com>

On Tue, Feb 24, 2015 at 04:25:40AM +0000, Vithal S Mohare wrote:
> 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?  
> 
> -sh-3.2$ cat /proc/cpuinfo 
> 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 constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr popcnt lahf_lm
> 
> Thanks,
> -Vithal
> 

Hi Vithal,

Something doesn't seem right here. The i7-920 should support up to SSE4.2, 
therefore including ssse3. See:
http://ark.intel.com/products/37147/Intel-Core-i7-920-Processor-8M-Cache-2_66-GHz-4_80-GTs-Intel-QPI

Regards,
/Bruce

> -----Original Message-----
> From: Neil Horman [mailto:nhorman@tuxdriver.com] 
> 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 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
> > 
> > 
> > 

  reply	other threads:[~2015-02-24  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17  8:39 Vithal S Mohare
2015-02-17 13:01 ` Neil Horman
2015-02-18  4:09   ` Vithal S Mohare
2015-02-19 12:43     ` Neil Horman
2015-02-24  4:25       ` Vithal S Mohare
2015-02-24  9:49         ` Bruce Richardson [this message]
2015-02-24 11:30         ` Neil Horman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150224094933.GB8416@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=vmohare@arubanetworks.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).