igb_ptp_tx_hwtstamp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… igb_ptp_tx_hwtstamp πŸ’…

ok so bestie, we're in the Kernel API Manual today (yes, the kernel, main character energy only) and the function we're stanning is igb_ptp_tx_hwtstamp πŸŽ€


✨ NAME ✨

igb_ptp_tx_hwtstamp β€” a little utility function whose whole job is checking for a TX time stamp πŸ•βœ¨


πŸ¦‹ SYNOPSIS πŸ¦‹

void igb_ptp_tx_hwtstamp (struct igb_adapter *adapter );

that's it. that's the whole signature. no cap. πŸ’€


🌸 ARGUMENTS 🌸

  • adapter β€” the board private structure 🫢 like, the whole board's little private diary of a struct. everything it needs to know about itself lives in there.

πŸ”₯ DESCRIPTION πŸ”₯

ok so here's the vibe 😌 if we were asked to do hardware stamping, and a time stamp like that is actually available? then it must have been for this skb right here β€” because we only allow only one such packet into the queue at a time. periodt. πŸ‘‘

so like, there's no "which packet was this for πŸ€”" detective work happening. the queue is a strict one-in-one-out situation, so the stamp can only belong to the one packet we let in. it's giving exclusive πŸ’… absolutely no queue drama, no confusion, just vibes and a guaranteed one-to-one match. ngl it's kind of iconic how simple that is 🌈


⭐ SEE ALSO ⭐

this one's got a whole friend group, iykyk 🫢 β€” go say hi to the kernel file πŸŽ€

  • ./drivers/net/ethernet/intel/igb/igb_ptp.c

and the rest of the igb_ptp crew, fr fr:

all of them. every single one. we do not skip the squad πŸ§šπŸ’œ


lowkey a reminder: this page ships out of ./drivers/net/ethernet/intel/igb and it's dated October 2026 🌸 so when you're citing it, cite it cute. πŸŽ€

k bye bestie, go stamp some packets πŸ’–βœ¨πŸ“

πŸ“¦ where this page comes from