drm_gem_get_huge_mnt(9)

💅 drm_gem_get_huge_mnt(9) — from the Kernel API Manual, bestie 🎀

okay so this is a page from the Kernel API Manual and it's about one single little function, and honestly? it's giving "short and iconic." let's get into it ✨

---

🌸 NAME 🌸

drm_gem_get_huge_mnt — the function that gets the huge tmpfs mountpoint used by a DRM device. that's it. that's the whole gig. slay 🫶

---

✨ SYNOPSIS ✨

struct vfsmount * drm_gem_get_huge_mnt (struct drm_device *dev );

like, it hands you back a struct vfsmount * and you feed it a struct drm_device *. the vibes are immaculate, the signature is literally right there 💖

---

🦋 ARGUMENTS 🦋

• dev — the DRM device. yeah. that's the one. that's your main character right there 👑

---

💫 DESCRIPTION 💫

okay so here's the tea, bestie ☕ — this function gets the huge tmpfs mountpoint used by DRM device dev.

and why do we care? because a huge tmpfs mountpoint is used instead of shm_mnt after a successful call to drm_gem_huge_mnt_create when CONFIG_TRANSPARENT_HUGEPAGE is enabled. no cap, that's the whole situation. so like — create it successfully, have that config on, and boom, shm_mnt is not the moment anymore 🔥

---

🌈 RETURN 🌈

• the huge tmpfs mountpoint in use 💖
• NULL otherwise 🙈

that's it. two outcomes. a binary icon.

---

👑 SEE ALSO 👑

the kernel file ./include/drm/drm_gem.h — go read it, iykyk 📖 and also literally all of these:

• enum drm_gem_object_status(9)
• struct drm_gem_object_funcs(9)
• struct drm_gem_lru(9)
• struct drm_gem_object(9)
• DRM_GEM_FOPS(9)
• DEFINE_DRM_GEM_FOPS(9)
• drm_gem_object_get(9)
• drm_gem_object_put(9)
• drm_gem_object_is_shared_for_memory_stats(9)
• drm_gem_is_imported(9)
• drm_gem_gpuva_init(9)
• drm_gem_for_each_gpuvm_bo(9)
• drm_gem_for_each_gpuvm_bo_safe(9)

like that's a whole friend group and every single one of them ate 💅

---

lowkey a reminder: this page lives under ./include/drm and it's dated October 2026 — so when you cite it, cite it cute 💜

okay bye bestie, go read your mountpoints, mwah 😭💖🧚