folio_mk_pud(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME

folio_mk_pud β€” okay so this is the one that Creates a PUD for this folio, and yes bestie that's a capital-P PUD, we'll get into it πŸ’…

Welcome to the Kernel API Manual, bestie!! This page is the whole vibe check on folio_mk_pud, and it's genuinely so much smaller than the SEE ALSO list at the bottom, which is sending me 😭


✨ SYNOPSIS

pud_t folio_mk_pud (const struct folio *folio , pgprot_t pgprot );

Two args, one return, one page-table-entry-shaped icon. Slay.


πŸŽ€ ARGUMENTS

  • folio β€” The folio to create a PUD for. Like, this folio. Your main character folio. πŸ‘‘
  • pgprot β€” The page protection bits to use. It's giving "what's allowed to touch this memory" energy, and the kernel is very serious about it fr fr.

πŸ¦‹ DESCRIPTION

So here's the tea β˜•: folio_mk_pud creates a page table entry for the first page of this folio. Just the first one β€” not all of them, not the whole squad, just page one.

And the reason it does that is because the resulting entry is suitable for passing to set_pud_at. That's it. That's the whole job. Lowkey elegant, highkey iconic. πŸ¦‹

No cap, it literally just builds the entry and hands it to you β€” what you do with set_pud_at afterward is your business πŸ’…

🌸 RETURN

A page table entry suitable for mapping this folio. That's the whole return value, bestie β€” a pud_t ready to go, no drama, no surprises. 🫢


🌈 SEE ALSO

Kernel file ./include/linux/mm.h β€” and then the actual guest list, which is long. Like, this function knows everybody at the party:

Like I said. Everybody. πŸ’€


And that's the page!! This little cutie lives in ./include/linux and bestie it's dated October 2026 β€” mark your calendars, the folio_mk_pud era is upon us πŸŽ€βœ¨πŸ’œ

πŸ“¦ where this page comes from