Jakub Kicinski writes:
> On Fri, 04 Dec 2020 18:26:10 +0100 Toke Høiland-Jørgensen wrote:
>> Jakub Kicinski writes:
>>
>> > On Fri, 4 Dec 2020 11:28:56 +0100 alar...@gmail.com wrote:
>> >> * Extend ethtool netlink interface in order to get access to the XDP
>> >>bitmap (XDP_PROPERTIES_G
On Fri, 04 Dec 2020 18:26:10 +0100 Toke Høiland-Jørgensen wrote:
> Jakub Kicinski writes:
>
> > On Fri, 4 Dec 2020 11:28:56 +0100 alar...@gmail.com wrote:
> >> * Extend ethtool netlink interface in order to get access to the XDP
> >>bitmap (XDP_PROPERTIES_GET). [Toke]
> >
> > That's a g
Jakub Kicinski writes:
> On Fri, 4 Dec 2020 11:28:56 +0100 alar...@gmail.com wrote:
>> * Extend ethtool netlink interface in order to get access to the XDP
>>bitmap (XDP_PROPERTIES_GET). [Toke]
>
> That's a good direction, but I don't see why XDP caps belong in ethtool
> at all? We use rtne
On Fri, 4 Dec 2020 11:28:56 +0100 alar...@gmail.com wrote:
> * Extend ethtool netlink interface in order to get access to the XDP
>bitmap (XDP_PROPERTIES_GET). [Toke]
That's a good direction, but I don't see why XDP caps belong in ethtool
at all? We use rtnetlink to manage the progs...
From: Marek Majtyka
Implement support for checking if a netdev has native XDP and AF_XDP zero
copy support. Previously, there was no way to do this other than to try
to create an AF_XDP socket on the interface or load an XDP program and
see if it worked. This commit changes this by extending exis
