[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160920224747.23b7a33b@redhat.com>
Date: Tue, 20 Sep 2016 22:47:47 +0200
From: Jesper Dangaard Brouer <brouer@...hat.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Alexei Starovoitov <alexei.starovoitov@...il.com>,
Tom Herbert <tom@...bertland.com>,
Tariq Toukan <ttoukan.linux@...il.com>,
Tariq Toukan <tariqt@...lanox.com>,
"David S. Miller" <davem@...emloft.net>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
Eran Ben Elisha <eranbe@...lanox.com>,
Saeed Mahameed <saeedm@...lanox.com>,
Rana Shahout <ranas@...lanox.com>, brouer@...hat.com
Subject: Re: [PATCH net-next 7/8] net/mlx5e: XDP TX forwarding support
On Tue, 20 Sep 2016 20:59:39 +0200 Jesper Dangaard Brouer <brouer@...hat.com> wrote:
> On Tue, 20 Sep 2016 10:39:20 -0700 Eric Dumazet <eric.dumazet@...il.com> wrote:
>
[...]
>
> > Many existing supervision infrastructures collect device snmp
> > counters, and run as unprivileged programs.
>
> A supervision infrastructures is a valid use-case. It again indicate
> that such XDP stats need to structured, not just a random driver
> specific ethtool counter, to make it easy for such collection daemons.
>
>
> > tracepoints might not fit the need here, compared to a mere
> > tx_ring->tx_drops++
>
> I do see your point. I really liked the tracepoint idea, but now I'm
> uncertain again...
I've document the need for Troubleshooting and Monitoring, so we don't
forget about it. See:
Commit:
https://github.com/netoptimizer/prototype-kernel/commit/3925249089ae4
Online doc:
https://prototype-kernel.readthedocs.io/en/latest/networking/XDP/implementation/userspace_api.html#troubleshooting-and-monitoring
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
Powered by blists - more mailing lists