* [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
@ 2022-05-17 14:33 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2022-05-17 14:33 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-05-17 14:33 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-17 14:33 [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 bugzilla
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).