DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_memcpy.h: additional cflags required with OVS
Date: Mon, 9 Mar 2015 17:51:23 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2ECC6E8@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <DC5AD7FA266D86499789B1BCAEC715F846D4EB43@irsmsx105.ger.corp.intel.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kavanagh, Mark B
> Sent: Monday, March 9, 2015 4:44 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] rte_memcpy.h: additional cflags required with OVS
> 
> Compilation of Open vSwitch fails when linked against current HEAD of DPDK
> (f2552cd5).
> 
> The source of this issue appears to be commit ID 9144d6b: "eal/x86:
> optimize memcpy for SSE and AVX", and can be resolved by passing an
> additional argument to OVS when building same (CFLAGS="-march=native").
> It seems that without this flag, OVS doesn't pick up one or more SSE
> #defines in DPDK, and doesn't include a relevant intrinsic header
> (emmintrin.h), leading to an 'implicit declaration' error for instrinsic
> '_mm_storeu_si128'.
> 
> Has anyone else observed this behavior?

Hi Mark,

I can confirm that behavior and that it was introduced by the new optimized memcpy. I'll look into how it might be mitigated, for Open VSwitch with DPDK.

In the meantime the following might work for OVS:

    $ ./configure CFLAGS='-Wno-bad-function-cast -march=native' --with-dpdk=$DPDK_BUILD
    $ make

But I'll look into it in more detail and update.

John
-- 

  reply	other threads:[~2015-03-09 17:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 16:44 Kavanagh, Mark B
2015-03-09 17:51 ` Mcnamara, John [this message]
2015-03-10  0:57   ` Mcnamara, John
2015-03-10  3:00     ` Qiu, Michael
2015-03-10  9:16     ` Kavanagh, Mark B
2015-03-10  3:04 ` Qiu, Michael
2015-03-10  7:52   ` Panu Matilainen
2015-03-10  8:27   ` Mcnamara, John
2015-03-10 10:03     ` Kavanagh, Mark B
2015-03-11  4:37       ` Wang, Zhihong
2015-03-11  8:06         ` Mcnamara, John

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=B27915DBBA3421428155699D51E4CFE2ECC6E8@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=mark.b.kavanagh@intel.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).