tlb_remove_tlb_entries(9)
π tlb_remove_tlb_entries(9) π
okay so bestie, welcome to the Kernel API Manual β this one's a tiny little function with a big job and honestly it's giving "quiet luxury" β¨
πΈ NAME πΈ
tlb_remove_tlb_entries β remember unmapping of multiple consecutive ptes for later tlb invalidation.
like, it's literally the "don't forget this happened" note-taker π so the tlb can get invalidated later. periodt.
β¨ SYNOPSIS β¨
void tlb_remove_tlb_entries (struct mmu_gather *tlb , pte_t *ptep ,
unsigned int nr , unsigned long address );
the way it returns void... it doesn't return anything, it just does things. main character energy fr fr π
π ARGUMENTS π
so about the args⦠the manpage is being super mysterious about these, no cap:
tlbβ-- undescribed --πptepβ-- undescribed --πnrβ-- undescribed --πaddressβ-- undescribed --π
ngl the docs just did not elaborate on these four. that's it, that's the tea π no invented details here, we don't do that. if the source doesn't say, we don't say π«Ά
π¦ DESCRIPTION π¦
So. It's basically tlb_remove_tlb_entry's louder, more extra sibling β similar to tlb_remove_tlb_entry, but instead of remembering the unmapping of only a single one, it remembers the unmapping of multiple consecutive ptes. π―
like, one pte? cute. a whole consecutive run of them? now we're talking. it remembers them all for later tlb invalidation, and that's the whole vibe. iconic behavior honestly π
β SEE ALSO β
- the kernel file
./include/asm-generic/tlb.hπ tlb_remove_tlb_entry(9)β the single-pte original, the blueprint, the blueprint's blueprint π§
π sign-off π
that's the whole page babes β brought to you by the fine folks at ./include/asm-generic, dated October 2026, and living rent-free in your kernel headers. go unmap some consecutive ptes responsibly πβ¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms