Adds host function f to a compute stream, with optional data related to the call. If data is not provided, places hstream under data.

Attaches memory mem of size size, specified by flag to a hstream asynchronously. For available flags, see internal.constants/mem-attach-flags. Te default is :single. If :global flag is specified, the memory can be accessed by any stream on any device. If :host flag is specified, the program makes a guarantee that it won’t access the memory on the device from any stream on a device that has no concurrent-managed-access capability. If :single flag is specified and hStream is associated with a device that has no concurrent-managed-access capability, the program makes a guarantee that it will only access the memory on the device from hStream. It is illegal to attach singly to the nil stream, because the nil stream is a virtual global stream and not a specific stream. An error will be returned in this case.

When memory is associated with a single stream, the Unified Memory system will allow CPU access to this memory region so long as all operations in hStream have completed, regardless of whether other streams are active. In effect, this constrains exclusive ownership of the managed memory region by an active GPU to per-stream activity instead of whole-GPU activity.

See CUDA Stream Management.

Queries if a device may directly access a peer device’s memory. See CUDA Peer Access Management

Compiles the given prog using a list of string options.

Creates a CUDA context on the device using a keyword flag. For available flags, see internal.constants/ctx-flags. The default is none. The context must be released after use.

See CUDA Context Management.

Frees the runtime device memory that has been created by cuda-malloc. See CUDA Runtime API Memory Management

Returns a Pointer to byte-size bytes of uninitialized memory that will be automatically managed by the Unified Memory system. The pointer is managed by the CUDA runtime API. Optionally, accepts a type of the pointer as a keyword (:float or Float/TYPE for FloatPointer, etc.). This pointer has to be manually released by cuda-free!. For a more seamless experience, use the wrapper provided by the mem-alloc-runtime function. See CUDA Runtime API Memory Management

Returns the CUDA context bound to the calling CPU thread. See CUDA Context Management.

Binds the specified CUDA context ctx to the calling CPU thread. See CUDA Context Management.

Returns a device specified with its ordinal number id or string PCI Bus id. See CUDA Device Management.

Returns the number of CUDA devices on the system. See CUDA Device Management.

Disables direct access to memory allocations in a peer context and unregisters any registered allocations. See CUDA Peer Access Management

Computes the elapsed time in milliseconds between start-event and end-event. See CUDA Event Management

Enables direct access to memory allocations in a peer context and unregisters any registered allocations. See CUDA Peer Access Management

Creates an event specified by keyword flags. For available flags, see internal.constants/event-flags. See CUDA Event Management

Returns CUDA kernel function named name located in module m. See CUDA Module Management

Returns CUDA global device memory object named name from module m. Global memory is typically defined in C++ source files of CUDA kernels. See CUDA Module Management

Creates a 1-dimensional GridDim record with grid and block dimensions x. Note: dim-x is the total number of threads globally, not the number of blocks.

Creates a 2-dimensional GridDim record with grid and block dimensions x and y. Note: dim-x is the total number of threads globally, not the number of blocks.

Creates a 3-dimensional GridDim record with grid and block dimensions x, y, and z. Note: dim-x is the total number of threads globally, not the number of blocks.

Pushes the context ctx to the top of the context stack, evaluates the body with ctx as the current context, and pops the context from the stack. Does NOT release the context, unlike with-context. See CUDA Context Management.

Initializes the CUDA driver. This function must be called before any other function from ClojureCUDA in the current process. See CUDA Initialization

Invokes the kernel fun on a grid-dim grid of blocks, usinng params PointerPointer. Optionally, you can specify the amount of shared memory that will be available to each thread block, and hstream to use for execution. See CUDA Module Management

Invokes the CUDA linker on data provided as a vector [[type source <options> <name>], ...]. Produces a cubin compiled for a particular Nvidia architecture. Please see relevant examples from the test folder. See CUDA Module Management

Completes the link state created by link, so that it can be loaded by the module function. Please see relevant examples from the test folder.

Adds a host function listener to a compute stream, with optional data related to the call, and connects it to a Clojure channel chan. If data is not provided, places hstream under data.

Load module’s data from a ptx string, nvrtc program, java path, or binary data. Please see relevant examples from the test folder. See CUDA Module Management

