[PATCH v2 1/9] bpf: document packet callback unload sequence
Konstantin Ananyev
konstantin.v.ananyev at yandex.ru
Mon Oct 19 22:44:26 CEST 2026
> Add a detailed comment with the sequence diagram to bpf_pkt.c describing
> the current de-facto synchronization protocol on BPF program unload
> between the control plane and the data plane.
>
> Signed-off-by: Marat Khalili <qm2k21 at gmail.com>
> ---
> lib/bpf/bpf_pkt.c | 65 ++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 64 insertions(+), 1 deletion(-)
>
> diff --git a/lib/bpf/bpf_pkt.c b/lib/bpf/bpf_pkt.c
> index f072fdaaed..4223ef624e 100644
> --- a/lib/bpf/bpf_pkt.c
> +++ b/lib/bpf/bpf_pkt.c
> @@ -21,9 +21,72 @@
> #include "bpf_impl.h"
>
> /*
> - * information about installed BPF rx/tx callback
> + * CP-DP synchronization mechanism
> + *
> + * After the callback is installed to a port/queue, removing it safely is a non-trivial task.
> + * The `rte_bpf` object can only be destroyed while the callback is not being executed,
> + * while the number of synchronization calls in the packet callback must be minimized.
> + *
> + * APIs `rte_eth_remove_rx_callback` and `rte_eth_remove_tx_callback` remove the callback from
> + * the callback list and upon return guarantee that it will not be called again,
> + * but not that any existing invocation of the callback has completed.
> + *
> + * Current synchronization mechanism relies on the following per-port/queue entities:
> + * 1. List of installed port/queue callbacks ("cbs" on the diagram);
> + * 2. Member `cb` of struct `bpf_eth_cbi`;
> + * 3. Member `use` of struct `bpf_eth_cbi`;
> + *
> + * BPF program is only executed if the first two are set, and increments `use` at the start and
> + * end of the callback execution so that in the safe state its value is even.
> + * This relies on only one thread calling the per-port/queue callback at a time.
> + *
> + * Unload processing starts with clearing the first two entities,
> + * then waits for `use` to become even before destroying the BPF program.
That's not entirely correct.
As I said before, it is sort of hand-made RCU.
So first it checks if there is active users:
if ((puse & BPF_ETH_CBI_INUSE) != 0) {
then, if so, it waits till active user ends its 'current quiescent' period:
RTE_WAIT_UNTIL_MASKED((__rte_atomic uint32_t *)(uintptr_t)&cbi->use,
UINT32_MAX, !=, puse, rte_memory_order_acquire);
Note that 'cbi->use' can be odd, as long as its value is not equal to
puse, i.e.
quiecent period had changed.
> + * The whole operation is protected by a control-plane-only spinlock (not shown on the diagram).
> + *
> + * Typical sequence of synchronization actions between CP and DP on unload is shown below:
> + * ```
> + * +----+ +-----+ +-----+ +----+ +-----+ +----+
> + * | CP | | cbs | | use | | cb | | bpf | | DP |
> + * +----+ +-----+ +-----+ +----+ +-----+ +----+
> + * | | | | | |
> + * | |<---------------------- fetch callback -----------------------|
> + * | | | | | |
> + * | | |<------------- increment to odd --------------|
> + * | | | | | |
> + * |-- remove callback -->| | | | rte_smp_mb()
> + * | | | | | |
> + * | | | |<------ fetch non-NULL --------|
> + * | | | | | |
> + * |------------------- store NULL --------------------->| | |
> + * | | | | | |
> + * rte_smp_mb() | | | | |
> + * | | | | | |
> + * rte_smp_mb() | | | | |
> + * | | | | | |
> + * +-if use is odd | | | | if cb not NULL-+
> + * | | | | | | | |
> + * | +------------ fetch odd ------------>| | |<-- execute --+ |
> + * | | | | | | BPF program | |
> + * | +-while use is same | | | | +-+
> + * | | | | | | | |
> + * | | +---------- fetch odd ------------>| | | rte_smp_rmb()
> + * | | | | | | | |
> + * +-+-+ | |<------------- increment to even -------------|
> + * | | | | | |
> + * |------------- fetch even ------------>| | | |
> + * | | | | | |
> + * |----------------- destroy BPF program and cleanup ----------------->| |
> + * | | | | | |
> + * +----+ +-----+ +-----+ +----+ +-----+ +----+
> + * | CP | | cbs | | use | | cb | | bpf | | DP |
> + * +----+ +-----+ +-----+ +----+ +-----+ +----+
> + * ```
> */
>
> +/*
> + * information about installed BPF rx/tx callback
> + */
> struct __rte_cache_aligned bpf_eth_cbi {
> /* used by both data & control path */
> RTE_ATOMIC(uint32_t) use; /*usage counter */
More information about the dev
mailing list