DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vithal S Mohare <vmohare@arubanetworks.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_memcpy optimization patch to dpdk ver 1.7
Date: Wed, 18 Feb 2015 04:09:25 +0000	[thread overview]
Message-ID: <98DB008FA2AC6644B40AD8C766FAB271020CA68463@BOREAL.arubanetworks.com> (raw)
In-Reply-To: <20150217130131.GA2729@neilslaptop.think-freely.org>

Ok, crash, as expected.   So, now dpdk mandates either AVX2 or SSSE2 supported CPUs.   OR applications needs to handle it run-time.

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-18  4:09 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 [this message]
2015-02-19 12:43     ` Neil Horman
2015-02-24  4:25       ` Vithal S Mohare
2015-02-24  9:49         ` Bruce Richardson
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=98DB008FA2AC6644B40AD8C766FAB271020CA68463@BOREAL.arubanetworks.com \
    --to=vmohare@arubanetworks.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.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).