DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yerden Zhumabekov <e_zhumabekov@sts.kz>
To: "Chilikin, Andrey" <andrey.chilikin@intel.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	Kamraan Nasim <knasim@sidebandnetworks.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Yuanzhang Hu <YHu@sidebandnetworks.com>
Subject: Re: [dpdk-dev] Load-balancing position field in DPDK load_balancer sample app vs. Hash table
Date: Fri, 14 Nov 2014 23:20:42 +0600	[thread overview]
Message-ID: <546639EA.3040404@sts.kz> (raw)
In-Reply-To: <AAC06825A3B29643AF5372F5E0DDF05335024E42@IRSMSX106.ger.corp.intel.com>

Thank you. And one more thing, does Fortville (or Niantic) support
various L2 headers when calculating RSS hash? I mean MPLS, QinQ, etc.?

14.11.2014 22:57, Chilikin, Andrey пишет:
> Fortville supports symmetrical hashing on HW level, a patch for i40e PMD was submitted a couple of weeks ago. For Niantic you can use symmetrical  rss key recommended by Konstantin.
>
> Regards,
> Andrey
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ananyev, Konstantin
> Sent: Friday, November 14, 2014 4:50 PM
> To: Yerden Zhumabekov; Kamraan Nasim; dev@dpdk.org
> Cc: Yuanzhang Hu
> Subject: Re: [dpdk-dev] Load-balancing position field in DPDK load_balancer sample app vs. Hash table
>
>> -----Original Message-----
>> From: Yerden Zhumabekov [mailto:e_zhumabekov@sts.kz]
>> Sent: Friday, November 14, 2014 4:23 PM
>> To: Ananyev, Konstantin; Kamraan Nasim; dev@dpdk.org
>> Cc: Yuanzhang Hu
>> Subject: Re: [dpdk-dev] Load-balancing position field in DPDK 
>> load_balancer sample app vs. Hash table
>>
>> I'd like to interject a question here.
>>
>> In case of flow classification, one might possibly prefer for packets 
>> from the same flow to fall on the same logical core. With this '%' 
>> load balancing, it would require to get the same RSS hash value for 
>> packets with direct (src to dst) and swapped (dst to src) IPs and 
>> ports. Am I correct that hardware RSS calculation cannot provide this symmetry?
> As I remember, it is possible but you have to tweak rss key values.
> Here is a paper describing how to do that:
> http://www.ndsl.kaist.edu/~shinae/papers/TR-symRSS.pdf
>
> Konstantin
>

-- 
Sincerely,

Yerden Zhumabekov
State Technical Service
Astana, KZ

  reply	other threads:[~2014-11-14 17:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 18:29 Kamraan Nasim
2014-11-14 10:53 ` Bruce Richardson
2014-11-14 14:44 ` Ananyev, Konstantin
2014-11-14 16:23   ` Yerden Zhumabekov
2014-11-14 16:50     ` Ananyev, Konstantin
2014-11-14 16:55       ` Yerden Zhumabekov
2014-11-14 16:57       ` Chilikin, Andrey
2014-11-14 17:20         ` Yerden Zhumabekov [this message]
2014-11-17 10:15           ` Chilikin, Andrey
2014-11-14 18:49         ` Matt Laswell
2014-11-15  7:10           ` Yerden Zhumabekov
2014-11-15 15:28             ` Matt Laswell
2014-11-17  0:48         ` Zhang, Helin

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=546639EA.3040404@sts.kz \
    --to=e_zhumabekov@sts.kz \
    --cc=YHu@sidebandnetworks.com \
    --cc=andrey.chilikin@intel.com \
    --cc=dev@dpdk.org \
    --cc=knasim@sidebandnetworks.com \
    --cc=konstantin.ananyev@intel.com \
    /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).