From: Nagesh Mallappa <mallappanagesh@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: RSS Hash value returned by the gvnic pmd dpdk driver not matching Toeplitz
Date: Thu, 16 May 2024 13:48:22 +0530 [thread overview]
Message-ID: <CABH5nGbwrCYsbYSn_Z_o=a8a9yQ3kp8DK+mBJ1wZXWeszOgH2A@mail.gmail.com> (raw)
In-Reply-To: <20240515155748.0a2881ef@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Hi Stephen,
Yes we have tried on Freebsd driver, we are hitting RCC hash issues here
too.
The Issue seems to be with the backend Gvnic on C3 GCP Instance.
Trying to get help from the DPDK community if there is any workaround or
fix for the RSS Issue on GVNIC DPDK PMD for C3 GCP Instance.
Thanks,
Nagesh
On Thu, May 16, 2024 at 4:27 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Wed, 15 May 2024 21:19:15 +0530
> Nagesh Mallappa <mallappanagesh@gmail.com> wrote:
>
> > Hi Stephen,
> >
> > Thanks for your response,
> > I have verified that too, but that is not the case.
>
> Does it work the same with Linux native kernel driver.
> If so, then comparing the code there might give some insight.
>
> PS: I don't use or any connection with Google, just trying to
> give insight based on other previous drivers with similar bugs.
>
[-- Attachment #2: Type: text/html, Size: 1341 bytes --]
next prev parent reply other threads:[~2024-05-16 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 8:20 Nagesh Mallappa
2024-05-15 15:04 ` Stephen Hemminger
2024-05-15 15:49 ` Nagesh Mallappa
2024-05-15 22:57 ` Stephen Hemminger
2024-05-16 8:18 ` Nagesh Mallappa [this message]
2024-05-16 8:56 ` Ferruh Yigit
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='CABH5nGbwrCYsbYSn_Z_o=a8a9yQ3kp8DK+mBJ1wZXWeszOgH2A@mail.gmail.com' \
--to=mallappanagesh@gmail.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).