[dpdk-users] RTE_MACHINE_TYPE Error

Wiles, Keith keith.wiles at intel.com
Tue Oct 9 21:59:09 CEST 2018



> On Oct 9, 2018, at 9:56 AM, Cliff Burdick <shaklee3 at gmail.com> wrote:
> 
> 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!

Ok great.

> 
> On Tue, Oct 9, 2018 at 7:37 AM Cliff Burdick <shaklee3 at 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 at intel.com> wrote:
> 
> 
> > On Oct 8, 2018, at 11:10 PM, Cliff Burdick <shaklee3 at 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
> 

Regards,
Keith



More information about the users mailing list