Application programming interface to indicate event dependencies
Apparatuses, systems, and techniques to perform an application programming interface (API) to add one or more graph nodes to a software graph, wherein the API is to store an indication of whether a node within a software graph was performed based, at least in part, on a dependency type indicated by the API. In at least one embodiment, one or more nodes are added to a graph in accordance to one or more dependency types.
1 . One or more processors, comprising:
circuitry to, in response to an application programming interface (API) call, store an indication of whether a node within a software graph was performed based, at least in part, on a dependency type indicated by the API call.
2 . The one or more processors of claim 1 , wherein the circuitry is to store the indication of whether the node within the software graph was performed, based, at least in part, on one or more edges of the software graph, the one or more edges terminating to or originating from the node.
3 . The one or more processors of claim 1 , wherein the API call is to further indicate a port identifier of a graph node associated with the node.
4 . The one or more processors of claim 1 , wherein the circuitry is to store the indication of whether the node within the software graph was performed by identifying one or more graph nodes of the software graph dependent to or dependent on the node.
5 . The one or more processors of claim 1 , wherein the dependency type includes one or more of a full execution dependency, a launch order dependency, or an anti-deadlock dependency.
6 . The one or more processors of claim 1 , wherein the node is to be performed by one or more graphics processing units (GPUs) based, at least in part, on the dependency type.
7 . The one or more processors of claim 1 , wherein the API call is to receive a set of parameters comprising an identifier of the node and dependency information corresponding to the dependency type.
8 . A computer-implemented method comprising:
receiving an application programming interface (API) call; and
in receipt of the API call, storing an indication of whether a node within a software graph was performed based, at least in part, on a dependency type indicated by the API call.
9 . The computer-implemented method of claim 8 , further comprising, storing the indication of whether the node within the software graph was performed, based, at least in part, on one or more edges of the software graph, the one or more edges terminating to or originating from the node.
10 . The computer-implemented method of claim 8 , wherein the API call is to further indicate a port identifier of a graph node associated with the node.
11 . The computer-implemented method of claim 8 , further comprising, storing the indication of whether the node within the software graph was performed by identifying one or more graph nodes of the software graph dependent to or dependent on the node.
12 . The computer-implemented method of claim 8 , wherein the dependency type includes one or more of a full execution dependency, a launch order dependency, or an anti-deadlock dependency.
13 . The computer-implemented method of claim 8 , wherein the node is to be performed by one or more graphics processing units (GPUs) based, at least in part, on the dependency type.
14 . The computer-implemented method of claim 8 , wherein the API call is to receive a set of parameters comprising an identifier of the node and dependency information corresponding to the dependency type.
15 . A computer system comprising:
one or more processors and memory storing executable instructions that, if performed by the one or more processors, are to cause the one or more processors to, in response to an application programming interface (API) call, store an indication of whether a node within a software graph was performed based, at least in part, on a dependency type indicated by the API call.
16 . The computer system of claim 15 , wherein the is one or more processors are to store the indication of whether the node within the software graph was performed, based, at least in part, on one or more edges of the software graph, the one or more edges terminating to or originating from the node.
17 . The computer system of claim 15 , wherein the API call is to further indicate a port identifier of a graph node associated with the node.
18 . The computer system of claim 15 , wherein the is one or more processors are to store the indication of whether the node within the software graph was performed by identifying one or more graph nodes of the software graph dependent to or dependent on the node.
19 . The computer system of claim 15 , wherein the dependency type includes one or more of a full execution dependency, a launch order dependency, or an anti-deadlock dependency.
20 . The computer system of claim 15 , wherein the API call is to receive a set of parameters comprising an identifier of the node and dependency information corresponding to the dependency type.