STRUCT THUNDERBOLT_IP_FRAME_HEADER(9)

✨ NAME ✨

struct thunderbolt_ip_frame_header — the lil' header that rides on every single Thunderbolt frame 🦋 no cap, every frame has one

okay so bestie, welcome to struct thunderbolt_ip_frame_header(9) 💅 this is the Kernel API Manual page for it, and we're gonna get you obsessed with frame headers, fr fr 🌸

---

🌩️ SYNOPSIS 🌩️

the whole struct, literally right here, character for character 🎀

struct thunderbolt_ip_frame_header {
    __le32 frame_size;
    __le16 frame_index;
    __le16 frame_id;
    __le32 frame_count;
 };

it's giving "small struct, big responsibilities" ngl 😭

🧩 Members

• frame_size — the size of the data that's chillin' with the frame, like how much stuff is actually in there 🍓
• frame_index — the running index on the frames, just counting along as they go ✨
• frame_id — the ID of the frame, and its whole job is matching frames to a specific packet, iykyk 🎀
• frame_count — how many frames assemble a full packet, like the headcount for the packet's group chat 💬

💬 Description

so here's the vibe 💅 every data frame that gets passed to the high-speed DMA ring has this header with it. that's just how it is, periodt.

and here's the tea 🫖 if the XDomain network directory announces that TBNET_MATCH_FRAGS_ID is supported, then frame_id gets filled in. if it's not supported? frame_id just stays 0. iconic behavior honestly 🙈

no extra lore here bestie — that's literally the whole description, don't let anyone tell you otherwise 💀

---

👀 SEE ALSO 👀

• the kernel file ./drivers/net/thunderbolt/main.c — go read it, it's right there 📂
• struct tbnet(9) — the related struct, absolutely worth a look 👑

---

and that's the page, bestie!! 🧚 source + version: ./drivers/net/thunderbolt, dated October 2026 ⭐ slay, go forth and match those frames to their packets 💖🌈