From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1012] The rte_sched_queue_read_stats API requires a queue_id parameter but there is no public API to generate a queue_id
Date: Tue, 17 May 2022 14:33:01 +0000 [thread overview]
Message-ID: <bug-1012-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1012
Bug ID: 1012
Summary: The rte_sched_queue_read_stats API requires a queue_id
parameter but there is no public API to generate a
queue_id
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: adewar@ciena.com
Target Milestone: ---
The rte_sched_queue_read_stats API has a queue_id parameter, but there is no
public API to generate a queue_id from a combination of port, subport-id,
pipe-id, traffic-class-id and wrr-queue-id.
There is the static inline function called rte_sched_port_qindex that does what
is required, perhaps it could be turned into a public API?
rte_sched_queue_read_stats is the only public API to return the current length
of a specific queue.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-05-17 14: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-1012-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).