System and method to generate a network-on-chip (NoC) description using incremental topology synthesis

Abstract

Systems and methods are disclosed synthesis of network, such as a network-on-chip (NoC). The network is initially synthesized. In accordance with various embodiments and aspects of the invention, a tool is used to synthesize and generate the NoC from a set of constraints. The tool produces consistent results between different synthesis runs, which have slight varying constraints.

Description

FIELD OF THE INVENTION

The present technology is in the field of system design and, more specifically, related to topology synthesis to generate a network-on-chip (NoC) description.

BACKGROUND

Multiprocessor systems have been implemented in systems-on-chips (SoCs) that communicate through network-on-chips (NoCs). The SoCs include instances of master (initiators) intellectual properties (IPs) and slave (targets) IPs. Transactions are sent from a master to one or more slaves using industry-standard protocols. The master, connected to the NoC, sends a request transaction to a slave, using an address to select the slave. The NoC decodes the address and transports the request from the master to the slave. The slave handles the transaction and sends a response transaction, which is transported back by the NoC to the master.

Typically, a NoC description is generated using a synthesis tool during the design process. The tool generates a NoC from a set of constraints. If changes are made, then the tool will have to be restarted and re-executed. Accordingly, every time the input constraints change, the tool is restarted or the synthesis is re-executed. As such, there is a risk of giving a completely different solution from one run to the next, even if the changes to the constraints are limited or minor. This is due to the nature of the network synthesis process, which typically uses a constraint solver approach to minimizing metrics, and the constraint solver may find very different solutions in response to slightly different set of constraints. As such, the tool may find a different solution every time it runs for slightly different constraints. Thus, the tool has a reduced usability when used by a SoC designer to automatically create the NoC. During the design time of SoC, the constraints change and evolve. If the tool generates substantially different results each time the software runs and every time the user makes a small change, then this will lead to the designer being unable to reuse some of the implementation work already done.

For example, consider the situation when the NoC has already been generated from a set of constraints. The result has been processed through the ASIC design flow with logic synthesis and place and route steps done. The steps typically take a lot of time, e.g. multiple days. After this first generation, it is decided to remove a component from the SoC, which result in slight modification of the floorplan and the connectivity. The tool generating the NoC is run again with the updated constraints. The tool gives a completely different result compared to the first run. As such, all the previous work on logic synthesis and place and route need to be done again from scratch, even if the constraint change was very small. This is very costly for the project.

Accordingly, there is a need for a tool that ensures, as between two different runs using two different set of small or minor constraint changes, minimum changes to the solution, which is needed to adapt to the changed constraints. Therefore, what is needed is a method to allow the tool to generate a NoC from a set of constraints while producing consistent results between runs that have slightly different/varying constraints, with the goal of minimizing the differences between the current run result and the previous run result.

SUMMARY OF THE INVENTION

In accordance with various embodiments and aspects of the invention, systems and methods are provided to allow a tool to synthesize and generate a NoC from a set of constraints while producing consistent results between synthesis runs that have slight varying constraints. One advantage of the invention is minimizing the differences between results of different synthesis runs, such as two consecutive synthesis runs, when there is a minor change in any one constraint.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a logic view of a network-on-chip (NoC) that includes an assembly of various elements to create the network.

FIG. 2 shows a method for generating a NoC description or synthesis based on a set of constraints.

FIG. 3 shows a process for NoC synthesis using the previous run as a constraint in accordance with various aspects and embodiments of the invention.

FIG. 4 shows an implementation of a NoC based on an initial run in accordance with the various aspects and embodiments of the invention.

FIG. 5 shows an implementation of a NoC based on a subsequent run relative to the synthesis of the NoC of FIG. 4, in accordance with the various aspects of the invention.

FIG. 6 shows an implementation of a NoC based on a subsequent run relative to the synthesis of the NoC of FIG. 4, in accordance with the various aspects of the invention.

DETAILED DESCRIPTION

The following describes various examples of the present technology that illustrate various aspects and embodiments of the invention. Generally, examples can use the described aspects in any combination. All statements herein reciting principles, aspects, and embodiments as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents and equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.

