[OpenJDK 2D-Dev] Question about SurfaceData lock functions
Jim Graham
james.graham at oracle.com
Sat Jul 2 01:03:42 UTC 2011
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 it does not implement lock/unlock/getrasinfo because there are
no "loops" defined for its surfaces and it makes sure that it redirects
all calls at the upper levels into OGL API calls...
...jim
On 7/1/2011 1:03 AM, Clemens Eisserer wrote:
> 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 fallbacks work with the OpenGL pipeline? I just realized it
> doesn't implement the native lock/unlock/getrasinfo functions, and
> getRaster() seems to be unimplemented also.
>
> Thanks, Clemens
More information about the 2d-dev
mailing list