From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"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: Tue, 10 Mar 2015 00:57:18 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2ECC997@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2ECC6E8@IRSMSX103.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mcnamara, John
> Sent: Monday, March 9, 2015 5:51 PM
> To: Kavanagh, Mark B; dev@dpdk.org
> Subject: Re: [dpdk-dev] rte_memcpy.h: additional cflags required with OVS
>> In the meantime the following might work for OVS:
>>
>> $ ./configure CFLAGS='-Wno-bad-function-cast -march=native' --with-
>> dpdk=$DPDK_BUILD
>> $ make
>>
>>
Hi,
It will also need a patch like the following to netdev-dpdk to account for changes in the RSS flags:
$ git diff
diff --git a/lib/netdev-dpdk.c b/lib/netdev-dpdk.c
index 1ba8310..90dd06f 100644
--- a/lib/netdev-dpdk.c
+++ b/lib/netdev-dpdk.c
@@ -97,8 +97,7 @@ static const struct rte_eth_conf port_conf = {
.rx_adv_conf = {
.rss_conf = {
.rss_key = NULL,
- .rss_hf = ETH_RSS_IPV4_TCP | ETH_RSS_IPV4 | ETH_RSS_IPV6
- | ETH_RSS_IPV4_UDP | ETH_RSS_IPV6_TCP | ETH_RSS_IPV6_UDP,
+ .rss_hf = ETH_RSS_IP | ETH_RSS_UDP | ETH_RSS_TCP,
},
},
.txmode = {
next prev parent reply other threads:[~2015-03-10 0:57 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
2015-03-10 0:57 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE2ECC997@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).