[code-reflection] Integrated: Hat testing buffer marking 1
Gary Frost
gfrost at openjdk.org
Fri Feb 21 15:36:40 UTC 2025
On Fri, 21 Feb 2025 15:31:43 GMT, Gary Frost <gfrost at openjdk.org> wrote:
> Step 1 using buffer marking to minimize copies.
>
> This works with most samples/examples. We check markings at kernel dispatch time, and if a buffer is still 'device dirty' (meaning the last update to the segment was a kernel dispatch) then we avoid copying back to the device.
> This saves 15% or so on violajones
>
> Next step is not writing buffers after each kernel, and lazily pulling from the device if Java code requires the buffer. Plumbing for this is in place, but not turned on yet.
>
> We also need to mark buffers based on kernel usage. I planned to eventually statically analyze kernels. At present I rely on annotations of kernel params @RO, @RW and @WO.
This pull request has now been integrated.
Changeset: 576b09a9
Author: Gary Frost <gfrost at openjdk.org>
URL: https://git.openjdk.org/babylon/commit/576b09a901e5d201ef9bdec0518918ee4b16f6ff
Stats: 3089 lines in 50 files changed: 1773 ins; 831 del; 485 mod
Hat testing buffer marking 1
-------------
PR: https://git.openjdk.org/babylon/pull/325
More information about the babylon-dev
mailing list