On Wed, Aug 8, 2012 at 11:19 AM, Michel Dänzer michel@daenzer.net wrote:
On Mit, 2012-08-08 at 10:36 -0400, j.glisse@gmail.com wrote:
From: Jerome Glisse jglisse@redhat.com
Use the ttm bo delayed destruction queue so that we don't block userspace when destroying bo. The virtual address destruction will happen at same time as the real bo destruction when everythings using the bo is done.
I'm on the fence about whether it's better to block or not here. If we don't, userspace will still need to defer at least the virtual address space deallocation. It might be easier (and less prone to subtle bugs) to just defer the BO destruction in userspace to avoid blocking here.
Doesn't mean user space should not do thing properly like using pool of bo or sub allocation. User space might get the wrong impression with that patch. Anyway just proposing it as it might be usefull in some case to not force user space to wait on bo idle when destroying bo.
Cheers, Jerome