From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jose Gavine Cueto <pepedocs@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] intel x540-at2
Date: Sun, 05 Jan 2014 15:54:51 +0100 [thread overview]
Message-ID: <1734676.i5HPyu6JDa@x220> (raw)
In-Reply-To: <CAJ5bv6HntjZH_SO9VBTAc06QAYr-m-HwaxKoTWSmJZgcqnTXhg@mail.gmail.com>
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
next prev parent reply other threads:[~2014-01-05 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 9:18 Jose Gavine Cueto
2014-01-02 14:24 ` Thomas Monjalon
2014-01-03 9:09 ` Jose Gavine Cueto
2014-01-03 9:16 ` Jose Gavine Cueto
2014-01-03 9:56 ` Thomas Monjalon
2014-01-03 10:09 ` Jose Gavine Cueto
2014-01-03 10:26 ` Thomas Monjalon
2014-01-03 10:31 ` Jose Gavine Cueto
2014-01-03 13:43 ` Venkatesan, Venky
2014-01-03 13:59 ` Thomas Monjalon
2014-01-05 14:31 ` Jose Gavine Cueto
2014-01-05 14:54 ` Thomas Monjalon [this message]
2014-01-06 6:03 ` Jose Gavine Cueto
2014-01-08 6:13 ` Jose Gavine Cueto
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=1734676.i5HPyu6JDa@x220 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=pepedocs@gmail.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).