[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44ae964a-d3dd-6b7f-4bcc-21e07525bf41@gmail.com>
Date: Sat, 20 Apr 2019 18:16:36 -0600
From: David Ahern <dsahern@...il.com>
To: Toke Høiland-Jørgensen <toke@...hat.com>,
Jesper Dangaard Brouer <brouer@...hat.com>
Cc: David Miller <davem@...emloft.net>, mst@...hat.com,
makita.toshiaki@....ntt.co.jp, jasowang@...hat.com,
netdev@...r.kernel.org, virtualization@...ts.linux-foundation.org,
hawk@...nel.org, Jakub Kicinski <jakub.kicinski@...ronome.com>,
John Fastabend <john.fastabend@...il.com>,
Daniel Borkmann <borkmann@...earbox.net>,
Saeed Mahameed <saeedm@...lanox.com>,
Tariq Toukan <tariqt@...lanox.com>
Subject: Re: Stats for XDP actions
On 4/18/19 8:24 AM, Toke Høiland-Jørgensen wrote:
>>>
>>
>> Understood. Hopefully in March I will get some time to come back to this
>> and propose an idea on what I would like to see - namely, the admin has
>> a config option at load time to enable driver counters versus custom map
>> counters. (meaning the operator of the node chooses standard stats over
>> strict performance.) But of course that means the drivers have the code
>> to collect those stats.
>
> Hi David
>
> I don't recall seeing any follow-up on this. Did you have a chance to
> formulate your ideas? :)
>
Not yet. Almost done with the nexthop changes. Once that is out of the
way I can come back to this.
Powered by blists - more mailing lists