DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@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>,
	"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] buf->hash.rss always empty with i40e
Date: Tue, 7 Feb 2017 01:59:39 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E71A9B86FA@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1444803498.22738050.1486393664880.JavaMail.zimbra@ulg.ac.be>

Hi Tom

Sorry, by default, i40e HW is a bit different from ixgbe HW. It will not treat UDP as an IP packet, when setting hash enable flags.
But, a feature of configuring 'input set' can help to change the default HW behavior. Please refer to testpmd input set part to understand how to use that. Thanks!

Regards,
Helin

-----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


----- Mail original -----
De: "Konstantin Ananyev" <konstantin.ananyev@intel.com>
À: "tom barbette" <tom.barbette@ulg.ac.be>, "Bruce Richardson" <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Envoyé: Lundi 6 Février 2017 13:25:59
Objet: RE: buf->hash.rss always empty with i40e

Hi Tom,

> 
> That also leave the question of how to HASH only on the IP tuple for 
> TCP and UDP packets? The use case is that I want all packets from the same IP src/dst pair to be hashed to the same queue. This cannot be enforced with a complete hash on TCP/UDP fields.
> 

That's for IPv4 only?
It was a while ago, when I looked at it, but as I remember you can achieve that by filling first 64 bits of RSS hash with some meaningful values, and keeping remaining RSS bits as zeroes.
You probably can give it a quick try with testpmd.

There is a nice article about similar subject:
http://www.ndsl.kaist.edu/~kyoungsoo/papers/TR-symRSS.pdf

Konstantin


  reply	other threads:[~2017-02-07  1:59 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 [this message]
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=F35DEAC7BCE34641BA9FAC6BCA4A12E71A9B86FA@SHSMSX103.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@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).