# Patent

## Title
System clock distribution in a distributed computing environment

## Abstract

A system clock signal is distributed to computing devices within a distributed computing system. The distributed computing devices, which may be dual-die chip carriers, include input and output ports on which system clock signals are propagated. The input and/or output ports of various distributed computing devices may be configured and reconfigured according to system preferences or requirements.

## Background
INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS
Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are incorporated by reference under 37 CFR 1.57 and made a part of this specification.
BACKGROUND
Field
The present application relates to distributed computing, and in particular, to systems, methods and apparatus configured to enable distributed computing.
Background
The architecture of a typical modern computer is based on the von Neumann architecture. The von Neumann architecture is a basic design for a stored-program digital computer that includes a processor that is separated from a memory, which is used to store computer program instructions and data. Even though typical modern computer architectures are more complex than the original von Neumann architecture, typical modern computers retain the separation between the processor and the bulk memory.
Specifically, along with a number of other components, the processor and memory are provided on a printed circuit board, referred to as a motherboard (or “main board”, “system board” or “logic board”). On a typical motherboard, the processor and memory communicate via printed circuit data bus. Throughput, or data transfer rate, on the data bus is much lower than the rate at which a modern processor can operate. The difference between the data bus throughput and the processor speed significantly limits the effective processing speed of the computer when the processor is instructed to process large amounts of data stored in the memory. The processor is forced to wait for data to be transferred to or from the memory, leaving the processor under-utilized.
The performance limitation caused by separating the processor and the memory on a motherboard is referred to as the von Neumann bottleneck. The severity of the bottleneck tends to increase because over time processor speeds and memory sizes tend to increase at a faster rate than the improvements in throughput over the data bus connecting new processors to bigger memories. Previous attempts to alleviate the problem have only been partially successful. For example, previous hardware solutions that address the von Neumann bottleneck include providing a cache between the processor and the bulk memory, and/or providing separate caches with separate access paths for data and instructions; and, previous software solutions include branch predictor algorithms. However, none of the previous solutions fully address the problem.
Additionally, the performance degradations caused by the von Neumann bottleneck are exacerbated in a distributed computing environment in which computer processing of data is carried out by a number of processors operating simultaneously on smaller portions of a larger task. In a conventional distributed computing environment, such as a data center, multiple computers, each with a respective processor and memory, are coupled to one another. Typically, in an effort to reduce overhead, multiple motherboards are connected to one another within one cabinet. Each motherboard is subject to performance degradation caused by the von Neumann bottleneck even if some of the measures discussed above have been taken to alleviate the full impact of the problem. As such, delays in the processing of data caused by the respective data buses on the various motherboards are compounded, as processing service requests between processors are subject to delays on each motherboard that a service request is processed. Accordingly, there lies a challenge to alleviate delays so that memory access bottlenecks are not compounded within distributed computing systems.
SUMMARY
Various embodiments of systems, methods and devices within the scope of the appended claims each have several aspects, no single one of which is solely responsible for the desirable attributes described herein. Without limiting the scope of the appended claims, some prominent features are described herein. After considering this discussion, and particularly after reading the section entitled “Detailed Description,” one will understand how the features of various embodiments are used to enable distributed and dynamically reconfigurable computing systems and devices.
Certain embodiments disclosed herein provide a process of distributing a single-frequency clock signal within a distributed computing system. The process may include generating a system clock signal of a first frequency and providing the system clock signal to a first integrated circuit chip carrier of a plurality of interconnected chip carriers via a first input of the first chip carrier. The process may further include providing a copy of the system clock signal from the first chip carrier to a second chip carrier of the plurality of chip carriers over a configurable input port of the second chip carrier. In certain embodiments, each of the plurality of interconnected chip carriers receives a master clock signal of the first frequency according to a system clock distribution network.
The process may further include reconfiguring the system clock distribution network. In certain embodiments, the system clock distribution network includes a primary clock distribution path and one or more secondary clock paths branching therefrom. The process may further including superimposing a data signal on the copy of the system clock signal. In certain embodiments, the process further includes providing a signal to a third chip carrier of the plurality of chip carriers using the data signal, wherein the third chip carrier is remotely disposed with respect to the first chip carrier.
In certain embodiments, the second integrated circuit chip carrier is one of a processing chip or a memory chip. The process may further include grouping the plurality of chip carriers into nodes, and may further include reconfiguring the node groupings. In certain embodiments, the system clock signal has a frequency of approximately 1 GHZ or greater.
Certain embodiments disclosed herein provide a computing system including a system clock generator configured to generate a system clock signal and provide the system clock signal over a first output line and a plurality of interconnected chip carriers. The plurality of interconnected chip carriers may include a first integrated circuit chip carrier having a plurality of independently-configurable first input lines and independently-configurable first output lines, the plurality of first input lines including a master clock input line in electrical communication with the first output line of the system clock generator for receiving the system clock signal, the plurality of first output lines including a primary clock output line configured to output a copy of the system clock signal. The plurality of interconnected chip carriers may further include a second integrated circuit chip carrier having a plurality of independently-configurable second input lines and independently-configurable second output lines, the second chip carrier being configured to receive the copy of the system clock signal on one of the second input lines. In certain embodiments, the primary clock output line remains active during system operation. The first integrated circuit chip carrier may not be configured to shut off the copy of the system clock signal on the primary clock output line.
The interconnected chip carriers may be substantially hexagonally-shaped chip carriers for accommodating non-orthogonal inter-device communication. Furthermore, the interconnected chip carriers may each include a first die and a second die disposed above the first die. In certain embodiments, the system clock signal includes a substantially square-wave signal.
The system clock generator may be further configured to provide the first clock signal directly to at least one additional chip carrier over a second output line. In certain embodiments, the plurality of interconnected chip carriers includes 2-100 chip carriers, or more. The plurality of interconnected chip carriers may be grouped into one or more independent sub-nodes, nodes, nodes-of-nodes, or super-nodes. In certain embodiments, the plurality of first output lines includes a secondary clock output line, wherein the first integrated circuit chip carrier is configured to deactivate the secondary clock output line during system operation. The first integrated circuit chip carrier may be configured to provide a response signal back to the system clock generator.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a simplified perspective view of one embodiment of a distributed computing architecture including an arrangement of a number of integrated circuit dies.
FIG. 2 is a simplified side view of one embodiment of the distributed computing architecture shown in FIG. 1.
FIG. 3A is a simplified perspective view of one integrated circuit die shown in FIG. 1.
FIG. 3B is a simplified perspective view of another integrated circuit die shown in FIG. 1 which is arranged facing the integrated circuit die shown in FIG. 3A.
FIG. 4 is a simplified plan view of one embodiment of an arrangement of chip carriers configured to enable distributed computing systems, methods and apparatus.
FIG. 5 is a block diagram of one embodiment of integrated circuit components arranged to enable distributed computing systems, methods and apparatus.
FIG. 6 is a block diagram of another embodiment of integrated circuit components arranged to enable distributed computing systems, methods and apparatus.
FIG. 7 is a cross sectional view of one embodiment of a chip carrier and two integrated circuit dies.
FIG. 8 is a simplified perspective view of one embodiment of a hexagonal chip carrier.
FIG. 9A is a top view of a tape automated bonding sheet.
FIG. 9B is an enlarged plan view of the tape automated bonding sheet of FIG. 9A.
FIG. 10 is a simplified perspective view of one embodiment of a distributed computing module including a number of hexagonal chip carriers illustrated in FIG. 8.
FIG. 11 is a cross sectional view of one embodiment of two chip carriers.
FIG. 12 is another cross sectional view of one embodiment of two chip carriers.
FIG. 13 is a plan view of one embodiment of a substrate including ground and power connections.
FIG. 14A is a plan view of one embodiment of an arrangement of chip carriers.
FIG. 14B is a plan view of one embodiment of an arrangement of chip carriers.
FIGS. 15A-B are flow diagrams illustrating embodiments of closed loop communication in a distributed computing environment.
FIGS. 15C-D are flow diagrams illustrating embodiments of open loop communication in a distributed computing environment.
FIG. 15E is a signal flow diagram of one embodiment of a method of distributed computing.
FIG. 16 is a flowchart illustrating one embodiment of a method of distributed computing.
FIG. 17 is a flowchart illustrating one embodiment of a method of distributed computing.
FIG. 18 is a flowchart illustrating one embodiment of a method of distributed computing.
FIG. 19 is a flowchart illustrating one embodiment of a method of shifting to a sleep mode of operation in a distributed computing system.
FIG. 20 is a flowchart illustrating one embodiment of a method of shifting to a sleep mode of operation in a distributed computing system.
FIG. 21 is a flowchart illustrating one embodiment of a method of reactivating an integrated circuit in a sleep mode of operation in a distributing computing system.
FIG. 22 is a flowchart illustrating one embodiment of a method of shifting to a sleep mode of operation in a distributed computing system.
FIG. 23 is a flowchart illustrating one embodiment of a method of reactivating an integrated circuit in a sleep mode of operation in a distributing computing system.
FIG. 24A is a block diagram of an embodiment of a distributed computing system.
FIG. 24B provides an illustration of an embodiment of a device of a distributed computing system.
FIG. 25 is a block diagram of an embodiment of a distributed computing system including multiple system clock sources.
FIG. 26 is a flowchart illustrating an embodiment of a method of configuring a clock input.
FIG. 27 is a flowchart illustrating an embodiment of a process for designating I/O ports in a chip package.
FIG. 28 is a flowchart illustrating an embodiment of a process for configuring a chip package.
FIGS. 29A-H illustrate embodiments of clock signal distribution configurations in a distributed computing system.
FIG. 30 is a schematic diagram illustrating an embodiment of a clock distribution system.
FIG. 31 is a flowchart illustrating an embodiment of a process of managing sleep mode in an integrated circuit chip.
FIG. 32 is a flowchart illustrating an embodiment of a process for communication between devices operating at different clock speeds.



