[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877do56reh.fsf@toke.dk>
Date: Fri, 22 Jan 2021 14:19:02 +0100
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Björn Töpel <bjorn.topel@...il.com>,
ast@...nel.org, daniel@...earbox.net, netdev@...r.kernel.org,
bpf@...r.kernel.org
Cc: Björn Töpel <bjorn.topel@...il.com>,
bjorn.topel@...el.com, magnus.karlsson@...el.com,
maciej.fijalkowski@...el.com, kuba@...nel.org,
jonathan.lemon@...il.com, maximmi@...dia.com, davem@...emloft.net,
hawk@...nel.org, john.fastabend@...il.com, ciara.loftus@...el.com,
weqaar.a.janjua@...el.com, andrii@...nel.org
Subject: Re: [PATCH bpf-next 0/3] AF_XDP clean up/perf improvements
Björn Töpel <bjorn.topel@...il.com> writes:
> This series has some clean up/performance improvements for XDP
> sockets.
>
> The first two patches are cleanups for the AF_XDP core, and the
> restructure actually give a little performance boost.
>
> The last patch adds support for selecting AF_XDP BPF program, based on
> what the running kernel supports.
>
> The patches were earlier part of the bigger "bpf_redirect_xsk()"
> series [1]. I pulled out the non-controversial parts into this series.
What about the first patch from that series, refactoring the existing
bpf_redirect_map() handling? I think that would be eligible for sending
on its own as well :)
-Toke
Powered by blists - more mailing lists