cgroup_writeback_by_id(9)

cgroup_writeback_by_id(9) 💅✨

✨ NAME ✨

cgroup_writeback_by_id — initiate cgroup writeback from bdi and memcg IDs. okay so this page is straight out of the Kernel API Manual, and it's literally the “start the flush by IDs” moment. no cap, we're keeping every detail, bestie. 💖

💅 SYNOPSIS 💅

here's the exact signature, character-for-character, do not @ me:

int cgroup_writeback_by_id (u64 bdi_id , int memcg_id , enum wb_reason
       reason , struct wb_completion *done );

the signature says it returns int, and the vibe is very kernel API. 💀

🎀 ARGUMENTS 🎀

four args, all main characters:

• bdi_id — target bdi id, the one and only. 🦋
• memcg_id — target memcg css id, slay. 🌸
• reason — reason why some writeback work initiated; it's giving context. 💅
• done — target wb_completion, the completion bestie. 🫶

🌈 DESCRIPTION 🌈

okay so what it does: initiate flush of the bdi_writeback identified by bdi_id and memcg_id with the specified parameters. that's the whole description, and honestly it ate. ✨

🔥 SEE ALSO 🔥

Kernel file ./fs/fs-writeback.c is where this lives, and here are all the related besties — no skips, periodt:

• inode_io_list_move_locked(9)
• wb_wait_for_completion(9)
• inode_cgwb_move_to_attached(9)
• locked_inode_to_wb_and_lock_list(9)
• inode_to_wb_and_lock_list(9)
• inode_switch_wbs(9)
• cleanup_offline_cgwb(9)
• wbc_attach_and_unlock_inode(9)
• wbc_attach_fdatawrite_inode(9)
• wbc_detach_inode(9)
• wbc_account_cgroup_owner(9)
• wb_split_bdi_pages(9)
• bdi_split_work_to_wbs(9)
• cgroup_writeback_umount(9)
• wb_start_background_writeback(9)
• filemap_dontcache_kick_writeback(9)
• __mark_inode_dirty(9)
• writeback_inodes_sb_nr(9)
• writeback_inodes_sb(9)
• try_to_writeback_inodes_sb(9)
• sync_inodes_sb(9)
• write_inode_now(9)
• sync_inode_metadata(9)

mwah 💋 this cutie is from the ./fs source/version and is dated October 2026 — title still cgroup_writeback_by_id(9), bye bestie! 🎀