In accordance with common practice the various features illustrated in the drawings may not be drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may not depict all of the components of a given system, method or apparatus. Finally, like reference numerals may be used to denote like features throughout the specification and figures.
DETAILED DESCRIPTION
Various aspects of embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein may be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely illustrative. Based on the present disclosure one skilled in the art should appreciate that an aspect described herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented and/or such a method may be practiced using other structure and/or functionality in addition to or other than one or more of the aspects set forth herein.
FIG. 1 is a simplified perspective view of one embodiment of an architecture for a distributed computing system 100 including an arrangement of a number of integrated circuit dies. For the sake of clarity, the packaging around individual pairs of dies and connections between dies are not shown. However, those skilled in the art will appreciate from the present disclosure, and especially with reference to FIGS. 8 and 10, that in one embodiment, individual pairs of dies can be packaged within a dual-chip carrier also disclosed herein. The system 100 includes a first layer of integrated circuit dies arranged over a second layer of integrated circuit dies. As illustrated in FIG. 1, the first layer of integrated circuit dies includes, for example, twelve dies 101a, 101b, 101c, 101d, 101e, 101f, 101g, 101h, 101i, 101j, 101k, 1011, arranged in a 3×4 matrix. Similarly, the second layer of integrated circuit dies includes twelve corresponding dies 102a, 102b, 102c, 102d, 102e, 102f, 102g, 102h, 102i, 102j, 102k, 1021, arranged in a 3×4 matrix disposed facing the first layer. While FIG. 1 shows twenty-four dies arranged in two layers each having three rows and four columns, those skilled in the art will appreciate from the present disclosure that various embodiments of the architecture include any number integrated circuit dies arranged in two layers each having any number of rows and any number of columns. In particular, in one embodiment, the first and second layers include a different number of integrated circuit dies as compared to one another.
FIG. 2 is a simplified side view of a portion of the system 100 illustrated in FIG. 1. Specifically, six of the twenty-four integrated circuit dies of FIG. 1 are illustrated in FIG. 2, including integrated circuit dies 101a, 101b, 101c included in the first layer and integrated circuit dies 102a, 102b, 102c included in the second layer and disposed facing the corresponding dies of the first layer. The portion of the system 100 illustrated in FIG. 2 also includes example data connections between the respective pairs of integrated circuit dies located on different layers. For example, die 101a and die 102a share a serial connection 120a and a parallel connection 130a. Similarly, die 101b and die 102b share a serial connection 120b and a parallel connection 130b. Similarly, die 101c and die 102c share a serial connection 120c and a parallel connection 130c. Moreover, while each pair of dies discussed above share both serial and parallel connections, alternatively, a given pair of dies can be configured to share at least one of serial connectivity, parallel connectivity or a combination thereof. Moreover, the respective serial and parallel connections discussed above may be implemented via a number of forms including one or more solder balls and/or one or more wire leads.
The portion of the system 100 illustrated in FIG. 2 also includes example data connections between the respective integrated circuit dies located on the same layer. For example, die 101a and die 101b share a serial connection 110a. Similarly, die 101b and die 101c share a serial connection 110b. Similarly, die 102a and die 102b share a serial connection 112a. Similarly, die 102b and die 102c share a serial connection 112b. Moreover, while all the data connections between dies in the same layer are shown to be serial data connections, those skilled in the art will appreciate that each connection may be a serial connection, a parallel connection or a combination operable as serial data connection and a parallel data connection. Moreover, the respective serial connections discussed above may be implemented in a number of forms including one or more wire leads between chip carriers each housing two dies arranged facing one another within a particular chip carrier.
FIG. 3A is a simplified perspective view of the integrated circuit die 101f shown in FIG. 1. The integrated circuit die 101f includes a number of data connections to surrounding dies. For example, the die 101f shares respective serial data connections 110e, 111b, 111f, 110f with the corresponding dies 101e, 101b, 101j, 101g, which are all included in the first layer. Also, for example, the die 101f shares a respective serial data connection 120f with the die 102f. Similar to FIG. 3A, FIG. 3B is a simplified perspective view of the integrated circuit 102f die shown in FIG. 1. For example, the die 102f shares respective serial data connections 112e, 113b, 113f, 112f with the corresponding dies 102e, 102b, 102j, 102g, which are all included in the second layer.
FIG. 4 is a simplified plan view of one embodiment of an arrangement 400 of chip carriers configured to permit distributed computing systems, methods and apparatus. Specifically, as an illustrative example only, the arrangement includes seven chip carriers 401, 402, 403, 404, 405, 406, 407. Those skilled in the art will appreciate from the present disclosure that any number of chip carriers so configured may be arranged together. Each of the seven chip carriers 401, 402, 403, 404, 405, 406, 407 is configured to house two dies, one from each of two layers of dies (e.g. as illustrated in FIG. 1). The chip carrier 401 is placed at the center of a ring of chip carriers including chip carriers 402, 403, 404, 405, 406, 407. Accordingly, each of the chip carriers 402, 403, 404, 405, 406, 407 is a neighboring chip carrier to the chip carrier 401. And as shown in FIG. 4, each chip carrier, other than the chip carrier 401 has three neighboring chip carriers including the chip carrier 401. For example, the chip carrier 403 has the chip carriers 401, 402, 404 as neighbors. In one embodiment, a chip carrier has direct communication with at least one of the neighboring chip carriers. In one embodiment, a chip carrier has direction communication with all of the neighboring chip carriers. Furthermore, in one embodiment, a chip carrier communicates with non-neighboring chip carriers through a data path that traverses one or more neighboring chip carriers. As described in further detail below with reference to FIGS. 5 and 6, in various embodiments, the dies included within each chip carrier include features to enable more efficient communication with neighbors and non-neighbors. For example, a data path between the chip carrier 403 and the chip carrier 406 exists through the chip carrier 401 and at least another data path exists through chip carriers 404 and 405. Either of the aforementioned data paths can be made more efficient by routing data away from the primary functional blocks on the dies included in the chip carriers 401, 404 and 405. In other words, by preventing transient data from interfering substantially with the primary function of chip carriers on the data path, which do not directly contribute to the processing of the data at either end of the data path, delays in some cases are reduced.
FIG. 5 is a block diagram of one embodiment of integrated circuit components arranged to enable distributed computing systems, methods and apparatus. Specifically, FIG. 5 illustrates an on-chip system 500 that includes features, in addition to the primary function of the chip, to enable more efficient communication with neighbors and non-neighbors. In particular, the system 500 includes an internal function module F(X) 501 which is the primary functional module of the on-chip system. For example, the internal function is a graphics processor, a general purpose processor, a data storage element or any other type of device that may be embodied as an integrated circuit. That is, the internal function module 501 can be any one of several functions, such as a processor, a memory, a multi-core processor, intelligent memory, a multi-array memory, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), an array sensor, a motion sensor, or a linear circuit. The internal function of the block is dependent on the ICs packaged within the chip carrier. Processed data from the internal function block is received in a parallel fashion and formatted into serial data which is output from the building block.
The system 500 also includes an external communications interface module (ECI) 520, a non-blocking cross-point switch 530, a configuration control processor (CCP) 540, a local private memory (LPM) 550, and an internal function interface (IFI) 510. The ECI 520 is coupled to the non-blocking cross-point switch (CPS) 530, and the CCP 540. The ECI 520 also includes an external connection 521 that is connectable to external devices off-chip either serially or in parallel or a combination of serial and parallel. The non-blocking cross-point switch 530 is also coupled to the CCP 540 and the IFI 510. The LPM 550 is also coupled to the CCP 540 and the IFI 510. The IFI 510 is coupled to the internal function module 501. In one embodiment, the connection between the IFI 510 and the internal function module is a parallel data interface. In one embodiment, the connection between the IFI 510 and the internal function module is a serial data interface.
The ECI 520 provides direct unshared and shared communication connection with neighboring chip carriers. For example, the ECI 520 provides communication connection with six neighboring devices. Indirect communication with remote (non-neighboring) devices is also provided data paths through neighboring devices. A communication connection between devices provides transfer of information such as instructions, data, commands, and status.
In one embodiment, the ECI 520 contains six output signal lines and six input signal lines for communication outside the die. Thus a hexagonal chip carrier can be configured to have six interface sets, one set on each of the six sides of the chip carrier. In one embodiment, each of the six sets is made up of four signal lines, two independent full-duplex serial communication signal pairs, wherein one pair is connected to a first IC and the second pair is connected to a second IC. As mentioned above, each interface set can also include two power connections and five ground connections.
In one embodiment, static and/or dynamic control of the ECI 520 is performed by the CCP 540. For example, the CCP 540 provides activation and deactivation of the input signal lines, activation and deactivation of the output signal lines, activation and deactivation of a power-conserving sleep mode, selection of digital or linear transmission mode, configuration to select an orientation of the installed die to its device package, internal clock signal selection, preamble message disassembly and dissection, and exception handling.
In one embodiment, the CCP 540 also controls other elements of the device. One function of the CCP 540 is to provide assembly information and static and dynamic control of various elements of the device, including the ECI 520, the CPS 530, the LPM 550, and the IFI 510, to which the CCP 540 is connected via one or more buses.
Certain configuration information such as a very small iterative routine and history data can be written into a Write Once Read Many (WORM) element of the LPM 550 during manufacture. During various stages of manufacturing, assembly, and test operations, other data can be written into the LPM WORM by the CCP 540, such as the date of die wafer manufacture; various tests, dates, and results; wafer lot number; and other information.
Static and dynamic configuration and reconfiguration performed by the CCP 540 can be conducted at any time, including during program loading and execution. Safeguards can be implemented to prevent interference of executing programs or routines, except at prescribed operating points. For example, in one embodiment, the system can change from operating with one set of operating rules to operating with another set of operating rules. In one embodiment, more than one operating system will reside in a device package to allow the system to quickly change operating functions, on demand, to be able to respond to a different set of operational conditions. The system can respond by changing from one operating system to another, resulting from an external stimulus, to provide dynamic reconfiguration. Dynamic reconfiguration has the potential to expand the capability of a processing system by including multiple operating systems that can be selected to handle different computing needs, problems, or assignments. This can expand the range of work, processing power, and speed in handling complex tasks. It also allows the processing system to address multiple incoming threats, improving overall security. Multiple operating systems can quickly respond to a threat and, if the threat increases, while in a threat operating environment, the operating system can be elevated to a higher threat level by changing to another operating system. In another embodiment, the system, or portions thereof, can load a secondary operating system based on the primary threat. As mentioned above, the CCP 540 can control this configuration and reconfiguration of all the elements of a device die.
In one embodiment, the CCP 540 is configured to operate from firmware and software stored in the LPM 550. The LPM 550 can include, for example, write once read many (WORM) memory, random access memory (RAM), and electrically erasable and programmable read-only memory (EEPROM), which include flash memory. In another embodiment, the CCP 540 is additionally or alternatively configured to operate from firmware and software stored in a bulk memory system of the internal function of one or both of the embedded ICs.
In one embodiment, the CCP 540 of a device can read and write from the memory of the device, including erasing EEPROM of the device. In another embodiment, the CCP 540 can directly address the memory of neighboring devices and indirectly address remote memories, including both bulk memories of the internal functions and the LPM 550 of remote devices. In one embodiment, only the local CCP 540 of a device can write information into the WORM memory of the device; however, at least a portion of the information stored in the WORM memory can be accessible to other devices on a read only basis. In one embodiment, some of the information in the LPM 550 or bulk memory can only be accessed by the local CCP 540.
In one embodiment, the LPM WORM memory is used to retain information that is not intended to change, such as information relative to the history of the die, process tracking information that becomes available during the manufacture and assembly process, or a start-up “boot strap” routine. In one embodiment, the “boot strap” firmware routine is a sparingly programmed reiterative loop routing intended to provide communication in a simple form so as to provide only the ability to load another program with a more substantial communication routine. In one embodiment, the routing includes a method whereby the CCP 540 escapes the reiterative loop to execute the second more substantial routine that allows further communication with other memories, registers, and logic of the die.
In one embodiment, the LPM 550 includes random access memory (RAM), accessible by the CCP 540. The RAM can include a volatile RAM scratch pad memory. The RAM can provide, among other things, volatile software program storage and temporary data storage. Because of the RAM memory volatility, any data in RAM memory can be lost in the event of a power failure or a complete power shut down. Thus, in one embodiment, a minimal “keep alive” current or voltage is implemented to prevent data from being lost when the chip is in a sleep mode of operation.
In one embodiment, the LPM 550 includes EEPROM for storage of data that is semi-permanent, such as constants, or storage of firmware. The EEPROM is non-volatile but can be electrically erased and re-written.
Write Once Read Many (WORM), Random Access Memory (RAM) and Electrically Erasable Programmable Read Only Memory (EEPROM) can be addressed as a block, that is, each has an addressable block of addresses within a block of addresses.
In one embodiment, the LPM 550 stores permanent data as well as dynamically changing data. Permanent data includes information such as manufacturing and assembly information and specific bootstrapping information. Dynamic data includes Configuration Control Processor program code and parameter data for the setup and control of internal portions of the device, including the local internal function module 501.
In operation, the CPS 530 generally provides selective connection between lines of the ECI and the IFI. In one embodiment, the CPS is a non-blocking switch which takes as input, signals from the ECI and the IFI and provides, as output, one of those same signals to the inputs of the ECI and IFI.
In one embodiment, the CPS 530 receives data from twelve ECI inputs and four IFI inputs. In one embodiment, the source and destination of signals are addressed via address registers which can include: source of all sixteen input signals as a group, destination of all sixteen output signals as group, source of all ECI input signals as a group, destination of all ECI output signals as a group, source of all external ECI input signals as a group, destination of all external ECI output signals as a group, source of all internal ECI input signals as a group, destination of all internal ECI input signals as a group, source of all IFI signals as a group, destination of all IFI signals as a group, source and destination of all input and output signals as group, or individually selected source and destination input and output signals as group.
The content of the CPS address registers can be updated by the incoming data address. The content can also be overwritten on at least a temporary basis by the CCP until control is released by the CCP 540. In one embodiment, when the CCP 540 takes control, it shuts down or diverts the effected signals and alerts the effected devises so as to prevent loss of data. Also, in one embodiment, the CCP 540 has the ability to redirect the input to output signal switch selection where data is routed between two devices via this intervening device.
In one embodiment, the CPS 530 is a 16×16×1 switch that steers data between six external data connections of a die and/or four internal data connections of the IFI with the die under direction of the CCP 540. In one embodiment, the chip carrier die utilizes six of the twelve external connections for communication to neighboring chip carrier and the remaining connections to the other die within the chip carrier. Although in one embodiment, the steering is performed by the CCP 540, in another embodiment, such as can be used during bootstrap/debug operations, firmware can set specific CPS 530 connections to steer data and controls from the ECI 520 to locations within the LPM 550 and to the controls of the CCP 540.
The CPS 530 contains connections to the ECI 520 and the IFI 510. The ECI 520 is described in detail above, whereas the IFI 510 is described below. The IFI 510 provides connections (buses) to the internal function module 501 which can include any logic function such as memory, data processor, ASIC, FPLA, sensor, etc. For example, depending on the internal function module 501, the IFI 510 can provide multiple 128-bit buses for connection to the internal function module 501.
In operation, the IFI 510 controls direct communication access to the internal function module 501. As such, it receives all or substantially all signals originating from the internal function module 501. The ECI 520 controls direct communication access with external devices. In one embodiment, the ECI 520 determines whether or not a received packet is addressed to be processed by the internal function module 501. If the packet can be and/or is addressed to be processed by the internal function module 501, the ECI 520 passes the packet to the non-blocking CPS 530. The packet is then passed through the IFI 510 to the internal function module 501 for substantive processing.
On the other hand, if the packet is addressed for another chip and/or cannot be serviced locally, and is thus merely passing through the system 500, the ECI 520 retransmits the packet to another chip, thereby preventing the packet from disturbing the primary function of the on-chip system 500.
In one embodiment, the chip carrier operates internally in serial fashion, with the exception of the IFI 510 which can operate in serial or parallel. In one embodiment, the internal function includes a parallel internal function, PF(x). For example, PF(x) can be implemented as a parallel processor or as a parallel memory, sensor, scan array, any function that originates as a parallel device that can be contained in the allotted area of the chip carrier.
In another embodiment, the internal function includes a serial internal function, SF(x). Serial processing arithmetic logic units (ALUs) provide certain advantages over parallel ALUs. One advantage is that serial processors are generally implemented with fewer logic elements than a parallel processor of equal capability. In some cases, a serial processing unit is much simpler than the parallel equivalent, having less transistors and/or a simpler design layout.
Further, many peripheral devices such as keyboard, mouse, data storage disks, monitors, music, USB, internet, etc., use a serial transmission interface. Using serial communications uses fewer wires, smaller less expensive connectors, and each device does not require a parallel-to-serial data converter to receive data and a serial-to-parallel data converter to send data. Since the above devices are all naturally serial devices, the logical transmission interface can be serial transmission of data.
Embodiments illustrating communication with a serial device are described below. In one embodiment, the system uses the clock signal supplied by the peripheral device to transfer data in both directions. Although the clock signal supplied by the system to the peripheral device can be many, many times faster than the peripheral clock rate, reliable transmission can still occur. When the system wishes to communicate with the peripheral device, the system places its high speed clock signal on the transmit line to the peripheral device. Whether or not the peripheral device can follow the clock signal, it will easily be able to discern the presence of signal on the line and send its slower clock signal back to the system on its transmit line. In response, the system can switch from its normal transmitted clock frequency to the speed of the peripheral clock signal and send the lower speed clock signal back to the peripheral device. Using this lower-speed received clock from the system, the peripheral device can then accept the signal data.
In the above embodiment, the system initiated communication with the peripheral device. In another embodiment, communication is initiated by the peripheral device. In one embodiment, A similar method is used.
Described below are various modes of communication operation and nodal control processing (NCP) enabled by these various modes. Those of skill in the art will appreciate that alternative embodiments can exclude some of the described modes or include other modes not described in detail herein.
Direct addressing of resources of near neighbor devices for passage of instructions, data, commands and status can use the (TRA) address contained in a standard format and protocol, as in all communications between devices. If the direct path port is busy or reserved, the message can be placed in a port queue for later transmission or sent as an indirect message via another intervening device. If the port is not available for some other reason, such as failure, the message can also be sent indirectly via another intervening device. If the port is reserved it can still be able to transmit messages, stored in queue, during non-busy periods of the reserved transmission port. Reserved ports can be configured to operate in one of at least two ways. In one embodiment, the reserved port is locked to a device other than the reserving device. In another embodiment, the device can share the port, holding priority access to the port for the reserving device.
With indirect addressing, the path to the remote destination terminal device can be selected in several ways. In one embodiment, indirect remote addressing takes place via at least one intervening device.
In one embodiment, particularly useful when there is a great amount of data to be transmitted or if time sensitivity cannot tolerate interruptions, there is provided a pre-dedicated path from the sending device to the remote receiving terminal device. To dedicate paths in intervening devises, an originating device can send a message to a remote receiving terminal device and via this message pre-dedicates the path along the way, even in intervening devices. In one embodiment, this message includes an indication to either lock the dedicated path or to not lock the dedicated path. In one embodiment, the pre-dedicated path remains in effect until instructed by the originating device to sever the path in a similar manner to that used to initiate the path. In another embodiment, the pre-dedicated path is severed after a pre-determined amount of time if it is not used, thereby freeing system resources. In one embodiment, if the message indicates that the path is not to be locked, a higher priority transmission can request temporary use of the path on a non-interfering basis.
Reserving a path, in one case, simply means that the reserving device has the highest priority and will bypass the transmission queue and go to the first position of the queue. The reserved port can still be available to transmit messages from the port queue on a First In First Out (FIFO) basis. If the transmission path must always be available to the reserving device, a second case can provide the ability of the CCP 540 to lock out storage of messages to and/or transmissions from the queue.
Another embodiment of remote transmission is to place data in an available port queue for transmission on a first in (come) first out (served) (FIFO) basis when the queue is available.
Yet another embodiment of remote transmission is to pre-assign, by priority, positions in the port queue for transmission. This embodiment can advantageously be used for non-interfering transmission to/from the queue.
Yet another embodiment of remote transmission is a so-called “Hand-Off” of a message destined for a remote terminal device from the originating device to a near neighbor device. The receiving near neighbor device has the option to follow the addressing guideline it receives from the originating device; however, it also has the option to modify the address route because the addressed port has a large built up queue, the port is reserved, there is a better route available, to balance traffic of a transmission port, or for other reasons. The received device will then hand off the message to the next device over the selected port.
Still another embodiment of remote transmission can advantageously be used when a message is to be sent to all or a prescribed set of devices. Thus, the message is broadcast to the devices by spidering out from the originating device to the intended devices. This broadcast will take place in one of at least three ways: i) directly and automatically after an authority device transmits a “Device Reset” to the intended devices; ii) on a demand basis; or iii) on a non-interfering basis. A broadcast can take place via devices that are not a designated broadcast recipient. Broadcasting can be used, for example, to distribute software code and/or data to many carriers in a spider-type fashion to ‘bulk load’ groups of carriers.
Connection between the IFI 510 and the CPS 530 provide a pathway for instructions, addresses, commands, data, status, and other information between the ECI 520 and the internal function module 501. For test purposes, the CCP 540 can test the internal function or interact with the signals of the ECI 520 to perform tests of the ECI 520 or the internal function. The CCP 540 can, for example, cause the diversion of pre-determined signals to be read from certain locations of LPM 550 and signals to be stored in certain locations of LPM 550. In this way, the CCP 540 can access both local private memories and the internal function memory via the interface registers.
As shown in FIG. 5, the IFI 510 provides connections between the CCP 540, LPM 550, CPS 530 and the internal function module 501. In one embodiment, the internal function includes a processor in the lower die position and at least one of a memory, sensor, imager, or second processor in the upper die position. In one embodiment, the internal function includes a processor in the lower die position and a bulk memory in the upper die position. This processor-memory configuration can directly execute software or firmware applications stored in the memory through the use of parallel signal buses. In another particular embodiment, the internal function includes a processor in the lower die position and a sensor or imager in the upper die position, wherein the sensor or imager in the upper die position also includes memory. This memory can, for example, store software or firmware to support the sensor or imager functionalities.
A node can be capable of processing that standalone elements are incapable of. In one embodiment, “lock step execution” is controlled, not on a clock basis, but on an instruction execution basis. A provision to prevent system lockup can also be included.
In one embodiment, NCP provides direct access from the periphery input signal of a chip carrier through the ECI 520 and the CPS 530 to the IFI 510 parallel register that services the internal function. Likewise, the internal function data is placed in a parallel output register in the IFI 510, passed directly through the CPS 530 and the ECI 520 to the periphery signal connection. In one embodiment, NCP can disallow port communication access, of unused ports, so as to not allow disruptive requests from other processes external to a node and not used in the node.
Each node can be assigned to specific functions or perform as a general purpose processor. For example, in various embodiments, a node can be used as a single processor, a pre-processor, a data processor, a post processor, an input processor, an output processor, an intelligent memory control, an interface control processor, a memory control processor, an array processor, a wave front processor, or various permutations and combinations of the above. It will be appreciated that other interoperability uses of nodes is also envisioned. Further, each node can be dynamically and statically controlled to, e.g., change nodal connections.
FIG. 6 is a block diagram of another embodiment of integrated circuit components arranged to enable distributed computing systems, methods and apparatus. Specifically, FIG. 6 illustrates an on-chip system 600 that includes features, in addition to the primary function of the chip, to enable more efficient communication with neighbors and non-neighbors. The on-chip system 600 is similar to and adapted from the on-chip system 500 illustrated in FIG. 5. Accordingly, elements common to both on-chip systems 500 and 600 share common reference indicia, and only differences between the two are described herein for the sake of brevity. Within the system 600, the external communications interface and internal communication interface are combined into a dual external-internal communications interface 610. The dual external-internal communications interface 610 includes a serial input 601 and a serial output 603 that are connectable to external devices off-chip. The dual external-internal communications interface 610 also includes a parallel output 605 and a parallel input 607 that are connectable to the internal function module 501.
Accordingly, in operation, the serial input 601 receives serial data communications from off-chip devices. The dual external-internal communications interface 610 converts the received serial data communications into a parallel stream which is transmitted to the internal function module 501 via the parallel output 605. In a reciprocal manner, the parallel input receives data communications from the internal function module 501. The dual external-internal communications interface 610 converts the received parallel data communications into a serial stream which is transmitted to external devices via the serial output 603.
FIG. 7 is a cross sectional view of one embodiment of a chip carrier 700 and two integrated circuit dies 701, 702. The chip carrier 700 includes a first conductive tray, serving as a package cap 740, and a second conductive tray, serving as the package base 750. The first die 701 is substantially housed by the package cap 740. The first die 701 is optionally soldered to the package cap 740, as shown in FIG. 7. However, in one embodiment, the first die 701 is not soldered or connected to the package cap 740. The second die 702 is substantially housed by the package base 750. Connection pads on the two dies are coupled together using solder balls (or the like) 721, 722, 723. The second die 702 is connectable to another chip carrier or an external device via a signal tab 710 that is coupled to at least one connection tab on the second die 702.
FIG. 8 is a simplified perspective view of one embodiment of a hexagonal chip carrier 800. The chip carrier 800 includes sixty connections that can be uniformly distributed about the six sides of the hexagon. The connections include six power connections, thirty ground connections, and twenty-four signal connections. As mentioned above, in one embodiment, the power connections and ground connections are attached directly to the substrate, whereas the signal pins are flying connections.
Specifically, the chip carrier 800 has a generally hexagonal shape and includes a first conductive tray 801 and a second conductive tray 802. A generally hexagonal or substantially hexagonal shape can vary from a hexagon by, for example, having rounded edges, squared edges, beveled edges etc. For the sake of example only, the first conductive tray 801 is referred to herein as the package cap 801, and the second conductive tray 802 is referred to herein as the package base 802. In one embodiment, the cap 801 and the base 802 are approximately 1.25 inches across and are made of aluminum nitride, which is an insulator with a relatively high thermal conductivity and a thermal coefficient of expansion similar to that of silicon (Si), of which the ICs can be made.
The chip carrier 800 also includes power supply lines 810a, 810b, 810c, 810d, 810e, 810f, each of which is located at a respective corner of the chip carrier 800. The power supply lines 810a, 810b, 810c, 810d, 810e, 810f are electrically isolated from the conductive package base 802 and cap 801 by corresponding insulating jacket portions 811a, 811b, 811c, 811d, 811e, 811f. 
Each side of the chip carrier 800 includes five ground pins coupled to both the package base 802 and the package cap 801. For example, five ground pins 901, 903, 905, 907, 909 are visible on one side of the chip carrier 800. Each side of the chip carrier 800 also includes four signal pins that extend into and out of gaps in the sides of the chip carrier 800. For example, signal pins 902, 904, 906, 908 are visible on one side of the chip carrier 800. The signal pins 902, 904, 906, 908 extend through corresponding gaps 822, 824, 826, 828, respectively. In one embodiment, each signal pin is jacketed by a respective electrically insulating sleeve at least within the respective gap through which the signal pin extends. Moreover, while the chip carrier 800 shown has four signal pins and five ground pins on each side, those skilled in the art will appreciate that each side of a chip carrier of any shape can be configured to include any number of signal pins and any number of grounds pins.
Moreover, the chip carrier can be made in a variety of shapes, including triangular, square, rectangular, and hexagonal as shown in FIG. 8. In one embodiment, the chip carrier includes leaded connections, which are electrical connections having a length of wire or soldering pad that comes from the device. Leaded connections can be used for physical support, to transfer power, to probe circuits, and to transmit information. Leaded connections from through-hole components are called pins. These pins can bend under the package body like the letter J, called a J-lead, or come out, down, and form a flat foot for securing to the board, called an S-lead. In another embodiment, the chip carrier includes leadless connections. A leadless chip carrier (LCC) is a type of packaging for integrated circuits that includes leadless connections, which includes rounded pins through the edges of the package.
FIG. 9A is a top view of a tape automated bonding (TAB) sheet 900. The TAB sheet 900 provides one method of providing signal and ground tabs to one or more integrated circuit dies included in the package 800 described above with reference to FIG. 8. Accordingly, as a continuation of the example of FIG. 8, the signal pins 902, 904, 906, 908 and ground pins 901, 903, 905, 907, 909 illustrated in FIG. 8 are also shown in FIG. 9A. FIG. 9B is an enlarged plan view of a portion of the TAB sheet 900 of FIG. 9A, which specifically shows enlarged illustrations of the ground pins 901, 903, as well as the signal pin 902.
With further reference to FIG. 9A, the signal pins 902, 904, 906, 908 are formed when the excess material of the TAB sheet 900 is cut away along line 911. Similarly, ground pins 901, 903, 905, 907, 909 are formed when the excess material of the TAB sheet 900 is cut away along line 913. The signal pins and ground pins for other sides of the chip carrier 800 are formed in a similar manner using the unmarked pins shown in FIG. 9A. In one embodiment, all of the pins are formed simultaneously by shearing away the excess material after the TAB sheet 900 is placed over the combination of the package base 802 and at least one die.
In one embodiment, the TAB sheet 900 is made of relatively thin beryllium copper, on the order of two to three thousandths of an inch. In one embodiment the TAB sheet 900 is made of a thin material so as to provide flexure of the signal tabs between two adjacent chip carriers (see FIG. 10) to compensate for thermal expansion and contraction. One method of manufacturing the TAB sheet 900 is to etch the center area, leaving a patterned periphery to be sheared to the proper length during assembly along lines 911 and 913 for example.
FIG. 10 is a simplified perspective view of one embodiment of a distributed computing module, referred to herein as a process module element (PME) 1000, including a number of hexagonal chip carriers illustrated in FIG. 8. A PME as described herein is an assembly of multiple substrates with mounted chip carriers and input/output connectors, including signal and power connections. In one embodiment, the PME is constructed from approximately sixty piece parts, whereas the typical motherboard is assembled of upwards of six-hundred piece parts, including an approximately circuit board substrate having between eight and ten layers. As a result, such systems are generally assembly-intensive products.
FIG. 10 illustrates one embodiment of a PME 1000 including eleven hexagonal chip carriers 800a, 800b, 800c, 800d, 800e, 800f, 800g, 800h, 800i, 800j, 800k, each having substantially the same design as the chip carrier 800 shown in FIG. 8. The PME 1000 also includes a mounting substrate 1060 which is described in further detail below with reference to FIG. 13. However, briefly, the mounting substrate 1060 includes ground vias, such as the first and second vias 1070a and 1070b, and the power supply vias, such as the first, second and third power supply vias 1061a, 1061b, 1061c. The hexagonal chip carriers 800a, 800b, 800c, 800d, 800e, 800f, 800g, 800h, 800i, 800j, 800k are mounted on one side of the substrate 1060. A ribbon shaped heat sink 1050b is located on the opposite surface of the substrate 1060 as compared to the chip carriers. The ribbon shaped heat sink 1050b extends across the surface of the substrate 1060 and includes kerfs, such as kerfs 1080, spaced periodically or intermittently across the heat sink 1050b. The PME 1000 also include a heat transfer blade 1040 arranged on the opposite side of the heat sink 1050b as compared to the substrate 1060. The PME 1000 also includes sidewalls 1020a, 1020b, 1020c that serve the dual function of physically protecting the chip carriers and providing external connections to the hermaphroditic connectors 1010.
In the embodiment illustrated in FIG. 10, the hermaphrodite connector is approximately five inches high and approximately seven eighths of an inch wide. The HCON also has a surround shroud shell including an interference fit socket one half of the connector with a mating plug on the other half of the connector. The surround shroud shell can connect the power return ground. In one embodiment, the surround shroud shell is longer than the power and signal connections, thus being the first electrical connection between two devices as they are mated, whereas the power pins are next in length and next to make power connection. As the power return ground is the first connected and the power is next connected, both prior to signal connection, “hot swapping” of PME modules is made possible.
In one embodiment, the surrounding sidewalls provide a receiver for a number of input/output modules that contain signal drivers and receivers. The input/output insert modules can be one of a variety of insert modules, including a one meter drive fiber optic driver and receiver pair, a 30-meter drive fiber optic driver/receiver pair, a single-ended driver/receiver pair, or a double-ended driver/receiver pair. In one embodiment, the connector insert modules include the driver/receiver electronic circuitry as well as the connector pins and sockets.
The hermaphrodite connector allows a PME to be tested to be inserted into an operating PME having testing functionality. This PME to be tested can be introduced to an operating PME on a “hot swap” basis as described above, wherein plugging one unit into another will not disrupt an ongoing process in either module. While the operating PME can be structurally similar to the unit under test, the operating PME can also be a test module built for the test PME devices. In a similar manner, a test PME can be inserted into an operational PME to be tested.
In one embodiment, NCP provides direct access from the periphery input signal of a chip carrier through the ECI and the CPS to the IFI parallel register that services the internal function module. Likewise, the internal function data is placed in a parallel output register in the IFI, passed directly through the CPS and the ECI to the periphery signal connection. In one embodiment, NCP can disallow port communication access, of unused ports, so as to not allow disruptive requests from other processes external to a node and not used in the node.
Each node can be assigned to specific functions or perform as a general purpose processor. For example, in various embodiments, a node can be used as a single processor, a pre-processor, a data processor, a post processor, an input processor, an output processor, an intelligent memory control, an interface control processor, a memory control processor, an array processor, a wave front processor, or various permutations and combinations of the above. It will be appreciated that other interoperability uses of nodes is also envisioned. Further, each node can be dynamically and statically controlled to, e.g., change nodal connections.
In one embodiment, all chip carriers in a node are similar and/or substantially identical. In other embodiments, multiple different kinds of chip carriers are present in a node. While each of the chip carriers in a node may or may not be identical, a few of the chip carriers (by reason of their unique mounted position on the substrate) can be used as interface controllers. Various interface embodiments are described above. Another functionality of a chip carrier is a Nodal Control Processor, which provides setup and control of a node or multiple nodes. Multiple nodes can be combined to work as a super-node.
Once a chip carrier, a node, a PME or a combination thereof has been manufactured, a programmer can utilize an external host computer to load and control program code into the device, designated the client device. Various software modules and tools can reside in a host computer such as a laptop, desktop, or a previously configured chip carrier-based computer running an operating system such as Linux. This software can be programmed to assist in the development of software modules, routines, nodal control, software tools, and operating systems that will load and control the program code residing in the client device. Such external software executes in the host computer and not in the client device. The host tools and software can include functionality to support the client device during manufacture, initial programming, testing, integration, application development, and debugging.
In one embodiment, the host provides software development tools for portions of a client device. For example, the client device can include a processor (and/or a memory, sensor, etc.) identified as the internal function. External tools to support the internal function include editors, compilers, linker, and loaders that produce code that can be executed on the client device. Other external tools can include tools and libraries stored on the host device to provide software mechanisms for communication with and control of the client device.
In one embodiment, the host operating system includes host driver software to initiate an interface connection between the host hardware and the client device hardware. These drivers can be low-level language routines called through software tools and the host operating system for communication with the client device.
Once the physical communications connections and the software mechanisms are in place, host software tools can use these communications mechanisms to setup and control the client device. These tools can be programmed to formulate message sequences and control bits to access the client device. These tools can include an initial bootstrapping sequence to load more intelligent and complex loaders and routines into the client device. The host can then treat the client device as a ‘smart’ device and communicate with it using high-level messages such that the client device can remotely perform setup and configuration processes at the direction of the host.
The host and client device can operate in tandem. The host, for example, can execute a user application partially on the host and partially on the client. As described above, the client device can be configured as one or more processing nodes having many chip carriers per processing node. In one embodiment, the host issues processing tasks to the client device and receives the results reported back to the host. In another embodiment, the host delegates an entire processing problem to the client device and then retrieves the solution from the client device.
Various software and firmware modules can also be executed by the client device. The client device can, for example, execute software applications designed specifically for the one or more of the internal function processors that resides within the client device. As mentioned above, at least some portions of the client device are externally controllable from the host for initial communication and bootstrap loading. In another embodiment, other portions of the client device are controllable from within the client device itself. For example, portions of the setup, controls, and internal logic are accessible from a configuration control processor through the use of internal software routines and tools. In one embodiment, internal software performs the main setup and configuration of the client hardware to support a user application and to communicate with the host. The user application can, for example, dynamically change hardware settings from within the user application by making calls to library routines which reside in an operating system of the internal function processor.
In one embodiment, operating system library routines executed by the internal function of the client device support the extensive capabilities of the client device. The routines can communicate to other portions of the hardware either through the CCP or directly. Internal software library routines can include routines for configuration/reconfiguration and the sending/receiving of messages across the communications paths of the client device. In one embodiment, messages pass through the input/output portions of the client device without interfering with the operation of the internal function processing. In another embodiment, messages are received into the internal function. In yet another embodiment, messages are sent from the internal function or memory of the client device.
In one embodiment, the internal software contains library routines available to a user application executed on a host device for performing control, setup, and data transfer. At the completion of data transfer, a signal can be returned through the library routine to the user application.
In one embodiment, the client device also contains a set of internal status and control routines that respond to queries from the host or other client devices. These queries can provide the hooks for debugging both the user application and client operating system. A programmer, developer, or application tester can use these status and control routines for software debugging. The routine can include routines for controlling the internal function, interrogating specific hardware, and viewing and changing memory. In a similar fashion, the host can include corresponding commands in the host software to status and debug the client device through a data connection path to these internal software status and control routines.
The internal software can be configured to support several chip carriers configured into a processing node with a group of local communications paths. When the processing node is operating, these communications paths, data transfers and signaling routines facilitate the user application coordination across the multiple chip carriers of the processing node.
As mentioned above with respect to the dynamic and static reconfigurability of such devices, at the completion of the user application, internal software can switch to another user application that is to be executed in the client device. In response, the operating system can reconfigure the hardware and the communications paths to support the new user application. In another embodiment, the operating system itself can be switched to a one of a different complexity based on the specific user application and its processing requirements.
In one embodiment, a client device is configured by software executed on a host device to initially define the interconnections between client devices. After the interconnections are defined, the operating system and user application software of the client device is loaded into the associated hardware by using software tools executed on a host computer.
Additional software executed on a host device can reconfigure the interconnections and communications paths within the client device while the current user application is executing on the client device. The reconfiguration can also allow the change of the user application and an operating system defined to support the application requirements. In one embodiment, when the first user application completes, the second user application is ready to reconfigure the hardware architecture and required communications paths within a few clock cycles.
Dynamic configuration can be directed from a host computer or it can be directed from within the client device itself through, e.g., library routine calls. These calls can be based from the currently configured client devices or it can be from an additional device directing the reconfiguration, such as with the PME Module Control Processor.
Dynamic configuration can, in one embodiment, support a ‘failed component’ workaround. For example, if the failed component is an input/output, a different input/output path can be selected to be used. If the failed component is the internal function processor of a first chip carrier, a second chip carrier can be used, wherein the input/output connections are reassigned and the program and data in the memory of the first chip carrier are reassigned to the second chip carrier.
In one embodiment, chip carriers embodied in a client device are uniquely determined by their physical location on the client device, an internal identifier, and by software which executes within each chip carrier. In one embodiment, the client device itself has similar identification information stored within it. This chip carrier software can range from ‘stand-alone’ mathematical type routines to operating systems. The desired configuration of the client device can be changed at any time to support this range of processing capabilities.
In one embodiment, a user can determine the complexity of support required for the particular application and select the appropriate operating system. In another embodiment, the appropriate operating system is automatically selected based on the support required. A number of operating systems of varying complexity are available for selection. The complexity can, for example, be based on the range of operating system calls that the user software uses. For example, a first operating system can support a few tasks which communicate with near neighbor chip carriers of a processing node and does not support dynamic reconfiguration. A second operating system can support communication between processing nodes either on the same or distant PME and also support dynamic reconfiguration of subordinate processing nodes to add or subtract processing power of the user application software.
During the development of the particular application, software tools executed on a host computer can configure the particular client device operating systems and libraries to form the executable code which will execute in the client device or the chip carriers thereof. This executable code, including operating systems and user applications, can be transferred to the client device hardware to form a configured system. After this configuration is set, the software tools executed on the host computer can download changes in the background to the initial configuration concurrently while the client device is executing other software. In one embodiment, these changes are coordinated with the client device hardware and software so as to not interfere with the current client device processing.
FIG. 10 above illustrates one embodiment of a PME which can be used as a client device. From the figure, it is evident that certain of the chip carriers are proximal to the input/output interfaces. These chip carriers, or others, can be designated Module Control Processors (MCPs) and loaded with MCP Software to control the interaction of the PME with other devices. The MCP can also be configured to handle the configuration/reconfiguration of the other chip carriers on the PME. The MCP can also be configured to set up the communications paths between chip carriers and to initialize the user application software in the chip carriers. While, in one embodiment described above, these tasks are handled by a host computer, in another embodiment, they are instead ‘off-loaded’ to the MCP for additional flexibility. With this flexibility, the MCP(s) of the client device can direct their own reconfiguration by calling appropriate software reconfiguration routines.
Data passed to/from the PME communications paths are routed through the input/output portion of the MCPs. In one embodiment, the data is passed directly to other chip carriers on the PME bypassing the internal function and memory of the MCP, whereas in another embodiment, the MCP captures the data, interprets the data, and then directs the data to the appropriate processing node or chip carrier. This capture, interpretation, and direction forms an intermediate level of task control within the client device. In some embodiments, multiple PMEs operate together as a processing node. The Module Control Processors within the multi-PME node can be configured to handle intermediate data transfer and reconfiguration control for the processing node.
As mentioned above, the messages can be transmitted in a broadcasting fashion. Broadcasting can be used, for example, to distribute software code and/or data to many carriers in a spider-type fashion to ‘bulk load’ groups of carriers. Broadcasting, as described above, can be used to load software into many client devices without the need for the host to individually load each client device.
In one embodiment, software for individual client devices is broadcast to all devices and each individual client device discards information not intended for the device. The broadcast software can address individual client devices using a unique identification number stored within each client device (or chip carrier thereof) during manufacture or testing.
In one embodiment, bootstrapping is used to set up the communications paths to and through multiple client devices. After this is completed, information is broadcast to a number of devices and the client devices can begin processing. Broadcasting can be used in the initial setup of devices or for upgrading portions of the devices. These broadcast techniques allow the host to transmit information to specifically identified client devices.
As described above, processor nodes support distributed processing with additional features such as pre-processing, instruction processing, and post-processing. In one embodiment, a processor node is dynamically configurable to operate as a distributed processing system, whereas in another embodiment, a processor node is dynamically configured to operate in a traditional processing method as utilized by contemporary systems.
Distributed processing can be used to provide greater process transaction throughput by using more than one chip carrier of a processor node (or more than one processor node) to operate on data in a pipeline fashion. For example, using five dual-die chip carriers (DDCCs) forming a node could at any point in time operate on five or more different instructions simultaneously. In one embodiment, during a first time period, an instruction is fetched by one chip carrier operating as an Instruction Fetch Processor (IFP); during a second time period, the instruction is interpreted by the IFP and other chip carriers operating as Operand Fetch Processors (OFPs) are directed where to fetch operands; during a third clock period, the OFPs fetch various operands; during a fourth clock period, a chip carrier acting as an Instruction Processor (IP) performs the instruction directed by the IFP; and during a fifth clock period, a chip carrier acting as an Instruction Result Processor (IRP) stores the data, from the IP, in the location directed by the IFP. FIG. 10 illustrates a processor node with components designated as in the above example. The Instruction Fetch Processor (IFP), in one embodiment, works in a look-ahead program timing mode and thus, out of sequence jumps (branch) to other locations can be anticipated in most cases and therefore reduce precious processing time.
FIG. 11 is a cross sectional view of one embodiment of two chip carriers 1100 mounted on a substrate 1060. The first of the two chip carriers 1100 includes a package base 1120a, a lower die 1102a, a ground tab 1103a, an upper die 1101a and a package cap 1110a. The package base 1120a is fused to the substrate 1060 with solder 1105a. The lower die 1102a is fused to the package base 1120a with solder 1106a. The ground tab 1103a is electrically coupled both the package base 1120a and the package cap 1110a to receive ground potential. The ground tab 1103a is also coupled to both the upper die 1101a and the lower die 1102a using solder balls (or the like). Similarly, the second of the two chip carriers 1100 includes a package base 1120b, a lower die 1102b, a ground tab 1103b, an upper die 1101b and a package cap 1110b. The package base 1120b is fused to the substrate 1060 with solder 1105b. The lower die 1102b is fused to the package base 1120b with solder 1106b. The ground tab 1103b is electrically coupled both the package base 1120b and the package cap 1110b to receive ground potential. The ground tab 1103b is also coupled to both the upper die 1101b and the lower die 1102b using solder balls (or the like).
With further reference to FIG. 11, one method of manufacturing such a chip carrier is as follows. First, align and reflow solder the lower die 1102 to the cavity of the carrier package base 1120a. Second, position a TAB sheet over the package base 1120a housing the lower die 1102a. Third, position the upper die 1101a over the TAB sheet and lower die assembly. Fourth, reflow solder the upper die 1101a to the TAB sheet, the lower die 1102a and the package cap 1110a. In one embodiment, the upper die 1101a is not soldered to the package cap 1110a. Fifth, reform the signal leads of the TAB sheet for connection to neighboring devices so as to provide compensation of expansion and contraction due to temperature variations. Sixth, place and cement the package cap 1110a to the assembly providing a micro strip coaxial transmission path embedded in a dielectric insulator for each signal line. Finally, solder the power and ground to the package cap 1110a, package base 1120a and TAB sheet. Those skilled in the art will appreciate that the above describes but one embodiment of manufacturing a stack and that other methods formed by removing, adding, or altering the above steps can be used. Moreover, those skilled in the art will appreciate that specific connections to particular signal pins and connection pads have not been exhaustively described for the sake of brevity.
FIG. 12 is another cross sectional view of one embodiment of two chip carriers 1200. The two chip carries 1200 are similar to and adapted from the two chip carriers 1100 illustrated in FIG. 11. Accordingly, elements common to both chip carriers 1100 and 1200 share common reference indicia, and only differences between the two are described herein for the sake of brevity. Specifically, the two chip carriers 1200 include first and second signal tabs 1115a and 1115b in place of the first and second ground tabs 1103a and 1103b illustrated in FIG. 11. The first signal tab 1115a is coupled to a connection pad on the lower die 1102a and is electrically shielded from the package base 1120a and package cap 1110a. Similarly, the second signal tab 1115b is coupled to a connection pad on the upper die 1101b and is electrically shielded from the package base 1120b and package cap 1110b. The first and second signal tabs 1115a and 1115b are electrically connected with solder ball 1117, which thereby creates a data path from the lower die 1102a to the upper die 1101b. Moreover, those skilled in the art will appreciate that from the present disclosure that any combination of connections can be made between the dies 1101a, 1102a, 1101b, 1102b using signal tabs, and the scope of the claims is in no way limited by the example illustrated in FIG. 12. The signal tabs 1115a and 1115b may be referred to as “flying leads.”
FIG. 13 is a plan view of one embodiment of the substrate 1060 included in the PME illustrated in FIG. 10. In one embodiment, the substrate 1060 is conductive and includes a number of voltage connections arranged so as to provide at least one of power and ground levels to one or more chip carriers. For example, in one embodiment, in operation the substrate 1060 is at the same potential as electrical ground. The ground potential is established and maintained by ground vias, such as the first and second vias 1070a and 1070b. The first and second vias 1070a and 1070b, for example, are electrically coupled to the substrate 1060. In the example illustrated in FIG. 13, the ground vias are interspersed between the power supply vias, such as the first, second and third power supply vias 1061a, 1061b, 1061c. The power supply vias are electrically insulated from the substrate and are arranged so as to connect to insulated power lines located at the corners of the hexagonal chip carriers. Moreover, while the substrate 1060 is specifically arranged for receiving and supporting hexagonally-shaped chip carriers, those skilled in the art will appreciate that in another embodiment, the ground and power vias can be arranged to accommodate other shapes of chip carriers, such as rectangular and square chip carriers.
FIG. 14A is a plan view of one embodiment of an arrangement 1400a of rectangular chip carriers arranged in a row-by-column manner, such that each chip carrier has four neighbors with which communication is potentially available. Specifically, the arrangement 1400a includes nine chip carriers 1401a, 1401b, 1401c, 1401d, 1401e, 1401f, 1401g, 1401h, 1401i. The chip carrier 1401e is in the center of a ring formed by the chip carriers 1401a, 1401b, 1401c, 1401d, 1401f, 1401g, 1401h, 1401i. However, since the chip carriers 1401a, 1401c, 1401g, 1401i are located diagonally away from the corners of chip carrier 1401e, it is difficult for chip carrier 1401e to establish direct communication with the chip carriers 1401a, 1401c, 1401g, 1401i. On the other hand, the chip carriers 1401b, 1401d, 1401f, 1401h are beside broad sides of the chip carrier 1401e, and as such, it is relatively more convenient for the chip carrier 1401e to establish direct communication with these neighboring chip carriers.
FIG. 14B is a plan view of one embodiment of another arrangement 1400b of rectangular chip carriers arranged in a brick pattern, such that each chip carrier has six neighbors with which communication is potentially available. Specifically, the arrangement 1400b includes nine chip carriers 1402a, 1402b, 1402c, 1402d, 1402e, 1402f, 1402g, 1402h, 1402i. The chip carrier 1402e is in the center of a ring formed by the chip carriers 1401b, 1401c, 1401d, 1401f, 1401h, 1401i. Moreover, as result of the brick pattern arrangement, each of the chip carriers 1401b, 1401c, 1401d, 1401f, 1401h, 1401i is considered a neighbor to the chip carrier 1402e. Accordingly, in one embodiment the chip carrier 1402e is able to establish direct communication with each of the chip carriers 1401b, 1401c, 1401d, 1401f, 1401h, 1401i without sending signals through other chip carriers or over a printed circuit board.
Inter-Device Communication Methods
Transfer of data between distributed devices may be achieved by superimposing data on clock signal lines between the devices. In addition to any primary, secondary and/or tertiary clock signal paths transmitted between the devices (discussed in greater detail below), the remaining device connections may also be used for communication. These connections may use internal clock signals to pass data between devices. Two types of communication that may be used in distributed computing systems include (1) communications between two directly connected devices; and (2) communications between remotely connected devices, which may require communication via intervening devices. Each distributed computing device may have multiple output and input ports. In certain embodiments, each output and input port is configured independently. This may allow device signals to operate in an “open loop” or “closed loop” communication manner. Open loop and closed loop communication are described in detail below.
Closed loop communication may refer to communications in which a message is sent over a transmit connection from an originating device to a physically connected receiving device. The receiving device may then determine the validity of the message and respond by sending an acknowledgement message back to the originating device, thereby closing the communication loop. In closed loop communication, the input and output signals may operate together as a dependent pair. Furthermore, it may be necessary for the receiving device's CCP to be involved in the transaction because the CCP may need to store the message in memory and check the message's validity before responding to the originating device. There may be intermediate points between the originating source and the final destination. In certain embodiments, each of these intermediate points requires the message to be stored and validated before forwarding. Such communication process may be referred to as “store and forward.” This technique may result in reduced system performance due to one or more of the following: (1) increase in time to send each message; (2) involvement of intervening CCPs; (3) store and forward of intervening messages; and (4) required memory storage. Certain embodiments disclosed herein provide greater latitude with the input and output signals because such signals operate independently.
FIG. 15A is a flow diagram illustrating an embodiment of a closed loop communication between near-neighbor devices. In the diagram of FIG. 15A, a first device (DDCC1) sends a message to a second device (DDCC2). After receiving the message, DDCC2 responds with a message back to DDCC 1, which closes the communication loop. FIG. 15B is a flow diagram illustrating an embodiment of a closed loop communication between near-neighbor devices in which the receiving device DDCC2 responds with a signal, rather than a message, back to DDCC 1. Use of a signal response, rather than a message, may serve to reduce the size of the response and therefore allow for better usage of the return path for other purposes. The response signal may be returned upon acceptance and validation of the request message.
Certain embodiments disclosed herein provide “open loop” communication between devices, which may provide a number of benefits. Firstly, the speed of message transmission between remote neighbor devices via intervening devices may be increased. For example, message transmission via intervening devices may occur without intervening device processor involvement with the message transmission. This may eliminate interruption of current processing tasks being performed by the intervening processors. Secondly, open loop communication may provide a reduction in system memory storage requirements because transmitted messages need not be stored to memory and then forwarded.
Open loop communication techniques disclosed herein may allow for individual device input and output communication port connections to operate independently of each other for signals and/or messages. Such signals and messages sent in opposite directions may or may not be related in any way.
In certain embodiments, signaling techniques for open loop communication do not require ‘direct handshaking’ of messages passed from the originating source device to the destination device via intervening devices. However, certain embodiments include transmission of “transmit not acknowledged” (TNAK) and “transmit acknowledged” (TACK) signals (described in greater detail below) to each previous device on the previous sending device's transmit line. Overall open loop message communication may be closed when the destination device returns an independent response message back to the originating device via intervening devices. This message from the final destination device to the originating device may provide the error status of the overall received message (for example, ‘error free’ or ‘error indicated’). This may allow intervening devices to simply pass-on the message data to the next intervening device to the final destination without performing any data validation. The intervening device processors may not be interrupted, and the message not stored for forwarding with the message data transfer.
In certain embodiments, however, an intervening addressed device specified in the original message may also be a recipient of the message. In such a case, the message may be stored for processing by the intervening device. If the intervening device discovers an error, after responding with a TNAK/TACK signal back to the previous sending device, and having already passed-on the message to the next device in the transmission chain, the intervening device may send a response message back to the originating device in addition to the final destination device response message. Such error detection by the intervening addressed device may allow for the message to be resent from the originating source device sooner than if the final destination DDCC device alone had detected the error. The intervening addressed device may require support of the device's Configuration Control Processor (CCP) for the return message, which handles such actions in certain embodiments. Therefore, the device's Functional Intent F(X) processor may not be interrupted from its processing tasks to assist in forming the response message.
In certain embodiments of distributed computing systems, a primary distribution device (described in detail below) is configured to send a Not Acknowledge (NAK) or Acknowledge (ACK) status signal or message back to a system clock generator module (described in detail below) upon receipt of an EOT. Periodic signals or messages may also be sent to the system clock generator. In certain embodiments, open loop data transmission functionality utilizes a particular signaling sequence, wherein the transmit connection of the sending device enters a high impedance state for a specific number of finite periods after sending an “end of block” (EOB) or “end of transmission” (EOT) signal. For example, the transmit connection may enter a high impedance state for three or more finite periods.
The finite time periods in which the transmit connection enters a high impedance state may allow the receiving device to turnaround its receive connection to send responses back to the sending device during the sending device's high-impedance time periods. In certain embodiments, during a first period, a Transmit-Not-Acknowledge (TNAK) signal may be unconditionally sent back to the sending device. During a second period, a Transmit Acknowledge (TACK) signal may be conditionally sent back to the sending device if no error condition in the transmission is detected. Such TNAK/TACK response signal back to the originating device may not necessarily mean that the overall message was sent without error, but may simply mean that the EOB or EOT was received by the receiving device. A Cyclic Redundancy Character Check (CRCC) check may or may not have been performed on the message.
Certain transmission error conditions may be detected using the open loop communication techniques discussed above. For example, the following conditions may be detected: (1) non-detection of an unconditional TNAK in response in the first time period by the originating device; (2) detection of an unconditional TNAK signal in the first time period by the originating device without subsequent detection of a TACK response signal in the second time period; and (3) detection of a TACK signal in the second time period but by the originating device without having detected a TNAK signal in the first time period. In certain embodiments, a successful TNAK/TACK response to the sending device comprises receipt of an unconditional TNAK signal followed by a conditional concatenated TACK signal in first and second time periods, respectively.
In certain embodiments, to complete the an open loop message transaction, the final destination device transmits a response message back to the originating device. Such transmission may be sent over a separate communications path than the transmit connection from the destination device to the originating device through intervening devices.
Open loop communication techniques as described herein may provide a mechanism for testing communications paths between physically connected devices. For example, the Transmission Not Acknowledged (TNAK) and Transmission Acknowledged (TACK) response signals, as described herein, may be used to identify and isolate an error on a transmit connection, or an error on a receive connection. Furthermore, an individual die within a device may also be tested with the use of a third device that is physically connected to both the testing device and the tested device. Therefore, a grouping of three devices, which are physically connected, can work together to determine and isolate a failure using TNAK/TACK response signaling to determine a failed input or output connection. In certain embodiments, by involving additional devices, any port or die in a packaged device may be tested. In certain embodiments, even if two or more errors exist, using TNAK/TACK signaling, the errors can be identified, isolated, and/or worked around by re-routing message communications paths.
FIG. 15C is a flow diagram illustrating an embodiment of an open loop communication between near-neighbor devices with a return signal. The near neighbor device returns a TNAK/TACK signal back over the receive connection to the sending device in response to receiving the EOB or EOT of the received message. In certain embodiments, the return signal represents only that the message was received, but not that it was validated. Upon receipt of the EOT, the near neighbor device may or may not send a response status message to the originating device to close the loop. FIG. 15C is a flow diagram illustrating an embodiment of an open loop communication to a remote device, wherein at least one intervening device is involved in the transmission. In certain embodiments, each intervening device, as well as the final destination device, returns a TNAK/TACK signal to its sending device in response to the EOB or EOT of the received message. The TNAK/TACK signals may only represent that the message was received, but not that it was validated. Upon receipt of the EOT message and performance of error checking, the final device may send a message via various routing paths from the final destination device to the originating DDCC device.
FIG. 15E is a signal flow diagram 1500E of one embodiment of a method of distributed computing. As described above, in one embodiment a chip carrier includes two integrated circuit dies, the two integrated circuit dies are arranged so that they are adjacent to one another and are in communication with one another. As such, as described herein communication with a dual chip carrier includes communication with one or both of the integrated circuit dies included therein.
Specifically, FIG. 15E depicts signaling to facilitate the establishment of a data tunnel between two chip carriers that each includes one or more integrated circuit dies. A resulting data tunnel may exist between two adjacent chip carriers or between two chip carriers that are separated by one or more other chip carriers. While the signal flow diagram 1500E of FIG. 15E includes only three chip carriers 1501, 1502, 1503, those skilled in the art will appreciate that FIG. 15E is merely an illustrative example. Those skilled in the art will also understand from the present disclosure that any number of chip carriers may be involved with transmitting, processing and responding to a service request and/or transmitting and/or processing data associated with a service request.
Turning to the example illustrated in FIG. 15E, as indicated by block 1510, the method includes the first chip carrier 1501 determining and/or generating a service request for the third chip carrier 1503. Given that the third chip carrier 1503 is not an immediate neighbor of the first chip carrier 1501, the service request traverses the communication interface of the second chip carrier 1502. To that end, as indicated signal 1511, the method includes the first chip carrier transmitting a local packet including the service request to the second chip carrier 1502. As indicated by signal 1512, the method includes the second chip carrier 1502 responding to the first chip carrier 1501 by transmitting a “transmission not-acknowledged” (TNACK) signal which indicates that the local packet may not have been successfully received. As indicated by signal 1513, if the local packet was successfully received, the method includes the second chip carrier 1502 transmitting a “transmission acknowledged” (TACK) signal to the first chip carrier 1501, which negates the automatically transmitted TNACK signal. In one embodiment, the first chip carrier 1501 is configured wait for a TACK signal after first receiving a TNACK signal for a period of time before relying on the TNACK signal. In one embodiment, the chip carrier receiving a local packet transmits the TNACK and TACK signals back over the same physical connection that the local packet is received on, thereby freeing other signal pins on both chip carriers to communicate. In other words, the TNACK and TACK signals are received by the chip carrier that originally transmitted the local packet on a signal pin normally used for transmission. As such, signal pins on that chip carrier that are normally used for receiving signals are free for other communication.
As indicated by signal 1514, the method includes the second chip carrier 1502 transmitting the local packet to the third chip carrier 1503. The second chip carrier 1502 may transmit the local packet before, during or after the second chip carrier transmits the TNACK signal and/or the TACK signal. Additionally and/or alternatively, the second chip carrier 1502 retransmits portions of the local packet as they are received from the first chip carrier 1501.
As indicated by signal 1515, the method includes the third chip carrier 1503 responding to the second chip carrier 1502 by transmitting a TNACK message which indicates that the local packet may not have been successfully received. As indicated by signal 1516, if the local packet was successfully received, the method includes the third chip carrier 1503 transmitting a “transmission acknowledged” TACK message to the second chip carrier 1502, which negates the automatically transmitted TNACK message. In one embodiment, the second chip carrier 1502 is configured wait for a TACK message after first receiving a TNACK message for a period of time before relying on the TNACK message.
As indicated by block 1517, the method includes the third chip carrier 1503 processing the service request originally sent by the first chip carrier 1501. As indicated by block 1518, the method includes the first and third chip carriers establishing a data tunnel through the second chip carrier 1502. In one embodiment, in instances where the resulting data tunnel includes a path including one or more chip carriers (e.g. the second chip carrier 1502) between the two chip carriers where the data tunnel terminates (e.g. the first and third chip carriers 1501, 1503), the data tunnel is established using the respective communication interfaces of the middle chip carriers without interfering with the primary function of the integrated circuits included on those middle chip carriers. In other words, each respective communication interface substantially routes data away from the primary functional units on the respective integrated dies that do not originate a service request and/or process the service request. As such, only the chip carrier at which a service request originates and the chip carrier in which the service request is processed substantially request, process, access, create and/or consider data traversing the data tunnel. In the example illustrated in FIG. 15E, the communication interface of one or more of the dies included in the second chip carrier 1502 routes data away from the primary functional units included in the one or more of the dies, so that the computing operations of those functional units is substantially unaffected.
FIG. 16 is a flowchart illustrating one embodiment of an open-loop method of distributed computing. The illustrated method can be modified in a variety of ways. For example, in another embodiment, various portions of the illustrated method can be combined, can be rearranged in an alternate sequence, removed, or the like. Specifically, FIG. 16 illustrates a method of requesting remote processing of a service request. For example, with further reference to the signal flow diagram 1500 of FIG. 15, the flowchart of FIG. 16 illustrates one method the first chip carrier 1501 may follow to establish a data tunnel with the third chip carrier 1503. To that end, as represented by block 16-1, the method includes determining a remote service requirement. In other words, an integrated circuit within one chip carrier determines through operation of CCP software and/or firmware that data or service is required from another integrated circuit not located within the same chip carrier. As represented by block 16-2, the method includes preparing a service request. As represented by block 16-3, the method includes transmitting the service request to neighboring chip carrier. As represented by block 16-4, the method includes waiting for an acknowledgement for a first period of time. If an acknowledgement message is not received during the first period (TO path from 16-4), as represented by block 16-5, the method includes determining whether or not a fault threshold has been breached. In one embodiment, a fault threshold is a predetermined number. The predetermined number is representative of times that a service request can be sent to the same neighboring chip carrier without receiving an acknowledgement regarding the reception before the sending chip carrier ceases to transmit service requests to that particular neighboring chip carrier. If the fault threshold has not been breached (No path from 16-5), the method includes looping back to repeat the transmission of the service request as represented by block 16-3. On the other hand, if the fault threshold has been breached (Yes path from 16-5), as represented by block 16-6, the method includes transmitting the service request to an alternate neighboring chip carrier.
Referring again to block 16-4, if a TNACK message is received within the first period of time (TNACK path from 16-4), as represented by block 16-7, the method includes waiting for an acknowledgement for a second period of time. The second period of time can be the same or different than the first period of time discussed above. If an acknowledgement message is not received during the second period (TO path from 16-7), as again represented by block 16-5, the method includes determining whether or not a fault threshold has been breached as discussed above. On the other hand, if a TACK message is received within the second period of time (TACK path from 16-7), as represented by block 16-8, the method includes waiting for a response to the service request for a third period of time. The third period of time may be dynamically set based on the estimated transmission delays and processing time for a particular service request. Additionally and/or alternatively, the third period of time may be a random number or a predetermined fixed number or any other value useful for a particular arrangement of chip carriers.
If a response message is not received during the third period (TO path from 16-8), as again represented by block 16-5, the method includes determining whether or not a fault threshold has been breached as discussed above. On the other hand, if a response message is received within the third period of time (TR path from 16-8), as represented by block 16-9, the method includes receiving a response to the service request through a data tunnel. As represented by block 16-10, the method includes providing confirmation of reception message and/or further service requests over the data tunnel to the servicing chip carrier.
FIG. 17 is a flowchart illustrating one embodiment of a method of distributed computing. The illustrated method can be modified in a variety of ways. For example, in another embodiment, various portions of the illustrated method can be combined, can be rearranged in an alternate sequence, removed, or the like. Specifically, FIG. 17 illustrates a method of receiving and processing a service request. For example, with further reference to the signal flow diagram 1500 of FIG. 15, the flowchart of FIG. 17 illustrates one method the second and third chip carriers 1502, 1503 may follow to establish a data tunnel back to the first chip carrier 1501. To that end, as represented by block 17-1, the method includes receiving a service request within a local packet. As represented by block 17-2, the method includes transmitting a TNACK signal in response to receiving the local packet. If the packet was validly received, as represented by block 17-3, the method includes transmitting a TACK signal to the chip carrier from which the local packet was received. As represented by block 17-4, the method includes determining whether or not the service request is a request for local service. If it is determined that the service request is a request for local service (Yes path from 17-4), as represented by block 17-5, the method includes processing the service request locally in order to generate a response to the service request. As represented by block 17-6, the method includes establishing a data tunnel back to the requesting chip carrier. In one embodiment, the data tunnel traverses the same path that the service request traversed to the servicing chip carrier. In one embodiment, the data tunnel traverses a shorter and/or more efficient path. As represented by block 17-7, the method includes transmitting a first response over the data tunnel to the requesting chip carrier. In another embodiment, the data tunnel is established before or while the service request is processed locally.
Referring again to block 17-4, on the other hand, if it is determined that the service request is not a request for local service (No path from 17-4), as represented by block 17-8, the method includes transmitting the service request within a local packet to the next chip carrier in the path to the servicing chip carrier. As represented by block 17-9, the method includes determining whether or not a transmission acknowledgement has been received. If a transmission acknowledgement has been received (Yes path from 17-9), as represented by block 17-10 the method concludes. On the other hand, if a transmission acknowledgment has not been received (No path from 17-9), as represented by block 17-11, the method includes determining whether or not a fault threshold has been breached. If the fault threshold has been breached (Yes path from 17-11), as represented by block 17-12 the method includes transmitting the local packet to an alternate neighbor. If the fault threshold has not been breached (No path from 17-11), as represented by block 17-8, the method includes retransmitting the local packet to the same chip carrier.
In some embodiments, testing can occur whenever communications occur between devices. When a communication to a device is not acknowledged (e.g., when TACK is not received within an acknowledgement window or clock cycle), the system can be configured to test and dynamically reconfigure the distributed computing system such that a different communications link and/or device is used. For example, after a failed communication from a first device to a second device, the system can perform a method of determining whether other devices neighboring the second device can successfully communicate with the second device.
FIG. 18 is a flowchart illustrating one embodiment of a method of distributed computing. The illustrated method can be modified in a variety of ways. For example, in another embodiment, various portions of the illustrated method can be combined, can be rearranged in an alternate sequence, removed, or the like. Specifically, FIG. 18 illustrates a method of testing and dynamically reconfiguring a distributed computing system, such as the system 100 described above with reference to FIGS. 1 and 2. As represented by block 18-1, the method includes selecting a chip carrier for testing. As noted above, a chip carrier as described herein can be configured to house one or two integrated circuit dies. As such, by selecting a chip carrier, one or two separate integrated circuit dies are selected for simultaneous or individual testing depending on the particular configuration of the chip carrier selected. As represented by block 18-2, the method includes indentifying neighboring chip carriers of the chip carrier selected for testing. In one embodiment, a subset of the neighboring chip carriers is identified. In one embodiment, all of the neighboring chip carriers are identified. As represented by block 18-3, the method includes selecting a first neighboring chip carrier from which to transmit a test packet.
As represented by block 18-4, the method includes transmitting a test packet (or test vector or the like) from the selected neighbor to the chip carrier under test. As represented by block 18-5, the method includes waiting to receive an acknowledgement for a first duration of time. In one embodiment, for example, the first duration is one of a predetermined duration, a duration randomly determined during operation, a duration determined based on expected processing time of the test packet. Nevertheless, those skilled in the art will appreciate that the first duration can be set in any number of ways and the example provided herein merely illustrate particular possibilities for setting the first duration.
If an acknowledgement is received during the first duration (ACK path from 18-5), as represented by block 18-6, the method includes confirming communication access to the chip carrier under test. Further, in one embodiment, the method further including testing the functionality of the one or two integrated circuit dies included in the chip carrier under test once communication access to the chip carrier has been confirmed. Testing the functionality of a particular internal function module is dependent on the actual functionality of that particular internal function module. Those skilled in the art will appreciate how to conduct such testing for a particular chip once communication access to the chip has been confirmed.
If an acknowledgement is not received during the first duration (TO path from 18-5), as represented by block 18-7, the method includes determining whether or not there are identified neighboring chip carriers that have not yet attempted to transmit a test packet to the chip under test. If there are one or more such neighboring chip carriers (Yes path from 18-7), as represented by block 18-8, the method includes selecting an alternative neighboring chip carrier from the subset of one or more chip carriers that have not yet transmitted a test packet to the chip carrier under test. Further, the method includes looping back to the portion of the method represented by block 18-4 so as to repeat the transmission of the test packet from the newly selected neighboring chip carrier.
Referring again to block 18-7, if there are no more neighboring chip carriers that have yet to transmit a test packet (No path from 18-7), as represented by block 18-9, the method includes deeming the chip carrier under test to be in a failed state because none of the neighbors involved in the testing were able to confirm communication access with the chip carrier under test. As represented by block 18-10, the method includes rerouting service requests and/or functions previously delegated to the chip carrier under test to alternate chip carriers where possible. In one embodiment, rerouting service requests and/or functions includes computer software that distributes service requests and/or delegates functions to operable chip carriers, taking into account the loss of capacity of chip carriers that are currently deemed to be in a failed state.
If communication to the second device through an alternate neighbor is successful, then it can be assumed that there is a problem with the communication link between the first device and the second device. Accordingly, communications within the system can be re-routed to avoid using that communication link. If communication to the second device through an alternate neighbor is unsuccessful, then it can be assumed that there is a problem with the second device. Accordingly, the system can be configured to reassign functions and/or communications that would otherwise be designated for the second device.
Sleep Mode Management
FIG. 19 is a flowchart illustrating one embodiment of a method of shifting to a sleep mode of operation in a distributed computing system. The illustrated method can be modified in a variety of ways. For example, in another embodiment, various portions of the illustrated method can be combined, can be rearranged in an alternate sequence, removed, or the like. Specifically, FIG. 19 illustrates a method of initializing a sleep mode operation. As represented by block 19-1, the method includes at least one of powering up an internal function module (referenced as F(X) in FIGS. 19-23) and resetting a sleep command flag internal to the internal function module. As represented by block 19-2, the method includes enabling external communications interface (ECI) receivers. In one embodiment, ECI receivers are assumed to be in active state so long as the chip receives power. As represented by block 19-3, the method includes a configuration control process (CCP) configuring an internal function module, an associated cross-point switch (CPS), an associated local private memory (LPM), and an associated internal function interface (IFI). As represented by block 19-4, the method includes configuring automatic sleep mode timeout periods. Examples of sleep mode timeout periods are discussed in further detail below with reference to FIG. 22.
FIG. 20 is a flowchart illustrating one embodiment of a method of shifting to a sleep mode of operation in a distributed computing system. The illustrated method can be modified in a variety of ways. For example, in another embodiment, various portions of the illustrated method can be combined, can be rearranged in an alternate sequence, removed, or the like. In one embodiment, the method responds to an instruction that signals an orderly completion of some or all transactions of modules included on a chip so that one or more of the modules can safely enter an idle state. Specifically, FIG. 20 illustrates a method of directing an internal function module into a sleep mode of operation. As represented by block 20-1, the method includes providing an internal function module with a command to enter a sleep mode of operation. As represented by block 20-2, the method includes an ECI decoding the sleep mode command. As represented by block 20-3, the method includes sending the decoded command to a CCP. As represented by block 20-4, the method includes the CCP decoding the sleep mode command destination. As represented by block 20-5, the method includes determining whether or not the sleep mode command is applicable to the entire chip or merely a subset of particular modules included on the chip.
If the sleep mode command is applicable to the entire chip (Yes path from 20-5), as represented by block 20-15, the method includes completing the ECI transaction. That is, each ECI port is directed to enter sleep mode by the CCP. In certain embodiments, the command originates from a different ECI port than the particular ECI port directed into the sleep mode. In another embodiment, the command originates from the same ECI port directed to enter sleep mode or even the CCP itself. By completing the transaction on a particular ECI port directed to enter sleep mode both ends of the transaction complete in a normal manner. On the other hand, if a ECI port immediately entered the sleep mode the transaction would have been truncated and an error would be indicated and/or induced on the communicating partner of the ECI port.
As represented by block 20-16, the method includes turning off the ECI output clock. As represented by block 20-17, the method includes placing the internal function module F(X) into sleep mode. As represented by block 20-18, the method includes deactivating the internal function module clocks. As represented by block 20-19, the method includes shutting down the IFI. As represented by block 20-20, the method includes shutting down the CCP. In one embodiment, the various components discussed above are shutdown in the order presented herein. However, those skilled in the art will appreciate that the order presented is merely one example of the order in which various components on a chip can be placed into sleep mode.
Referring again to block 20-5, if the sleep mode command is not applicable to the entire chip (No path from 20-5), as represented by blocks 20-6 through 20-14, the method includes determining which modules the sleep command is applicable to and shutting down those modules. For example, as represented by block 20-6, the method includes determining whether or not the sleep command is applicable to the internal function module F(X). If the sleep command is applicable to the internal function module (Yes path from 20-6), as represented by block 20-7, the method includes placing the internal function module into sleep mode and turning off the internal function module clocks. As represented by block 20-8, the method includes determining whether or not the sleep command is applicable to the ECI port. If the sleep command is applicable to the ECI port (Yes path from 20-8), as represented by blocks 20-9 and 20-10, the method includes completing the ECI transaction and turning off the ECI output clock. As represented by block 20-11, the method includes determining whether or not the sleep command is applicable to the IFI. If the sleep command is applicable to the IFI (Yes path from 20-11), as represented by block 20-12, the method includes shutting down the IFI. As represented by block 20-13, the method includes determining whether or not the sleep command is applicable to the CCP. If the sleep command is applicable to the CCP (Yes path from 20-13), as represented by block 20-14, the method includes shutting down the CCP. As represented by block 20-21, after processing the portions of the method discussed above, the method includes providing an indication that the sleep mode of operation has been entered as directed.
FIG. 21 is a flowchart illustrating one embodiment of a method of reactivating an integrated circuit in a sleep mode of operation in a distributing computing system. The illustrated method can be modified in a variety of ways. For example, in another embodiment, various portions of the illustrated method can be combined, can be rearranged in an alternate sequence, removed, or the like. Specifically, FIG. 21 illustrates a method of directing a chip die into an active mode of operation that is wholly or partially in a sleep mode of operation. As represented by block 21-1, the method includes providing a chip with a command to exit the sleep mode of operation. As represented by block 21-2, the method includes an ECI decoding the command. As represented by block 21-3, the method includes determining whether the CCP is in a sleep mode of operation. If the CCP is currently in a sleep mode (Yes path from 21-3), as represented by block 21-4, the method includes reactivating the CCP. On the other hand, if the CCP is already active (No path from 21-3), as represented by block 21-5, the method includes sending the decoded command to a CCP. As represented by block 21-6, the method includes the CCP decoding the command destination(s). As represented by block 21-7, the method includes determining whether or not the command is applicable to the entire chip or merely a subset of particular modules included on the chip.
If the command is applicable to the entire chip (Yes path from 21-7), as represented by block 21-15, the method includes activating the IFI. As represented by block 21-16, the method includes activating the internal function module clock. As represented by block 21-17, the method includes activating the internal function module. As represented by block 21-18, the method includes activating the ECI output clock. In one embodiment, the various components discussed above are activated in the order presented herein. However, those skilled in the art will appreciate that the order presented is merely one example of the order in which various components on a chip can be reactivated from a sleep mode of operation.
Referring again to block 21-7, if the command is not applicable to the entire chip (No path from 21-7), as represented by blocks 21-8 through 21-14, the method includes determining which modules the command is applicable to and activating those modules. For example, as represented by block 21-8, the method includes determining whether or not the command is applicable to the IFI. If the command is applicable to the IFI (Yes path from 21-8), as represented by block 21-9, the method includes activating the IFI. As represented by block 21-10, the method includes determining whether or not the command is applicable to the internal function module. If the command is applicable to the internal function module (Yes path from 21-10), as represented by blocks 21-11 and 21-12, the method includes reactivating the internal function module clocks and the internal function module. As represented by block 21-13, the method includes determining whether or not the command is applicable to the ECI port. If the command is applicable to the ECI port (Yes path from 21-13), as represented by block 21-14, the method includes activating the ECI output clock. After processing the portions of the method discussed above, the method includes providing an indication that the sleep mode of operation has been exited as directed at block 21-19.
FIG. 22 is a flowchart illustrating one embodiment of a method of shifting to a sleep mode of operation in a distributed computing system. The illustrated method can be modified in a variety of ways. For example, in another embodiment, various portions of the illustrated method can be combined, can be rearranged in an alternate sequence, removed, or the like. Specifically, FIG. 22 illustrates a method enabling a chip to sense conditions indicative of lower activity and automatically and autonomously enter a sleep mode of operation. In one embodiment, when one or more clock signals provided to a chip become unavailable the chip responds by transitioning into a reset state and powers down one or more functional blocks with the possible exception of the ECI receivers. In one embodiment, even in a sleep mode of operation, the LPM and internal function module are provided with a keep-alive power supply in order to retain information stored in volatile memory. As represented by block 22-1, the method includes configuring an automatic sleep mode sensing scheme. As represented by block 22-2, the method includes determining whether externally provided clocks are no longer available. If it is determined that the external clocks are no longer available (Yes path from 22-2), as represented by block 22-12, the method includes automatically deactivating a number of modules included on a chip, but maintaining active operation of the ECI receivers.
On the other hand, if the external clocks are available (No path from 22-2), as represented by block 22-3 through 22-11, the method includes determining which modules have a sufficiently low level of activity for a sufficiently long enough period of time to justify placing the modules individually into a sleep mode of operation. For example, as represented by block 22-3, the method includes determining whether or not the internal function module is idle. If the internal function module is not idle (No path from 22-3), in one embodiment it is assumed that entering a sleep mode of operation would be disruptive to ongoing computing by the chip. As such, as indicated by block 22-13, the method terminates. On the other hand, if the internal function module is idle (Yes path from 22-3), as represented by block 22-4, the method includes determining if a internal function module sleep timer has expired, indicating that the internal function module has been idle for at least as long as the initial value of the timer. If the timer has not expired (No path from 22-4), as represented by block 22-13, the method terminates. If the timer has expired (Yes path from 22-4), as represented by block 22-5, the method includes deactivating the idle internal function module.
As represented by block 22-6, the method includes determining whether or not the IFI is idle. If the IFI is not idle (No path from 22-6), in one embodiment it is assumed that entering a sleep mode of operation would be disruptive to ongoing computing by the chip. As such, as indicated by block 22-13, the method terminates. On the other hand, if the IFI is idle (Yes path from 22-6), as represented by block 22-7, the method includes determining if an IFI sleep timer has expired, indicating that the IFI has been idle for at least as long as the initial value of the timer. If the timer has not expired (No path from 22-7), as represented by block 22-13, the method terminates. If the timer has expired (Yes path from 22-7), as represented by block 22-8, the method includes deactivating the idle IFI.
As represented by block 22-9, the method includes determining whether or not the CCP is idle. If the CCP is not idle (No path from 22-9), in one embodiment it is assumed that entering a sleep mode of operation would be disruptive to ongoing computing by the chip. As such, as indicated by block 22-13, the method terminates. On the other hand, if the CCP is idle (Yes path from 22-9), as represented by block 22-10, the method includes determining if a CCP sleep timer has expired, indicating that the CCP has been idle for at least as long as the initial value of the timer. If the timer has not expired (No path from 22-10), as represented by block 22-13, the method terminates. If the timer has expired (Yes path from 22-10), as represented by block 22-11, the method includes deactivating the idle CCP. And as represented by block 22-13, the method terminates.
FIG. 23 is a flowchart illustrating one embodiment of a method of reactivating an integrated circuit in a sleep mode of operation in a distributing computing system. The illustrated method can be modified in a variety of ways. For example, in another embodiment, various portions of the illustrated method can be combined, can be rearranged in an alternate sequence, removed, or the like. Specifically, FIG. 23 illustrates a method of enabling a chip to sense conditions indicative of higher activity and automatically and autonomously exit a sleep mode of operation into an active state. In one embodiment, a chip is configured to sense and respond to a clock signal in accordance with one of three configurations. In a first configuration, the ECI and CPS are reactivated and other elements remain in a sleep mode of operation. In this configuration, the ECI and CPS have the ability to pass transmission from a device to another device as in a normal operation but without intervention by the CCP or the internal function module. In a second configuration, substantially the on-chip elements are reactivated except for the IFI and the internal functional module. In this configuration transmission test and test of the dual interface may be performed by a reactivation command of the IFI to test the operation and integrity of the IFI. In a third configuration, the entire chip is fully activated.
As represented by block 23-1, the method includes configuring an automatic sleep mode reactivation sensing scheme. As represented by block 23-2, the method includes determining whether available externally provided clocks were previously available. If it is determined that the external clocks were not previously available (No path from 23-2), as represented by block 23-9, the method includes automatically reactivating a number of modules included on a chip that were previously placed into a sleep mode of operation. As represented by block 23-10, the method includes initializing the reactivated modules on the chip. In one embodiment, initializing the reactivated modules on the chip includes setting the all the modules on the chip with predetermined values and/or biasing the modules to particular operating points. As represented by block 23-11, the method includes enabling the ECI output clocks.
Referring again to block 23-2, if the external clocks were available (Yes path from 23-2), as represented by block 23-3 through 22-8, the method includes determining which modules are in sleep mode and reactivating those modules. For example, as represented by block 23-3, the method includes determining whether or not the CCP is in sleep mode. If the CCP is in sleep mode (Yes path from 23-3), as represented by block 23-4, the method includes reactivating the CCP. As represented by block 23-5, the method includes determining whether or not the IFI is in sleep mode. If the IFI is in sleep mode (Yes path from 23-5), as represented by block 23-6, the method includes reactivating the IFI. As represented by block 23-7, the method includes determining whether or not the internal function module is in sleep mode. If the internal function module is in sleep mode (Yes path from 23-7), as represented by block 23-8, the method includes reactivating the internal function module. In one embodiment, the various components discussed above are activated in the order presented herein. However, those skilled in the art will appreciate that the order presented is merely one example of the order in which various components on a chip can be reactivated from a sleep mode of operation.
System Clock Distribution
In multichip distributed computing environments, communication distances and chip interconnections can present complications with respect to clock signal distribution within the distributed system. However, distribution of a synchronous global clock signal throughout the distributed environment, or at least a portion thereof, may be desirable, or necessary, to enable a sufficiently high speed performance, as described herein. Furthermore, synchronous global clock distribution may reduce system complexity. Certain embodiments disclosed herein provide systems and/or methods of distributing a single-frequency clock signal throughout at least a portion of a distributed computing system, such as via communication messages and digital signals. Within a distributed system, data may be superimposed on the single-frequency clock for messaging and/or signaling throughout the system. For example, the system may utilize amplitude modulation, pulse-width modulation, or other modulation scheme for encoding data in the system clock signal. In certain embodiments, data is not transmitted between distributed devices in the absence of a clock signal. Therefore, clock signal distribution may be based at least in part on communication requirements of the distributed system, and may mirror the communication fabric of the system. As described above, distributed computing devices through which system clock signals are propagated may comprise flying leads, which may not suffer from impedance matching issues potentially associated with other connection mechanisms.
Synchronous clock distribution may provide the fabric of a distributed system of reconfigurable processing and memory devices. In certain embodiments, devices of a distributed system include dynamically-reconfigurable clock input receiving connections, wherein clock signals may selectively be received on one or more of a plurality of input connections. For example, an integrated circuit that is part of a distributed computing system may not have a dedicated clock input port and may instead comprise a plurality of configurable input ports, any of which may be designated as a clock input port according to a system clock distribution scheme. Configurable and/or reconfigurable clock input and/or output ports may provide increased flexibility in distributed system design. Furthermore, as described in greater detail below, synchronous clock distribution may allow for the configuration of computing devices within a distributed system into nodes or other groupings.
Distributed systems may include chip carriers comprising two integrated circuit dies as described above (may be referred to as “Dual Die Chip Carriers,” or “DDCC”), wherein the chip carriers receive system clock signals over configurable clock input ports. References herein to chips, devices, chip carriers, packages, and the like may refer to dual-die chip carriers, single-die chip carriers, or any other packages containing or including one or more integrated circuit dies. Furthermore, such references may refer to components of a package or die, such as one or more of a group of devices contained within a single electronic die or package.
FIG. 24 is a block diagram of an embodiment of a distributed computing system 2400. In certain embodiments, at least a portion of the distributed computing devices of the system 2400 comprise a hexagonal-shaped package. As described above, hexagonal packaging may allow for both orthogonal and non-orthogonal communication, whereas square and rectangle packages may only allow for orthogonal communication. Non-orthogonal communication paths may provide greater configuration flexibility, as well as a faster, more direct communication path through intervening devices between originating and the final destination devices. In certain embodiments, such features may provide significant benefits with respect to message communication among configured nodes, sub-nodes, nodes-of-nodes or super-nodes of distributed computing devices that are remotely positioned from one another.
In certain embodiments, two or more hexagonally-shaped integrated circuit dies are disposed within each device. Such integrated circuit die may be referred to herein as “upper” or “lower” dies. However, such terms are used for convenience only, and may or may not refer to relative physical position or configuration. Therefore, discussion herein relating to an upper die may be applicable to a lower die, and vice versa.
Dual-die chip carriers as shown in the system 2400 of FIG. 24 may comprise a “dual interface,” which includes an external interface and an internal interface. This dual interface may be substantially identical for both upper and lower dies. In certain embodiments, an identical dual interface of the upper die is simply flipped over and mated to a lower die using ball grid solder bumps, or other electrical connection mechanism, to provide parallel signal connections between the two die. In addition to the parallel signal connections, six or more serial bus connections may be provided between the two circuit dies. The dual interface may comprise one or more of the following logic modules: (a) External Communication Interface (ECI); (b) Cross-Point Switch (CPS); (c) Local Private Memory (LPM); (d) Configuration Control Processor (CCP); and (e) Internal Function Interface (IFI), the functionalities of which are described below.
The ECI module may provide an interface to other external devices and interface compliant devices. The ECI may contain high impedance digital signal and linear external inputs and outputs, input and output shift and holding registers, and associated combinatorial control logic. In certain embodiments, the ECI connects to the CPS, LPM and/or CCP. The ECI may be configured to direct a received clock signal on an assigned input port and pass it through to a different output port of the device to extend the clock string and to pass signal or message data. In certain embodiments, substantially all data communication between interconnected devices is accomplished through super-imposing data on distributed clock signals.
The CPS may provide digital and linear signal routing between the ECI and IFI, between the ECI input and ECI output, and/or between the IFI and the ECI. The LPM may contain local memory to support the CCP such as Read Only Memory (ROM), Random Access Memory (RAM), Write Once Read Many (WORM) or Electrically-Erasable Programmable Read Only Memory (EEPROM). The CCP may be a Reduced Instruction Set Computer (RISC). In certain embodiments, the CCP is used to configure and re-configure the ECI, CPS and/or IFI. Such CCP functionality may help to decrease the burden on the internal function module (F(X)) of the device to performing such tasks.
The Internal Function Interface (IFI) of the dual interface may pass linear signals to/from the F(X) module. The IFI digital signals contain input and output shift and holding registers configured to provide data and configuration control interfaces of the F(X) module. The IFI may also contain parallel transfer and holding registers that operate the parallel path between the F(X) of the upper and lower circuit dies.
The internal function module F(X) of each circuit die may be incorporated into the design of the die, at the layout stage of the die, interfacing with the Internal Function Interface (IFI). The internal function module may be a processor, a memory, a Field Programmable Gate Array (FPGA), logic function, or other functional unit. The internal function F(X) may not be limited to digital functions, and may incorporate mixed signal functionality. For example, the dual interface may provide a mixed signal interface connection to other devices.
In certain embodiments, collections of chips have clock signals configured at each of the associated chips. Clock signal inputs may provide the distribution fabric of the clock at each chip, as well as a mechanism for data transfer messaging between chips, such as through super-imposing data messages on such clock signals. Variations of the fabric of clock signals may allow for the configuration of nodes, or other groupings of chips, as described herein, as well as data messaging paths from device to device, including remote communications through intervening devices. In certain embodiments, the fabric of the clock signals may be reconfigured to reform the device groupings and message routing paths of processing nodes.
In certain embodiments, distributed computing devices include an input clock used to input data into the External Communication Interface (ECI) serial input registers for each of the multiple communications ports. Normal clock operation of the individual input port data/clock signals between distributed devices may rely on the device's internal clock. In certain embodiments, the device's input clock is set to an ‘off’ state when the device is configured for mixed signal input to the Internal Function F(X).
Distributed computing devices may further include an output clock used to output data from the device's External Communication Interface (ECI) serial output registers for each of multiple communications ports. Similarly to the input port, normal clock operation of the individual output port data/clock signals between distributed devices may rely on the device's internal clock. In certain embodiments, the device's output clock is set to an ‘off’ state when the device is configured for mixed signal output from the Internal Function F(X).
In certain embodiments, for a device in a pass-through configuration, the output clock may utilize the input port clock to pass data from the input port to the output port through the External Communications Interface (ECI). In addition, for a device in a compliant device configuration, the output clock may utilize the input port clock provided by the compliant device to pass data from the input port to the output port through the (ECI). When data is received on an input port, the data may be passed through the device to the specified output port or multiple output ports without requiring the data to be stored into memory to forward.
With further reference to FIG. 24A, the system 2400 includes a system clock generator 2410 that provides a system clock signal to one or more distributed devices, such as dual-die chip carriers. The diagram of FIG. 24, as well as FIGS. 25-27 below, may be useful in illustrating system flexibility associated with initial distribution, and subsequent reconfiguration, of clock signals using derived clocks for many operational modes.
The system clock generator 2410 may be configured to produce a single-frequency system clock signal that provides a source for other clock signals in the system 2400. The signal clock generator 2412, for example, may generate a square wave, as shown. It may be desirable for the system clock signal provided by the system clock generator to have high stability. For example, in certain embodiments, the system clock signal varies in frequency less than half a cycle over a period of one second. Additionally, in certain embodiments, the system clock is continuous and contains no spurious signal artifacts or abrupt or other changes in frequency.
In embodiments in which data is superimposed on the clock signal, such data transmission advantageously may not perturb or alter the clock signal substantially, or in any detrimental way. The system clock generator 2410 may be configured to operate at frequencies of 1 GHz or higher. For example, the system clock generator 2410 may be configured to operate at a minimum frequency of approximately 8 GHz. In certain embodiments, the system clock generator operates at a frequency of 25-30 GHz or higher. In order to achieve system requirements, the system clock signal reference 2412 of the system clock generator may operate in a thermally-controlled environment. For example, the system clock reference 2412 may comprise an oven-controlled crystal oscillator, or the like.
The system 2400 includes one or more primary distribution devices 2420 positioned and configured to receive the system clock signal 2415 from the system clock generator 2410 upstream with respect to other devices of the distributed system 2400. For example, the primary distribution device 2420 may receive the system clock signal 2415 substantially directly from the system clock generator 2410.
The system clock signal 2415 may be distributed to the system as a primary, secondary, or tertiary clock signal. As used herein, primary, secondary and tertiary clock signals may refer to clock signals that vary in some way with respect to how they are controlled and/or distributed within the system. For example, a primary clock signal as distributed throughout the system 2400 may be a copy of the continuous system clock 2415 input that is passed through the primary distribution device 2420. The system 2400 may be configured such that primary clock outputs from the primary distribution device may not be deactivated during system operation.
A secondary clock signal may be a copy of the continuous system clock input, but unlike a primary clock signal, it may be individually configurable to be activated or deactivated at the primary distribution device. In certain embodiments, multiple secondary clock signals may be spawned from primary or secondary clock signals at various configurable points throughout the system. A tertiary clock signal may be a copy of the continuous system clock input that, similarly to a secondary clock signal, may be individually configurable to be activated or deactivated at the primary distribution device 2420. Multiple tertiary clock signals may be spawned from primary, secondary, or tertiary clock signals at various configurable points throughout the system.
It may be beneficial for system devices to identify a single input as the devices' master clock input. In certain embodiments, each primary distribution device 2420 is configured to identify the source port on which it receives the system clock signal 2415 as its master clock input. An individual downstream device 2430 may be configured to identify a source port on which it receives the system clock from a preceding clock-source device as its master clock. In certain embodiments, the master clock is assigned to a primary clock signal. However, the master clock input may be a primary clock, secondary clock, or tertiary clock signal.
The device from which a current device receives the clock which it considers to be its master clock may be considered the current device's parent device. The device's internal clock may be derived from the distributed master clock. In certain embodiments, the device's internal clock is used to configure and control certain device functions, such as, for example, ‘External Communications Interface’ (ECI); ‘Configuration Control Processor’ (CCP); ‘Cross Point Switch’ (CPS); ‘Local Private Memory’ (LPM); ‘Internal Function Interface’ (IFI); or communication with the corresponding circuit die of the device, or other function. The internal clock may further provide operational timing to the Internal Function F(X) of the device. In certain embodiments, the internal clock remains present to the Internal Function F(X) even though the Internal Function F(X) may not be used or may be configured in an off state.
The device's internal clock signal may be configured as an input clock signal or an output clock signal on data communications ports of the External Communications Interface (ECI). At a given point in time, each distributed computing device chip die may have access to more than one clock source, only one of which may be assigned as the device's master clock. The master clock source selection may change from time to time consistent with system and application requirements and re-configuration of clock signal routing.
In certain embodiments, the frequency of clock signals propagating through the distributed environment is substantially identical, operating at the frequency defined by the system clock reference 2412. The phase front of each clock source may differ to some degree from other clock signals propagating in the system. In certain embodiments in which the frequency of each clock signal is substantially identical, Phase Locked Loop (PLL) synchronization is not required for inter-device communications. Rather, synchronization of clock signals may be achieved using a simple single Flip-Flop circuit of each device's External Communications Interface (ECI) input port circuitry. In certain embodiments, external devices that are compliant with the distributed computing system interface may also use the system clock signal 2415 to connect to the distributed system, or sections or portions thereof.
The system 2400 includes a host system 2480 configured to interact with the system clock generator 2410 and/or network of distributed devices over a compatible interface (e.g., driver). For example, the host 2480 may include a processor configured to control the system clock generator 2410, possibly depending on the capabilities or configuration of the system clock generator. Furthermore, the system 2400 may allow for the host computer to communicate with the primary distribution device(s) or other devices of the system. The host processor may be external or contained internally within the system of distributed computing devices. In certain embodiments, system clock generator alarm signals can be reported to the host system 2480.
The continuous system clock signal source, as noted above, may be connected to any of a plurality of data port signal lines of a primary distribution device. Unlike certain traditional input/output communications pairing, in which input and output lines are dependent on each other, each port signal line connection can operate as independent input and output signal lines. The system clock signal may be routed from the primary distribution device 2420 to specified downstream devices of the system or portion thereof in a spider web fashion. Root device secondary and tertiary clock signals may also be routed to specified downstream devices in a similar manner.
A computing device that is a tributary spawning point for the propagation of its received primary, secondary, or tertiary clock signals to one or more downstream devices may be considered a root device. While the primary distribution device 2420 may be configured to prevent the primary clock signal from being shut off, downstream devices may be able to stop propagation of the primary clock signal at various points in the clock path.
The primary distribution device 2420 may output more than one primary clock signal, or a combination of primary, secondary and/or tertiary clock signals. Secondary and tertiary clock signals emanating from the primary distribution device 2420 may be root device signals to downstream devices, and may be permitted to be shut off at the primary distribution device. Primary, secondary, or tertiary clock signals may also be spawned as tributaries from downstream devices, wherein the downstream devices are root devices configured to pass-on clock signals on the tributary path. Such root devices may be further be configured to shut off clock signals for downstream devices.
FIG. 24A shows three connections leaving the primary distribution device 2420. Although three outputs are shown, devices in the system 2400 may comprise any suitable or desirable number of input and/or output connections. The three connection lines may represent three independently-configured output lines and three independently configured input lines. The designation ‘P’ associated with each of the lines indicates a primary clock signal line. However, in certain embodiments, each line is configurable to be a primary (P), secondary (S), or tertiary (T) clock distribution connection. In certain embodiments, at least one of the connections leading from the primary distribution device 2420 is a primary (P) clock line, wherein the clock signal passed on such line is not configured to be shut off at the output of the primary distribution device. Secondary (S) or tertiary (T) clock distribution connections of a primary distribution device may be individually configurable in an off state under program control. FIG. 24B provides an illustration of a reference device representative of one or more devices 2431 of a distributed computing system, wherein the device(s) includes multiple source clock inputs. As with FIG. 24A, the device 2431 may represent a plurality of interconnected chip packages, as described herein.
In certain embodiments, communications between interconnected devices 2430 is accomplished at least in part by superimposing data on clock signal lines distributed between devices. In addition to primary, secondary and tertiary clock signal paths, which are described above, additional device connections may also be used for communication. Such connections may, for example, utilize device internal clock signals (e.g, master clock signals) to pass data between devices.
FIG. 25 is a block diagram of an embodiment of a distributed computing system including multiple system clock sources. The system 2500 includes a system clock generator 2510. The system clock generator may be similar to that shown in FIG. 24A and described above, in certain respects. However, the system clock generator 2510 comprises a plurality of system clock sources (2514A-N), each providing system clock output connections from the system clock generator. Such a system configuration may serve to accommodate distributed systems over a range of complexity and/or scale. For example, the system clock generator may be configured to service a single stand-alone computing device, small systems comprising multiple computing devices, large systems comprising hundreds of computing devices, or substantially large systems comprising up to thousands of devices, or tens of thousands or more. For example, a distributed computing system designed for applications to simulate human brain function may comprise thousands of devices, and may therefore require multiple system clock sources for distribution of the clock throughout the system.
The use of multiple clock sources represented by system clock sources 2514A-N may further provide for improved reliability. For example, in environments in which clock signal dependability is critical or desirable, redundant clock sources may provide added security in case of failure of one or more clock sources. Without multiple clock sources, failure of the single system clock source may result in the entire system shutting down. Therefore, to protect against such failures, multiple system clocks may be made available, as shown in FIG. 25. In certain embodiments, one or more of the system clock sources provides a square wave signal. In certain embodiments, automatic, or semi-automatic, switching from one system clock source to another is performed by the system if the initially-selected clock source fails. For example, system hardware and/or software may be designed to accommodate such changeover from one clock source to an alternate backup clock source.
The system 2500 may comprise a distributed network of computing devices 2530, wherein the devices form separately-clocked sections or groupings, which may help guard against the failure of larger sections of the system, or the entire system. For example, each section may utilize one or more primary distribution devices (2520A, 2520B, 2520N) to distribute clock signals, wherein if one section of the larger system experiences a clock failure, other independent sections may continue to operate.
While the illustrated system 2500 shows three primary distribution devices 2520A, 2520B, 2520N, the system 2500 may comprise any suitable or desirable number of primary distribution devices. In certain embodiments, at least one of the clock connections leaving each primary distribution device is a primary clock signal. The system 2500 may be configured such that primary clock signals may not be shut off at the primary distribution device level. In certain embodiments, the primary clock output signal(s) are physically routed to a next-in-line device for distribution to downstream connected computing devices.
FIG. 26 is a flowchart illustrating a process 2600 of configuring a clock input according to one or more embodiments disclosed herein. Block 2602 includes receiving a system clock signal at a source port of a computing device. The computing device may be, for example a chip carrier including one or more circuit dies, as described in greater detail above. The process 2600 further includes designating a source port on which the clock signal is received as the device's master clock port, as shown at block 2604. For example, in certain embodiments, a packaged device includes upper and lower circuit dies, each including a Configuration Control Processor (CCP) and a Read-Only-Memory with a stored minimal bootstrap loop program. A clock signal, at initial configuration signal routing, may be routed to the resident Configuration Control Processor (CCP) that recognizes the clock signal and configures the clock signal to be temporarily assigned as the master clock.
The internal clock of the device is derived from the master clock signal. In certain embodiments, phase alignment is performed without phase-lock loop (PLL) circuitry. For example, a single flip-flop may be employed to align the rising or falling edges of the clock signals, thereby providing cost and/or computational efficiency compared to PLL circuitry. Such efficiency may be desirable or necessary in a system comprising reconfigurable clock input functionality, wherein any of a group of input lines may be configured to provide a clock signal thereon. The process 2600 further includes reconfiguring the master clock input designation at a subsequent point in time. For example, such reconfiguration may be performed automatically in response to changing system conditions or needs.
FIG. 27 is a flowchart illustrating an embodiment of a process 2700 for designating I/O ports in a chip package. The process 2700 may be performed with respect to a chip package at or during an initial set-up process, in connection with the package being mounted to a motherboard or other substrate. The process 2700 includes constructing a chip package with address fuses at, or associated with, input and/or output ports of the package. The chip package is then mounted to a substrate. In certain embodiments, each circuit die of a packaged device must have, for example, upper and lower die input and output ports aligned to one another for proper port configuration identification and clock signal distribution. In addition, when the packaged device is attached to the mounting substrate, it may be necessary for such orientation to be maintained. Various methods exist for mounting the properly oriented die(s) to the chip carrier package, and orienting and mounting the package to the substrate. As one example, certain potentially expensive tooling, fixtures and machinery may be employed to rotate and position circuit dies for assembly, while tracking orientation positions of the chip carrier package and each of its individual circuit dies, including rotational and positional relationships of the packaged device when it is mated to its mounting substrate. However, in addition to various other potential drawbacks of such a method, mistakes made during the production cycle can be substantially costly to correct, and may lead to irreparable damage to one or more packaged devices.
In certain embodiments, package mounting may advantageously be performed irrespective of specific physical orientation of the package. For example, address fuses, or other identification mechanism, at each I/O port may be provided to allow for identification of each port after the packaged device is mounted to its substrate and is assembled into a module. Such a port address assignment process may be performed as a onetime process at initial “power-up” using the host processor and programming to configure each port address. Performing this process after module assembly may help assure the correct identification of each circuit die I/O port. In certain embodiments, lower circuit die port addresses are assigned in a clockwise direction. The upper circuit die is flipped over to mate face-to-face and registered with the lower circuit die. The upper die port addresses may be assigned in a counter-clockwise direction in order to match the upper die port addresses to the lower die port addresses.
The address fuses may be configured to identify one or more clock signal inputs of the packaged device. Such inputs may be determined based at least in part on physical orientation of the package on the substrate. For example, relative position of input ports with respect to other devices or transmission lines may make appropriate clock input lines apparent. At block 2708, fuses associated with certain input and/or output ports may be blown as a mechanism for identifying port assignments. Some or all of the process 2700 may be performed during manufacturing of a computing device.
FIG. 28 is a flowchart illustrating an embodiment of a process 2800 for configuring a primary distribution device. Upon power-up of a distributed computing system according to one or more embodiments disclosed herein, a host processor may impose its clock on a connected primary distribution device to enable preliminary configuration of the system, or subsection of the system. The host processor may have direct access to configure the primary distribution device and/or may have indirect communication access to the primary distribution device through a system clock generator module, possibly depending on the capabilities or configuration of the system clock generator. The host processor may be an external processor or an integral processor of the distributed computing network. The process 2800 may provide for configuration of a primary distribution device by a host processor for input and output communications and/or clock distribution of the primary distribution device clock to one or more downstream devices.
The process 2800 includes assigning I/O ports of a primary distribution device to identify physical alignment of upper and/or lower dies of the primary distribution device. This step, performed at block 2810, may be a one-time process of port address assignment by the blowing of fuses that make a consistent identifiable physical alignment of the upper and lower die and the device package when mounted on a substrate surface. The process 2800 further includes directing an input port to receive a connection to accept a system clock signal into the primary distribution device, and to assign that port as the device's master clock port.
In certain embodiments, the output connection of the above signal communications receive port is used to respond to a system clock generator to provide status signal information communication associated with the system clock signal or messages transferred across the receive port.
At block 2830, the master clock is assigned as the internal clock of the the lower die (or upper die, depending on configuration) of the primary distribution device. In certain embodiments, the master clock input connection may be directed to at least one additional lower die output port connection to propagate the master clock signal as the primary clock signal.
The master clock input connection may distribute secondary or tertiary clock signals to devices downstream. If the internal clock (e.g., master clock) signal is to be propagated to the upper die, the internal clock of the lower die may be configured to be connected from the lower to an upper die internal input port connection, as performed at block 2850. Alternatively, If the internal upper die master clock input connection is not from the lower die, then the upper die may receive the master clock signal from another source at the upper die level.
The process 2800 further includes configuring the upper die at block 2870, which may complete the configuration of the primary distribution device. Once the primary distribution device is configured, individual downstream devices and groups of devices may be grouped into nodes, sub-nodes, nodes-of-nodes, or super-nodes. As described in greater detail above, communication between distributed computing devices may include communications between directly connected (near-neighbor) devices, as well as communications between remotely connected devices, which may require communication via intervening devices. In certain embodiments, when configuring distributed computing devices to propagate more than one clock signal to other devices, the number of ports remaining for data message communications may be limited with respect to remote devices.
FIGS. 29A-H illustrate embodiments of clock signal distribution configurations in a distributed computing system. The Example configurations of FIGS. 29A-H provide alternate configurations and possible reconfiguration examples for the distribution of primary, secondary and/or tertiary clock signals in a distributed computing environment. In the diagrams of FIGS. 29A-H, the three types of clock connections (primary, secondary, tertiary) are represented by lines of different widths. The widest line width represents primary clock connections, which are also identified with the letter (P). Lines of medium width represent secondary clock connections and are identified with letter (S). Lines having thin widths represent tertiary clock connections and are identified with letter (T).
Each of FIGS. 29A-H show a network of hexagonal chip packages arranged in an example physical arrangement. While shown as three rows of packages three and four packages in length, the concepts described herein and illustrated in FIGS. 29A-H may be applicable to other device arrangements and/or devices of other shapes or sizes. Furthermore, the arrangements shown are not necessarily drawn to scale. FIG. 29A provides a legend for reference and convenience in describing the distributions and configurations shown in the remaining figures. In FIG. 29A, the various devices are labeled ‘A’ through ‘K,’ where the individual hexagons represent individual chip packages.
FIGS. 29B-D illustrate three possible primary clock signal routings, as shown by the wide-width lines and the designation ‘P.’ FIG. 29E shows a primary clock signal being input to device ‘A’ directly from the left parent device, which may be a root device. The primary clock is shown to exit each of the devices in the path to the device directly to the right. The primary clock signal is propagated as a string of devices initially from device ‘A’ to ‘B,’ from device ‘B’ to ‘C,’ from device ‘C’ to ‘D’ and from ‘D’ to an output port of ‘D.’ In addition, device ‘A’ spawns a copy (as a root) of the primary clock signal to device ‘E,’ under configuration control, as a secondary clock (S) (medium width line) signal in this example. Device ‘E’ then propagates the secondary clock signal from device ‘E’ to ‘F,’ from ‘F’ to ‘J,’ from T to ‘I,’ and from ‘I’ to ‘H,’ where the propagation of the Secondary Clock signal, in this string, ends. Each of devices ‘E,’ ‘F,’ ‘J,’ ‘I’ and ‘H’ may be considered a parent device to the next downstream device in the string of devices. Device ‘A’ is the root device for the entire secondary clock signal string consisting of ‘E,’ ‘F,’ ‘J,’ ‘I’ and ‘H,’ as the secondary clock string tributary is spawned from device ‘A.’
The device ‘C’ spawns a tertiary clock (T) signal from device ‘C’ to ‘G,’ and further to ‘K,’ where the tertiary clock signal string ends. While the various strings are illustrated as primary, secondary, or tertiary strings, such designations are provided as examples only, and the various strings may comprise different types of clock signals than those illustrated.
With further reference to FIG. 29E, any device in a string, including the root device ‘A,’ may be configurable to cut off the propagation of the respective clock signal(s) to devices downstream of the device. For example, root device ‘C’ may stop the propagation of the tertiary clock signal to all devices downstream. Likewise, any upstream parent device may stop the propagation of the primary clock signal, secondary clock signal, or tertiary clock signal to devices downstream of the parent device.
FIG. 29F provides a reconfiguration of the example arrangement shown in FIG. 29E. In FIG. 29F, a primary clock signal input is received by device ‘A’ from the left, as in FIG. 29E. The primary clock signal is propagated from device ‘A’ to ‘B,’ ‘B’ to ‘C,’ ‘C’ to ‘D,’ and from ‘D’ to an output port, similarly to FIG. 29E. The embodiment of FIG. 29F may be reconfigured in various ways in addition to the example shown in FIG. 29F. In FIG. 29E, the device ‘E’ may stop propagation of the secondary clock signal to device ‘F’ and instead output that clock signal to device ‘H’ which may, in turn, cause devices ‘J,’ ‘I’ and ‘H’ ports in FIG. 29E to be reconfigured. The root and parent device of such secondary clock string would be device ‘A.’ In an embodiment, device ‘E’ may then propagate the secondary clock signal from ‘E’ to ‘H,’ ‘H’ to ‘I,’ and ‘I’ to ‘J.’ Device ‘A’ also propagates the primary clock signal to device ‘B,’ where device ‘B’ propagates a tributary as tertiary root and parent device to device ‘F.’ Device ‘B’ further propagates the primary clock signal as a parent to device ‘C.’ Device ‘C’ is configured to propagate the primary clock signal to device ‘G,’ and further to ‘K.’
FIG. 29G provides an embodiment in which a tertiary clock signal is spawned from a secondary clock signal; the tertiary clock signal is spawned from device ‘F’ as the root and parent device to devices ‘G’ and ‘K.’ A secondary clock signal is input to device ‘A’ by a parent device upstream from device ‘A.’ All of the devices shown in FIG. 29G downstream from the input secondary clock signal may be under configuration control of this the parent or root input to device ‘A.’ Device ‘A’ also acts as a root device to spawn the secondary clock signal string to devices ‘E,’ ‘H,’ ‘I,’ ‘J’ and ‘F.’ Device ‘F’ is the root and parent device to devices ‘G’ and ‘K.’ Device ‘A’ also propagates the secondary clock signal to devices ‘B,’ ‘C,’ and ‘D,’ and to an output port on Device ‘D.’
FIG. 29H provides an embodiment in which a tertiary clock signal is spawned as a tributary from a primary clock signal. Device ‘B’ is the parent and root device for the tertiary clock string including devices ‘F,’ ‘G’ and ‘K.’ FIG. 29G also includes a secondary clock signal spawned from device ‘A’ to device ‘E.’ Additionally, a separate secondary clock string is input to device ‘H,’ and passed to ‘I’ and further to ‘J.’
FIG. 30 is a schematic diagram illustrating an embodiment of a clock distribution system. The illustrated system 3000 may be helpful in showing how distributed computing devices may be grouped, and regrouped, into nodes, sub-nodes, nodes-of-nodes, and/or super-nodes. Nodal grouping of devices may provide increased computational efficiency, wherein device configurations are designed to address performance of specific tasks, or types of tasks. In certain embodiments, system clock distribution paths are configured to service distributed devices according to nodal groupings. For example, a secondary clock string may branch off of a primary clock path to be distributed to devices making up a node. Such a configuration may allow for activation/deactivation of the secondary clock to the node as a whole, thereby allowing for increased flexibility in controlling operation of groups of similar devices.
Variations of the fabric of clock signals may allow for the configuration of the type of nodes and the desired data messaging paths from device to device, including remote communications through intervening devices. In certain embodiments, processing or memory devices may be grouped together or reconfigured into nodes to provide increased computational power, thereby potentially reducing processing time and/or increasing transactional throughput. Certain embodiments include hierarchical configurations including nodes, sub-nodes, nodes-of-nodes or super-nodes. For example, sub-nodes may be under the control of a node, and may consist of as few as one chip carrier device, or may comprise many devices; nodes-of-nodes may comprise two or more nodes that are configured to support common functionality; super-nodes may comprise nodes, sub-nodes or nodes-of-nodes that support a single purpose, or related purposes; super-nodes may be configured to provide solutions to relatively complex problems. In certain embodiments, the fabric of the clock signals may be reconfigured to reform the device groupings and message routing paths of processing nodes.
FIG. 30 shows examples of various interconnected devices grouped into process/memory nodes, sub-nodes, nodes-of-nodes or super-nodes. Similarly to the examples shown in FIGS. 29A-H, the three types of clock connections (primary, secondary, tertiary) are represented by lines of different widths. The widest line width represents primary clock connections, which are also identified with the letter (P). Lines of medium width represent secondary clock connections and are identified with letter (S). Lines having thin widths represent tertiary clock connections and are identified with letter (T).
In the illustrated embodiment, primary (P), secondary (S) and tertiary (T) clock signals enter at the top of a “node” array, where hexagons represent distributed computing devices. These three clock signals may be, for example, output from a primary distribution device, as described above with respect to FIG. 24A. The diagram includes coordinate references along the right side identifying rows of devices (using capital and lower case letters) and at the bottom identifying columns of devices (using numbers). Individual devices are referenced herein according to respective row/column identifiers.
Primary clock distribution within the system 3000 is shown by a wide line width, which connects various of the distributed devices as a string, starting as the input to the device at row A, column 5 (A-5), and ending at device (h-6). Following the wide line width shows the path of the string of individual devices.
Distribution of the externally-sourced secondary clock signal is shown as the medium line width starting as input to device (B-3), passing therethrough, and ending at device (d-4). Secondary clock strings are also spawned at devices (F-3), (h-2) and (b-6), which are identified by the reference circle ‘A.’
Distribution of the externally-sourced tertiary clock signal is shown as the thin line width starting as input to device (A-7), passing therethrough, and ending at device (B-9). A tertiary clock string is also spawned at device (E-7), identified by reference circle ‘B.’
Reference circles “C”, “D” and “E” identify devices that may connect to one of two or more clock signals as the source of the device's master clock. In certain embodiments, regardless of clock distribution within the distributed system, any clock signal—primary, secondary, or tertiary—provided to a device may be configured as the master clock within the device.
Clock Signal Sleep Mode Management
Certain embodiments disclosed herein provide for management of entry into, and wake-up from, low power operational states by distributed computing device at least partially through use of clock signals. FIG. 31 is a flowchart illustrating an embodiment of a process of managing sleep mode in an integrated circuit chip. The process 3100 may be performed by a controller of a distributed computing system comprising a plurality of interconnected distributed computing devices. In an embodiment, a device receives one or more clock signals on one or more input ports, wherein one of the ports is designated as the master clock input port of the device.
The process 3100 is associated with a computing device, such as a dual-die chip carrier, that is in a normal operating state at block 3110. The process 3100 includes determining whether a signal is present on the designated master clock input port of the device. If no signal is present on the master clock input port, the process may involve determining whether any clock signals are present on any remaining input ports. When there are no clocks provided to the device on any input port, the process 3100 may include the device entering a low-power sleep mode at block 3140. In certain embodiments, the device internal circuitry may be powered off during sleep mode except for the ECI input port receivers when the device enters sleep mode.
If clocks are present on any of the remaining ports when the master clock is shut off, then the device may enter a partial sleep mode, wherein the device's External Communications Interface (ECI) input/output communications may continue until such clock signals are no longer present for a finite period of time.
Clock Signal Frequency Adaption
In certain embodiments, normal clock operation of individual input port data/clock signals between distributed computing devices uses the device's internal clock signal. However, when communicating with a device, such as an external device, operating at a clock frequency slower than the internal clock signal, it may be necessary to reconcile the different clock signals in order to effect communication between the devices. FIG. 32 is a flowchart illustrating an embodiment of a process for communication between devices operating at different clock speeds. In certain embodiments, individual input data/clock configuration can provide the ability to adapt to connected system-compliant device clock frequencies. In certain embodiments, such clock frequencies must be lower than the internal clock signal of the system device. A system-compliant may, for example, be comprise similar connection leads as system devices, and may be configured to communicate over the communication interface presented by system devices.
The process 3200 includes connecting a first device to a second device operating at a lower frequency than the first device at block 3210. In certain embodiments, the first device is a component of a distributed computing system as disclosed here, and the second device is an external device communicatively coupled to the distributed computing system and compliant therewith. It may be necessary for the second device to be configured to recognize the presence of the higher input frequency of the first device's internal clock, as performed at block 3220. However, it may generally not be necessary that the second device follow the incoming frequency. When the first device's higher frequency internal clock signal is detected, the second device may provide its lower-frequency clock signal back to the first device as a signal to the first device to use the second device's lower-frequency clock as the input clock to the first device and output clock from the first device to the second device. The process 3200 may allow either the first device or the second device to initiate or respond to communication and to send or receive data.
The above description is provided to enable any person skilled in the art to make or use embodiments within the scope of the appended claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
For example, a skilled artisan will recognize from the present disclosure that various methods of manufacture, design, and materials can be used to make the various components described herein. Additionally, other combinations, omissions, substitutions and modifications will be apparent to the skilled artisan in view of the disclosure herein. It is contemplated that various aspects and features of the invention described can be practiced separately, combined together, or substituted for one another, and that a variety of combination and sub-combinations of the features and aspects can be made and still fall within the scope of the invention. Furthermore, the systems described above need not include all of the modules and functions described in the preferred embodiments. Accordingly, the present invention is not intended to be limited by the recitation of the preferred embodiments, but is to be defined by reference to the appended claims.
It should be understood that any reference to an element herein using a designation such as “first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed there or that the first element must precede the second element in some manner. Also, unless stated otherwise a set of elements may comprise one or more elements.
Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is intended in its ordinary sense and is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous, are used in their ordinary sense, and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Conjunctive language such as the phrase “at least one of X, Y and Z,” unless specifically stated otherwise, is understood with the context as used in general to convey that an item, term, element, etc. may be either X, Y or Z. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y and at least one of Z to each be present.
Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
Those of skill would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source coding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as “software” or a “software module), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
It is understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