It is noted that, as used herein, the singular forms “a,” “an” and “the” include plural referents unless the context clearly dictates otherwise. Reference throughout this specification to “one embodiment,” “an embodiment,” “certain embodiment,” “various embodiments,” or similar language means that a particular aspect, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention.

As used herein, a “master” and a “initiator” refer to similar intellectual property (IP) modules or units and the terms are used interchangeably within the scope and embodiments of the invention. As used herein, a “slave” and a “target” refer to similar IP modules or units and the terms are used interchangeably within the scope and embodiments of the invention. As used herein, a transaction may be a request transaction or a response transaction. Examples of request transactions include write request and read request.

Thus, appearances of the phrases “in one embodiment,” “in at least one embodiment,” “in an embodiment,” “in certain embodiments,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment or similar embodiments. Furthermore, aspects and embodiments of the invention described herein are merely exemplary, and should not be construed as limiting of the scope or spirit of the invention as appreciated by those of ordinary skill in the art. The disclosed invention is effectively made or used in any embodiment that includes any novel aspect described herein. All statements herein reciting principles, aspects, and embodiments of the invention are intended to encompass both structural and functional equivalents thereof. It is intended that such equivalents include both currently known equivalents and equivalents developed in the future. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a similar manner to the term “comprising.”

Referring now to FIG. 1, a network-on-chip (NoC) 100 is shown in accordance with various aspects and embodiments of the invention. The NoC uses elementary network functions that are assembled, such as: network interface units (NIUs) 102, 104, 106, 108, 110, 112, 130, 132, and 134, switches 114, 116, 118, 120, and 122; adapters, such as adapter 126; and buffers, such as buffer 124. The NoC elementary network functions use an internal transport protocol, which is specific to the NoC 100, to communicate with each other, typically based on the transmission of packets. The NIUs convert the protocol used by the attached system-on-chip (SoC) unit (not shown), into the transport protocol used inside the NoC 100. The switches route flows of traffic between source and destinations. The buffer 124 is used to insert pipelining elements to span long distances, or to store packets to deal with rate adaptation between fast senders and slow receivers or vice-versa. The adapter 126 handles various conversions between data width, clock, and power domains.

Referring now to FIG. 2, a process is shown for generating synthesis of a NoC, such as the NoC of FIG. 1. The process includes receiving as inputs a set of constraints, which may include: physical (floorplan related, technology related) 210; power and clock domain definitions 212; connectivity of the elements 214; definitions of connected IP 216; performance related constraints including latency and throughput through the NoC; and any other kind of metric to be optimized, such as area of the resulting network and wire length. Additionally, various scenarios, such as scenario 1, can be included as a constraint. The information is provided to a NoC synthesis tool 220.

Referring now to FIG. 3, a process 300 is shown wherein a tool 302 generates a NoC description 304 from a set of input constraints 306. The tool 302 also accepts, as an additional set of constraints, a previous result 308 associated with a previous run. The tool 302 uses the previous result 308 to minimize the amount of change in the new result compared to the old result, such as the NoC description 304. Thus, the tool 302 uses given constraints, such as those outline in FIG. 2, along with the previous result, to generate a new result. In accordance with some aspects of the invention, acceptance of a description of previous result, as a constraint, is optional. Thus, the designer or user decides if using the previous result for subsequent runs is important to minimize the amount of change compared to the previous run. In accordance with some aspects of the invention, for a first run there is no previous result.

In accordance with the various aspects and embodiments of the invention, the format and information of the constraints, the result, and the previous result used as constraint, are all implementation dependent. In accordance with some aspects of the invention, the previous result description includes more than just the previous NoC description. The tool receives the data that includes information about global parameters used in the previous run. The tool re-consumes data generated from the previous run and maintains some of the global parameters. The inclusion of the previous run also provides profile information about the solution and decisions made throughout the process of developing the constraints that were used as part of the previous run, including the global information. As such, the global information is persistent and reintroduced to be re-consumed during subsequent runs. For example, while the location of an element may be slightly altered, the physical neighborhood where that element is to be re-positioned is retained along with the definitions and connectivity constraints. Additional examples include possibly some other internal data structures used by the synthesis tool, such as intermediate calculations, to produce the resulting synthesis.

