folioq_append_mark(9)

📦 version 7.3.1, in nixpkgs unstable

💅 folioq_append_mark(9) — from your friends over in the Kernel API Manual ✨

okay bestie, gather round, because this one is short and sweet and honestly kind of iconic 🎀

🌸 NAME 🌸

folioq_append_mark — literally just adds a folio to a folio queue segment 💖 that's the whole vibe.

🦋 SYNOPSIS 🦋

unsigned int folioq_append_mark (struct folio_queue *folioq , struct
       folio *folio );

so it hands you back an unsigned int, and it eats two things — the queue segment and the folio — that's it, no cap 🫶

✨ ARGUMENTS ✨

  • folioq — the segment you're adding to, the main character of this operation 👑
  • folio — the folio you're adding, the one sliding into the queue 🧚

🔥 DESCRIPTION 🔥

okay so picture this: we're adding a folio to the tail of the sequence in a folio queue segment 🌈 it bumps the occupancy count up, and it returns the slot number for the folio that just got added — iykyk, that slot number is your little souvenir 🎀

the folio size gets extracted and stored in the queue, the first mark is set, and the second and third marks are left unmodified 💅 so don't come for marks two and three, they're minding their business.

⚠️ and here's the part where you gotta be a responsible adult, bestie: it's left up to the caller to check that the segment capacity will not be exceeded and to extend the queue. this function is not doing your homework for you 😭 not a single capacity check in sight, fr fr. you check it, you extend it, then you call. periodt 🍓

💜 SEE ALSO 💜

all my faves in one place, look at this lineup ⭐

Kernel file ./include/linux/folio_queue.h plus:

and that's the whole page, bestie 🫶 huge shoutout to the source directory ./include/linux and the date stamp October 2026, and yes the page answers to the name folioq_append_mark(9) — go forth and append responsibly 💖✨

📦 where this page comes from