[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201205095948.5e0eba28@kicinski-fedora-pc1c0hjn.DHCP.thefacebook.com>
Date: Sat, 5 Dec 2020 09:59:48 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Vinicius Costa Gomes <vinicius.gomes@...el.com>
Cc: netdev@...r.kernel.org, jhs@...atatu.com, xiyou.wangcong@...il.com,
jiri@...nulli.us, m-karicheri2@...com, vladimir.oltean@....com,
Jose.Abreu@...opsys.com, po.liu@....com,
intel-wired-lan@...ts.osuosl.org, anthony.l.nguyen@...el.com
Subject: Re: [PATCH net-next v1 8/9] igc: Add support for exposing frame
preemption stats registers
On Tue, 1 Dec 2020 20:53:24 -0800 Vinicius Costa Gomes wrote:
> Expose the Frame Preemption counters, so the number of
> express/preemptible packets can be monitored by userspace.
>
> These registers are cleared when read, so the value shown is the
> number of events that happened since the last read.
>
> Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@...el.com>
You mean expose in a register dump? That's not great user experience..
Are there any stats that the standards mandate?
It'd be great if we could come up with some common set and expose them
via ethtool like the pause frame statistics.
Powered by blists - more mailing lists