idpf_ptp_request_ts(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… idpf_ptp_request_ts β€” the Kernel API Manual, bestie edition πŸŽ€

okay so this is idpf_ptp_request_ts(9) from the Kernel API Manual, and it's literally the girl whose whole job is grabbing you a Tx timestamp slot before you yeet your packet out the door ✨ no cap, she's the plug for timestamp indexes.


🌸 NAME 🌸

idpf_ptp_request_ts β€” request an available Tx timestamp index 🫢


⭐ SYNOPSIS ⭐

int idpf_ptp_request_ts (struct idpf_tx_queue *tx_q , struct sk_buff
*skb , u32 *idx );

like… she takes three things and hands you back an int, periodt πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • tx_q β€” the transmit queue where you're asking for this Tx timestamp. that's the vibes location, bestie πŸŽ€
  • skb β€” the SKB you're tying to this timestamp request. your packet, your problem, your main character energy πŸ’–
  • idx β€” index of the Tx timestamp latch. this is the little number that comes back out πŸ”₯

🌈 DESCRIPTION 🌈

so what she actually does: she requests the Tx timestamp index that got negotiated during PTP init, and that index is the one that's gonna be set into the Tx descriptor. iykyk πŸ‘‘

like, that's it. that's the whole job. she gets you the index, you put it in the descriptor, everybody slays ✨


πŸ‘‘ RETURN πŸ‘‘

on success she gives you 0 and the index β€” the very same index you can hand straight to the Tx descriptor πŸŽ€ otherwise you get -errno. it's giving "no notes, just vibes" when it works and "we don't talk about it" when it doesn't 😭


πŸ’œ SEE ALSO πŸ’œ

kernel file: ./drivers/net/ethernet/intel/idpf/idpf_ptp.c πŸ¦‹

and now the whole friend group, alphabetically-ish, all of them, because we don't leave a single bestie out of the group chat:


that's the whole page, bestie, and yes she ate πŸ’… this one came from ./drivers/net/ethernet/intel/idpf, dated October 2026, and the manual it lives in is the Kernel API Manual β€” so go forth, request those timestamps, and slay πŸ”₯βœ¨πŸŽ€

πŸ“¦ where this page comes from