Allocates the byte-size bytes of uninitialized memory that will be automatically managed by the Unified Memory system, specified by a keyword flag. For available flags, see internal.constants/mem-attach-flags. Returns a CUDA device memory object, which can NOT be extracted as a Pointer, but can be accessed directly through its address in the device memory. See CUDA Driver API Memory Management

Allocates byte-size bytes of uninitialized host memory, ‘mapped’ to the device. Optionally, accepts a type of the pointer as a keyword (:float or Float/TYPE for FloatPointer, etc.). Mapped memory is optimized for the memcpy! operation, while ‘pinned’ memory is optimized for memcpy-host!. See CUDA Driver API Memory Management

Allocates byte-size bytes of uninitialized page-locked memory, ‘pinned’ on the host, using keyword flags. For available flags, see internal.constants/mem-host-alloc-flags; the default is :none. Optionally, accepts a type of the pointer as a keyword (:float or Float/TYPE for FloatPointer, etc.). Pinned memory is optimized for the memcpy-host! function, while ‘mapped’ memory is optimized for memcpy!. See CUDA Device Driver API Memory Management

Allocates the byte-size bytes of uninitialized memory that will be automatically managed by the Unified Memory system. Returns a CUDA device memory object managed by the CUDA runtime API, which can be extracted as a Pointer. Equivalent unwrapped Pointer can be created by cuda-malloc. See CUDA Runtime API Memory Management

Registers previously instantiated host pointer, ‘pinned’ from the device, using keyword flags. For available flags, see internal.constants/mem-host-register-flags; the default is :none. Returns the pinned object equivalent to the one created by mem-alloc-pinned. Pinned memory is optimized for the memcpy-host! function, while ‘mapped’ memory is optimized for memcpy!. See CUDA Device Driver API Memory Management

Creates CUDA device memory object that references a sub-region of mem from origin to byte-count, or maximum available byte size.

Copies byte-count or maximum available device memory from src to dst. TODO mapped, pinned If hstream is provided, executes asynchronously. See CUDA Memory Management

Copies byte-count or all possible memory from src to dst, one of which has to be accessible from the host. If hstream is provided, executes asynchronously. A polymorphic function that figures out what needs to be done. Supports everything except pointers created by cuda-malloc!. See CUDA Memory Management

Copies byte-count or all possible memory from host src to device dst. Useful when src or dst is a generic pointer for which it cannot be determined whether it manages memory on host or on device (see cuda-malloc!). If hstream is provided, executes asynchronously. See CUDA Memory Management

Copies byte-count or maximum available memory from device src to host dst. Useful when src or dst is a generic pointer for which it cannot be determined whether it manages memory on host or on device (see cuda-malloc!). If hstream is provided, executes asynchronously. See CUDA Memory Management

Sets n elements or all segments of dptr memory to value (supports all Java primitive number types except double, and long with value larger than Integer/MAX_VALUE). If hstream is provided, executes asynchronously. See CUDA Memory Management

Creates a new CUDA module and loads a string, nvrtc program, or binary data. See CUDA Module Management

Queries attributes of the link between two devices. See CUDA Peer Access Management

Creates an PointerPointers to CUDA parameter’s. parameter can be any object on device (Device API memory, Runtime API memory, JavaCPP pointers), or host (arrays, numbers, JavaCPP pointers) that makes sense as a kernel parameter per CUDA specification. Use the result as a parameter argument in launch!.

Pops the current CUDA context ctx from the current CPU thread. See CUDA Context Management.

Creates a CUDA program from the source-code, with an optional name and an optional hash map of headers (as strings) and their names.

Returns the log string generated by the previous compilation of prog.

Returns the PTX generated by the previous compilation of prog.

Pushes a context ctx on the current CPU thread. See CUDA Context Management.

Determines status (ready or not) of a compute stream or event obj. See CUDA Stream Management and CUDA Event Management

Records an even! ev on optional stream. See CUDA Event Management

Sets the ith parameter in a parameter array pp and the rest of parameters in places after i.

Creates a stream using an optional integer priority and a keyword flag. For available flags, see internal.constants/stream-flags See CUDA Stream Management

Blocks the current thread until the context’s or hstream’s tasks complete.

Makes a compute stream hstream wait on an event ev. See CUDA Event Management

Pushes the context ctx to the top of the context stack, evaluates the body, and pops the context from the stack. Releases the context, unlike in-context. See CUDA Context Management.

Initializes CUDA, creates the default context and executes the body in it. See CUDA Context Management.