folio_zero_segments(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 folio_zero_segments(9) — the Kernel API Manual, bestie edition 🎀

Okay so real talk, welcome to folio_zero_segments(9) from the Kernel API Manual. This one's short and sweet but she does exactly what she says on the tin — let's get into it 💅

✨ NAME ✨

folio_zero_segments — zero two byte ranges in a folio. Two of them. Like, a duo. A little zeroing duo 🫶

✨ SYNOPSIS ✨

void folio_zero_segments (struct folio *folio , size_t start1 , size_t
xend1 , size_t start2 , size_t xend2 );

That's the whole signature, no notes, copy it exactly, periodt ✨

✨ ARGUMENTS ✨

  • folio — the folio you're writing to, like the main character of the whole operation 👑
  • start1 — the first byte to zero, in the first range. The opening act 🌸
  • xend1 — one more than the last byte in the first range. Yes, "one more" — it's giving exclusive, not inclusive 🙈
  • start2 — the first byte to zero in the second range. Round two, bestie 💖
  • xend2 — one more than the last byte in the second range. Same deal as xend1, just for the sequel 💫

✨ SEE ALSO ✨

Here's the little friend group — all from the kernel file ./include/linux/highmem.h 💜 lowkey a whole squad:

Every single one, accounted for, no cap 🧚

Heads up bestie: this page lists no description, no options, no return value, nothing else — just the args and the friends. So that's the whole vibe check. Don't go inventing extra behaviour, iykyk 💀

And that's the page, mwah 💋 — brought to you by ./include/linux, dated October 2026, filed very officially under folio_zero_segments(9). Slay, go zero those two ranges 💅✨🌷

📦 where this page comes from