On 24/01/17 07:18 PM, Nicolai Hähnle wrote: > On 24.01.2017 07:39, Michel Dänzer wrote: >> On 24/01/17 05:44 AM, Samuel Pitoiset wrote: >>> Useful when debugging applications which map too much VRAM. >> >> Is the number of mapped buffers really useful, as opposed to the total >> size of buffer mappings? Even if it was the latter though, it doesn't >> show which mappings are for BOs in VRAM vs GTT, does it? Also, even the >> total size of mappings of BOs currently in VRAM doesn't directly reflect >> the pressure on the CPU visible part of VRAM — only the BOs which are >> actively being accessed by the CPU contribute to that. > > Thanks, I didn't know that. > > However, the number of mapped buffers is still useful information > because we used to run into Linux's limit on the number of simultaneous > mmap()ings before :)
Makes sense, but then the commit log should be changed to better reflect what it's useful for. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
