STRUCT SDMA_ENGINE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct sdma_engine(9) β€” bestie edition

okay so sticky note first: this is a page from the Kernel API Manual, and the star of the show is struct sdma_engine(9). yes the title is literally the name of the struct. iconic behavior tbh.


✨ NAME ✨

struct sdma_engine β€” the data that pertains to each SDMA engine. one of these per engine, no cap. πŸ¦‹


🌸 SYNOPSIS 🌸

like, here's the whole struct, and honestly it's giving "small but mighty":

struct sdma_engine {
    struct hfi1_devdata *dd;
    struct hfi1_pportdata *ppd;
 };
lowkey obsessed with how short that is. two pointers. that's the whole vibe. πŸ’€

πŸŽ€ Members πŸŽ€

  • dd β€” a back-pointer to the device data. it's the "who's your device" link, fr fr. 🫢
  • ppd β€” the per port back-pointer. one port, one pointer, periodt. ✨

πŸ’– Description πŸ’–

so this structure has the state for each sdma_engine. that's it, that's the whole job β€” it's the main character energy container holding an engine's state. πŸ‘‘

and here's the part where i have to be a responsible bestie: accessing the non-public fields is not supported, because those private members are subject to change. like, they will absolutely get rearranged on you. so don't go poking at the private stuff, ngl. πŸ™ˆ

⚠️ warning, gently: private members = subject to change = not your business. touch the public stuff only. πŸ’…

🌈 SEE ALSO 🌈

go read these next, i promise they're worth it:


okay that's the whole page, you ate that πŸ“ and for the record, this one lives in ./drivers/infiniband/hw/hfi1 and it's dated October 2026 β€” so like, future vibes πŸ’œ bye bestie!! 🧚πŸ”₯

πŸ“¦ where this page comes from