Class INTELThreadLocalExec


  • public final class INTELThreadLocalExec
    extends java.lang.Object
    Native bindings to the intel_thread_local_exec extension.

    This extension allows the user to execute OpenCL tasks and kernels with the user application's threads. The extension defines a token that can be passed to CreateCommandQueue, creating a queue with the "thread local exec" capability.

    All enqueue APIs (e.g., clEnqueueRead) submitted to such a queue never enqueue commands. An Enqueue API call is executed by the caller host-thread itself without involving any of the OpenCL runtime threads, much like function calls. The queue would typically stay empty - the queue handler argument is used only for compatibility of the enqueue APIs (i.e., keeping the same API signatures) and checking, at runtime, whether the enqueue API needs to be executed in such a fashion. Enqueue API calls on a "local" command queue can still use event dependency lists and output events. A non-NULL event dependency list will block the caller application thread until all the corresponding events are completed. Output events will be accessible only after the return of the enqueue API call (as with regular command queues) and should always have completed status (as expected). They might be useful for querying event status and profiling data. "Local" command queues behave the same regardless if they are defined as in-order or out-of-order. However, with in-order queues, threads may be blocked until execution of previously enqueued commands (by other threads) is completed. Given an enqueue API with a blocking flag (e.g., EnqueueReadBuffer), both its blocking non-blocking calls behave the same and have the exact same impact on the application. Calls to Finish and Flush, EnqueueBarrier and EnqueueMarker are valid although meaningless for these command queues. An optimal implementation of these APIs for Immediate command queues will incur the minimal overhead of a function call and possibly an if-then-else to distinguish between a local command queue and a regular one. EnqueueNDRangeKernel and EnqueueTask should have optimized implementations using a single execution thread.

    • Method Summary

      • Methods inherited from class java.lang.Object

        equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
    • Field Detail

      • CL_QUEUE_THREAD_LOCAL_EXEC_ENABLE_INTEL

        public static final int CL_QUEUE_THREAD_LOCAL_EXEC_ENABLE_INTEL
        cl_command_queue_properties
        See Also:
        Constant Field Values