destroy_workqueues(9)

💅 destroy_workqueues — the Kernel API Manual, but make it make sense 🎀

okay so this is destroy_workqueues(9), straight out of the kernel API manual, and it's genuinely one of those little functions that does exactly what its name says, no plot twist, no cap. Let me walk you through it bestie 🫶

---

✨ NAME ✨

destroy_workqueues — literally destroys the per-port workqueues 💀

that's it. that's the whole vibe. it's giving cleanup era.

---

🌸 SYNOPSIS 🌸

void destroy_workqueues (struct hfi1_devdata *dd );

so it returns void, meaning it hands nothing back to you — no status, no error code, nada. she's a "do the thing and go" kind of function 👑

---

🦋 ARGUMENTS 🦋

• dd — the hfi1_ib device 🎀 that's the one and only thing you hand her. just the device, that's the whole guest list.

---

⭐ SEE ALSO ⭐

the group chat is full of related functions, so let me list every single one because we don't gatekeep here 💖

• the kernel file itself: ./drivers/infiniband/hw/hfi1/init.c 🗂️
• hfi1_rcd_free(9)
• hfi1_rcd_put(9)
• hfi1_rcd_get(9)
• allocate_rcd_index(9)
• hfi1_rcd_get_by_index_safe(9)
• hfi1_rcd_get_by_index(9)
• hfi1_free_ctxt(9)
• init_after_reset(9)
• create_workqueues(9)
• enable_general_intr(9)
• hfi1_init(9)
• shutdown_device(9)
• hfi1_free_ctxtdata(9)
• hfi1_free_devdata(9)
• hfi1_alloc_devdata(9)
• hfi1_create_rcvhdrq(9)
• hfi1_setup_eagerbufs(9)

like, that's a whole friend group 😭 and honestly create_workqueues(9) is literally her opposite-number bestie — one builds them up, this one tears them down. the duality 🔥

---

ngl there are no options, no flags, no environment variables, no exit statuses and no signals on this page — she's a single-argument, fire-and-forget situation and we respect that 🙈

---

and that's the whole page, bestie, no filler, we ate and left no crumbs 💅✨

sign-off szn: this lil gem lives in the ./drivers/infiniband/hw/hfi1 directory, dated October 2026, and it's part of the Kernel API Manual 🧚💜 mwah, go destroy those workqueues responsibly 🍓