ttm_bo_unpin(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ttm_bo_unpin(9) β€” the Kernel API Manual era πŸŽ€

okay so bestie. welcome to the ttm_bo_unpin(9) page, straight out of the Kernel API Manual. this is the bit where we let a buffer object be free again, and honestly? it's giving "letting your ex back into the wild" energy. let's get into it ✨


🌸 NAME 🌸

ttm_bo_unpin β€” unpin the buffer object. that's it. that's the whole name. short, sweet, iconic. πŸ‘‘


✨ SYNOPSIS ✨

void ttm_bo_unpin (struct ttm_buffer_object *bo );

literally one function, one arg, returns nothing (void, so don't go looking for a return value, there isn't one, periodt). πŸ’œ


πŸ¦‹ ARGUMENTS πŸ¦‹

  • bo β€” the buffer object you're unpinning, bestie. that's the one you're setting free. 🫢

πŸ”₯ DESCRIPTION πŸ”₯

so here's the vibe check: this lets the buffer object get evicted again during memory pressure. like, you'd pinned it down (main character behaviour, very possessive), and now you're releasing it so the kernel can actually do its thing when memory gets tight. no cap, it's the un-cling 🧚

ngl, if you've still got stuff pointed at this buffer, maybe think about that first. this page isn't here to babysit you, it's just telling you what the function does. πŸ’€

🌈 SEE ALSO 🌈

go read these, iykyk. all of them. no skipping. πŸ“š


and that's the page, bestie πŸ’– this whole thing lives under ./drivers/gpu/drm/ttm, dated October 2026, and yes the header said ttm_bo_unpin(9) the whole time, we been knew 🌟 mwah, go unpin something πŸ’…πŸŽ€

πŸ“¦ where this page comes from