Re: [PATCH] ethdev: remove telemetry Rx mbuf alloc failed field

2023-03-02 Thread Ferruh Yigit
On 3/1/2023 2:08 PM, Andrew Rybchenko wrote: > On 3/1/23 14:37, Thomas Monjalon wrote: >> 28/02/2023 19:02, Ferruh Yigit: >>> 'eth_dev->data->rx_mbuf_alloc_failed' field is not directly exposed to >>> user via ethdev APIs but it is used internally to set "stats->rx_nombuf' >>> which is exposed via

Re: [PATCH] ethdev: remove telemetry Rx mbuf alloc failed field

2023-03-01 Thread Andrew Rybchenko
On 3/1/23 14:37, Thomas Monjalon wrote: 28/02/2023 19:02, Ferruh Yigit: 'eth_dev->data->rx_mbuf_alloc_failed' field is not directly exposed to user via ethdev APIs but it is used internally to set "stats->rx_nombuf' which is exposed via ehtdev stat APIs. But telemetry exposes this field to user

Re: [PATCH] ethdev: remove telemetry Rx mbuf alloc failed field

2023-03-01 Thread Thomas Monjalon
28/02/2023 19:02, Ferruh Yigit: > 'eth_dev->data->rx_mbuf_alloc_failed' field is not directly exposed to > user via ethdev APIs but it is used internally to set "stats->rx_nombuf' > which is exposed via ehtdev stat APIs. > > But telemetry exposes this field to user via "/ethdev/info", > instead us

[PATCH] ethdev: remove telemetry Rx mbuf alloc failed field

2023-02-28 Thread Ferruh Yigit
'eth_dev->data->rx_mbuf_alloc_failed' field is not directly exposed to user via ethdev APIs but it is used internally to set "stats->rx_nombuf' which is exposed via ehtdev stat APIs. But telemetry exposes this field to user via "/ethdev/info", instead user can get 'rx_nombuf' value from stats via