put_iova_domain(9)

🎀 put_iova_domain — the Kernel API Manual moment 💅

okay so bestie, we're in put_iova_domain(9) today — this is the Kernel API Manual page for it, and honestly it's giving "short but devastating" 🦋

✨ NAME ✨

put_iova_domain — literally destroys the iova domain. that's it. that's the whole job. no cap. 💀

✨ SYNOPSIS ✨

void put_iova_domain (struct iova_domain *iovad );

like, it returns void (nothing back, she's not a giver 💅) and it takes exactly one thing: a pointer to a struct iova_domain named iovad.

✨ ARGUMENTS ✨

• iovad — the iova domain in question, aka the main character of this whole operation 👑 and heads up: all the iova's in that domain are destroyed. every single one. it's giving cleanup era fr fr 🧹✨

✨ SEE ALSO ✨

bestie go read the kernel file ./drivers/iommu/iova.c for the full lore iykyk, and also these iconic siblings:

• alloc_iova(9)
• find_iova(9)
• __free_iova(9)
• free_iova(9)
• alloc_iova_fast(9)
• free_iova_fast(9)
• reserve_iova(9)

🫶 friendly reminder: this one is a destroys everything in the domain situation, so vibe check your iova's before you call her, okay? 😭

and that's the page!! mwah 💖 this came to you from ./drivers/iommu, dated October 2026, and yes the header/footer said put_iova_domain(9) both times because she's consistent like that ⭐ slay 🌈