kunmap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… kunmap β€” kernel API manual, but make it make sense πŸ’…

okay so bestie, welcome to kunmap(9) β€” straight out of the Kernel API Manual, and honestly? she's a supporting character who does her job flawlessly and never asks for credit. we stan a humble icon 🫢


✨ NAME ✨

kunmap β€” the girl whose whole job is unmapping the virtual address that was mapped by kmap(). that's it. that's the gig. reverse uno card energy πŸ”„πŸ’–


🌸 SYNOPSIS 🌸

void kunmap (const struct page *page );

like. she takes one argument. void return. no drama, no cap. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • page β€” Pointer to the page which was mapped by kmap. that's the exact same struct page * you handed to kmap earlier, bestie. don't get cute and pass a different one πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

so the tea is: kunmap is the counterpart to kmap. kmap maps, kunmap unmaps. they're a matched set, a duo, the main character and her ride-or-die. πŸ‘‘

and here's the part that lowkey slays: she's a NOOP (that's "no operation", for the uninitiated πŸ’€) when CONFIG_HIGHMEM=n. also a NOOP for mappings of pages in the low memory area. so sometimes she literally does nothing and that's correct behaviour, not laziness. honestly? queen. she knows when not to act. 🌈✨

fr fr though β€” this is not a "maybe it did something" situation. it is defined to be a no-op in those cases. no guessing, no vibes-based kernel debugging. 🧚

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./include/linux/highmem.h β€” go read her whole friend group, they're all icons:

like, that's a whole squad. group chat is poppin' off. πŸ“πŸ’œ


okay that's the whole page, bestie β€” this cutie lives in ./include/linux, dated October 2026, and that's the vibe check complete. go unmap something responsibly. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from