ttm_buffer_object_transfer(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

ttm_buffer_object_transfer — and bestie, the OG page literally leaves it at that. No little tagline, no "this does X" summary, nothing. Just the name sitting there with main character energy and zero explanation. We respect it. 🫶

Oh and hey, real quick before we dive in — you're reading the Kernel API Manual page for ttm_buffer_object_transfer(9), so like... kernel API business, not your regular userland stuff. Iykyk. ✨

✨ SYNOPSIS ✨

int ttm_buffer_object_transfer (struct ttm_buffer_object *bo , struct
ttm_buffer_object **new_obj );

🎀 ARGUMENTS 🎀

  • bo — a pointer to a struct ttm_buffer_object. That's the one you're transferring from, the original, the source of truth, the moment before the glow-up. 💖
  • new_obj — a pointer to a pointer to a newly created ttm_buffer_object. Yes, double pointer, that's not a typo, bestie, that's how it hands you back the fresh object. This new one holds the data of bo with the old placement. 🦋

🌸 DESCRIPTION 🌸

Okay so here's the vibe. This is a utility function, and you may call it after an accelerated move has been scheduled. Like, the move is already in motion, the driver is out here doing its thing, and now you need a lil placeholder to hold onto the old stuff while it's being copied.

So a new buffer object gets created as a placeholder for the old data while it's being copied. That's its whole job. It sits there, it holds the old data, it's doing background-character-with-a-purpose energy. 🧚

Then, when that buffer object is idle — and only then, like let it rest — it can be destroyed, which releases the space of the old placement. Slay. Clean up after yourself. 💅

⭐ RETURN ⭐

  • !0 — Failure. That's it, that's the listed return value. No big triumphant success number documented, just... if it's not zero, something went wrong. 😭

🔥 SEE ALSO 🔥

Okay this is the part where the page just goes feral and lists literally everyone. The kernel file in question is ./drivers/gpu/drm/ttm/ttm_bo_util.c, and the whole squad is:

Like, the whole friend group showed up to the function. Obsessed. 👑

Heads up bestie: this page is from the ./drivers/gpu/drm/ttm corner of the kernel tree — the TTM neighbourhood — so that's where you go looking if you wanna read the actual code. 🍓

And that's the whole page, periodt. Shoutout to the Kernel API Manual, source living over at ./drivers/gpu/drm/ttm, dated October 2026, page ttm_buffer_object_transfer(9) — mwah, no notes. 💜🎀🌈

📦 where this page comes from