From: Yaron Illouz <yaroni@radcom.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Rss hash on mellanox 100G card
Date: Sun, 9 Jan 2022 12:20:37 +0000 [thread overview]
Message-ID: <AM9PR09MB4995C12F3B37F0357CF12E57A14F9@AM9PR09MB4995.eurprd09.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
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?
[-- Attachment #2: Type: text/html, Size: 5918 bytes --]
next reply other threads:[~2022-01-09 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 12:20 Yaron Illouz [this message]
2022-01-10 11:01 ` Medvedkin, Vladimir
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=AM9PR09MB4995C12F3B37F0357CF12E57A14F9@AM9PR09MB4995.eurprd09.prod.outlook.com \
--to=yaroni@radcom.com \
--cc=dev@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).