This application relates to the management of a distributed clock in a memory system.
In a computer system, the central processor (CPU) accesses program information and data that is stored in a memory system. There is a hierarchy of memory systems, in size, in speed and capacity that a computer systems architect selects during the design phase, which may comprise, for example, cache memory, main memory and secondary memory. Cache memory is typified by low latency, high bandwidth and high cost per bit, and may be integral to the CPU. Cache memory may be a semiconductor device and which may be, for example, SRAM (static random access memory). Main memory, which is also a semiconductor technology, and which is typically a form of DRAM (dynamic random access memory), is used for less frequently accessed data and program data. At present, personal computers may have up to about 4 GB of DRAM, while high end servers may have about 16 GB or more of DRAM. Strategies such as using a plurality of memory controllers and computer cores may provide access to larger amounts of such memory; however, many of the computer bus systems have practical upper limits due to propagation time, bus loading, power consumption and the like. Larger amounts of data may be stored on mass storage; for example, magnetic disks, where a single disk may contain a terabyte (TB) of memory, FLASH memory disks (sometimes called solid state drives—SSD), and clusters of disks may be used. The access time for data stored on magnetic disks is significantly longer than that for data stored in main memory.
Large amounts of DRAM or other memory such as FLASH may be provided in memory appliances such as that described in U.S. patent application Ser. No. 11/405,083, filed on Apr. 17, 2006. To the extent that large memory arrays have a latency approaching that of conventional main memory, such memory arrays may be considered as similar to main memory and provide rapid access to large amounts of data that would have otherwise been stored in mass storage, such as rotating disk media.
Data is moved between memories and other devices and the central processor on pathways known as buses, which may of various architectures, including parallel, serial, point-to-point, daisy chained, or multi-stub, as examples.
A data bus may be operated in a synchronous manner if the clock frequency for the transmission and reception of data is the same at all points in the system, and a known phase relationship exists between the data bits at each point where the data is to be sensed (e.g., received). However, considering the transmission of data in a parallel bus between two adjacent nodes, the phase relationship of the data bits in different lines changes, depending on the time-delay skew. In slow speed data transmission, and for short bus lengths, this may be tolerated, but in high speed data transmission, the data bits may be received in varying phase relationships to the system clock, and may be delayed by more than one clock interval, resulting in errors, or requiring de-skewing and phase alignment, typically at each memory node.
This problem may be mitigated by transmitting the clock and data on each of the lines, and recovering the clock for each channel at a node. This clock differs in time delay with respect to the system clock from line-to-line. Also, when the clock is transmitted along with the data, transmission of data, or at least an idle data pattern, may be required so as to maintain the synchronization of the clock for each line.
Alternatively, the data may be recovered at each node by accumulating the data for each line in a buffer, determining the time delay adjustment needed to compensate for the data skew, and reconstructing the data received at each node prior to acting on the data (where the word data is understood to include in-band commands such as read, write, and the like as well as information, which may include instructions, that is to be written to, or read from memory.) In order to make the skew-compensation adjustment, the amount of data that must be buffered may be up to the number of clock cycles of skew that may accumulate along the bus. The overall delay in transmitting data from one end of a bus to the other is the sum of the maximum skew of each of the individual node-to-node skew values along the data path. An example of this type of bus is the FB-DIMM (fully-buffered DIMM) which is the subject of a JEDEC standard.
A bus may also be operated as a multi-drop bus where the data is transmitted from a sending end (such as a memory controller) and received at a target memory module: for example the 3rd memory module along a linear bus. The module may be a dual-in-line memory module (DIMM), as is known in the art, and the maximum total skew may be equal to that of the specific bus line having the longest transmission delay. The transmission delays result from differences in trace lengths for the individual data lines, and the differences in trace lengths may include the traces on a mother board as well as the traces on the circuit card containing the memory module. The total skew may limit the length of the bus or the signaling speed.
As described in U.S. application Ser. No. 11/405,083, the effect of skew between the lines of a bus operating, for example, in a serial point-to-point manner, or in a branching manner, may be mitigated by suitably exchanging the logical assignment of the data lanes to specific bus lines, depending on the amount of skew experienced in each bus line between communicating nodes, such that, at the node at the intended receiving end of the bus, the skew is minimized, known, or controlled. As such, the amount of correction needed for skew compensation at the receiving node where the data is to be acted upon may be reduced, with a concomitant reduction in device complexity and power consumption.
An interconnection system is disclosed, including a first node and a second node in communication with the first node. A first clock is provided to the first node and the second node; and, a second clock is generated with reference to the first clock, having an first integral relationship to the first clock, and having a time delay offset with respect to the first clock adjusted such that the transmission time of bits between an output the first node and an output of the second node is maintained substantially constant.
A data transmission system is disclosed, the system including at least two modules connectable by a data bus. A module has a transmitter for transmitting serial data, and a receiver for receiving serial data. The module is supplied with a signal from a common clock, and has a clock generator producing an internal clock on the each module that is derived from the common clock. A clock data recovery circuit produces a received data clock that maintains synchronism with the bits of the serial data signal, and an alignment buffer is operable to establish and maintain synchronism between the bits of the serial data and the internal clock. A switch is operable to route the received serial data to one of an external port or an internal port. The module may have a plurality of external and internal ports.
In another aspect, a memory system includes a plurality of modules, connected by links, and at least one module has a data memory. A system clock is distributed to at least two modules, and a data clock rate of data being transmitted between modules is integrally related to the system clock. A buffer on a module is operable to maintain synchronism between a bit position of a received data character and a previously established bit position.
In yet another aspect, a data interface includes a clock data recovery circuit; a clock phase alignment buffer, and a data transmission circuit. The clock data recovery circuit recovers a clock having a same frequency as the clock used in the data transmission circuit, and the phase alignment circuit compensates for a change in a time-of-arrival of the data.
In still another aspect, a memory module has a data receiver; a clock data recovery circuit, a routing switch, a memory interface, and a data transmitter. The clock data recovery circuit recovers a clock having the same frequency as a clock used in the data transmission circuit, and the phase alignment buffer circuit compensates for a time-of-arrival of the data.
In yet another aspect, a node of an interconnection system includes a data receiving circuit; a data transmitting circuit; a switch connecting the data receiving and the data transmitting circuits. A circuit is operable to maintain a sampling time in a fixed relationship to a first bit of a character of a received character having a plurality of bits; and an input data buffer is configured to resample the first bit so that an overall time delay measured between the resampled bit and a corresponding bit transmitted by another module is maintained substantially constant.
A method of transmitting data between modules is disclosed, the method comprising providing at least two modules, the modules including a receiver, a transmitter, a clock data recovery circuit, a phase alignment buffer, and a routing switch. The modules are connectable by lines. A character of a frame of data is assigned to a first line. The first line at the receiving end thereof is initialized so that a first bit of a character is sampled so as to maintain the alignment of alignment of the sampling of the first bit of the character when a time delay between the transmitted character and the receipt of the character changes.
In yet another aspect, a method of managing an interconnection system is described, where the system includes a plurality of nodes in communication with each other. The method includes transmitting a character of data comprising a plurality of bits from a first node to a second node; receiving the character at a second node; recovering a clock from the received data and aligning a sampling time to a first bit of the character; and, re-sampling the sampled data at a submultiple of the clock frequency and adjusting the phase or time delay of the re-sampling clock so that the overall time delay between the transmitted data and the resampled data is substantially constant.
Exemplary embodiments may be better understood with reference to the drawings, but these examples are not intended to be of a limiting nature. Like numbered elements in the same or different drawings perform equivalent functions. Elements may be either numbered or designated by acronyms, or both, and the choice between the representation is made merely for clarity, so that an element designated by a numeral, and the same element designated by an acronym or alphanumeric indicator should not be distinguished on that basis.
It will be appreciated by a person of skill in the art that the methods described and the apparatus shown in the figures may be configured or embodied in machine-executable instructions, e.g., software, or in hardware, or in a combination of both. The instructions can be used to cause a digital processor, or the like, that is programmed with the instructions to perform the operations described. Alternatively, the operations might be performed by specific hardware components that contain hardwired logic or firmware instructions for performing the operations described, or by any combination of programmed computer components and custom hardware components, which may include analog circuits. As examples, a microprocessor, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC) may be used. Such circuits may have integral or associated memory to store any necessary instructions or data.
The methods may be provided, at least in part, as a computer program product that may include a machine-readable medium having stored thereon instructions which may be used to program a computer (or other electronic devices) to perform the methods. For the purposes of this specification, the terms “machine-readable medium” shall be taken to include any medium that is capable of storing or encoding a sequence of instructions or data for execution by a computing machine or special-purpose hardware and that cause the machine or special purpose hardware to perform any one of the methodologies or functions of the present invention. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic disks, magnetic memories, optical memories, and carrier wave signals. The term carrier wave signals is understood to encompass the electronics and instructions needed to generate or receive electrical signals having instructions or data imposed thereon, whether such signals are conducted or radiated.
For example, but not by way of limitation, a machine readable medium may include read-only memory (ROM); random access memory (RAM) of all types (e.g., SRAM, DRAM); programmable read only memory (PROM); electronically alterable read only memory (EPROM); magnetic random access memory; magnetic disk storage media; flash memory; and, transmission using electrical, optical, acoustical or other forms of signals.
Furthermore, it is common in the art to speak of software, in one form or another (e.g., program, procedure, process, application, module, algorithm or logic), as taking an action or causing a result. Such expressions are merely a convenient way of saying that execution of the software by a computer or equivalent device causes the processor of the computer or an equivalent device to perform an action or a produce a result, as is well known by persons skilled in the art.
When describing a particular example, the example may include a particular feature, structure, or characteristic, but every example may not necessarily include the particular feature, structure or characteristic. This should not be taken as a suggestion or implication that portions of the features, structure, or characteristics of two or more examples should not or could not be combined, except when such a combination is explicitly excluded. When a particular feature, structure, or characteristic is described in connection with an example, a person skilled in the art may give effect to such feature, structure or characteristic in connection with other examples, whether or not explicitly described.
In the interest of clarity, not all the routine features of the implementations disclosed herein are described. It will of course be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made to achieve a developers' specific goals, such as compliance with system and business related constraints, and that these goals will vary from one implementation to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art, having the benefit of this disclosure.
A connector or connector interface as described herein, such as a memory module connector interface, is not limited to physically separable interfaces where a male connector or interface engages a female connector or interface. A connector interface also includes any type of physical interface or connection, such as an interface where leads, solder balls or connections from a memory circuit are electrically connected to another memory circuit or a circuit board. For example, in a stacked die approach, a number of integrated circuit die (e.g., memory devices, buffer devices, or the like) may be stacked on top of one another with a substrate forming a base and an interface to a memory module, memory controller, or processor through a ball grid array or other type of connector interface. As another example, the memory devices and buffer device may be interconnected via a flexible tape interconnect and interface to a memory controller through one of a ball grid array type connector interface or a physically separable socket type connector interface. Connection types may include the interface between integrated circuit chips, interconnection conductors on a substrate, between substrates, or on printed circuit boards, or the like.
Although the examples are described in terms of memory modules in a computer system, nothing herein is intended to limit scope of the disclosure to such a localized system. The apparatus and techniques described herein may be used for a data communication system where the modules are physically separated, and where data transmission techniques using wireless technologies, or the like, may be used in whole or in part. Similarly, a plurality of memory modules may be fabricated or assembled on a common substrate, including the interconnections therebetween. The choice of physical embodiment depends on engineering and economic consideration at the time a product is designed.
The memory modules may be connected to each other and the memory controller by a plurality of electrical connections, printed wiring connections, or lines, which are often collectively called a bus, line, or channel. In this example, some memory modules MM are shown as being serially connected, such as MM1 to MM2 and some MM being connected in a branching arrangement, such as MM2 to MM3 and MM4.
In a mesosynchronous system, a system clock (SYSC) is distributed to modules (for example, MM) in a domain so that a plurality of modules of a group of modules may have access to a clock source of a common frequency. Various clock frequencies may be derived from SYSC which may be multiples or submultiples of the SYSC clock frequency. As such, the clocks throughout the system of a particular multiple or submultiple of the SYSC clock frequency have the same frequency, but may differ in time or phase offset from each other. This offset may be described in fractions of the clock period, or as a phase offset, where 0, 90, 180, 270 degrees of phase correspond to 0.0, 0.25, 0.5, and 0.75 of the clock period. The offset may vary slowly with time due to temperature or circuit aging. Slowly will be understood to mean that a multiplicity of characters may be transmitted before a sufficient change in offset occurs that may need a change in a compensation or alignment.
Since the overall clocking rate of the data is the same, or related to the same clock, over a plurality of modules, padding characters may not be needed to compensate for differences between clocks on different modules. Similarly the use of synchronization characters on a frame-by-frame basis can be avoided. In another aspect, since the clocking rate is the same at the plurality of modules, gaps in the data transmission or preambles may be avoided.
Data may be manipulated and computations may be performed using the various clocks for timing of operations, and it is known that operations may be performed, for example, on the rising edge of a clock signal, or on both the rising and falling edges of the clock signal. The latter type of operation is usually called double-data-rate (DDR) clocking. For simplicity of presentation, the present discussion is in terms of a rising-edge clock operation, as a person of skill in the art will understand the application to a system where double-data-rate clocking, or the like, is performed. Other clocking schemes are known and may be used.
A bus, link, or channel connects the two devices for the purposes of high speed data, address and command transmission. While there are many configurations of channels, typically the channel may have a group of lines, which may use unipolar, bipolar, or differential signaling technology. The lines may be unidirectional or bi-directional. In this example, a differential line is used, which may include a pair of traces on a motherboard, terminated at a memory module in a differential signaling electronic circuit, as is known in the art. (The electrically differential line is shown as a single line in the drawings.) At present, this type of connection is being used for high-speed interfaces in contemporary product design, but any type of connection may be used, including optical or wireless techniques, and the like.
In an aspect, the channel may have a unidirectional group of lines. In the present example, ten unidirectional lines are provided of which nine may be in use at any time, and the tenth line may be a spare. Other numbers of lines and spares may be used. A spare line is not required. Data may be transmitted over the channel in the form of characters which may be of a fixed length in clock cycles, and a data bit of the character may be associated with a clock cycle. In this example, a 20 bit character length is used, associated with 20 clock cycles. The characters on a plurality of lines may be grouped into logical clusters and called frames. That is, as shown in
The transmission of data between a first module and a second module may be controlled at the transmitting module and the receiving module can accept the data at the mesosynchronous clock data rate.
A similar channel may exist in the reverse direction. In this discussion, the direction of signal propagation will be described as in the downstream direction; however, it will be appreciated that signal propagation in the upstream direction will have similar characteristics.
The passage of a character from an upstream device, such as a MC or MM to a downstream device, such as a MM may be termed a hop. In this discussion, for clarity, the transmission of data is between two memory modules MM, without loss of generality. The term line or lines is usually used when describing the physical nature of the connection between two modules in a hop, and these lines may be associated with, for example, traces on a printed circuit board, ancillary components such as connectors, and the sending and receiving end interface electronics. The term lane is usually used to represent the logical assignment of data of a character in a frame. Each of the lanes may be assigned (or “bound”) to a line by operation of the MC, MM or the like, and this binding may change from hop-to-hop, and may change with time. In this discussion, the binding is considered to be static once the system is configured, but may be different at each module. That is, the association of a lane with a line in each hop is established at a prior time of system configuration, and remains in the assigned state for the duration of operation, or until a reconfiguration is performed. Lanes may be bound to different lines in different hops so as to manage, and perhaps to reduce or minimize, the skew between the arrival time of characters in a frame at a destination module.
A channel or link between two modules may be considered to exist when the modules have been initialized, and been trained, and where lanes have been bound to lines and a process of frame alignment has been completed. This process may be called configuration.
A group of lines exiting from a module in the downstream direction connecting with another module by a hop is called an output sub-port and the entry of such lines into the another module is through an input sub-port. Another similar group of lines, configured as sub-ports, may exist in the upstream direction, and the combination of the output and input sub-ports associated with the hop between two modules may be termed a port.
A character in a data frame may include steering data, and this generally means the addressing information needed to route the data in a frame, which may be the present frame or another frame on another line or a subsequent frame on the present line, to a destination module. This may be steering data such as is described in U.S. Ser. No. 11/405,083. Other means of providing addressing or routing of the data are known by persons of skill in the art and may be used. The same lane or a plurality of lanes, which may not include the steering lane, may contain characters for commands, addresses, or data.
b is an example of the physical interface between two modules, which may be memory modules MM. Pairs of traces on a motherboard may connect between connectors on the mother board. Single or multiple connectors may be used so that the MM may plug into a motherboard and connect to printed circuit wiring. Other connections such as, for example, power, power management, clock and test may also be present, but are not shown.
Associated with the MM may be a memory, which may be integral to the MM or in communication with the MM, and which may be any of the types of data memory that have been previously mentioned. The memory may be replaced or supplemented by an interface to other computer or communications equipment, or other external device, so that a memory address may, for example, result in the input or output of data from the MM to a display, network interface, or the like.
The device performing the routing and other related functions may be called a configurable switching element (CSE).
One of the lines connecting modules MM is discussed as being representative of the process used on the other lines. The input line at port P0 may be received by, or interfaced to, an analog circuit that may provide impedance matching, which may include explicit or intrinsic bandwidth filtering, and which may convert the differential signal on the line into an electrical signal suitable for further data processing or manipulation. As mentioned, this discussion presumes that the module has previously been configured with respect to the remainder of the system, including the alignment of clocks or determination of clock phase offsets; as such, the configuration process, error detection, error recovery, and the like, are not discussed in any detail.
As shown in
The recovered data-rate-clock (RDC) may be offset from a locally generated data clock (DC) by a phase offset (or at least a fractional bit time) that is due to the different propagation paths taken by the clock signal SYSC from the common system clock to different modules, differential time delays in the modules, and by the differing signal propagation delays for different lines between adjacent modules.
The difference in propagation delay time between modules may be termed a skew, and the skew may have both fixed and variable components. The additional propagation time differential delays experienced by each path on the module is also relevant and, when skew is described, the total differential time delay is meant, unless specifically otherwise characterized. For example, the propagation time between modules may include the propagation time of the signals along the traces on the mother board, which may at a speed greater than about half the velocity of light, and the propagation delays in the filters of the transmitter TX of the previous module and the receiver RX of the present module and in digital buffers, or the like. Practical analog electronic circuits have finite bandwidths, and such circuits operating near a bandwidth limit may result in additional propagation delay in processing signals.
The propagation delay may be thought of as either a phase delay or a time delay. Analog circuits may have time delays of the order of a clock period, and the delay may be a function of the component values, which may be temperature dependent. Some ageing may occur, but this is generally on a long time scale. So, therefore, the phase or time relationship between the incoming first bit of a character and a corresponding module clock edge may not be known a priori. Where a time scale for the variation of skew or propagation in a fixed circuit configuration is described, a long time is understood to mean that the time scale of the variation is greater than a small multiple of the character duration at the clock rate.
An alignment of the clocks and the data may be made during a configuration process, and may use training characters to establish a relationship between a character or frame boundary, the signal valid window, and the RDC, for each line. Once established, the relationship is maintained by the DLL or the PLL, and the RDC may also used to clock a deserializer (DES). The DLL or PLL may be updated by the CDR circuit so that the sampling point is maintained with a valid data window, even if the propagation time delay of the hop changes, for example, due to environmental factors (usually temperature). That is, the association between the specific clock bit in the recovered data clock (RDC) at a module for a line and the 0th bit of the character remains unchanged even when the time delay on the hop varies. As this variation is slow compared with the frame or character rate, and the DDL or PLL may not be continuously updated. Depending on the system design, if data is not continuously transmitted on line of a hop, a periodic synchronization transmission may be initiated to adjust the RDC to maintain the association.
An example of the conversion of a serial data stream, which may represent the bits of character on a line to a plurality of parallel data streams which may be processed locally at a lower data rate, is shown in
It will be appreciated that, if the time duration of the bits were shown, rather than a logical representation, the time duration or interval between successive bits of the data in the half-rate domain would be twice that of the incoming data, and the duration of the data bits in the quarter-rate domain would be four times that of the incoming data. In this example, the data are shown as the even and odd bits of the incoming character, however this notation is merely for convenience in description and is not intended to restrict the manner in which the data bits are routed within the module.
A phase alignment buffer (PAB) is used to align the output of the deserializer (DES) with the internal switch clock (SWC). The switch rate clock is shown as being distributed from the switch SW as SWC1 and SWC11 to connote that the SWC used for the PABs at the input and the output of the switch have clock rates that are both the same frequency as that of the SWC, but may each have a different but substantially fixed phase or time offset from the SWC used in the switch (SW) itself.
In an aspect, the bit length of the PAB may be less than a character, and when a routing scheme described in U.S. Ser. No. 11/405,083 is used, the routing information may be obtained before a complete character is received by the receiving module. The PAB length may be less than 18 bits and may be 5 bits in length.
In this example, the character is deserialized into four packets of five data bits, and the clock rate SWC is one fourth of the DC. The PAB may act so that the 0th bit of the input character is aligned with a leading edge of the SWC. Subsequent bits of the deserialized data of the character (the 1st, 2nd and 3rd) may be aligned with relative phases of the SWC (90, 180 and 270°), respectively. Subsequent bits of the character, which follow in time may be processed similarly.
The packet may be processed by the switch (SW) so as to route the packet to a memory, or to one of the output ports P1, P2. This routing may be dynamic, based on a received steering data character. In addition, the switch (SW) may perform a lane exchange by, for example, transferring an input character on line 1 of P0, to an output line 3 on P1. The logical lane to physical line association may be static in nature, and the process may be called “binding”. In this manner, an input character may be routed along a path to a memory location, or to another module, and the assignment of lanes to lines may be used, for example, to manage the differential skew between characters of a frame at the destination module. The term spare line is used to designate any line connecting two ports that is not presently bound to a lane.
An interface between the switch (SW) and an on-module memory may be similar to a module-to-module interface, and provide for the reception of characters in a packet that are intended to be to or from the local memory. This reception may include deskewing the characters within a frame and transferring the frame to the memory. Such local data recovery is described in patent application U.S. Ser. No. 11/405,083.
After processing in the switch (SW), where the data has been routed to an output port (for example, P1 or P2), the packets of the character are output as the input to an output phase alignment buffer PAB. The output PAB serves to maintain the alignment of the 0th bit of a character with the clock edge of the data clock DC at the output serializer SER that was established during the configuration process. Since the processing in the switch (SW) is a generally synchronous process, the skew between the switch clock (SWC) and the data clock (DC) tends to remain relatively static, once established. That is, the propagation delay time of a bit through the switch is substantially constant. However, the phase or relative time of the data input to the switch (SW) may differ for each line, with respect to the data clock (DC). Output PABs may be used to align the bits of the character on a line with the appropriate clock cycle of the data clock (DC) for the line. This alignment is performed on a line-by-line basis, and the characters of a frame need not be resynchronized at each hop as they are processed separately.
The serializer then merges the bits of the packets of the character into a character having the same timing as a previously transmitted character on the line. That is, the association of bit 0 of the nth following character with a clock edge of the data clock DC delayed by 20n clock cycles from the 0th bit of the previous character is maintained, where n is a positive integer. Thus, the timing of the characters is maintained even when there is no actual character being transmitted. The output of the serializer (SER) may be converted to a differential analog data signal in the TX circuit for transmission on the next hop.
The other characters on the other lines in the frame are treated similarly. However, each of the lines has a separate CDR circuit, and the RDC for each line may have different phases with respect to each other and with respect to the SWC. The variation of the phase on each line may also have a different dependence on time or temperature, corresponding to the circuit details, such as line length, amplifier or filter characteristics, or the like.
The result of this process may be to maintain the association of a bit (for example the 0th bit) of a character transmitted by a memory controller MC to a same clock edge of the data clock DC, where the data clock is the data clock DC at any of the modules, even when the time delay of the transmission of data over the hops changes with time.
This concept is shown in
In the previous discussion, the time delay of the system clock (SYSC) at a module with respect to the clock edge at the SYSC clock source, which may not be on a module, has been tacitly assumed to be constant. This time delay may also vary with environmental factors or ageing, however, since the phase alignment buffers (PAB) on each module compensate for the relative time delay between the DC and the SWC and the RDC, the variations of SYSC clock delay may also be compensated.
The result of the arrangement described is that a full character or more may not need to be buffered at the input PAB of the MM in order to adjust for the change in delay of a hop. The depth of the PAB may be approximately the variation of the skew over the operating temperature range for the line in the hop, rather than, for example, the total variation of skew over all of the lines of the hop. At the time of configuration, the data may be positioned at a suitable point in the buffer for transfer between clock speed domains so that the data bit position is maintained in the buffer during the transfer period.
A result of the phase alignment buffer is that the overall time delay through the memory module may be optimized, taking account of the changes in the skew due to environmental factors. When the data is propagated over a path with multiple hops, the overall time delay between the MC and the destination module may be reduced, when compared with an approach which recovers the data of a frame at an intermediate module and performs deskewing by adding delays along the data path. A delay may be added to one or more of the lines at a source or destination module in order to deal with the remaining skew, or may be added during configuration so as to optimize the overall skew.
Since the association, which may be termed synchronization, of the data clock DC with the data of any line is maintained after the association has been established, and is maintained locally at a module pair, the data transmission on each line does not have to be continuous except when required for system bandwidth or latency performance reasons. When the lines are not needed, power can be removed from the transmitter and receiver components, as well as perhaps from portions of the CDR and other circuitry. As data is typically routed from an input port to either the local memory or one of the two output ports, at least one of the output ports may be shut down when not needed.
One of the lines in a group of lines of the sub-port may be maintained in an active state for purposes of signaling, such as alerting the remaining lines to a data frame in a previously inactive link, or to data being sent for refresh purposes. However, a signal presence indicator may also be used, so that the presence on data on a line will activate the receiver and associated circuitry. Thus, in steady-state operation, a line may be either active or inactive, and when the data line is active, data, where data may be steering data, a command (including addressing), data being stored or read, or a clock maintenance transmission, is being transmitted.
Although only a few exemplary embodiments of this invention have been described in detail above, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of the invention. Accordingly, all such modifications are intended to be included within the scope of this invention.
This application claims the benefit of U.S. provisional application Ser. No. 60/997,899, filed Oct. 5, 2007, and is a continuation-in-part of U.S. Ser. No. 11/405,083, filed on Apr. 17, 2006, which claims priority to U.S. provisional application Ser. No. 60/698,626, filed on Jul. 11, 2005 and U.S. provisional application Ser. No. 60/674,189, filed on Apr. 21, 2005, each of which is incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3728679 | McIntosh | Apr 1973 | A |
3970798 | Epenoy et al. | Jul 1976 | A |
4128882 | Dennis | Dec 1978 | A |
4240143 | Besemer et al. | Dec 1980 | A |
4263651 | Donath | Apr 1981 | A |
4322849 | Calabrese | Mar 1982 | A |
4323849 | Smith | Apr 1982 | A |
4363094 | Kaul | Dec 1982 | A |
4383314 | Tam | May 1983 | A |
4386323 | Jansen | May 1983 | A |
4543630 | Neches | Sep 1985 | A |
4558455 | Epenoy et al. | Dec 1985 | A |
4701756 | Burr | Oct 1987 | A |
4703451 | Calabrese | Oct 1987 | A |
4756011 | Cordell | Jul 1988 | A |
4805195 | Keegan | Feb 1989 | A |
4845709 | Matsumoto et al. | Jul 1989 | A |
4860201 | Stolfo et al. | Aug 1989 | A |
4881165 | Sager et al. | Nov 1989 | A |
4910669 | Gorin et al. | Mar 1990 | A |
4922409 | Schoelkopf et al. | May 1990 | A |
5041964 | Cole et al. | Aug 1991 | A |
5053942 | Srini | Oct 1991 | A |
5200746 | Yoshifuji | Apr 1993 | A |
5283877 | Gastinel | Feb 1994 | A |
5285441 | Bansal | Feb 1994 | A |
5313501 | Thacker | May 1994 | A |
5467040 | Nelson et al. | Nov 1995 | A |
5507029 | Granato | Apr 1996 | A |
5513377 | Capowski | Apr 1996 | A |
5621774 | Ishibashi | Apr 1997 | A |
5652530 | Ashuri | Jul 1997 | A |
5828253 | Murayama | Oct 1998 | A |
5832286 | Yoshida | Nov 1998 | A |
5872959 | Nguyen | Feb 1999 | A |
5920704 | Olnowich | Jul 1999 | A |
5923830 | Fuchs et al. | Jul 1999 | A |
5960034 | Lo | Sep 1999 | A |
6031847 | Collins | Feb 2000 | A |
6105144 | Wu | Aug 2000 | A |
6138185 | Nelson | Oct 2000 | A |
6157229 | Yoshikawa | Dec 2000 | A |
6185654 | Van Doren | Feb 2001 | B1 |
6208667 | Caldara | Mar 2001 | B1 |
6260151 | Omizo | Jul 2001 | B1 |
6301167 | Lee | Oct 2001 | B1 |
6301244 | Huang | Oct 2001 | B1 |
6310814 | Hampel | Oct 2001 | B1 |
6317352 | Halbert et al. | Nov 2001 | B1 |
6335647 | Nagano | Jan 2002 | B1 |
6335930 | Lee | Jan 2002 | B1 |
6345321 | Litaize et al. | Feb 2002 | B1 |
6356610 | Ott | Mar 2002 | B1 |
6359815 | Sato | Mar 2002 | B1 |
6369605 | Bonella et al. | Apr 2002 | B1 |
6370200 | Takahashi | Apr 2002 | B1 |
6378018 | Tsern | Apr 2002 | B1 |
6417713 | DeRyckere | Jul 2002 | B1 |
6425114 | Chan | Jul 2002 | B1 |
6442644 | Gustavson et al. | Aug 2002 | B1 |
6445719 | Schneider et al. | Sep 2002 | B1 |
6446174 | Dow | Sep 2002 | B1 |
6449667 | Ganmukhi et al. | Sep 2002 | B1 |
6473439 | Zerbe et al. | Oct 2002 | B1 |
6473827 | McMillen | Oct 2002 | B2 |
6493205 | Bauer | Dec 2002 | B2 |
6493250 | Halbert et al. | Dec 2002 | B2 |
6502161 | Perego et al. | Dec 2002 | B1 |
6553450 | Dodd et al. | Apr 2003 | B1 |
6557110 | Sakamoto | Apr 2003 | B2 |
6601178 | Gulik | Jul 2003 | B1 |
6611518 | Ngo | Aug 2003 | B1 |
6618791 | Dodd | Sep 2003 | B1 |
6625687 | Halbert et al. | Sep 2003 | B1 |
6636932 | Regev | Oct 2003 | B1 |
6636993 | Koyanagi | Oct 2003 | B1 |
6647027 | Gasparik | Nov 2003 | B1 |
6658509 | Bonella et al. | Dec 2003 | B1 |
6678783 | Ozawa | Jan 2004 | B2 |
6681338 | Kollipara | Jan 2004 | B1 |
6697974 | Craft | Feb 2004 | B2 |
6735397 | Herrity | May 2004 | B2 |
6799235 | Bormann et al. | Sep 2004 | B2 |
6803872 | DeRyckere | Oct 2004 | B2 |
6807377 | Watanabe | Oct 2004 | B1 |
6833618 | Ono et al. | Dec 2004 | B2 |
6845461 | Kim | Jan 2005 | B1 |
6871253 | Greef et al. | Mar 2005 | B2 |
6874097 | Aliahmad | Mar 2005 | B1 |
6882082 | Greef et al. | Apr 2005 | B2 |
6904050 | Chao | Jun 2005 | B2 |
6928571 | Bonella et al. | Aug 2005 | B1 |
6937681 | Watanabe | Aug 2005 | B2 |
6961347 | Bunton et al. | Nov 2005 | B1 |
6968419 | Holman | Nov 2005 | B1 |
6983354 | Jeddeloh | Jan 2006 | B2 |
7012811 | Jiang et al. | Mar 2006 | B1 |
7013361 | Liron | Mar 2006 | B2 |
7065101 | Ziegler et al. | Jun 2006 | B2 |
7085950 | Ehmann | Aug 2006 | B2 |
7113012 | Amin | Sep 2006 | B2 |
7123660 | Haq | Oct 2006 | B2 |
7130317 | Annadurai | Oct 2006 | B2 |
7139347 | Fujita | Nov 2006 | B2 |
7164615 | Park | Jan 2007 | B2 |
7193429 | Okuyama | Mar 2007 | B2 |
7200790 | Sharma et al. | Apr 2007 | B2 |
7205803 | Chung | Apr 2007 | B2 |
7280538 | Li | Oct 2007 | B2 |
7304520 | Cho | Dec 2007 | B2 |
7328362 | Chiang | Feb 2008 | B2 |
7430728 | Rahut | Sep 2008 | B1 |
7433441 | Jenkins | Oct 2008 | B2 |
7490189 | Eberle | Feb 2009 | B2 |
7516029 | Kim et al. | Apr 2009 | B2 |
7525356 | Hui | Apr 2009 | B2 |
7551640 | Klecka et al. | Jun 2009 | B1 |
7609695 | Zhu | Oct 2009 | B2 |
7643517 | Annadurai | Jan 2010 | B2 |
7653776 | Cornelius | Jan 2010 | B2 |
7668271 | Kim et al. | Feb 2010 | B2 |
7668272 | Obeidat | Feb 2010 | B1 |
7734867 | Keeton | Jun 2010 | B1 |
7751713 | Perkins | Jul 2010 | B2 |
7817767 | Tell et al. | Oct 2010 | B2 |
20010039601 | Leung | Nov 2001 | A1 |
20020009169 | Watanabe | Jan 2002 | A1 |
20020084458 | Halbert et al. | Jul 2002 | A1 |
20020112119 | Halbert et al. | Aug 2002 | A1 |
20020124153 | Litaize et al. | Sep 2002 | A1 |
20030018880 | Litaize et al. | Jan 2003 | A1 |
20030058021 | Lee et al. | Mar 2003 | A1 |
20030061447 | Perego et al. | Mar 2003 | A1 |
20030091039 | Ziegler | May 2003 | A1 |
20030117172 | Wu et al. | Jun 2003 | A1 |
20030120895 | Litaize et al. | Jun 2003 | A1 |
20030126485 | Wilcox | Jul 2003 | A1 |
20030163606 | Fukaishi | Aug 2003 | A1 |
20030193927 | Hronik | Oct 2003 | A1 |
20030206164 | Juenger | Nov 2003 | A1 |
20030208511 | Earl et al. | Nov 2003 | A1 |
20030236939 | Kleveland et al. | Dec 2003 | A1 |
20040004897 | Kang | Jan 2004 | A1 |
20040117569 | Kyung | Jun 2004 | A1 |
20040122985 | Parra et al. | Jun 2004 | A1 |
20040230718 | Polzin et al. | Nov 2004 | A1 |
20040243769 | Frame et al. | Dec 2004 | A1 |
20040256638 | Perego et al. | Dec 2004 | A1 |
20050005184 | Lindt | Jan 2005 | A1 |
20050007805 | Ware et al. | Jan 2005 | A1 |
20050010737 | Ware et al. | Jan 2005 | A1 |
20050060483 | Azuma | Mar 2005 | A1 |
20050071693 | Chun et al. | Mar 2005 | A1 |
20050086549 | Solomon et al. | Apr 2005 | A1 |
20050089037 | Kojima | Apr 2005 | A1 |
20050190622 | Choi | Sep 2005 | A1 |
20050246362 | Borland | Nov 2005 | A1 |
20050259692 | Zerbe | Nov 2005 | A1 |
20060026450 | Bounitch | Feb 2006 | A1 |
20060089107 | Domino | Apr 2006 | A1 |
20060253721 | Johnson | Nov 2006 | A1 |
20070079219 | Nagai | Apr 2007 | A1 |
20070088754 | Brannon et al. | Apr 2007 | A1 |
20070124532 | Bennett | May 2007 | A1 |
20070162516 | Thiel et al. | Jul 2007 | A1 |
20080175586 | Perkins | Jul 2008 | A1 |
20080175589 | Perkins | Jul 2008 | A1 |
20080183953 | Flynn | Jul 2008 | A1 |
20090052892 | Perkins | Feb 2009 | A1 |
20090324220 | Perkins | Dec 2009 | A1 |
Number | Date | Country |
---|---|---|
WO 9930240 | Jun 1999 | WO |
WO 9941667 | Aug 1999 | WO |
Number | Date | Country | |
---|---|---|---|
20090150707 A1 | Jun 2009 | US |
Number | Date | Country | |
---|---|---|---|
60997899 | Oct 2007 | US | |
60674189 | Apr 2005 | US | |
60698626 | Jul 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11405083 | Apr 2006 | US |
Child | 12245349 | US |