## Claims

1. A distributed computing system configured to distribute clock signals to interconnected integrated circuit dies, the system comprising:
a system clock generator configured to generate a system clock signal; and
a plurality of distributed interconnected integrated circuit dies, wherein at least some of the plurality of interconnected integrated circuit dies comprise:
a unidirectional receive serial connection to each of at least three neighboring dies;
a unidirectional transmit serial connection to each of the at least three neighboring dies;
a plurality of independently-configurable inputs capable of receiving a clock signal, wherein a clock input is selected from the plurality of independently-configurable inputs to receive the clock signal based on a selection of a clock distribution scheme, and wherein data is superimposed on the clock signal at least a portion of the time that the interconnected integrated circuit die receives the clock signal; and
a plurality of independently-configurable outputs capable of transmitting a clock signal, wherein a clock output is selected from the plurality of independently-configurable outputs to output the clock signal based on the selection of the clock distribution scheme, and wherein data is superimposed on the clock signal at least a portion of the time that the interconnected integrated circuit die outputs the clock signal;

wherein the system clock signal is provided by the system clock generator and distributed to each of the plurality of interconnected integrated circuit dies based at least in part on data communication requirements of the distributed computing system.

2. The computing system of claim 1, wherein each of the plurality of distributed interconnected integrated circuit dies comprises an external communication interface module configured to receive a selection of an output clock transmission line and cause the system clock signal or copy thereof to be transmitted on the selected transmission line to a neighboring integrated circuit die.

