nft_pipapo_avx2_estimate(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nft_pipapo_avx2_estimate(9) — like, the whole vibe check for a set, bestie

Okay so this is a page straight out of the Kernel API Manual, and it's literally about figuring out whether a netfilter set can hang with the AVX2 pipapo crowd. Sit down, grab a 🍓, we're doing this.

✨ NAME ✨

nft_pipapo_avx2_estimate — the function that sets the size, the space, and the lookup complexity estimates. That's it, that's the whole job. Iconic, honestly.

🌸 SYNOPSIS 🌸

bool nft_pipapo_avx2_estimate (const struct nft_set_desc *desc , u32
       features , struct nft_set_estimate *est );

Return type is bool, no cap. Three args, all of them matter, we do not skip.

🦋 ARGUMENTS 🦋

  • desc — the set description. It's giving "everything you need to know about this set": the element count and the field description, all used for the estimation. 🎀
  • features — the flags, bestie. And listen: NFT_SET_INTERVAL needs to be there. Like, it's non-negotiable. If it's not there, that's a whole thing.
  • est — the storage spot where the estimation data gets stashed. Purely a place to put the results. 🫶

👑 RETURN 👑

It returns true if the set is compatible and AVX2 is available. Otherwise it returns false. That's the deal. 💀

Lowkey important: both conditions need to line up — compatible set and AVX2 present. Miss one and you get false, periodt.

🌈 SEE ALSO 🌈

The kernel file lives at ./net/netfilter/nft_set_pipapo_avx2.c — go look, it's right there, iykyk.

And the whole friend group, in order, no one left out:

The 4b_ ones and the 8b_ ones are literally siblings, don't make them compete. 🙈

Alright besties, that's the page! Sourced from ./net/netfilter, dated October 2026 — so yes, we're manifesting, and yes, this estimate is gonna slay. 🧚‍♀️💜✨

📦 where this page comes from