From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 530] Lack of Support for Inner RSS Header Hashing (Feature 2.21)
Date: Mon, 24 Aug 2020 19:57:44 +0000 [thread overview]
Message-ID: <bug-530-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=530
Bug ID: 530
Summary: Lack of Support for Inner RSS Header Hashing (Feature
2.21)
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: ohilyard@iol.unh.edu
Target Milestone: ---
As far as I can tell, testpmd doesn't report when inner rss header hashing
occurs. There is currently a field in log output (I enabled it using "set log
global 3") that shows the RSS hash when a packet is received, but there is no
indication of an inner RSS hash. Similarly, there is an offload flag
(PKT_RX_RSS_HASH) for rss hashing, but I was unable to find any flags relating
to inner rss offload like IPv4/IPv6, UDP, TCP and SCTP have. This makes testing
the feature difficult as there is no indication as to whether inner hashing was
preformed.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-08-24 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 19:57 bugzilla [this message]
2021-02-01 1:56 ` bugzilla
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-530-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 NNTP newsgroup(s).