Communication between dataflow processing units and memories
US-2018060034-A1 · Mar 1, 2018 · US
US11223703B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11223703-B2 |
| Application number | US-201916358356-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 19, 2019 |
| Priority date | Mar 19, 2019 |
| Publication date | Jan 11, 2022 |
| Grant date | Jan 11, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Various embodiments are provided for implementing instruction initialization in a dataflow architecture in a computing environment. A data packet may be transmitted from a selected node to one or more of a plurality of nodes using one or more existing data paths in an initialization network. A determination operation is performed to determine whether one or more of a plurality of nodes is a target node intended for the data packet. Those of the plurality of nodes determined to be a target node initialize one or more components of the target node using the data packet. The data packet may be forwarded by each of the one or more of a plurality of nodes to a subsequent node in the initialization network.
Opening claim text (preview).
The invention claimed is: 1. A method for implementing instruction initialization in a dataflow architecture in a computing environment by a processor, comprising: transmitting initialization data organized as a data packet, from a selected node to one or more of a plurality of nodes being in an initialization mode, using one or more existing data paths in an initialization network, wherein the initialization mode is entered by each of the plurality of nodes upon receiving, at an initialization input data port, a core-level initialization and distribution (“i_init”) signal comprising a synchronous, timed signal operating at a predefined frequency; responsive to receiving the data packet, reading and storing the initialization data of the data packet from the initialization input data port at each cycle during the initialization state without performing a handshake protocol otherwise used in an execution phase, and further determining, by each respective node of the one or more of a plurality of nodes, whether the respective node performing the determining is a target node intended for the data packet, wherein those of the plurality of nodes determined to be the target node initialize one or more components of the target node using the initialization data of the data packet; commensurate with determining that the respective node is not the target node, forwarding the data packet by the respective node to a subsequent node in the initialization network, wherein the initialization data is transmitted on an initialization output data port without performing the handshake protocol following a delay of a predetermined number of cycles; and commensurate with determining that the respective node is the target node, ceasing forwarding of and ignoring any subsequent data packets received at the initialization input data port of the respective node while in the initialization mode, wherein the initialization mode is exited by each of the plurality of nodes upon receiving a false value of the i_init signal propagated throughout each of the plurality of nodes in the initialization network. 2. The method of claim 1 , further including analyzing a header of the data packet for determining those of the plurality of nodes intended as the target node. 3. The method of claim 1 , further including initializing an instruction buffer in the target node using instructions within the initialization data from of the data packet upon determining those of the plurality of nodes is the target node. 4. The method of claim 1 , further including commencing an initialization phase by sending an initialization signal indicating to the selected node, the plurality of nodes, or a combination thereof at a selected time period for initiating the data packet prior to executing one or more applications in an execution phase. 5. The method of claim 4 , wherein forwarding the data packet includes forwarding the data packet received by each of the one or more of a plurality of nodes to one or more child nodes in the initialization network. 6. A system for implementing instruction initialization in a dataflow architecture in a computing environment, comprising: one or more computers with executable instructions that when executed cause the system to: transmit initialization data organized as a data packet, from a selected node to one or more of a plurality of nodes being in an initialization mode, using one or more existing data paths in an initialization network, wherein the initialization mode is entered by each of the plurality of nodes upon receiving, at an initialization input data port, a core-level initialization and distribution (“i_init”) signal comprising a synchronous, timed signal operating at a predefined frequency; responsive to receiving the data packet, read and store the initialization data of the data packet from the initialization input data port at each cycle during the initialization state without performing a handshake protocol otherwise used in an execution phase, and further determine, by each respective node of the one or more of a plurality of nodes, whether the respective node performing the determining is a target node intended for the data packet, wherein those of the plurality of nodes determined to be the target node initialize one or more components of the target node using the initialization data of the data packet; commensurate with determining that the respective node is not the target node, forward the data packet by the respective node to a subsequent node in the initialization network, wherein the initialization data is transmitted on an initialization output data port without performing the handshake protocol following a delay of a predetermined number of cycles; and commensurate with determining that the respective node is the target node, cease forwarding of and ignoring any subsequent data packets received at the initialization input data port of the respective node while in the initialization mode, wherein the initialization mode is exited by each of the plurality of nodes upon receiving a false value of the i_init signal propagated throughout each of the plurality of nodes in the initialization network. 7. The system of claim 6 , wherein the executable instructions analyze a header of the data packet for determining those of the plurality of nodes intended as the target node. 8. The system of claim 6 , wherein the executable instructions initialize an instruction buffer in the target node using instructions within the initialization data from of the data packet upon determining those of the plurality of nodes is the target node. 9. The system of claim 6 , wherein the executable instructions commence an initialization phase by sending an initialization signal indicating to the selected node, the plurality of nodes, or a combination thereof at a selected time period for initiating the data packet prior to executing one or more applications in an execution phase. 10. The system of claim 9 , wherein forwarding the data packet includes forwarding the data packet received by each of the one or more of a plurality of nodes to one or more child nodes in the initialization network. 11. A computer program product for implementing instruction initialization in a dataflow architecture by a processor in a computing environment, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising: an executable portion that transmits initialization data organized as a data packet, from a selected node to one or more of a plurality of nodes being in an initialization mode, using one or more existing data paths in an initialization network, wherein the initialization mode is entered by each of the plurality of nodes upon receiving, at an initialization input data port, a core-level initialization and distribution (“i_init”) signal comprising a synchronous, timed signal operating at a predefined frequency; an executable portion that, responsive to receiving the data packet, reads and stores the initialization data of the data packet from the initialization input data port at each cycle during the initialization state without performing a handshake protocol otherwise used in an execution phase, and further determines, by each respective node of the one or more of a plurality of nodes, whether the respective node performing the determining is a target node intended for the data packet, wherein those of the plurality of nodes determined to be the target node initialize one or more components of the target node using the initialization data of the data packet; an executable portion that in
Routing a service request depending on the request content or context · CPC title
Parsing or analysis of headers · CPC title
Software download or update · CPC title
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
Routing instructions carried by the data packet, e.g. active networks · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.