collapse_max_ptes_none(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ collapse_max_ptes_none πŸ’…

okay so bestie, this is the Kernel API Manual page for collapse_max_ptes_none(9) β€” yes, we're in kernel land, and it's giving very specific mm energy. Don't panic, it's shorter than a group-chat argument. 🫢


✨ NAME ✨

collapse_max_ptes_none β€” calculates the maximum allowed empty PTEs or PTEs mapping the shared zeropage for the given collapse operation. That's the whole assignment, no cap. πŸ’–

🌸 SYNOPSIS 🌸

unsigned int collapse_max_ptes_none (struct collapse_control *cc ,
struct vm_area_struct *vma , unsigned int order );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • cc β€” the collapse control struct, aka struct collapse_control *. It's literally the collapse control struct, so it's main-character energy by default. πŸ’…
  • vma β€” the vma to check for userfaultfd, aka struct vm_area_struct *. yes, we're checking that one. πŸ‘€
  • order β€” the folio order being collapsed to (unsigned int). big folio energy. ✨

πŸ”₯ RETURN πŸ”₯

It returns the maximum number of empty/shared zeropage PTEs for the collapse operation. That's the number, periodt. πŸ‘‘

πŸ‘€ SEE ALSO πŸ‘€

Go peek at these, bestie:


Catch you later, bestie β€” this one's collapse_max_ptes_none(9) from source/version ./mm, dated October 2026. bye and slay πŸ’–βœ¨

πŸ“¦ where this page comes from