iavf_flex_rx_tstamp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… iavf_flex_rx_tstamp(9) πŸ’…

okay so bestie, welcome to the kernel API manual, and today's main character is iavf_flex_rx_tstamp β€” the little function whose whole job is grabbing the Rx timestamp off the descriptor and handing it up the stack. it's giving "small but essential", fr fr. ✨


🌸 SYNOPSIS 🌸

void iavf_flex_rx_tstamp (const struct iavf_ring *rx_ring , __le64 qw2 ,
__le64 qw3 , struct sk_buff *skb );

no return value, no drama β€” it's void, it does its thing, it leaves. periodt. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • rx_ring β€” the descriptor ring, aka the whole vibe of where this descriptor lives. it's a const struct iavf_ring * so nobody's out here editing it, we're just looking. πŸ‘€
  • qw2 β€” quad word 2 of the descriptor. yes, "quad word", it's a whole thing, we don't question it, it's an __le64.
  • qw3 β€” quad word 3 of the descriptor. also an __le64. the two of them are lowkey a duo. 🫢
  • skb β€” the struct sk_buff * currently being received β€” the packet-in-progress, the one that's about to get its timestamp glow-up. πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does it actually do? it reads the Rx timestamp value straight out of the descriptor and passes it to the stack. that's it, that's the function. iconic behaviour, honestly. πŸŽ€

⚠️ big caveat energy: this function only operates on the VIRTCHNL_RXDID_2_FLEX_SQ_NIC flexible descriptor writeback format. like β€” only that one. if you're picturing some other descriptor format, nope, not here, this function is not for you. no cap. πŸ’€

🌈 SEE ALSO 🌈

first up, the source of truth, the place where it actually lives:

  • Kernel file ./drivers/net/ethernet/intel/iavf/iavf_txrx.c

and now the extended friend group β€” the whole squad of related functions, all here, all accounted for, screenshot-worthy list incoming πŸ“Έ:

like, the way that list just keeps going?? obsessed. πŸ’œ


and that's the whole page bestie, you ate that πŸ“ β€” this little gem lives down in ./drivers/net/ethernet/intel/iavf, dated October 2026, and it's forever known as iavf_flex_rx_tstamp(9). mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from