Re: [dpdk-dev] intel x540-at2

[Jose Gavine Cueto <pepedocs@gmail.com>]

Hi Thomas,

On Sun, Jan 5, 2014 at 10:54 PM, Thomas Monjalon
<thomas.monjalon@6wind.com>wrote:

> 05/01/2014 22:31, Jose Gavine Cueto :
> > venky.venkatesan@intel.com> wrote:
> > > Was the DPDK library compiled on a different machine and the used in
> the
> > > VM? It looks like it has been compiled for native AVX (hence the
> > > vzeroupper). Could you dump cpuinfo in the VM and see what instruction
> set
> > > the VM supports?
> >
> > Yes, it was compiled in a different machine and it was used in my VM.
> [...]
> > model name      : Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz
> > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca
> > cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm
> constant_tsc
> > rep_good nopl pni monitor ssse3 lahf_lm
> [...]
> >  It seems that there is no avx here, does this mean this doesn't support
> > avx instructions ?
>
> Yes, you have no avx on this machine.
> Tip to clearly check this type of flag:
>         grep --color -m1 avx /proc/cpuinfo
>
> So, you have 2 solutions:
> 1) build DPDK on this machine
> 2) build DPDK for a default machine:
>         CONFIG_RTE_MACHINE=default
> defconfig files are wrongly called "default" but have CONFIG_RTE_MACHINE
> set to
> native. So the compilation flags are guessed from /proc/cpuinfo. You can
> look
> for AUTO_CPUFLAGS to better understand it.
>
> --
> Thomas
>

Thanks and I will try your suggestion.  I will also post the result
whenever it is available, for the meantime I will be rebuilding the DPDK
lib.

Cheers,
Pepe

-- 
To stop learning is like to stop loving.