3. A method of distributing a single-frequency clock signal within a distributed computing system having interconnected integrated circuit chips, the method comprising:
generating a system clock signal of a single frequency;
providing the system clock signal to a first integrated circuit die of a plurality of interconnected integrated circuit dies via a first input of the first integrated circuit die, wherein the first integrated circuit die includes a plurality of inputs capable of receiving the system clock signal, and wherein the first input is selected from the plurality of inputs based at least in part on a designated system clock distribution network; and
providing a copy of the system clock signal from the first integrated circuit die to a second integrated circuit die of the plurality of integrated circuit dies over a configurable input port of the second integrated circuit die, wherein the second integrated circuit die includes a plurality of inputs capable of receiving the copy of the system clock signal, and wherein the configurable input port is selected from the plurality of inputs based at least in part on the designated clock distribution scheme;
wherein each of the plurality of interconnected integrated circuit dies receives a master clock signal of the single frequency according to the system clock distribution network.

4. The method of claim 3, further comprising reconfiguring the system clock distribution network to have a second system clock distribution path different from a first system clock distribution path.

5. The method of claim 3, wherein the system clock distribution network comprises a primary clock distribution path and one or more secondary clock paths branching therefrom.

6. The method of claim 3, further comprising superimposing a data signal on the copy of the system clock signal.

