skb_postpush_data_move(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… skb_postpush_data_move(9) β€” straight out of the Kernel API Manual ✨

okay so bestie, welcome to the glow-up era of skb_postpush_data_move β€” a little kernel function that quietly does the most after you've already shoved bytes onto your packet. no cap, it's giving "the cleanup crew that arrives after the main character walked in." πŸŽ€


🌸 NAME

skb_postpush_data_move β€” Move packet data and metadata after skb_push(). πŸ¦‹

like, both. data and metadata. it's an overachiever fr fr.


✨ SYNOPSIS

void skb_postpush_data_move (struct sk_buff *skb , const unsigned int
len , const unsigned int n );

🫢 ARGUMENTS

  • skb β€” the packet you're operating on πŸ’– like, the whole vibe you're working with
  • len β€” how many bytes got pushed onto sk_buff->data πŸ”₯
  • n β€” how many bytes to memmove from the pre-push sk_buff->data 🌈

πŸ‘‘ DESCRIPTION

See skb_data_move for details. 🧚

that's it. that's the whole description. the docs said "go read the other one," and honestly? iconic. lowkey the most efficient documentation ever written. πŸ’€

no seriously bestie, if you want the actual details, the manpage is pointing you at skb_data_move(9) β€” go check that one out. πŸ™ˆ

πŸ’œ SEE ALSO

Kernel file ./include/linux/skbuff.h β€” the home base for all of this πŸ’…

πŸ¦‹ skb basics, geometry & checksums

πŸŽ€ dst, refs & allocation

🌸 queues, sharing & cloning

πŸ’– frags, pages & DMA

πŸ”₯ copy-on-write, linearize, checksums & timestamps


and that's the whole page, bestie β€” you ate that πŸ’…βœ¨

this lil legend lives in ./include/linux, stamped October 2026, and it's part of the Kernel API Manual β€” so next time someone asks about post-push data moving, you can point them here and look like the main character. πŸŽ€πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from