resource scope dependencies

Paul Sandoz paul.sandoz at oracle.com
Tue Oct 12 19:21:44 UTC 2021


I think this is significantly better than any of the other prior approaches, all of which seemed awkwardly bolted on to the side. This makes the dependencies (the DAG) explicit and queryable (in a limited but useful way), one that is dynamically generated, and perhaps it may make sense via say JFR (or a debugger) to produce more a detailed introspection. 

In some respects the approach reminds me a little bit of the dynamic generation of dependencies between GPU kernel tasks (the result of one task may be used as the input of another task), and from that the liveness of memory is known (in addition to how to schedule tasks concurrently and wait for their results).

Paul.

> On Oct 12, 2021, at 7:04 AM, Maurizio Cimadamore <Maurizio.Cimadamore at Oracle.COM> wrote:
> 
> Hi,
> when we were working on the latest API changes, we stumbled upon a possible simplification of the story for expressing dependencies between scopes. I've tried to capture the idea in the following document:
> 
> https://inside.java/2021/10/12/panama-scope-dependencies/
> 
> Feedback welcome!
> 
> Cheers
> Maurizio
> 



More information about the panama-dev mailing list