DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
To: Yaron Illouz <yaroni@radcom.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Rss hash on mellanox 100G card
Date: Mon, 10 Jan 2022 12:01:24 +0100	[thread overview]
Message-ID: <aab17d45-6559-612a-fa99-f003b8390296@intel.com> (raw)
In-Reply-To: <AM9PR09MB4995C12F3B37F0357CF12E57A14F9@AM9PR09MB4995.eurprd09.prod.outlook.com>

Hi Yaron,

On 09/01/2022 13:20, Yaron Illouz wrote:
> I am using Mellanox Technologies MT27800 Family [ConnectX-5], using dpdk 
> 19 with multi rx queue with rss 
> port_conf.rx_adv_conf.rss_conf.rss_hf=(ETH_RSS_IP | ETH_RSS_UDP | 
> ETH_RSS_TCP)
> 
> I analyze traffic and need all packet of same session to arrive to the 
> same process ( session for now can be ip+port)
> 
> So Packet that have the same ip + port arrive to the same queue.
> 
> But If some packet are ip fragmented, packet arrive to different 
> process. It is a problem!
> 
> How can i calculate the hash value in the c++ code, like it is done in 
> the card, so i can reassemble packets and send them to the same process 
> like the non fragmented packets?
> 

I think you need rte_softrss/rte_thash_gfni() , details could be found here:
https://doc.dpdk.org/guides/prog_guide/toeplitz_hash_lib.html

Or as an alternative option you can configure your NIC hash function to 
calculate the hash on L3 fields only.

-- 
Regards,
Vladimir

      reply	other threads:[~2022-01-10 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 12:20 Yaron Illouz
2022-01-10 11:01 ` Medvedkin, Vladimir [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=aab17d45-6559-612a-fa99-f003b8390296@intel.com \
    --to=vladimir.medvedkin@intel.com \
    --cc=dev@dpdk.org \
    --cc=yaroni@radcom.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).