7. The method of claim 6, further comprising providing a signal to a third integrated circuit die of the plurality of integrated circuit dies using the data signal, wherein the third integrated circuit die is remotely disposed with respect to the first integrated circuit die.

8. The method of claim 3, wherein the second integrated circuit die is one of a processing die or a memory die.

9. The method of claim 3, further comprising grouping the plurality of integrated circuit dies into nodes.

10. The method of claim 9, further comprising reconfiguring the node groupings.

11. The method of claim 3, wherein the system clock signal has a frequency of approximately 1 GHz or greater.

12. The method of claim 3, wherein the system clock signal has a frequency of between approximately 25 and 30 GHz.

13. A computing system configured to distribute clock signals to many interconnected integrated circuit dies, the system comprising:
a system clock generator configured to generate a system clock signal and provide the system clock signal over a first output line; and
a plurality of interconnected integrated circuit dies comprising:
a first integrated circuit die having a plurality of independently-configurable first input lines and independently-configurable first output lines, wherein the plurality of first input lines include a master clock input line in electrical communication with the first output line of the system clock generator for receiving the system clock signal, wherein the plurality of first output lines include a primary clock output line configured to output a copy of the system clock signal, wherein the master clock input line is selected from the plurality of first input lines based on a selection of a clock distribution scheme; and
a second integrated circuit die having a plurality of independently-configurable second input lines and independently-configurable second output lines, wherein the second integrated circuit die is configured to receive the copy of the system clock signal on one of the second input lines, wherein the one of the second input lines is selected based on the selection of the clock distribution scheme, wherein data is superimposed on the copy of the system clock signal at least a portion of the time that the second integrated circuit die receives the copy of the system clock signal;

wherein the primary clock output line remains active during system operation.

14. The system of claim 13, wherein the first integrated circuit chip carrier is not configured to shut off the copy of the system clock signal on the primary clock output line.

15. The system of claim 13, wherein the interconnected chip carriers are substantially hexagonally-shaped chip carriers for accommodating non-orthogonal inter-device communication.

16. The system of claim 13, wherein the interconnected chip carriers each include a first die and a second die disposed above the first die.

17. The system of claim 13, wherein the system clock signal comprises a substantially square-wave signal.

18. The system of claim 13, wherein the system clock generator is further configured to provide the first clock signal directly to at least one additional chip carrier over a second output line.

19. The system of claim 13, wherein the plurality of interconnected chip carriers comprises 2-100 chip carriers, or more.

20. The system of claim 13, wherein the plurality of interconnected chip carriers is grouped into one or more independent sub-nodes, nodes, nodes-of-nodes, or super-nodes.

21. The system of claim 13, wherein the plurality of first output lines includes a secondary clock output line, wherein the first integrated circuit chip carrier is configured to deactivate the secondary clock output line during system operation.

22. The system of claim 13, wherein the first integrated circuit chip carrier is configured to provide a response signal back to the system clock generator.