On Thu, May 15, 2025 at 09:15:08AM -0700, Rob Clark wrote: > Basically it is a way to throttle userspace to prevent it from OoM'ing > itself. (I suppose userspace could throttle itself, but it doesn't > really know how much pre-allocation will need to be done for pgtable > updates.)
I assume you mean prevent a single process from OOM'ing itself by queuing up VM_BIND requests much faster than they can be completed and hence pre-allocations for page tables get out of control?
