Hi Jim,
I'm pretty sure that BufImgSurfaceData does not lock the toolkit lock. I
think only the X11SD needs that as it needs to serialize access to X11 and
it may need to read back pixels or send pixels via Xlib.
Thanks for the clarification. That should help scalability a lot for
my use-case
Hi,
Just to be sure, Is it allowed/possible to use a per-surface locking
structure for SurfaceData's lock/unlock functions to improve
concurrency?
All OpenJDK pipeline implementations seem to lock the toolkit lock, so
maybe the software routines expect the toolkit lock to be locked.
How do
Hi Clemens,
I'm pretty sure that BufImgSurfaceData does not lock the toolkit lock.
I think only the X11SD needs that as it needs to serialize access to X11
and it may need to read back pixels or send pixels via Xlib.
I'm not an expert on the internals of the OGL surface data, but I
imagine
