[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <602ad895e1810_3ed41208b6@john-XPS-13-9370.notmuch>
Date: Mon, 15 Feb 2021 12:24:53 -0800
From: John Fastabend <john.fastabend@...il.com>
To: Maciej Fijalkowski <maciej.fijalkowski@...el.com>,
daniel@...earbox.net, ast@...nel.org, bpf@...r.kernel.org,
netdev@...r.kernel.org
Cc: andrii@...nel.org, toke@...hat.com, bjorn.topel@...el.com,
magnus.karlsson@...el.com, ciara.loftus@...el.com,
Maciej Fijalkowski <maciej.fijalkowski@...el.com>
Subject: RE: [PATCH bpf-next 3/3] samples: bpf: do not unload prog within
xdpsock
Maciej Fijalkowski wrote:
> With the introduction of bpf_link in xsk's libbpf part, there's no
> further need for explicit unload of prog on xdpsock's termination. When
> process dies, the bpf_link's refcount will be decremented and resources
> will be unloaded/freed under the hood in case when there are no more
> active users.
>
> While at it, don't dump stats on error path.
>
> Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@...el.com>
> ---
Can we also use it from selftests prog so we have a test that is run there
using this? Looks like xdpxceiver.c could do the link step as well?
Powered by blists - more mailing lists