pipapo_free_scratch(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

Okay bestie, this is pipapo_free_scratch(9) from the Kernel API Manual, and it's here to free the per-CPU map at its original address. That's the assignment. πŸ’…βœ¨


✨ SYNOPSIS ✨

void pipapo_free_scratch (const struct nft_pipapo_match *m , unsigned
       int cpu );

It returns void, so there's no return-value drama here β€” it's giving "do the thing and dip." 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • m β€” matching data. The matching data in question, periodt. πŸ“
  • cpu β€” CPU number. The CPU number, because this per-CPU map business has a CPU to point at. πŸ’–

πŸ¦‹ SEE ALSO πŸ¦‹

If you're obsessed and want the full pipapo cinematic universe, go check these: Kernel file ./net/netfilter/nft_set_pipapo.c Theory of Operation(9), pipapo_refill(9), pipapo_get_slow(9), pipapo_get(9), nft_pipapo_lookup(9), nft_pipapo_get(9), pipapo_realloc_mt(9), lt_calculate_size(9), pipapo_resize(9), pipapo_bucket_set(9), pipapo_lt_4b_to_8b(9), pipapo_lt_8b_to_4b(9), pipapo_lt_bits_adjust(9), pipapo_insert(9), pipapo_step_diff(9), pipapo_step_after_end(9), pipapo_base_sum(9), pipapo_expand(9), pipapo_map(9), pipapo_realloc_scratch(9), pipapo_maybe_clone(9), nft_pipapo_insert(9), pipapo_clone(9), pipapo_rules_same_key(9), pipapo_unmap(9), pipapo_drop(9), pipapo_gc_scan(9), pipapo_gc_queue(9), pipapo_free_fields(9), pipapo_reclaim_match(9), nft_pipapo_commit(9), nft_pipapo_activate(9), nft_pipapo_deactivate(9), nft_pipapo_flush(9), pipapo_get_boundaries(9), pipapo_match_field(9), nft_pipapo_remove(9), nft_pipapo_do_walk(9), nft_pipapo_walk(9), nft_pipapo_privsize(9), nft_pipapo_estimate(9), nft_pipapo_init(9), nft_set_pipapo_match_destroy(9), nft_pipapo_destroy(9), nft_pipapo_gc_init(9). πŸ¦‹πŸ’œ


Okay that's the whole vibe. This page lives in the source ./net/netfilter, is dated October 2026, and is literally pipapo_free_scratch(9) β€” bye bestie, go free that map! πŸ’–βœ¨

πŸ“¦ where this page comes from