Application programming interface using node dependencies
Apparatuses, systems, and techniques to perform an application programming interface (API) to cause dependency type information of one or more user-indicated graph nodes of a software graph to be indicated. In at least one embodiment, one or more dependency types from a graph are indicated.
1. A processor, comprising:
one or more circuits to perform an application programming interface (API) to cause dependency type information of one or more user-indicated graph nodes of a software graph to be indicated based on an input parameter to the API indicating the one or more user-indicated graph nodes, and the dependency type information indicating one or more constraints on scheduling a first operation corresponding to a first graph node and a second operation corresponding to the one or more user-indicated graph nodes.
2. The processor of claim 1 , wherein the API is to cause dependency type information of one or more user-indicated graph nodes of a software graph to be indicated based, at least in part, on identifying one or more edges to the software graph, the one or more edges are dependent on or dependent from the one or more user-indicated graph nodes.
3. The processor of claim 1 , wherein the API is to receive an indication of a source node of the one or more user-indicated graph nodes, the source node having a dependency with one or more destination nodes of the software graph.
4. The processor of claim 1 , wherein the API is to cause one or more edges of the software graph to be indicated.
5. The processor of claim 1 , wherein the dependency type information includes a dependency which is one or more of a full execution dependency, a launch order dependency, or an anti-deadlock dependency.
6. The processor of claim 1 , wherein the one or more user-indicated graph nodes are to be performed by one or more graphics processing units (GPUs).
7. The processor of claim 1 , wherein the API is to receive a set of parameters comprising an identifier of the one or more user-indicated graph nodes.
8. A computer-implemented method comprising:
performing an application programming interface (API) to cause dependency type information of one or more user-indicated graph nodes of a software graph to be indicated based on an input parameter to the API indicating the one or more user-indicated graph nodes, and the dependency type information indicating one or more constraints on scheduling a first operation corresponding to a first graph node and a second operation corresponding to the one or more user-indicated graph nodes.
9. The computer-implemented method of claim 8 , wherein the API is to cause dependency type information of one or more user-indicated graph nodes of a software graph to be indicated based, at least in part, on:
identifying one or more edges to the software graph, the one or more edges dependent on or dependent from the one or more user-indicated graph nodes; and
annotating the one or more edges with the dependency type information.
10. The computer-implemented method of claim 8 , wherein the API is to receive an indication of a source node of the one or more user-indicated graph nodes, the source node having a dependency with one or more destination nodes of the software graph.
11. The computer-implemented method of claim 8 , wherein the API is to cause one or more edges of the software graph to be indicated.
12. The computer-implemented method of claim 8 , wherein the dependency type information includes a dependency which is 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 one or more user-indicated graph nodes are to be performed by one or more graphics processing units (GPUs).
14. The computer-implemented method of claim 8 , wherein the API is to receive a set of parameters comprising an identifier of the one or more user-indicated graph nodes.
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 perform an application programming interface (API) to cause dependency type information of one or more user-indicated graph nodes of a software graph to be indicated based on an input parameter to the API indicating the one or more user-indicated graph nodes, and the dependency type information indicating one or more constraints on scheduling a first operation corresponding to a first graph node and a second operation corresponding to the one or more user-indicated graph nodes.
16. The computer system of claim 15 , wherein the API is to cause dependency type information of one or more user-indicated graph nodes of a software graph to be indicated based, at least in part, on identifying one or more edges to the software graph, the one or more edges are dependent on or dependent from the one or more user-indicated graph nodes.
17. The computer system of claim 15 , wherein the API is to receive an indication of a source node of the one or more user-indicated graph nodes, the source node having a dependency with one or more destination nodes of the software graph.
18. The computer system of claim 15 , wherein the API is to cause one or more edges of the software graph to be indicated.
19. The computer system of claim 15 , wherein the dependency type information includes a dependency which is 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 is to receive a set of parameters comprising an identifier of the one or more user-indicated graph nodes.