drm_mm_scan_init_with_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

drm_mm_scan_init_with_range(9) πŸ’…

okay so hiii bestie, welcome to the Kernel API Manual era for drm_mm_scan_init_with_range(9) ✨. This is the function that sets up your range-restricted LRU scanning, and honestly it's giving very organized main character energy πŸŽ€.


🌸 NAME 🌸

drm_mm_scan_init_with_range β€” initialize range-restricted lru scanning. periodt. πŸ’–

✨ SYNOPSIS ✨

void drm_mm_scan_init_with_range (struct drm_mm_scan *scan , struct
       drm_mm *mm , u64 size , u64 alignment , unsigned long color , u64 start
       , u64 end , enum drm_mm_insert_mode mode );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • scan β€” the scan state. this is the glow-up target, bestie πŸ’«
  • mm β€” the drm_mm to scan πŸ‘€
  • size β€” size of the allocation πŸ“
  • alignment β€” alignment of the allocation πŸ“
  • color β€” opaque tag value to use for the allocation 🎨
  • start β€” start of the allowed range for the allocation 🚩
  • end β€” end of the allowed range for the allocation 🏁
  • mode β€” fine-tune the allocation search and placement πŸŽ›οΈ

πŸ”₯ DESCRIPTION πŸ”₯

This is literally just the setup: it gets the scanning routines ready with the parameters for the desired hole. that's it, that's the job β€” no overthinking, just wiring the scan with the right hole parameters πŸ•³οΈβœ¨

⚠️ Warning: while the scan list is non-empty, the only allowed operations are adding/removing nodes to/from the scan list. so yeah, while the scan list has anything in it, the only moves are adding/removing nodes to/from the scan list β€” don't try anything else, bestie πŸš¨πŸ’€

🌈 SEE ALSO 🌈


mwah πŸ’‹ β€” source/version: ./drivers/gpu/drm, date: October 2026, and the page is drm_mm_scan_init_with_range(9). stay slay, bestie 🫢

πŸ“¦ where this page comes from