From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 83] For RSS flow actions, e1000_ethdev.h uses IGB_MAX_RX_QUEUE_NUM instead of IGB_MAX_RX_QUEUE_NUM_82576
Date: Wed, 15 Aug 2018 17:34:00 +0000 [thread overview]
Message-ID: <bug-83-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=83
Bug ID: 83
Summary: For RSS flow actions, e1000_ethdev.h uses
IGB_MAX_RX_QUEUE_NUM instead of
IGB_MAX_RX_QUEUE_NUM_82576
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: dpdk@stormmq.com
Target Milestone: ---
NOTE: This report needs to be confirmed by someone who is familiar with this
code.
When using the rss_flow_action, the `queue_num` needs to be specified. The only
indication of what the maximum value for this is from
`rte_eth_dev_info.max_rx_queues`. This seems to work for all PMDs that support
this flow action *except* for the 82576 variant of e1000.
This is because at line 239, the 'queue' parameter of struct
igb_rte_flow_rss_conf is defined as IGB_MAX_RX_QUEUE_NUM, yet this device
reports its maximum queue size as being the same as IGB_MAX_RX_QUEUE_NUM_82576
in `rte_eth_dev_info.max_rx_queues` - although it doesn't reference the same
constant.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-08-15 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 17:34 bugzilla [this message]
2020-12-22 6:33 ` [dpdk-dev] [Bug 83] For RSS flow actions, e1000_ethdev.h uses IGB_MAX_RX_QUEUE_NUM instead of IGB_MAX_RX_QUEUE_NUM_82576 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-83-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.