* [dpdk-users] RTE_MACHINE_TYPE Error @ 2018-10-09 4:10 Cliff Burdick 2018-10-09 13:54 ` Wiles, Keith 0 siblings, 1 reply; 7+ messages in thread From: Cliff Burdick @ 2018-10-09 4:10 UTC (permalink / raw) To: users 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? ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] RTE_MACHINE_TYPE Error 2018-10-09 4:10 [dpdk-users] RTE_MACHINE_TYPE Error Cliff Burdick @ 2018-10-09 13:54 ` Wiles, Keith 2018-10-09 14:37 ` Cliff Burdick 0 siblings, 1 reply; 7+ messages in thread From: Wiles, Keith @ 2018-10-09 13:54 UTC (permalink / raw) To: Cliff Burdick; +Cc: users > 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] RTE_MACHINE_TYPE Error 2018-10-09 13:54 ` Wiles, Keith @ 2018-10-09 14:37 ` Cliff Burdick 2018-10-09 14:56 ` Cliff Burdick 2018-10-09 19:58 ` Wiles, Keith 0 siblings, 2 replies; 7+ messages in thread From: Cliff Burdick @ 2018-10-09 14:37 UTC (permalink / raw) To: keith.wiles; +Cc: users 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 > > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] RTE_MACHINE_TYPE Error 2018-10-09 14:37 ` Cliff Burdick @ 2018-10-09 14:56 ` Cliff Burdick 2018-10-09 19:59 ` Wiles, Keith 2018-10-09 19:58 ` Wiles, Keith 1 sibling, 1 reply; 7+ messages in thread From: Cliff Burdick @ 2018-10-09 14:56 UTC (permalink / raw) To: keith.wiles; +Cc: users 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 >> >> ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] RTE_MACHINE_TYPE Error 2018-10-09 14:56 ` Cliff Burdick @ 2018-10-09 19:59 ` Wiles, Keith 2018-10-09 20:45 ` Cliff Burdick 0 siblings, 1 reply; 7+ messages in thread From: Wiles, Keith @ 2018-10-09 19:59 UTC (permalink / raw) To: Cliff Burdick; +Cc: users, Richardson, Bruce, Ananyev, Konstantin > On Oct 9, 2018, at 9:56 AM, Cliff Burdick <shaklee3@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@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 > Regards, Keith ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] RTE_MACHINE_TYPE Error 2018-10-09 19:59 ` Wiles, Keith @ 2018-10-09 20:45 ` Cliff Burdick 0 siblings, 0 replies; 7+ messages in thread From: Cliff Burdick @ 2018-10-09 20:45 UTC (permalink / raw) To: keith.wiles; +Cc: users, bruce.richardson, konstantin.ananyev It was my mistake. It's a server haswell processor, but the BIOS had AES-NI disabled. I enabled it, recompiled with CONFIG_RTE_MACHINE="haswell", and it works great now. Thanks! On Tue, Oct 9, 2018 at 1:00 PM Wiles, Keith <keith.wiles@intel.com> wrote: > > > > On Oct 9, 2018, at 9:56 AM, Cliff Burdick <shaklee3@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@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 > > > > Regards, > Keith > > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] RTE_MACHINE_TYPE Error 2018-10-09 14:37 ` Cliff Burdick 2018-10-09 14:56 ` Cliff Burdick @ 2018-10-09 19:58 ` Wiles, Keith 1 sibling, 0 replies; 7+ messages in thread From: Wiles, Keith @ 2018-10-09 19:58 UTC (permalink / raw) To: Cliff Burdick; +Cc: users, Richardson, Bruce, Ananyev, Konstantin > On Oct 9, 2018, at 9: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? Not all the Haswell CPUs are the same and some SKUs do not have some features. Did you try with the haswell machine instead of the broadwell, if that does not work I am going to need to talk to someone that knows. I assume Bruce or Konstantin know the answer. Do not expect a reply until they get to the office in Ireland. > > > > > 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 > Regards, Keith ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2018-10-09 20:45 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-10-09 4:10 [dpdk-users] RTE_MACHINE_TYPE Error Cliff Burdick 2018-10-09 13:54 ` Wiles, Keith 2018-10-09 14:37 ` Cliff Burdick 2018-10-09 14:56 ` Cliff Burdick 2018-10-09 19:59 ` Wiles, Keith 2018-10-09 20:45 ` Cliff Burdick 2018-10-09 19:58 ` Wiles, Keith
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).