[code-reflection] RFR: [hat][proposal] ComputeRange and ThreadMesh API for defining 1D, 2D and 3D Ranges
duke
duke at openjdk.org
Mon Aug 11 09:56:25 UTC 2025
On Fri, 8 Aug 2025 14:00:23 GMT, Juan Fumero <duke at openjdk.org> wrote:
> This PR proposes an extension of the HAT API to leverage 1D, 2D and 3D ranges for the compute context dispatch.
> A `ComputeRange` is an entity that holds global and local thread mesh. In the future, we can add offsets to it.
>
> Each `ThreadMesh` is a triplet representing the number of threads for x,y, and z dimensions.
>
> How to dispatch 1D kernels?
>
>
> ComputeRange range1D = new ComputeRange(new ThreadMesh1D(size));
> cc.dispatchKernel(range1D,
> kc -> myKernel(...));
>
>
> How to dispatch 2D kernels?
>
>
> ComputeRange range2D = new ComputeRange(new ThreadMesh2D(size, size));
> cc.dispatchKernel(range2D,
> kc -> my2DKernel(...));
>
>
> How to enable local mesh?
>
> We pass a second parameter to the ComputeRange constructor to define local mesh. If it is not passed, then it is `null` and the HAT runtime can select a default set of values.
>
>
> ComputeRange computeRange = new ComputeRange(
> new ThreadMesh2D(globalSize, globalSize),
> new ThreadMesh2D(16, 16));
> cc.dispatchKernel(computeRange,
> kc -> matrixMultiplyKernel2D(kc, matrixA, matrixB, matrixC, globalSize)
> );
>
>
> In addition, this PR renames the `KernelContext` internal API to map the context ndrange object to native memory to `KernelBufferContext`.
>
>
> #### How to check?
>
>
> java @hat/run ffi-opencl matmul 1D
> java @hat/run ffi-opencl matmul 2D
>
> java @hat/run ffi-cuda matmul 1D
> java @hat/run ffi-cuda matmul 2D
@jjfumero
Your change (at version 6cdb52fffb1fd56fbcd65e86fd8a88ddfe180671) is now ready to be sponsored by a Committer.
-------------
PR Comment: https://git.openjdk.org/babylon/pull/516#issuecomment-3174007745
More information about the babylon-dev
mailing list