Referring now to FIG. 4, a path 406 is shown between a master (M) 402 and a slave (S) 404 through a NoC 400. The path 406 is determined using a tool performing a synthesis after an initial run.

Referring now to FIG. 5, one option for a path 506 is shown based on a small constraint change, such as a change in a location of a master 502, in accordance with the various aspects and embodiment of the invention. Based on the new position of the master 502, which is a small constraint variation, a path 506 is determined by the tool, which has almost the same length as the path 406 of FIG. 4, based on Manhattan distance measurements. The path 406 has a large change relative to the path 506.

Referring now to FIG. 6, another option for a path 606 through the NoC 400 is shown between a master 602, which is at a new location, and a slave 604 in accordance with the various aspects and embodiment of the invention. The master 602 is at a new location relative to the previous location, as shown by the broken detail lines. Based on the new position of the master 602, which is a small constraint variation relative to the original location of the master 602, a path 606 is determined by the tool, which has almost the same length as the path 406 of FIG. 4, based on Manhattan distance measurements. The path 606 has a small or minimum change relative to the path 406 from the previous run.

Referring collective to FIG. 4, FIG. 5, and FIG. 6, the tool generates the results for the second or subsequent runs. The tool might generate any number of options, such as the path 506 and the path 606. Providing the tool with the previous run, as one constraint, allows the tool to narrow the options to a path with the minimum change relative to the previous run that generated path 406. Accordingly, the ability to consider the initial run of the tool, which generated the path 406, as a constraint will enhance performance of the tool and minimizes variations when analyzing options, such as the path 506 and the path 606.

In accordance with some aspects and embodiments, the tool can be modified to use the same approach for only sub-sections of the NoC.

In accordance with some aspects and embodiments, the tool can be used to ensure multiple iterations of the synthesis are done for incremental optimization of the NoC, which includes a situation when one constraint provided to the tool is information about the previous run.

Certain methods according to the various aspects of the invention may be performed by instructions that are stored upon a non-transitory computer readable medium. The non-transitory computer readable medium stores code including instructions that, if executed by one or more processors, would cause a system or computer to perform steps of the method described herein. The non-transitory computer readable medium includes: a rotating magnetic disk, a rotating optical disk, a flash random access memory (RAM) chip, and other mechanically moving or solid-state storage media. Any type of computer-readable medium is appropriate for storing code comprising instructions according to various example.

Certain examples have been described herein and it will be noted that different combinations of different components from different examples may be possible. Salient features are presented to better explain examples; however, it is clear that certain features may be added, modified and/or omitted without modifying the functional aspects of these examples as described.

Various examples are methods that use the behavior of either or a combination of machines. Method examples are complete wherever in the world most constituent steps occur. For example and in accordance with the various aspects and embodiments of the invention, IP elements or units include: processors (e.g., CPUs or GPUs), random-access memory (RAM—e.g., off-chip dynamic RAM or DRAM), a network interface for wired or wireless connections such as ethernet, WiFi, 3G, 4G long-term evolution (LTE), 5G, and other wireless interface standard radios. The IP may also include various I/O interface devices, as needed for different peripheral devices such as touch screen sensors, geolocation receivers, microphones, speakers, Bluetooth peripherals, and USB devices, such as keyboards and mice, among others. By executing instructions stored in RAM devices processors perform steps of methods as described herein.

Some examples are one or more non-transitory computer readable media arranged to store such instructions for methods described herein. Whatever machine holds non-transitory computer readable media comprising any of the necessary code may implement an example. Some examples may be implemented as: physical devices such as semiconductor chips; hardware description language representations of the logical or functional behavior of such devices; and one or more non-transitory computer readable media arranged to store such hardware description language representations. Descriptions herein reciting principles, aspects, and embodiments encompass both structural and functional equivalents thereof. Elements described herein as coupled have an effectual relationship realizable by a direct connection or indirectly with one or more other intervening elements.

