From: Cliff Burdick <shaklee3@gmail.com>
To: keith.wiles@intel.com
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] RTE_MACHINE_TYPE Error
Date: Tue, 9 Oct 2018 07:56:46 -0700 [thread overview]
Message-ID: <CA+Gp1nZTTCrd8EvyjoYHjWHakSwTyVtx810KBirnHELaSM1duQ@mail.gmail.com> (raw)
In-Reply-To: <CA+Gp1nZV_Py8g_VNpBNEEW+VaS=UTJ1DTKBT2+xTG-YA1chs0A@mail.gmail.com>
I think I answered my own question -- the motherboards we're using had
AES-NI disabled in the BIOS, so DPDK was correctly not seeing it enabled
even though the processor supports it. I enabled it in the BIOS and it's
working properly now. Thanks again Keith!
On Tue, Oct 9, 2018 at 7:37 AM Cliff Burdick <shaklee3@gmail.com> wrote:
> Thanks Keith. You are right that /proc/cpuinfo on a E5-2680 v3 does not
> have AES listed. I was incorrect assuming this was a broadwell system, but
> it's Haswell. Either way, I'm still not quite clear what's going on since
> the gcc manual here (https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html)
> specifies this:
>
> ‘haswell’
>
> Intel Haswell CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3,
> SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND,
> FMA, BMI, BMI2 and F16C instruction set support.
>
> Is the gcc manual specifying some other AES feature that's not what DPDK
> is listing?
>
>
>
> On Tue, Oct 9, 2018 at 6:54 AM Wiles, Keith <keith.wiles@intel.com> wrote:
>
>>
>>
>> > On Oct 8, 2018, at 11:10 PM, Cliff Burdick <shaklee3@gmail.com> wrote:
>> >
>> > Hi, I'm trying to compile on a machine with an older-generation xeon
>> than
>> > the target, so I'm using CONFIG_RTE_MACHINE="broadwell" in the config.
>> > gcc's options show that broadwell supports the AES flag, and I verified
>> > that the build shows -march=broadwell. However, when I run my
>> application
>> > it prints immediately:
>> >
>> > ERROR: This system does not support "AES".
>> > Please check that RTE_MACHINE is set correctly.
>> > EAL: FATAL: unsupported cpu type.
>> > EAL: unsupported cpu type.
>> > EAL: Error - exiting with code: 1
>> > Cause: Error with EAL initialization
>> >
>> > This is gcc 7, so it supports that flag. Does anyone know how I can
>> compile
>> > for a later architecture on an older machine?
>>
>> Have you checked to make sure the CPU does support the feature by looking
>> that the CPU flags in /proc/cpuinfo ?
>>
>> Normally this is the reason the code will not run is the CPU does not
>> support it.
>>
>> Regards,
>> Keith
>>
>>
next prev parent reply other threads:[~2018-10-09 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 4:10 Cliff Burdick
2018-10-09 13:54 ` Wiles, Keith
2018-10-09 14:37 ` Cliff Burdick
2018-10-09 14:56 ` Cliff Burdick [this message]
2018-10-09 19:59 ` Wiles, Keith
2018-10-09 20:45 ` Cliff Burdick
2018-10-09 19:58 ` Wiles, Keith
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=CA+Gp1nZTTCrd8EvyjoYHjWHakSwTyVtx810KBirnHELaSM1duQ@mail.gmail.com \
--to=shaklee3@gmail.com \
--cc=keith.wiles@intel.com \
--cc=users@dpdk.org \
/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).