DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] rte_event_dev_xstats_by_name_get issues
@ 2019-12-12 10:32 Mattias Rönnblom
  0 siblings, 0 replies; only message in thread
From: Mattias Rönnblom @ 2019-12-12 10:32 UTC (permalink / raw)
  To: dev; +Cc: jerinjacobk, Richardson, Bruce

Hi.

I'm looking at implementing rte_event_dev_xstats_by_name() for DSW, and 
I have some API-related questions.

Shouldn't rte_event_dev_xstats_by_name_get() return mode and queue/port 
id? Otherwise the caller needs to know if the name refers to a device- 
or port-level stat, and in case of the latter also the port or queue id. 
  That information is needed in subsequent rte_event_dev_xstats_get() call.

Also, the API states that the function may return "negative value: 
-EINVAL if stat not found, -ENOTSUP if not supported", which is somewhat 
misleading, since the return value is of an unsigned type.

Regards,
	Mattias

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-12-12 10:32 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-12 10:32 [dpdk-dev] rte_event_dev_xstats_by_name_get issues Mattias Rönnblom

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).