[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8273458d-c4ef-bf53-bdf5-b5de53c012d3@intel.com>
Date: Fri, 15 May 2020 08:23:10 +0200
From: Björn Töpel <bjorn.topel@...el.com>
To: Björn Töpel <bjorn.topel@...il.com>,
ast@...nel.org, daniel@...earbox.net, davem@...emloft.net,
kuba@...nel.org, hawk@...nel.org, john.fastabend@...il.com,
netdev@...r.kernel.org, bpf@...r.kernel.org,
magnus.karlsson@...el.com, jonathan.lemon@...il.com,
jeffrey.t.kirsher@...el.com
Cc: maximmi@...lanox.com, maciej.fijalkowski@...el.com
Subject: Re: [PATCH bpf-next v2 00/14] Introduce AF_XDP buffer allocation API
On 2020-05-14 10:36, Björn Töpel wrote:
> Overview
> ========
>
> Driver adoption for AF_XDP has been slow. The amount of code required
> to proper support AF_XDP is substantial and the driver/core APIs are
> vague or even non-existing. Drivers have to manually adjust data
> offsets, updating AF_XDP handles differently for different modes
> (aligned/unaligned).
>
> This series attempts to improve the situation by introducing an AF_XDP
> buffer allocation API. The implementation is based on a single core
> (single producer/consumer) buffer pool for the AF_XDP UMEM.
I'll need to respin, adapting to Jesper's 'xdp-grow-tail' merge.
Cheers,
Björn
Powered by blists - more mailing lists