memcpy_from_folio(9)

🦋 memcpy_from_folio(9) 🦋

okay so bestie, this is the Kernel API Manual page for memcpy_from_folio, and it's giving “tiny byte road trip out of a folio” energy. No cap, it's literally a copy-from-folio moment. 💖

🌸 NAME 🌸

memcpy_from_folio — Copy a range of bytes from a folio. periodt.

✨ SYNOPSIS ✨

       void memcpy_from_folio (char *to , struct folio *folio , size_t offset ,
       size_t len );

yep, it's void, so there's no return value to obsess over. vibe check passed. 🫶

🎀 ARGUMENTS 🎀

• to — the memory you're copying to. drop the bytes here, bestie.
• folio — the folio you're reading from. main character source material.
• offset — the first byte in the folio you're reading. start here.
• len — the number of bytes to copy. how many bytes are coming along for the ride.

🫶 SEE ALSO 🫶

the whole friend group is here, bestie. The Kernel file is ./include/linux/highmem.h, and the refs are:

• kmap(9)
• kunmap(9)
• kmap_to_page(9)
• kmap_flush_unused(9)
• kmap_local_page(9)
• kmap_local_folio(9)
• kmap_atomic(9)
• clear_user_page(9)
• clear_user_pages(9)
• clear_user_highpage(9)
• clear_user_highpages(9)
• vma_alloc_zeroed_movable_folio(9)
• memcpy_to_folio(9)
• folio_zero_tail(9)
• folio_fill_tail(9)
• memcpy_from_file_folio(9)
• folio_zero_segments(9)
• folio_zero_segment(9)
• folio_zero_range(9)
• folio_release_kmap(9)

xoxo, bestie — sourced from ./include/linux, with the page/version memcpy_from_folio(9), dated October 2026. 💅✨