DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yerden Zhumabekov <e_zhumabekov@sts.kz>
To: "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 22:23:00 +0600	[thread overview]
Message-ID: <54662C64.9040500@sts.kz> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258213ADDFA@IRSMSX105.ger.corp.intel.com>

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?

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

  reply	other threads:[~2014-11-14 16:13 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 [this message]
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

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=54662C64.9040500@sts.kz \
    --to=e_zhumabekov@sts.kz \
    --cc=YHu@sidebandnetworks.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).