DPDK patches and discussions
 help / color / mirror / Atom feed
From: Masaru Oki <m-oki@stratosphere.co.jp>
To: Yaron Illouz <yaroni@radcom.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] compile dpdk with no avx
Date: Wed, 12 Nov 2014 22:48:16 +0900	[thread overview]
Message-ID: <CAFLKUzK2iiZRTdRETujAX_sd2Jdp=uUwnMgHdQEA3dx9CxdRTQ@mail.gmail.com> (raw)
In-Reply-To: <1A791056FCD70F458405B58B79F5C2F7069C605F@RAD-W2KSRV11.radcom.co.il>

Hi,

Some libraries need AVX instruction, but if you don't use, it can disable.
  e.g. CONFIG_RTE_LIBRTE_IXGBE_PMD=n in config file.


2014-11-12 21:45 GMT+09:00 Yaron Illouz <yaroni@radcom.com>:
> Hi
>
>
>
> I use dpdk in my product. I can't change my dpdk version.
>
> I compile it on a server that have avx.
>
> Most of the time, it run on machine that have avx, but not always.
>
>
>
> When running the product on a machine with no avx, it crash on illegal
> instruction.
>
> The current solution is to build it on a computer with no avx.
>
>
>
> Is there a compilation flag to disable avx? So it doesn't matter on
> which computer I compiled it.
>
>
>
> Compile flag
>
> defconfig_x86_64-default-linuxapp-gcc
>
>
>
> Dpdk version
>
> PACKAGE_VERSION_MAJOR_NUMBER=1
>
> PACKAGE_VERSION_MINOR_NUMBER=6
>
> PACKAGE_VERSION_PATCH_NUMBER=0
>
> PACKAGE_VERSION_BUILD_NUMBER=18
>
>
>
> Gcc version
>
> gcc (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4)
>
>
>
> OS
>
> CentOS release 6.3 (Final)
>
>
>
>
>
>
>
>
>

  reply	other threads:[~2014-11-12 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 12:45 Yaron Illouz
2014-11-12 13:48 ` Masaru Oki [this message]
2014-11-12 14:24   ` De Lara Guarch, Pablo
2014-11-12 15:23     ` Neil Horman
2014-11-12 16:16       ` Bruce Richardson
2014-11-12 19: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='CAFLKUzK2iiZRTdRETujAX_sd2Jdp=uUwnMgHdQEA3dx9CxdRTQ@mail.gmail.com' \
    --to=m-oki@stratosphere.co.jp \
    --cc=dev@dpdk.org \
    --cc=yaroni@radcom.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).