is_rcv_avail_int(9)

📦 version 7.3.1, in nixpkgs unstable

💅 is_rcv_avail_int(9) — a Kernel API Manual moment

okay so bestie, welcome to the is_rcv_avail_int(9) page 🎀 this one lives in the Kernel API Manual and it's short but it's iconic, trust.

✨ NAME ✨

is_rcv_avail_int — the User receive context available IRQ handler, and yes that's the whole vibe 💖

🌸 SYNOPSIS 🌸

void is_rcv_avail_int (struct hfi1_devdata *dd , unsigned int source );

like, that's it. that's the whole function. she's little but she's doing her job 🫶

🦋 ARGUMENTS 🦋

  • dd — a valid dd. that's it, that's the description. she must be valid, no cap 🙈
  • source — the logical IRQ source, specifically the offset from IS_RCVAVAIL_START. so it's giving "coordinates, not absolute address" energy 📍

⭐ DESCRIPTION ⭐

okay so this is the RX block receive available interrupt, and your girl handles it 💅 the source is < 160, noted, love that for her.

this is the general interrupt handler for user (PSM) receive contexts — main character energy fr fr 👑

⚠️ but here's the catch bestie: she can only be used for non-threaded IRQs. like, that's a hard limit, not a suggestion. do not come for her with your threaded IRQs, she will not be serving that 🫠

🔥 SEE ALSO 🔥

first up, the kernel file herself:

  • Kernel file ./drivers/infiniband/hw/hfi1/chip.c

and the whole friend group 🫶:

and that's the whole page, bestie, you ate that 🍓

💖 sign-off time 💖 this little icon lives in ./drivers/infiniband/hw/hfi1, dated October 2026, and she is — and always will be — is_rcv_avail_int(9). mwah 💋✨

📦 where this page comes from