From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "tom.barbette@ulg.ac.be" <tom.barbette@ulg.ac.be>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] buf->hash.rss always empty with i40e
Date: Mon, 6 Feb 2017 12:25:59 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772583F1114BE@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <55014943.22487464.1486373134907.JavaMail.zimbra@ulg.ac.be>
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
next prev parent reply other threads:[~2017-02-06 12:26 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 [this message]
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=2601191342CEEE43887BDE71AB9772583F1114BE@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=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).