[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210215154638.4627-1-maciej.fijalkowski@intel.com>
Date: Mon, 15 Feb 2021 16:46:35 +0100
From: Maciej Fijalkowski <maciej.fijalkowski@...el.com>
To: 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: [PATCH bpf-next 0/3] Introduce bpf_link in libbpf's xsk
Hi,
This set is another approach towards addressing the below issue:
// load xdp prog and xskmap and add entry to xskmap at idx 10
$ sudo ./xdpsock -i ens801f0 -t -q 10
// add entry to xskmap at idx 11
$ sudo ./xdpsock -i ens801f0 -t -q 11
terminate one of the processes and another one is unable to work due to
the fact that the XDP prog was unloaded from interface.
Previous attempt was, to put it mildly, a bit broken, as there was no
synchronization between updates to additional map, as Bjorn pointed out.
See https://lore.kernel.org/netdev/20190603131907.13395-5-maciej.fijalkowski@intel.com/
In the meantime bpf_link was introduced and it seems that it can address
the issue of refcounting the XDP prog on interface. More info on commit
messages.
Thanks.
Maciej Fijalkowski (3):
libbpf: xsk: use bpf_link
libbpf: clear map_info before each bpf_obj_get_info_by_fd
samples: bpf: do not unload prog within xdpsock
samples/bpf/xdpsock_user.c | 55 ++++----------
tools/lib/bpf/xsk.c | 147 +++++++++++++++++++++++++++++++------
2 files changed, 139 insertions(+), 63 deletions(-)
--
2.20.1
Powered by blists - more mailing lists