[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190822183324.79b74f7b@cakuba.netronome.com>
Date: Thu, 22 Aug 2019 18:33:24 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Saeed Mahameed <saeedm@...lanox.com>
Cc: "David S. Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Moshe Shemesh <moshe@...lanox.com>
Subject: Re: [net-next 4/8] net/mlx5e: Add device out of buffer counter
On Thu, 22 Aug 2019 23:35:52 +0000, Saeed Mahameed wrote:
> From: Moshe Shemesh <moshe@...lanox.com>
>
> Added the following packets drop counter:
> Device out of buffer - counts packets which were dropped due to full
> device internal receive queue.
> This counter will be shown on ethtool as a new counter called
> dev_out_of_buffer.
> The counter is read from FW by command QUERY_VNIC_ENV.
>
> Signed-off-by: Moshe Shemesh <moshe@...lanox.com>
> Signed-off-by: Saeed Mahameed <saeedm@...lanox.com>
Sounds like rx_fifo_errors, no? Doesn't rx_fifo_errors count RX
overruns?
Powered by blists - more mailing lists