From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1441] RSS Hash returned by the gvnic pmd dpdk driver not matching Toeplitz
Date: Wed, 15 May 2024 08:33:36 +0000 [thread overview]
Message-ID: <bug-1441-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2021 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1441
Bug ID: 1441
Summary: RSS Hash returned by the gvnic pmd dpdk driver not
matching Toeplitz
Product: DPDK
Version: 24.03
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: mallappanagesh@gmail.com
Target Milestone: ---
We are using a C3 GCP instance having GVNIC with DPDK enabled.
We are using latest version of DPDK ( dpdk-24.03 ) to configure RSS key, we
understand C3 GCP instance with gvnic supports Toeplitz rss algorithm (
Reference -
https://github.com/google/compute-virtual-ethernet-dpdk/blob/main/gve_ethdev.c
), but we are hitting below issue.
Problem Statement - The RSS Hash value returned by the gvnic driver is
different and is not matching the one computed by Toeplitz.
Using below script to compute rss hash value from Toeplitz.
(https://gist.github.com/joongh/16867705b03b49e393cbf91da3cb42a7)
Consider below data to compute RSS Hash value -
Source IP - 79.124.62.122
Destination IP - 192.168.7.28
Source Port - 49442
Destination Port - 55327
RSS Key - {0x94e3e97e, 0x4abac401, 0x1e0edbf, 0xe059e1f4, 0xb6e27dff,
0xdf55c916, 0xe9e6e4db, 0x1f9fb82c, 0x1e0edbf, 0xe059e1f4}
Hash Value returned by Toeplitz - 0x8bbafd0f
Gvnic dpdk pmd driver which uses Toeplitz RSS hash algorithm too is expected to
compute above RSS Hash value but we see the Hash value stored in dpdk mbuf to
be 0xc6a15941 which is not right.
From the DPDK side we have ensured RSS offloading configuration is done
appropriately, but still we are seeing above mismatch.
We request you to please help us understand why this mismatch is happening and
is this expected behavior of gvnic on C3 instance.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4067 bytes --]
reply other threads:[~2024-05-15 8:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1441-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).