ENUM TTM_BO_TYPE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ enum ttm_bo_type(9) πŸ’œ

okay bestie so this is a page from the Kernel API Manual, and we're about to become unwell about buffer types together. this enum has like three (3) members and honestly? each one is kind of a whole personality. let's get into it 🫢


🌸 NAME 🌸

enum ttm_bo_type β€” that's it, that's the name, no little tagline, the enum speaks for itself πŸ’…


✨ SYNOPSIS ✨

look at her. look at the whole entire girl:

enum ttm_bo_type {
    ttm_bo_type_device ,
    ttm_bo_type_kernel ,
    ttm_bo_type_sg

};

three constants, three vibes, zero notes. yes the spacing is like that, we don't judge, she's iconic as she is πŸŽ€


πŸ’– Constants πŸ’–

  • ttm_bo_type_device β€” these are the 'normal' buffers, and by normal we mean mmappable by user space, i.e. the ones the mortals can actually touch πŸ‘€ every single one of these bos takes up a slot in the device address space, and that slot is what you use for normal vm operations. main character buffer energy fr fr.
  • ttm_bo_type_kernel β€” literally the exact same situation as ttm_bo_type_device buffers, except user space cannot access these. kernel-only use, no entry, no exceptions, VIP section only. βœ‹ ngl it's giving backstage pass.
  • ttm_bo_type_sg β€” a buffer made from a dmabuf sg table that's shared with another driver. sharing is caring, we love a collaborative moment 🀝✨

πŸ¦‹ SEE ALSO πŸ¦‹

everything she's linked to, no gatekeeping:

that's a long list and she ate every single one of those links, periodt πŸ’€πŸ”₯


real talk: this is a kernel API page, so lowkey read the actual docs before you go poking at buffers. we're here for the vibe and the facts πŸ’œ

and that's a wrap bestie!! this one came from ./include/drm/ttm, dated October 2026, and it's still rocking the title enum ttm_bo_type(9) πŸ’… mwah, go touch some bos (responsibly) 🧚🌸

πŸ“¦ where this page comes from