Wednesday, November 14, 2018 6:18 PM, Tom Barbette:
> Subject: RE: [PATCH] mlx5: Report imissed stat
>
> Hi Shahaf,
>
> Yes we learned this distinction with rx_discards_phy the hard way. I would
> expect imissed to be only rx_out_of_buffer actually. I'd say people look at
> imissed to see if the
Hi Shahaf,
Yes we learned this distinction with rx_discards_phy the hard way. I would
expect imissed to be only rx_out_of_buffer actually. I'd say people look at
imissed to see if they consume packets fast enough. If the problem is pure CPU
power. And that is more the definition of imissed, it
Hi Again Tom,
Tuesday, November 13, 2018 12:17 PM, Tom Barbette:
> Subject: [PATCH] mlx5: Report imissed stat
>
> The imissed counters (number of packets dropped because the queues were
> full) were actually reported through xstats as "rx_out_of_buffer"
> but was not reported through stats.
>
>
The imissed counters (number of packets dropped because the queues were
full) were actually reported through xstats as "rx_out_of_buffer"
but was not reported through stats.
Following a recent discussion on the ML, as there is no way to tell the
user if a counter is implemented or not, this should
4 matches
Mail list logo