Practitioners skilled in the art will recognize many modifications and variations. The modifications and variations include any relevant combination of the disclosed features. Descriptions herein reciting principles, aspects, and embodiments encompass both structural and functional equivalents thereof. Elements described herein as “coupled” or “communicatively coupled” have an effectual relationship realizable by a direct connection or indirect connection, which uses one or more other intervening elements. Embodiments described herein as “communicating” or “in communication with” another device, module, or elements include any form of communication or link and include an effectual relationship. For example, a communication link may be established using a wired connection, wireless protocols, near-filed protocols, or RFID.

The scope of the invention, therefore, is not intended to be limited to the exemplary embodiments shown and described herein. Rather, the scope and spirit of present invention is embodied by the appended claims.

Claims

1. A method for topology synthesis of a network-on-chip (NoC) using a tool for synthesis and generation of the NoC, the method comprising: generating, using the tool, an initial synthesis of the NoC based on a plurality of constraints;providing a result based on the synthesis;receiving an updated plurality of constraints, wherein the updated plurality of constraints include at least one change to the plurality of constraints;generating, using the tool, a second synthesis of the NoC based on the updated plurality of constraints and the result from a previous run; andproviding an updated result based on the second synthesis,wherein the previous run is provided to ensure that the updated result represents a minimum change between the result and the update result when there is a minimum change between the plurality of constraints and the updated plurality of constraints.

2. The method of claim 1 further comprising generating a list of network elements and configurations as part of the updated result.

3. The method of claim 1 further comprising generating a position for each of a plurality of network elements within a floorplan of the NoC.

4. The method of claim 1 further comprising generating routes within a floorplan of the NoC for a plurality of connected network elements selected from a plurality of network elements.

5. The method of claim 1, wherein the plurality of constraints includes at least one of: physical information about a floorplan;clock domain definition;power domain definition;initiator definition;target definition;data width;path width;connectivity between initiators and targets; andtraffic class definition.

6. The method of claim 1, wherein the updated plurality of constraints includes at least one change in at least one constraint selected from the plurality of constraints.

7. The method of claim 1 further comprising receiving a plurality of global parameters used in the previous run.

8. The method of claim 7, wherein the previous run includes profile information.

9. A non-transitory computer readable medium for storing code, which when executed by one or more processors, would cause the processor to: process, using a tool, a plurality of constraints to generate an initial synthesis of a network-on-chip (NoC);provide a result based on the initial synthesis;receive, at the tool, an updated plurality of constraints that includes one or more changes to the plurality of constraints;generate, using the tool, a second synthesis for the NoC using the updated plurality of constraints and the result based on the initial synthesis; andproviding an updated result based on the second synthesis,wherein the tool utilizes a previous synthesis constraint to ensure that the updated result represents a consistent change between the result and the update result when there is a minor change between the plurality of constraints and the updated plurality of constraints and the minor change includes the previous synthesis constraint.

10. The non-transitory computer readable medium of claim 9, wherein the plurality of constraints includes at least one of: physical location information for a plurality of IP elements in a floorplan;clock domain definition;power domain definition;initiator definition;target definition;data width;path width;connectivity between initiators and targets; andtraffic class definition.

11. The non-transitory computer readable medium of claim 9, wherein the updated plurality of constraints include updating at least one of: physical location information for a plurality of IP elements in a floorplan;clock domain definition;power domain definition;initiator definition;target definition;data width;path width;connectivity between initiators and targets; andtraffic class definition.

12. A tool for synthesis and generation of a network-on-chip (NoC), the tool comprising computer implemented code stored on a non-transitory computer readable medium, which is executed by a processor to cause the tool to: generate a synthesis for the NoC based on a plurality of constraints;provide a result for the synthesis;receive one or more changes to the plurality of constraints;generate an updated synthesis for the NoC based on the one or more changes and the result, wherein the tool utilizes the result as a constraint to minimize variations between the synthesis and the updated synthesis; andproviding an updated result based on the updated synthesis.

13. The tool of claim 12, wherein the one or more changes includes a change in a location of an Intellectual Property (IP) element, which is in communication with the NoC, in a physical floorplan.

14. The tool of claim 13, wherein the tool is caused to determine an updated data path for the IP element based on the change in position.