pcpu_is_populated(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pcpu_is_populated β€” NAME

okay so bestie, welcome to the Kernel API Manual (yes, the whole entire vibe ✨) and today we're looking at pcpu_is_populated β€” which literally just determines if the region is populated. that's it. that's the function. no cap. πŸŽ€


πŸ¦‹ SYNOPSIS

bool pcpu_is_populated (struct pcpu_chunk *chunk , int bit_off , int bits , int *next_off );

🌸 ARGUMENTS

  • chunk β€” the chunk of interest, aka the main character of this whole operation πŸ’–
  • bit_off β€” the chunk offset, like where you're starting your little search bestie
  • bits β€” size of the area, so how much we're looking at
  • next_off β€” the return value for the next offset to start searching, iykyk 🌈

⭐ DESCRIPTION

so for atomic allocations, this checks if the backing pages are populated. periodt. that's the whole description, no need to overthink it bestie πŸ’…

πŸ‘‘ RETURN

it gives you a bool β€” if the backing pages are populated. also lowkey:

next_index is to skip over unpopulated blocks in pcpu_find_block_fit.

(and yes the page really does say next_index there even though the argument is named next_off, we don't question the kernel gods, we just vibe πŸ™ˆ)

✨ SEE ALSO

okay this list is iconic and long, buckle up besties, all from the kernel file ./mm/percpu.c:


and that's the whole page bestie! this gem lives in ./mm and the date stamped on it is October 2026 β€” so yeah, it's giving future vibes but we stan a timeless kernel API forever and always πŸ’œπŸ«ΆπŸ’–

πŸ“¦ where this page comes from