From: Bruce Richardson <bruce.richardson@intel.com>
To: tom.barbette@ulg.ac.be
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] buf->hash.rss always empty with i40e
Date: Mon, 30 Jan 2017 10:46:30 +0000 [thread overview]
Message-ID: <20170130104629.GB100504@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <1162792082.14836638.1485600516608.JavaMail.zimbra@ulg.ac.be>
On Sat, Jan 28, 2017 at 11:48:36AM +0100, tom.barbette@ulg.ac.be wrote:
> Hi all,
>
> No matter the number of queues or the ETH_RSS_X parameter the mbuf->hash.rss field is empty using XL710 NICs. The exact same configuration gives me good hash value values with ixgbe/82599 cards.
>
> Any idea? I checked it is the same problem on 2.2 and 16.11. FlowDirector is not used.
It's hard to diagnose the exact problem without the full settings you
have tried, but one thing to watch out for that has caught me in the
past is that turning on RSS for IP packets, does not give an RSS value
if there is also TCP or UDP in the packets too. It only applies to IP
packets without TCP or UDP.
Here are settings that work for me with i40e driver:
static const struct rte_eth_conf port_conf_default = {
.rxmode = {
.mq_mode = ETH_MQ_RX_RSS,
.max_rx_pkt_len = ETHER_MAX_LEN
},
.rx_adv_conf = {
.rss_conf = {
.rss_hf = ETH_RSS_IP | ETH_RSS_TCP | ETH_RSS_UDP,
}
}
};
Regards,
/Bruce
next prev parent reply other threads:[~2017-01-30 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1845201442.14836426.1485600385431.JavaMail.zimbra@ulg.ac.be>
2017-01-28 10:48 ` tom.barbette
2017-01-30 10:46 ` Bruce Richardson [this message]
2017-01-30 12:59 ` tom.barbette
2017-02-06 9:25 ` tom.barbette
2017-02-06 12:25 ` Ananyev, Konstantin
2017-02-06 15:07 ` tom.barbette
2017-02-07 1:59 ` Zhang, Helin
2017-02-08 1:24 ` Wu, Jingjing
2017-02-08 14:19 ` Thomas Monjalon
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=20170130104629.GB100504@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=tom.barbette@ulg.ac.be \
/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).