[Bug 103304] multi-threaded usage of Gallium RadeonSI leads to NULL pointer exception in pb_cache_reclaim_buffer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Comment # 4 on bug 103304 from
Yes, we use the glFenceSync() / glWaitSync() system.
We have multiple buffers going around and after each vsync a check is done
which can be recycled using the non blocking glWaitSync.
However, will check if this is done everywhere correctly in our code. 

Reason of the multi-threading was the format change done during texture upload
(which took a lot of cpu power). However, now we do this in a worker thread
with optimized code, before doing the texture upload (so to assure the format
is compatible with the GPU before requesting the texture upload).

Therefore I adapted the code so that both (texture upload and rendering/flush)
are now done in one thread as a work around.


You are receiving this mail because:
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux