hfi1_rcvhdrtail_kvaddr(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 hfi1_rcvhdrtail_kvaddr(9) — Kernel API Manual, bestie edition 🌸

okay so you're in the Kernel API Manual, section 9, and the star of the show is hfi1_rcvhdrtail_kvaddr 💅 she's a little function, she's got one job, and honestly? she ate.

✨ NAME ✨

hfi1_rcvhdrtail_kvaddr — return tail kvaddr, where @rcd is the receive context 🎀

like. that's it. that's her whole personality. return the tail kvaddr, and the thing you pass in is the receive context. iconic, no notes 🫶

💖 SYNOPSIS 💖

__le64 * hfi1_rcvhdrtail_kvaddr (const struct hfi1_ctxtdata *rcd );

look at her. a __le64 * return type, taking one const struct hfi1_ctxtdata * and naming it rcd. the way that signature is literally right there 😭✨

🦋 ARGUMENTS 🦋

  • rcd — -- undescribed -- 💀 bestie the manpage genuinely does not describe this one. that's not me being lazy, that's the actual text. the parameter is just... sitting there, mysterious, main character energy, undescribed 🙈 so we know it's rcd, and per the NAME section it's the receive context, and that is literally all the lore we get.
ngl if you were hoping for a whole essay on what rcd does, this is giving nothing. the docs said "undescribed" and meant it fr fr 💀

🔥 SEE ALSO 🔥

okay this is the part where she name-drops literally everyone she knows 🎀 all from the kernel file ./drivers/infiniband/hw/hfi1/hfi.h:

that's the whole group chat, every single one, go say hi 👑✨

🌈 and that's the page!! short, sweet, slightly under-documented, but we love her anyway 💜

sign-off time: this little masterpiece lives in ./drivers/infiniband/hw/hfi1, dated October 2026, and it's filed under hfi1_rcvhdrtail_kvaddr(9) 🎀 byeee, go read your receive contexts responsibly 💖✨🦋

📦 where this page comes from