DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Chilikin, Andrey" <andrey.chilikin@intel.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	Yerden Zhumabekov <e_zhumabekov@sts.kz>,
	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: Mon, 17 Nov 2014 00:48:57 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7C7E99@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <AAC06825A3B29643AF5372F5E0DDF05335024E42@IRSMSX106.ger.corp.intel.com>

Hi Andrey

Yes, Fortville supports hardware symmetric hashing offload. I am waiting for the
comments of its patch set submitted recently, and hopefully it can be accepted soon.
To use it, we need to enable the hash function of symmetric, but not the default
one of Toeplitz hash function. Then we need to set the swap configurations of it.
In detail, it is to set the offsets and length of the packet contents to be symmetric
hashed.

For more details, please refer to its datasheet (possible chapter of 7.1.10 Hash Functions)!

Regards,
Helin

> -----Original Message-----
> From: Chilikin, Andrey
> Sent: Saturday, November 15, 2014 12:57 AM
> To: Ananyev, Konstantin; Yerden Zhumabekov; Kamraan Nasim; dev@dpdk.org
> Cc: Yuanzhang Hu; Zhang, Helin
> Subject: RE: [dpdk-dev] Load-balancing position field in DPDK load_balancer
> sample app vs. Hash table
> 
> 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
> 
> >
> > 14.11.2014 20:44, Ananyev, Konstantin пишет:
> > > If you have a NIC that is capable to do HW hash computation, then
> > > you can do your load balancing based on that value.
> > > Let say ixgbe/igb/i40e NICs can calculate RSS hash value based on
> > > different combinations of dst/src Ips, dst/src ports.
> > > This value can be stored inside mbuf for each RX packet by PMD RX function.
> > > Then you can do:
> > > worker_id = mbuf->hash.rss % n_workersl
> > >
> > > That might to provide better balancing then using just one byte
> > > value, plus should be a bit faster, as in that case your balancer code don't
> need to touch packet's data.
> > >
> > > Konstantin
> >
> > --
> > Sincerely,
> >
> > Yerden Zhumabekov
> > State Technical Service
> > Astana, KZ
> >


      parent reply	other threads:[~2014-11-17  0:39 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
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 [this message]

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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A7C7E99@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=YHu@sidebandnetworks.com \
    --cc=andrey.chilikin@intel.com \
    --cc=dev@dpdk.org \
    --cc=e_zhumabekov@sts.kz \
    --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).