From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "tom.barbette@ulg.ac.be" <tom.barbette@ulg.ac.be>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Zhang, Helin" <helin.zhang@intel.com>
Subject: Re: [dpdk-dev] buf->hash.rss always empty with i40e
Date: Wed, 8 Feb 2017 01:24:57 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810CD637C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1444803498.22738050.1486393664880.JavaMail.zimbra@ulg.ac.be>
> -----Original Message-----
> From: tom.barbette@ulg.ac.be [mailto:tom.barbette@ulg.ac.be]
> Sent: Monday, February 6, 2017 11:08 PM
> To: Ananyev, Konstantin <konstantin.ananyev@intel.com>
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; dev@dpdk.org; Zhang,
> Helin <helin.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>
> Subject: Re: buf->hash.rss always empty with i40e
>
> Hi Konstantin,
>
> It seems a little overkill to play with the key... The XL710 seems to be able to
> hash on IP fields only. It seems only a configuration issue, I'm adding i40e
> maintainers in CC so they can confirm? I think the i40e driver should
> configure XL710 to hash on IP fields for TCP and UDP when only ETH_RSS_IP
> is given instead of hashing to 0. That would mimic ixgbe behaviour btw.
>
> Tom
>
Yes, the behavior of XL710 is different from ixgbe on that.
If only enable ETH_RSS_IP, rss will not work on TCP and UDP packets. So you need
To set ETH_RSS_IP | ETH_RSS_UDP |ETH_RSS_TCP
Thanks
Jingjing
next prev parent reply other threads:[~2017-02-08 1:25 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
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 [this message]
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=9BB6961774997848B5B42BEC655768F810CD637C@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@intel.com \
--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).