pcpu_chunk_refresh_hint(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, welcome to the Kernel API Manual πŸ’… β€” this page is all about pcpu_chunk_refresh_hint, and what it does is updates metadata about a chunk. that's the whole vibe. it keeps the chunk's bookkeeping cute and current ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

void pcpu_chunk_refresh_hint (struct pcpu_chunk *chunk , bool full_scan );

πŸŽ€ ARGUMENTS πŸŽ€

  • chunk β€” the chunk of interest πŸ‘€ like, the one we're looking at, bestie
  • full_scan β€” tells us if we should scan from the beginning πŸ”„

πŸ’– DESCRIPTION πŸ’–

so what it does is iterate over the metadata blocks to find the largest contig area β€” the biggest contiguous stretch, no cap 🧚

here's the tea: a full scan can be avoided on the allocation path, because this gets triggered if we broke the contig_hint. when that happens, the scan_hint will be before the contig_hint, or after it if the scan_hint == contig_hint 🫢

and ngl? this cannot be prevented on freeing, because when we're freeing we wanna find the largest area possibly spanning blocks. that's the whole point, periodt πŸ’€βœ¨


πŸ‘‘ SEE ALSO πŸ‘‘


and that's a wrap, bestie πŸŽ€ this page lives in ./mm, dated October 2026, and the whole thing is pcpu_chunk_refresh_hint(9) β€” mwah, slay, go read your percpu docs πŸ’œπŸ”₯

πŸ“¦ where this page comes from