[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r07v9np9.fsf@toke.dk>
Date: Fri, 01 Nov 2024 12:51:30 +0100
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Alexander Lobakin <aleksander.lobakin@...el.com>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski
<kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>
Cc: Alexander Lobakin <aleksander.lobakin@...el.com>, Alexei Starovoitov
<ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, John Fastabend
<john.fastabend@...il.com>, Andrii Nakryiko <andrii@...nel.org>, Maciej
Fijalkowski <maciej.fijalkowski@...el.com>, Stanislav Fomichev
<sdf@...ichev.me>, Magnus Karlsson <magnus.karlsson@...el.com>,
nex.sw.ncis.osdt.itp.upstreaming@...el.com, bpf@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v3 06/18] xdp: allow attaching already
registered memory model to xdp_rxq_info
Alexander Lobakin <aleksander.lobakin@...el.com> writes:
> One may need to register memory model separately from xdp_rxq_info. One
> simple example may be XDP test run code, but in general, it might be
> useful when memory model registering is managed by one layer and then
> XDP RxQ info by a different one.
> Allow such scenarios by adding a simple helper which "attaches" an
> already registered memory model to the desired xdp_rxq_info. As this
> is mostly needed for Page Pool, add a special function to do that for
> a &page_pool pointer.
>
> Signed-off-by: Alexander Lobakin <aleksander.lobakin@...el.com>
Reviewed-by: Toke Høiland-Jørgensen <toke@...hat.com>
Powered by blists - more mailing lists