On Tue, 20 Sep 2016 09:13:56 -0700 Eric Dumazet <eric.duma...@gmail.com> wrote:
> On Tue, 2016-09-20 at 18:06 +0200, Jesper Dangaard Brouer wrote: > > On Tue, 20 Sep 2016 08:58:30 -0700 > > Eric Dumazet <eric.duma...@gmail.com> wrote: > > > > Same for XDP_TX if/when packet is dropped because output ring is full. > > > > For the XDP_TX case a counter is already incremented[1] but it is a > > local ring counter (ring->tx_dropped++). > > > > Do you think we should maintain separate counters for XDP? (to have a > > more consistent interface across drivers...) > > No, as long as the admin can learn drops are occurring. Okay, so recording these drops is important for an admin, agreed. Now that we have the chance to define the API, wouldn't is be nice if the admin across drive drivers knew what counter to look for??? > "perf ... -e skb:kfree_skb ..." or drop monitor wont work, > unfortunately. That is actually a good idea... why not add a trace point for these rare drop cases, which is a hassle to debug for an admin? Let's actually take advantage of all the nice infrastructure the kernel provides(?) -- 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
