From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 573] [dpdk-20.11]rss_to_rte_flow/set_key_keylen: create rule failed: Invalid argument.
Date: Wed, 06 Jan 2021 07:34:29 +0000 [thread overview]
Message-ID: <bug-573-3-P1V4L9JiwL@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-573-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=573
kumar amber (Kumar.amber@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Kumar.amber@intel.com
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #5 from kumar amber (Kumar.amber@intel.com) ---
This looks not necessary for me, cause Intel NIC usually not support per RSS
queue group, For ice driver, we accept null queue configure, because a RSS
configure always apply on all queues implicitly and I think it should be the
same for i40e Otherwise, it’s always a burden for application to fill the queue
array for each rule creation.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-01-06 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 7:49 bugzilla
2021-01-06 7:34 ` bugzilla [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=bug-573-3-P1V4L9JiwL@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).