netfs_alloc_folioq_buffer(9)

🦋 netfs_alloc_folioq_buffer(9) 🦋

Okay bestie, welcome to the Kernel API Manual — this page is literally all about netfs_alloc_folioq_buffer(9), aka the function that allocates buffer space into a folio queue. It’s giving kernel-core main character energy, and we’re gonna read it together. Periodt. 💖

✨ NAME ✨

netfs_alloc_folioq_buffer — Allocate buffer space into a folio queue. That’s the vibe check, and it passed. 🌈

🎀 SYNOPSIS 🎀

The exact signature is right here, no cap:

int netfs_alloc_folioq_buffer (struct address_space *mapping , struct
       folio_queue **_buffer , size_t *_cur_size , ssize_t size , gfp_t gfp );

💅 ARGUMENTS 💅

• mapping — Address space to set on the folio (or NULL). Simple as that, bestie.
• _buffer — Pointer to the folio queue to add to. It may point to a NULL; it gets updated. Not me loving an in-place update 😭
• _cur_size — Current size of the buffer. And yes, it’s updated too. ✨
• size — Target size of the buffer.
• gfp — The allocation constraints. Respect the constraints, fr fr.

👑 SEE ALSO 👑

Go peek at these besties, iykyk:

• Kernel file ./fs/netfs/misc.c
• netfs_free_folioq_buffer(9)
• netfs_dirty_folio(9)
• netfs_unpin_writeback(9)
• netfs_clear_inode_writeback(9)
• netfs_invalidate_folio(9)
• netfs_release_folio(9)
• netfs_clear_stale_isize(9)

And that’s the page, bestie 🫶 This one comes from ./fs/netfs, dated October 2026, and its manual tag is netfs_alloc_folioq_buffer(9). Iconic footer behavior, honestly. Bye 💅💖