pipapo_resize(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– pipapo_resize(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ β€” today's main character energy is all about pipapo_resize, and she is literally here to handle a lookup table, a mapping table, or both πŸ’…. no cap, if the field's tables need a resize glow-up, this is the function. fr fr.

🌸 NAME 🌸

pipapo_resize β€” Resize lookup or mapping table, or both. that's the vibe check, bestie πŸ¦‹.

✨ SYNOPSIS ✨

int pipapo_resize (struct nft_pipapo_field *f , unsigned int old_rules ,
       unsigned int rules );

πŸŽ€ ARGUMENTS πŸŽ€

okay so here's the cast, and every single one matters, iykyk:

  • f β€” Field containing lookup and mapping tables. she's the whole field, periodt.
  • old_rules β€” Previous amount of rules in field. lowkey important context.
  • rules β€” New amount of rules. highkey the whole point.

πŸ’… DESCRIPTION πŸ’…

so what does she actually do? she can increase, decrease, or maintain tables size depending on the new amount of rules, and then copy data over ✨. it's giving resize plus data migration, and honestly? iconic.

and the important bit: in case the new size is smaller, she throws away data for the highest-numbered rules 😭. literally yeeting the highest-numbered rule data, no cap. that part is super important.

πŸ”₯ RETURN πŸ”₯

0 on success, -ENOMEM on allocation failure. that's the tea: clean 0 when it slays, sad -ENOMEM when allocation fails 😭.

πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad of related reads, iykyk πŸ‘‘:


xoxo, your Kernel API Manual bestie πŸ’– β€” source/version: ./net/netfilter; date: October 2026 ✨. slay and read your docs, periodt πŸ’….

πŸ“¦ where this page comes from