alloc_skb_with_frags(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

alloc_skb_with_frags β€” allocate skb with page frags

okay so this page is straight outta the Kernel API Manual, bestie, and it's all about alloc_skb_with_frags β€” the function that allocates an skb with page frags. it's giving kernel networking realness, no cap. πŸ’–


✨ SYNOPSIS ✨

struct sk_buff * alloc_skb_with_frags (unsigned long header_len ,
unsigned long data_len , int order , int *errcode , gfp_t gfp_mask );

yes queen, that's the whole signature. keep it cute, keep it exact. πŸŽ€


🌸 ARGUMENTS 🌸

  • header_len β€” size of the linear part. that's the linear bit, bestie. ✨
  • data_len β€” needed length in frags. so this is the length you need living in the frags. 🧚
  • order β€” max page order desired. the highest page order you're asking for, periodt. πŸ‘‘
  • errcode β€” pointer to error code if any. if something goes sideways, this pointer is where an error code can show up. πŸ™ˆ
  • gfp_mask β€” allocation mask. the allocation mask, exactly as advertised. πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

so basically: this can be used to allocate a paged skb, given a maximal order for frags. that's the whole vibe. it's not doing extra lore β€” it's just handing you that paged skb situation when you've picked your maximal order for the frags. 🌈


πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./net/core/skbuff.c β€” and the whole bestie squad is here:


okay that's the page, bestie. source/version corner: ./net/core; date on the page: October 2026; title energy: alloc_skb_with_frags(9). mwah πŸ’‹πŸ’–

πŸ“¦ where this page comes from