pipapo_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME

okay so bestie, pipapo_map is literally the function that inserts rules in mapping tables, mapping them between fields. that's it, that's the whole gig β€” she takes ya rules and files them into the mapping table, field by field. no cap. πŸŽ€


✨ SYNOPSIS

void pipapo_map (struct nft_pipapo_match *m , union
nft_pipapo_map_bucket map[NFT_PIPAPO_MAX_FIELDS] , struct
nft_pipapo_elem *e );

she returns void β€” no little return value to obsess over, she just does the thing. icon behavior honestly. ⭐


πŸ¦‹ ARGUMENTS

  • m β€” the matching data, and yes the mapping table is chillin' inside her too. she's the whole package, not just one thing πŸ’–
  • map β€” the table of rule maps: an array of the first rule and the amount of rules in the next field that a given rule maps to, for each field. that's the max, NFT_PIPAPO_MAX_FIELDS worth of entries β€” one little map-y bucket per field πŸ—ΊοΈβœ¨
  • e β€” for the last field, this is the nft_set_ext pointer that the matching rules map to. she only shows up at the end, main character energy fr πŸ’…

🌈 SEE ALSO

like, go read all of these, i'm not kidding, they're all connected:


ngl if you got here by grepping the source, you're already doing amazing β€” this one lives in ./net/netfilter and it's October 2026 energy, so go be a kernel girlie 🫢

🌸 mwah, that's the whole page, go insert some rules bestie πŸ’œ

πŸ“¦ where this page comes from