From: "Stokes, Ian" <ian.stokes@intel.com>
To: Darrell Ball <dball@vmware.com>, "users@dpdk.org" <users@dpdk.org>
Cc: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>,
Kevin Traynor <ktraynor@redhat.com>,
"O Mahony, Billy" <billy.o.mahony@intel.com>,
"Chandran, Sugesh" <sugesh.chandran@intel.com>,
"Bodireddy, Bhanuprakash" <bhanuprakash.bodireddy@intel.com>,
"Loftus, Ciara" <ciara.loftus@intel.com>
Subject: Re: [dpdk-users] RTE RSS configuration
Date: Thu, 13 Jul 2017 08:56:31 +0000 [thread overview]
Message-ID: <CD7C01071941AC429549C17338DB8A52890DE8B6@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <518F5428-003C-4E07-BE49-18F99F3D681C@vmware.com>
Adding Ciara to the thread.
Ian
From: Darrell Ball [mailto:dball@vmware.com]
Sent: Wednesday, July 12, 2017 10:55 PM
To: users@dpdk.org
Cc: Kavanagh, Mark B <mark.b.kavanagh@intel.com>; Stokes, Ian <ian.stokes@intel.com>; Kevin Traynor <ktraynor@redhat.com>; O Mahony, Billy <billy.o.mahony@intel.com>; Chandran, Sugesh <sugesh.chandran@intel.com>; Bodireddy, Bhanuprakash <bhanuprakash.bodireddy@intel.com>
Subject: RTE RSS configuration
Hi
OVS-DPDK uses a RTE RSS hash configuration of
ETH_RSS_IP | ETH_RSS_UDP | ETH_RSS_TCP
I want to get an idea of expected guarantees of bounds of behavior if any.
I am trying to understand the lower bound of fields that could go into the RSS hash.
For example, could the RSS hash just be based on L3 (ipv4 or ipv6) as best effort and the
RSS valid flag be still set to true ?
Or, is it guaranteed that if L4 fields are not supported that the RSS valid flag will be false ?
On the flip side could we be getting something else included as well like L2 fields
(DA and SA, for example) implicitly ?
next parent reply other threads:[~2017-07-13 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <518F5428-003C-4E07-BE49-18F99F3D681C@vmware.com>
2017-07-13 8:56 ` Stokes, Ian [this message]
2017-07-14 15:03 ` O Mahony, Billy
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=CD7C01071941AC429549C17338DB8A52890DE8B6@IRSMSX101.ger.corp.intel.com \
--to=ian.stokes@intel.com \
--cc=bhanuprakash.bodireddy@intel.com \
--cc=billy.o.mahony@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dball@vmware.com \
--cc=ktraynor@redhat.com \
--cc=mark.b.kavanagh@intel.com \
--cc=sugesh.chandran@intel.com \
--cc=users@dpdk.org \
/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).