CL_OUT_OF_HOST_MEMORY on clEnqueueAcquireGLObjects in 64bit linux

CL_OUT_OF_HOST_MEMORY on clEnqueueAcquireGLObjects in 64bit linux

When calling clEnqueueAcquireGLObjects the function fails with CL_OUT_OF_HOST_MEMORY. On the same machine under 32bit win7 the same code works perfectly. Only difference is how the window is made.

The distribution is 64bit ubuntu (natty), which is not officially supported however I considered this to be useful information nonetheless. AMD APP SDK is also installed in this system and it works fine with GL sharing (no wonder as it uses the gpu). As intel opencl implementation uses libnuma from system could this be the culprit?

EDIT:

I'm getting convinced it's numa. As the official distributions (atleast according to google) use libnuma 2.0.3 and ubuntu has 2.0.5. Intel uses only 2 symbols from the libnuma (numa_max_node and numa_node_to_cpus) and on libnuma 2.0.4 changelog there is "- Fix numa_node_to_cpus() (Sharyathi Nagesh)". So something there has changed.

P.S don't sue me, using nm -D is not reverse engineering ;)

4 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Hi,

Current version of Intel SDK dosn't support GL sharing extension in Linux, only Windows.

Evgeny

Hi,

If that is the case the linux release ought not to claim that it supports cl_khr_gl_sharing, so this can be considered as a bug.

clGetDeviceInfo returns these: cl_khr_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_gl_sharing cl_khr_byte_addressable_store cl_intel_printf cl_ext_device_fission

Our software does not attempt to do GL sharing when the device says it cannot, and obviously tries when the device claims to support it. In addition to removing this extension from the list it should fail when creating the context, as said on the extension specification.

Can we expect working OpenGL sharing support on linux anytime soon?

Hi,

Thank you for reporting the issue, it'll be fixed toward next release.

However, on this forum we can't comment on new features.

Evgeny

Leave a Comment

Please sign in to add a comment. Not a member? Join today