System and method for transmitting data packets in a computer system having a memory hub architecture

Information

  • Patent Grant
  • 7392331
  • Patent Number
    7,392,331
  • Date Filed
    Tuesday, August 31, 2004
    20 years ago
  • Date Issued
    Tuesday, June 24, 2008
    16 years ago
Abstract
A system and method for transmitting data packets from a memory hub to a memory controller is disclosed. The system includes an upstream reception port coupled to an upstream link. The upstream reception port receives the data packets from downstream memory hubs. The system further includes a bypass bus coupled to the upstream reception port. The bypass bus transports the data packets from the upstream reception port. The system further includes a temporary storage coupled to the upstream reception port and configured to receive the data packets from the upstream reception port. The system further includes a bypass multiplexer for selectively coupling an upstream transmission port to either one of a core logic circuit, the temporary storage, or the bypass bus. The system further includes a breakpoint logic circuit coupled to the bypass multiplexer and configured to switch the bypass multiplexer to selectively connect the upstream transmission port to either one of the core logic circuit, the bypass bus, or the temporary storage. The system further includes a local memory coupled to the core logic circuit and operable to receive and send the data packets to the core logic circuit.
Description
TECHNICAL FIELD

This invention relates to computer systems, and, more particularly, to a system and method for transmitting data packets in a computer system having a memory hub architecture.


BACKGROUND OF THE INVENTION

Computer systems use memory devices, such as dynamic random access memory (“DRAM”) devices, to store data that are accessed by a processor. These memory devices are normally used as system memory in a computer system. In a typical computer system, the processor communicates with the system memory through a processor bus and a memory controller. The processor issues a memory request, which includes a memory command, such as a read command, and an address designating the location from which data or instructions are to be read. The memory controller uses the command and address to generate appropriate command signals as well as row and column addresses, which are applied to the system memory. In response to the commands and addresses, data are transferred between the system memory and the processor.


Although the operating speed of memory devices has continuously increased, this increase in operating speed has not kept pace with increases in the operating speed of processors. Even slower has been the increase in operating speed of memory controllers coupling processors to memory devices. The relatively slow speed of memory controllers and memory devices limits the data bandwidth between the processor and the memory devices.


In addition to the limited bandwidth between processors and memory devices, the performance of computer systems is also limited by latency problems that increase the time required to read data from system memory devices. More specifically, when a memory device read command is coupled to a system memory device, such as a synchronous DRAM (“SDRAM”) device, the read data are output from the SDRAM device only after a delay of several clock periods. Therefore, although SDRAM devices can synchronously output burst data at a high data rate, the delay in initially providing the data can significantly slow the operating speed of a computer system using such SDRAM devices.


One approach to alleviating the memory latency problem is to use multiple memory devices coupled to the processor through a memory hub. In a memory hub architecture, a system controller or memory controller is coupled over a high speed link to several memory modules. Typically, the memory modules are coupled in a point-to-point or daisy chain architecture such that the memory modules are connected one to another in series. Thus, the memory controller is coupled to a first memory module over a first high speed link, with the first memory module connected to a second memory module through a second high speed link, and the second memory module coupled to a third memory module through a third high speed link, and so on in a daisy chain fashion.


Each memory module includes a memory hub that is coupled to the corresponding high speed links and a number of memory devices on the module, with the memory hubs efficiently routing memory requests and memory responses between the controller and the memory devices over the high speed links. Computer systems employing this architecture can have a higher bandwidth because a processor can access one memory device while another memory device is responding to a prior memory access. For example, the processor can output write data to one of the memory devices in the system while another memory device in the system is preparing to provide read data to the processor. Moreover, this architecture also provides for easy expansion of the system memory without concern for degradation in signal quality as more memory modules are added, such as occurs in conventional multi drop bus architectures.



FIG. 1 is a block diagram of a system memory 102 that includes memory modules 104a and 104b. The memory module 104a is coupled to a system controller 108 through a downstream link 128 and an upstream link 136. Each of the memory modules 104a, 104b includes a memory hub 112, which includes a link interface 116. In the memory module 104a, the link interface 116 is connected to the system controller 108 by the links 128, 136. The link interface 116 includes a downstream reception port 124 that receives downstream memory requests from the system controller 108 over the downstream link 128, and includes an upstream transmission port 132 that provides upstream memory responses to the system controller over the upstream link 136


The system controller 108 includes a downstream transmission port 140 coupled to the downstream link 128 to provide memory requests to the memory module 104a, and also includes an upstream reception port 144 coupled to the upstream link 136 to receive memory responses from the memory module 104a. The ports 124, 132, 140, 144 and other ports to be discussed below are designated “physical” interfaces or ports since these ports are in what is commonly termed the “physical layer” of a communications system. In this case, the physical layer corresponds to components providing the actual physical connection and communications between the system controller 108 and system memory 102 as will be understood by those skilled in the art.


The nature of the reception ports 124, 144 and transmission ports 132, 140 will depend upon the characteristics of the links 128, 136. For example, in the event the links 128, 136 are implemented using optical communications paths, the reception ports 124, 144 will convert optical signals received through the optical communications path into electrical signals and the transmission ports 140, 132 will convert electrical signals into optical signals that are then transmitted over the corresponding optical communications path.


In operation, the reception port 124 captures the downstream memory requests and provides the captured memory request to local hub circuitry 148, which includes control logic for processing the request and accessing the memory devices 156 over a bus system 152 to provide the corresponding data when the request packet is directed to the memory module 104a. The reception port 124 also provides the captured downstream memory request to a downstream transmission port 160 on a bypass bus 180. The downstream transmission port 160, in turn, provides the memory request over the corresponding downstream link 128 to a downstream reception port 124 in the adjacent downstream memory module 104b. The port 124 in module 104b operates in the same way as the corresponding port in the module 104a, namely to capture the memory request and provide the request to the local hub circuitry 148 for processing and to provide the request to a downstream transmission port 160. The port 160 in the module 104b then operates in the same way as the corresponding port in module 104a to provide the memory request over the corresponding downstream link 128 to the next downstream memory module (not shown in FIG. 1).


The memory hub 112 in the module 104a further includes an upstream reception port 164 that receives memory responses over the corresponding upstream link 136 from an upstream transmission port 132 in the adjacent module 104b. An upstream transmission port 132, in turn, provides the response over the upstream link 136 to the upstream physical reception port 144 in the system controller 108. Each of the memory modules 112 includes a corresponding downstream reception port 124, upstream transmission port 132, downstream transmission port 160, and upstream reception port 164. Moreover, these ports 124, 132, 160, 164 in each module 104b operate in the same way as just described for the corresponding ports in the module 104a.


In addition to the memory responses from the downstream hubs, the local hub circuitry 148 also receives memory responses from a local memory 156. The local memory 156 may be a DRAM type memory device or other suitable memory devices as will be appreciated by those skilled in the art. The local hub circuitry 148 provides the memory responses from the local memory 156 to the upstream transmission port 132 for transmission over the upstream link 136 to the upstream reception port 144 of the controller 108. Thus, the local hub circuitry 148 must monitor and control transmission of memory responses to the system controller 108 from the downstream memory module 104b and from the local memory 156. Since the hub circuitry 148 must monitor and control transmission of memory responses to the system controller 108 from the downstream memory module 104b and the local memory 156, the hub circuitry 148 must determine the priority of transmission of the memory responses. The hub circuitry 148 also must efficiently switch the transmission of memory responses from one source to another source. The hub circuitry 148 also must switch transmission of memory responses from one source to another source at an appropriate time.


The system controller 108 can control the timing of the memory responses inside the memory hubs 112. However, if there are a large number of memory hubs 112 coupled to the system controller 108, it becomes complicated for the system controller 108 to efficiently determine the priority of transmission of memory responses and to do the scheduling in all the memory hubs 112. Also when the system controller 108 controls the scheduling of memory responses inside the memory hubs 112, the bandwidth available for data transmission is reduced.


Accordingly, there is a need for a system and method for efficiently determining the priority of transmission of the memory responses inside the memory hub 112. There is a need for a system and method for efficiently switching transmission of the memory responses from one source to another source inside the memory hub 112. There is a need for a system and method for efficiently switching transmission of the memory responses from one source to another source at an appropriate point.


SUMMARY OF THE INVENTION

The present invention is directed to a system and method for transmitting data packets from a memory hub to a memory controller. In one embodiment, the system includes an upstream reception port coupled to an upstream link. The upstream reception port receives the data packets from downstream memory hubs. The system further includes a bypass bus coupled to the upstream reception port. The bypass bus transports the data packets from the upstream reception port. The system further includes a temporary storage coupled to the upstream reception port and configured to receive the data packets from the upstream reception port. The system further includes a bypass multiplexer for selectively coupling an upstream transmission port to either one of a core logic circuit, the temporary storage, or the bypass bus. The system further includes a breakpoint logic circuit coupled to the bypass multiplexer and configured to switch the bypass multiplexer to selectively connect the upstream transmission port to either one of the core logic circuit, the bypass bus, or the temporary storage. The system further includes a local memory coupled to the core logic circuit and operable to receive and send the data packets to the core logic circuit. The bypass bus transports data packets from the downstream hubs to the upstream link when the bypass multiplexer is switched to the bypass bus. The upstream temporary storage stores the data packets from the downstream hubs when the bypass multiplexer is switched to the core logic circuit. The core logic circuit transmits the data packets from the local memory when the bypass bus is switched to the core logic circuit. The data packets from the temporary storage are transported to the upstream link when the bypass multiplexer is switched to the temporary storage.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram illustrating an existing memory hubs system.



FIG. 2 is a block diagram of a memory hub in accordance with one embodiment of the invention.



FIG. 3 shows a clock signal and upstream data packets in accordance with one embodiment of the invention.



FIG. 4 shows breakpoints in upstream data packets.



FIG. 5 shows a memory hub in accordance with another embodiment of the invention.





DETAILED DESCRIPTION OF THE INVENTION


FIG. 2 is a block diagram of a memory hub 200 in accordance with one embodiment of the invention. The memory hub 200 includes a core logic circuit 204 coupled to the local memory 156. The core logic circuit 204 is also coupled to the downstream reception port 124 and the downstream transmission port 160. The downstream reception port 124 is coupled to the system controller 108 (not shown in FIG. 2) via the downstream link 128.


The downstream reception port 124 receives read and write requests from the system controller 108 (not shown in FIG. 2) over the downstream link 128. The core logic circuit 204 receives the read and write requests from the downstream reception port 124. The core logic circuit 204 sends to the local memory 156 those read and write requests that are destined for the local memory 156. Read and write requests that are destined for downstream hubs (not shown in FIG. 2) are moved from the reception port 124 to the transmission port 160 on the downstream bypass bus.


The memory hub 200 further includes the upstream transmission port 132 that is linked to the system controller 108 by the upstream link 136. As will be discussed further, read and write responses from the core logic circuit 204 and the downstream hubs (not shown in FIG. 2) are transmitted by the upstream transmission port 132 to the system controller 108 over the upstream link 136. A read response includes read data from the local memory 156 and a write response indicates one or more write requests have been completed.


The memory hub 200 further includes a bypass multiplexer 212 coupled to the core logic 204 and a temporary storage 216. The bypass multiplexer 212 is also connected to the upstream reception port 164 via a bypass bus 220. The bypass multiplexer 212 selectively couples either the core logic 204, the bypass bus 220 or the temporary storage 216 to the upstream transmission port 132.


In operation, read and write responses from the downstream hubs are received by the upstream reception port 164 over the upstream link 136 and are passed on to the upstream transmission port 132 over the bypass bus 220 and through bypass multiplexer 212. Read responses are received by the core logic 204 from the local memory 156 and are passed on to the upstream transmission port 132 through the bypass multiplexer 212. Write responses are generated in the core logic 204 and are also passed on to the upstream transmission port 132 through the bypass multiplexer 212. As will be discussed further, when the bypass multiplexer 212 couples the core logic 204 to the upstream transmission port 132, the temporary storage 216 is used to temporarily store read and write responses from the downstream hubs. In the following description, write and read responses from the core logic 204, the downstream hubs and the temporary storage 216 will be referred to simply as “data.”


As described above, the upstream transmission port 132 transmits data, over the upstream link 136, originating from one of several sources: (1) the local memory 156; (2) downstream hubs; and the temporary storage 216. The multiplexer 212 selectively couples the upstream link 136, through the transmission port 132, to either the core logic 204, the bypass bus 220 or the temporary storage 216. The multiplexer 212 is switched so that data originating from either the core logic 204, the bypass bus 220 or the temporary storage 216 are transmitted over the upstream link 136 to the system controller 108. A breakpoint logic 208 coupled to the bypass multiplexer 212 provides the switching algorithm to the bypass multiplexer 212. The switching algorithm locates switch points (also referred to as breakpoints) when a switch may occur. If the switching algorithm locates a breakpoint and it is determined that a switch should be made to another data source that has data available, the bypass multiplexer is switched so that the new data source is coupled to the upstream link 136 through the upstream transmission port 132.


In general, data is transferred among the memory hub 200, the system controller 108 and downstream hubs in a fixed data packet format. A data packet includes a beginning and an end. The breakpoint logic 208 determines the beginning or end of a data packet, and a switch is made at the beginning or end of a data packet.


In one embodiment, the core logic 204 operates at 400 MHz. The reception ports 124, 164, and the transmission ports 132, 160 operate at 1.6 GHz. The upstream link 136 and the downstream link 128 operate at 6.4 GHz.


The operating speed of these devices are selected due to design requirements. The upstream and downstream links are operated at very high speed (6.4 GHz) in order to provide a large bandwidth. However, the transmission ports 136, 160, the reception ports 124, 164, and the core logic 204 cannot be operated at such high speed using current technology. Thus, as data is transferred from the downstream link to the reception port, the transfer speed is reduced. As data is moved to the core logic, the speed is reduced further.



FIG. 3 shows a clock signal, indicated as a 4X clock, where X=400 MHz, and data packets in accordance with one embodiment of the invention. The length of the data packets depends on the type of data being transferred. A write response data packet transfers limited amount of information, primarily containing an ID number and control bits indicating that it is a write response. A read response data packet includes the same information as the write response data packet, but in addition the read response data packet includes the read data being returned. Thus the response data packet is longer than the write response data packet.


In FIG. 3, the clock being used is a 4X clock which transfers 64 bits (8 bytes) in each clock cycle. In the example of FIG. 3, the read response data packet includes 64 bytes of data. These 64 bytes take 8 clock cycles to transfer. The read response data packet also includes 4 header bytes and 4 Cycle Redundancy Code (CRC) bytes, which require 1 clock cycles to transfer. Thus, the read response data packet requires a total of 9 clock cycles to transfer. The write response includes 32 bytes of data (multiple write completes), 4 bytes of header and 4 bytes of CRC. As understood by those skilled in the art, the header bytes are control bytes, and the CRC bytes are used as standard error checking mechanism.



FIG. 3 also shows an idle packet, which is four clock cycles long. The idle packet contains 4 header bytes and 28 no operation (NOP) bytes. The idle packet is sent on the upstream bus by the downstream hubs when the hubs do not have any data to send. The idle packet allows the breakpoint logic to switch when no data is being sent by the downstream hubs.


In one embodiment, a data packet moves from the upstream reception port 164 to the upstream transmission port 132 in one 1.6 GHz clock period. However, the breakpoint logic 208, which switches the bypass multiplexer 212, requires three clock periods to complete the switch because of the time required to process a decode and drive logic to switch the bypass multiplexer 212. Thus, the beginning of the data packet is located as it enters the memory hub 200, and then switching is initiated three clock cycles prior to the breakpoint so that the bypass multiplexer 212 is switched in time as the data packet arrives.



FIG. 4 shows valid breakpoints in data packets. The bypass multiplexer 212 is switched at valid breakpoints. A valid breakpoint exists between two read responses, between a read response and a write response, and between a write response and a read response.


As described before, the determination that the bypass multiplexer 212 will be switched is made three clock cycles before the arrival of a data packet. By looking ahead three clock cycles before the data arrives, the switching process of the bypass multiplexer 212 can begin so that the switch coincides with the data arrival. The write response data packet in FIG. 4 shows that a determination that the bypass multiplexer 212 will be switched is made three clock cycles before a breakpoint.



FIG. 5 shows a memory hub 500 in accordance with another embodiment of the invention. The memory hub 500 includes the elements shown in FIG. 2 and described before. In addition, the memory hub 500 includes two temporary storages: an upstream buffer 512, and a bypass FIFO 516 coupled to the bypass multiplexer 212 and the bypass bus 220. The bypass FIFO is a high speed buffer operating at 4X clock speed, where X=400 MHz. The upstream buffer is a normal speed buffer operating at 1X clock speed.


When the bypass multiplexer 212 is switched to the core logic 204, incoming data packets from the downstream hubs are first stored in the bypass FIFO 516. Since the bypass FIFO 516 operates at high speed (4X clock speed), the bypass FIFO 516 can transfer data packets from its input to its output very quickly. Thus, if the core logic 204 completes sending data packet and the bypass multiplexer switches to the temporary storages, the data from the bypass FIFO 516 is available immediately.


However, if the bypass multiplexer 212 remains switched to the core logic 204, incoming data packets from the downstream hubs fill up the bypass FIFO 516. When the bypass FIFO 516 is filled up, the upstream buffer 512 is used to store data packets. As will be understood by those skilled in the art, the bypass FIFO 516 is fast, but is expensive to implement. Thus a small bypass FIFO 516 is typically used. The upstream buffer 512 is slower, but is less expensive to implement. Thus, a large upstream buffer 516 is used.


The memory hub 500 includes clock domain change circuits 520, 524, 508. As noted before, since the downstream ports 124, 160 operate at different clock frequency than the core logic 204, the downstream ports 124, 160 are not synchronous with the core logic 204. Thus, data packets cannot be directly transferred between the core logic and the downstream ports 124, 160. The clock domain change circuit 520 allows transfer of data packets from the downstream port 124 to the core logic 204, and the clock domain change circuit 524 allow the transfer of data packets from the core logic 204 to the downstream port 160. The core logic 204 is synchronous with the bypass multiplexer 212, and the clock domain change circuit 508 allows the transfer of data packets from the core logic 204 to the bypass multiplexer 212 through a core upstream FIFO 504.


In one embodiment, after power up, the breakpoint control logic 208 initially switches the bypass multiplexer 212 to the bypass bus 220, thus connecting the bypass bus 220 to the upstream link 136. The bypass bus 220 remains connected to the upstream link 136 until the core logic 204 has data to be sent and a breakpoint is available on the bypass bus 220. If the core logic 204 has data available and a breakpoint is available, the bypass multiplexer 212 is switched to the core logic 212.


When the bypass multiplexer 212 is switched to the bypass bus 220, data on the bypass bus 220 is sent to upstream link 136. When the bypass multiplexer 212 is switched to the core logic 204, data from the core logic 204 is sent to the upstream link 136. While the bypass multiplexer 212 remains switched to the core logic 204, incoming data on the bypass bus 220 is sent first to the bypass FIFO 516. When the bypass FIFO 516 is filled up, data is next to the upstream buffer 512.


In one embodiment, the bypass multiplexer 212 remains switched to the core logic 204 until the core logic 204 is empty or if a higher priority requires a switch. A higher priority is determined if the temporary storages, i.e., the bypass FIFO 516 or the upstream buffer 512, have available data. When the bypass multiplexer 212 is switched away from the core logic 204, the multiplexer 212 is first switched to the bypass FIFO 516. The data in the bypass FIFO 516 is sent upstream over the upstream link 136 until the bypass FIFO is exhausted. In general, after the bypass FIFO 516 is exhausted, the bypass multiplexer 212 is next switched to the upstream buffer 512, which is then emptied.


If the core logic 204 has data available, a switch can be made from the bypass FIFO 516 to the core logic 204 even though the bypass FIFO has not been exhausted. If a switch is made from the bypass FIFO 516 to the core logic 204, the next switch is made back to the bypass FIFO 516 in order to send the upstream data in the order it was received. When the bypass FIFO 516 empties, data is next taken from the upstream buffer 512. A switch to the core logic 204 can be made from the upstream buffer 512 even though the upstream buffer has not been exhausted. However, the next switch is made back to the upstream buffer 512 in order to send the upstream data in the order it was received.


After the bypass FIFO 516 and the upstream buffer 512 are cleared, the multiplexer 212 is normally switched to the bypass buss 220. If, however, the core logic 204 has available data, the multiplexer 212 is switched to the core logic 204. As discussed before, while the bypass multiplexer 212 is switched to the core logic 204, upstream data is first loaded into the bypass FIFO 516 and then into the upstream buffer 512. When the bypass multiplexer 212 is switched to the temporary storages, the bypass FIFO 516 is emptied first and then the upstream buffer 512 is emptied next. After the bypass FIFO 516 is emptied, it is not loaded again until the upstream buffer 512 has been emptied.


In the preceding description, certain details were set forth to provide a sufficient understanding of the present invention. One skilled in the art will appreciate, however, that the invention may be practiced without these particular details. Furthermore, one skilled in the art will appreciate that the example embodiments described above do not limit the scope of the present invention, and will also understand that various equivalent embodiments or combinations of the disclosed example embodiments are within the scope of the present invention. Illustrative examples set forth above are intended only to further illustrate certain details of the various embodiments, and should not be interpreted as limiting the scope of the present invention. Also, in the description above the operation of well known components has not been shown or described in detail to avoid unnecessarily obscuring the present invention. Finally, the invention is to be limited only by the appended claims, and is not limited to the described examples or embodiments of the invention.

Claims
  • 1. In a memory system having a plurality of memory modules each of which contains a memory hub connected to a plurality of memory devices, a system in at least one memory hub for receiving data packets through a first upstream link from a downstream memory module and the memory devices connected to the memory hub and for transmitting the received data packets through a second upstream link to either an upstream memory module or a controller, the system comprising: an upstream reception port coupled to the first upstream link and operable to receive data packets from the downstream memory module;a bypass bus coupled to the upstream reception port and operable to receive the data packets from the upstream reception port and to transport the data packets;a temporary storage coupled to the upstream reception port and operable to receive the data packets from the upstream reception port;an upstream transmission port coupled to the second upstream link, the second upstream link being isolated from the first upstream link;a bypass multiplexer for selectively coupling the upstream transmission port to each of a core logic circuit, the temporary storage, and the bypass bus; anda breakpoint logic circuit coupled to the bypass multiplexer and operable to switch the bypass multiplexer to selectively connect the upstream transmission port to each of the core logic circuit, the bypass bus, and the temporary storage.
  • 2. The system of claim 1 further comprising a local memory coupled to the core logic circuit and operable to receive and send the data packets to the core logic circuit.
  • 3. The system of claim 1 wherein the upstream transmission port is coupled to the memory controller by the second upstream link.
  • 4. The system of claim 1 wherein the bypass bus transports data packets from the downstream memory module to the second upstream link when the bypass multiplexer is switched to the bypass bus.
  • 5. The system of claim 1 wherein the temporary storage stores the data packets from the downstream memory module when the bypass multiplexer is switched to the core logic circuit.
  • 6. The system of claim 1 wherein the data packets from the temporary storage are transported to the second upstream link when the bypass multiplexer is switched to the temporary storage.
  • 7. The system of claim 1 wherein the bypass multiplexer is initially switched to the bypass bus after the memory hub is powered up.
  • 8. The system of claim 1 wherein the bypass multiplexer is switched to the core logic circuit when the core logic circuit has data packets available.
  • 9. The system of claim 1 wherein the bypass multiplexer is switched at the beginning of a data packet.
  • 10. The system of claim 1 wherein the bypass multiplexer is switched at the end of a data packet.
  • 11. A memory system, comprising: a memory controller;a plurality of memory hubs each of which is connected to a plurality of memory devices, the memory hubs being coupled to adjacent memory hubs through respective first and second upstream links that are isolated from each other, at least one of the memory hubs being coupled to the memory controller through the respective second upstream link;a system in at least some of the memory hubs for transmitting data packets from the memory hub to the second upstream link comprising:an upstream reception port coupled to the first upstream link and operable to receive data packets from the downstream memory hub though the first upstream link;a bypass bus coupled to the upstream reception port and operable to receive the data packets from the upstream reception port and to transport the data packets;a temporary storage coupled to the upstream reception port and operable to receive the data packets from the upstream reception port;an upstream transmission port coupled to the second upstream link;a bypass multiplexer for selectively coupling the upstream transmission port to each of a core logic circuit, the temporary storage, and the bypass bus; anda breakpoint logic circuit coupled to the bypass multiplexer and operable to switch the bypass multiplexer to selectively connect the upstream transmission port to each of the core logic circuit, the bypass bus, and the temporary storage.
  • 12. The memory system of claim 11 wherein the system for transmitting data packets from the memory hub to the memory controller further comprises a local memory coupled to the core logic circuit and operable to receive and send the data packets to the core logic circuit.
  • 13. The memory system of claim 11 wherein the upstream transmission port is coupled to the memory controller by the second upstream link.
  • 14. The memory system of claim 11 wherein the bypass bus transports data packets from the downstream memory hubs to the second upstream link when the bypass multiplexer is switched to the bypass bus.
  • 15. The memory system of claim 11 wherein the temporary storage stores the data packets from the downstream memory hub when the bypass multiplexer is switched to the core logic circuit.
  • 16. The memory system of claim 11 wherein the core logic circuit transmits the data packets from the local memory when the bypass bus is switched to the core logic circuit.
  • 17. The memory system of claim 11 wherein the data packets from the temporary storage are transported to the second upstream link when the bypass multiplexer is switched to the temporary storage.
  • 18. The system of claim 11 wherein the bypass multiplexer is initially switched to the bypass bus after the memory hub is powered up.
  • 19. The system of claim 11 wherein the bypass multiplexer is switched to the core logic circuit when the core logic circuit has data packets available.
  • 20. The system of claim 11 wherein the bypass multiplexer is switched at the beginning of a data packet.
  • 21. The system of claim 11 wherein the bypass multiplexer is switched at the end of a data packet.
  • 22. A system in a first memory hub for receiving data packets from a second memory hub, and for transmitting data from the first memory hub to a memory controller, comprising: a first upstream link coupled to the second memory hub;a second upstream link coupled to the memory controller, the second upstream link being isolated from the first upstream link;an upstream reception port coupled to the first upstream link and operable to receive data packets from the second memory hubs;an upstream transmission port coupled to the second upstream link and operable to transmit data packets to the memory controller;a bypass bus coupled to the upstream reception port and operable to receive the data packets from the upstream reception port and to transport the data packets;an upstream buffer coupled to the upstream reception port and operable to receive the data packets from the upstream reception port;a bypass FIFO coupled to the upstream reception port and operable to receive the data packets from the upstream reception port;a bypass multiplexer for selectively coupling the upstream transmission port to each of a core logic circuit, the upstream buffer, the bypass FIFO and the bypass bus; anda breakpoint logic circuit coupled to the bypass multiplexer and operable to switch the bypass multiplexer to selectively connect the upstream transmission port to each of the core logic circuit, the bypass bus, the upstream buffer and the bypass FIFO.
  • 23. The system of claim 22 further comprising a local memory coupled to the core logic circuit and operable to receive and send the data packets to the core logic circuit.
  • 24. The system of claim 22 wherein the bypass bus transports data packets from the downstream hubs to the second upstream link when the bypass multiplexer is switched to the bypass bus.
  • 25. The system of claim 22 wherein the bypass FIFO stores the data packets from the downstream hubs when the bypass multiplexer is switched to the core logic circuit.
  • 26. The system of claim 22 wherein the upstream buffer stores the data packets from the downstream hubs after the bypass FIFO is filled up.
  • 27. The system of claim 22 wherein the bypass multiplexer is initially switched to the bypass bus after the memory hub is powered up.
  • 28. The system of claim 22 wherein the bypass multiplexer is switched to the core logic circuit when the core logic circuit has data packets available.
  • 29. A method for transmitting data packets received by a memory hub through a first upstream link to a memory controller over a second upstream link that is isolated from the first upstream link, the data packets originating from a local memory and downstream hubs of the computer system, comprising: transmitting a data packet from the local memory by coupling the local memory to the second upstream link;if a data packet is not being transmitted from the local memory when a data packet is received from the downstream hub, transmitting the data packets from the downstream hubs by coupling a bypass bus between the first upstream link and the second upstream link;if a data packet is being transmitted from the local memory when a data packet is received from the downstream hub, storing the data packets from the downstream hubs in a temporary storage while the data packets from the local memory is being transmitted; andwhen a data packet is not being transmitted from the local memory, transmitting the data packets from the temporary storage by coupling the temporary storage to the second upstream link.
  • 30. The method of claim 29 further comprising transmitting the data packets from the local memory when there is a data packets from the local memory.
  • 31. The method of claim 29 further comprising transmitting the data packets from the temporary storage prior to transmitting the data packets from the downstream hubs.
  • 32. In a memory module having a memory device providing read data, an upstream reception port through which data are received, and an upstream transmission port through which data are transmitted, the upstream transmission port being isolated from the upstream reception port, a method of transmitting data from the memory module comprising: transmitting the read data provided by the memory device through the upstream transmission port;receiving data through the upstream reception port;if the read data provided by the memory device are not being transmitted through the upstream transmission port when the data are received through the upstream reception port, transferring the data received through the upstream reception port to the upstream transmission port for transmission through the upstream transmission port;if the read data provided by the memory device are being transmitted through the upstream transmission port when the data are received through the upstream reception port, temporarily storing the data received through the upstream reception port; andsubsequently transmitting the temporarily stored data through the upstream transmission port.
  • 33. The method of claim 32 wherein the act of subsequently transmitting the temporarily stored data through the upstream transmission port comprises transmitting the temporarily stored data through the upstream transmission port when data provided by the memory device are not being transmitted through the upstream transmission port.
  • 34. The method of claim 32 wherein the act of subsequently transmitting the temporarily stored data through the upstream transmission port comprises transmitting the temporarily stored data through the upstream transmission port when data transferred from the upstream reception port to the upstream transmission port are not being transmitted through the upstream transmission port.
  • 35. The method of claim 32 wherein the act of transferring the data received through the upstream reception port to the upstream transmission port for transmission through the upstream transmission port comprises transferring the data received through the upstream reception port to the upstream transmission port for transmission through the upstream transmission port only if the temporarily stored data are not being transmitted through the upstream transmission port.
US Referenced Citations (271)
Number Name Date Kind
3777154 Lindsey Dec 1973 A
4045781 Levy et al. Aug 1977 A
4240143 Besemer et al. Dec 1980 A
4245306 Besemer et al. Jan 1981 A
4253144 Bellamy et al. Feb 1981 A
4253146 Bellamy et al. Feb 1981 A
4443845 Hamilton et al. Apr 1984 A
4707823 Holdren et al. Nov 1987 A
4724520 Athanas et al. Feb 1988 A
4813772 Kowel et al. Mar 1989 A
4823403 Twietmeyer Apr 1989 A
4825208 Mueller et al. Apr 1989 A
4930128 Suzuki et al. May 1990 A
4953930 Ramsey et al. Sep 1990 A
5241506 Motegi et al. Aug 1993 A
5243703 Farmwald et al. Sep 1993 A
5251303 Fogg, Jr. et al. Oct 1993 A
5269022 Shinjo et al. Dec 1993 A
5307381 Ahuja Apr 1994 A
5317752 Jewett et al. May 1994 A
5319755 Farmwald et al. Jun 1994 A
5327553 Jewett et al. Jul 1994 A
5355391 Horowitz et al. Oct 1994 A
5379382 Work et al. Jan 1995 A
5414819 Redmond et al. May 1995 A
5423009 Zhu Jun 1995 A
5432823 Gasbarro et al. Jul 1995 A
5432907 Picazo, Jr. et al. Jul 1995 A
5442770 Barratt Aug 1995 A
5461627 Rypinski Oct 1995 A
5465229 Bechtolsheim et al. Nov 1995 A
5479370 Furuyama et al. Dec 1995 A
5497476 Oldfield et al. Mar 1996 A
5502621 Schumacher et al. Mar 1996 A
5544319 Acton et al. Aug 1996 A
5544345 Carpenter et al. Aug 1996 A
5566325 Bruce, II et al. Oct 1996 A
5568574 Tanguay, Jr. et al. Oct 1996 A
5577220 Combs et al. Nov 1996 A
5581767 Katsuki et al. Dec 1996 A
5606717 Farmwald et al. Feb 1997 A
5608264 Gaul Mar 1997 A
5623534 Desai et al. Apr 1997 A
5638334 Farmwald et al. Jun 1997 A
5659798 Blumrich et al. Aug 1997 A
5715456 Bennett et al. Feb 1998 A
5729709 Harness Mar 1998 A
5787475 Pawlowski Jul 1998 A
5818844 Singh et al. Oct 1998 A
5818984 Ahmad et al. Oct 1998 A
5819304 Nilsen et al. Oct 1998 A
5822255 Uchida Oct 1998 A
5831467 Leung et al. Nov 1998 A
5832250 Whittaker Nov 1998 A
5875352 Gentry et al. Feb 1999 A
5875454 Craft et al. Feb 1999 A
5928343 Farmwald et al. Jul 1999 A
5966724 Ryan Oct 1999 A
5973935 Schoenfeld et al. Oct 1999 A
5973951 Bechtolsheim et al. Oct 1999 A
5978567 Rebane et al. Nov 1999 A
5987196 Noble Nov 1999 A
6023726 Saksena Feb 2000 A
6026226 Heile et al. Feb 2000 A
6029250 Keeth Feb 2000 A
6031241 Silfvast et al. Feb 2000 A
6033951 Chao Mar 2000 A
6061263 Boaz et al. May 2000 A
6061296 Ternullo, Jr. et al. May 2000 A
6067262 Irrinki et al. May 2000 A
6073190 Rooney Jun 2000 A
6076139 Welker et al. Jun 2000 A
6078451 Ioki Jun 2000 A
6079008 Clery, III Jun 2000 A
6088774 Gillingham Jul 2000 A
6098158 Lay et al. Aug 2000 A
6101151 Watanabe et al. Aug 2000 A
6105075 Ghaffari Aug 2000 A
6105088 Pascale et al. Aug 2000 A
6111757 Dell et al. Aug 2000 A
6125431 Kobayashi Sep 2000 A
6131149 Lu et al. Oct 2000 A
6134624 Burns et al. Oct 2000 A
6137709 Boaz et al. Oct 2000 A
6144327 Distinti et al. Nov 2000 A
6144587 Yoshida Nov 2000 A
6167465 Parvin et al. Dec 2000 A
6167486 Lee et al. Dec 2000 A
6175571 Haddock et al. Jan 2001 B1
6185352 Hurley Feb 2001 B1
6186400 Dvorkis et al. Feb 2001 B1
6191663 Hannah Feb 2001 B1
6201724 Ishizaki et al. Mar 2001 B1
6226729 Stevens et al. May 2001 B1
6229712 Munoz-Bustamante et al. May 2001 B1
6229727 Doyle May 2001 B1
6233376 Updegrove May 2001 B1
6243769 Rooney Jun 2001 B1
6243831 Mustafa et al. Jun 2001 B1
6246618 Yamamoto et al. Jun 2001 B1
6247107 Christie Jun 2001 B1
6249802 Richardson et al. Jun 2001 B1
6256253 Oberlaender et al. Jul 2001 B1
6256692 Yoda et al. Jul 2001 B1
6266730 Perino et al. Jul 2001 B1
6272609 Jeddeloh Aug 2001 B1
6285349 Smith Sep 2001 B1
6294937 Crafts et al. Sep 2001 B1
6301637 Krull et al. Oct 2001 B1
6327642 Lee et al. Dec 2001 B1
6330205 Shimizu et al. Dec 2001 B2
6344664 Trezza et al. Feb 2002 B1
6347055 Motomura Feb 2002 B1
6349363 Cai et al. Feb 2002 B2
6356573 Jonsson et al. Mar 2002 B1
6366375 Sakai et al. Apr 2002 B1
6367074 Bates et al. Apr 2002 B1
6370068 Rhee Apr 2002 B2
6373777 Suzuki Apr 2002 B1
6381190 Shinkai Apr 2002 B1
6392653 Malandain et al. May 2002 B1
6401213 Jeddeloh Jun 2002 B1
6405273 Fleck et al. Jun 2002 B1
6405280 Ryan Jun 2002 B1
6421744 Morrison et al. Jul 2002 B1
6430696 Keeth Aug 2002 B1
6434639 Haghighi Aug 2002 B1
6434654 Story et al. Aug 2002 B1
6434696 Kang Aug 2002 B1
6434736 Schaecher et al. Aug 2002 B1
6438622 Haghighi et al. Aug 2002 B1
6438668 Esfahani et al. Aug 2002 B1
6449308 Knight, Jr. et al. Sep 2002 B1
6453377 Farnworth et al. Sep 2002 B1
6453393 Holman et al. Sep 2002 B1
6457116 Mirsky et al. Sep 2002 B1
6462978 Shibata et al. Oct 2002 B2
6463059 Movshovich et al. Oct 2002 B1
6470422 Cai et al. Oct 2002 B2
6473828 Matsui Oct 2002 B1
6477592 Chen et al. Nov 2002 B1
6477614 Leddige et al. Nov 2002 B1
6477621 Lee et al. Nov 2002 B1
6479322 Kawata et al. Nov 2002 B2
6490188 Nuxoll et al. Dec 2002 B2
6493784 Kamimura et al. Dec 2002 B1
6496909 Schimmel Dec 2002 B1
6501471 Venkataraman et al. Dec 2002 B1
6502161 Perego et al. Dec 2002 B1
6505287 Uematsu Jan 2003 B2
6507899 Oberlaender et al. Jan 2003 B1
6523092 Fanning Feb 2003 B1
6523093 Bogin et al. Feb 2003 B1
6526498 Mirsky et al. Feb 2003 B1
6539490 Forbes et al. Mar 2003 B1
6552304 Hirose et al. Apr 2003 B1
6552564 Forbes et al. Apr 2003 B1
6553479 Mirsky et al. Apr 2003 B2
6567963 Trezza May 2003 B1
6570429 Hellriegel May 2003 B1
6584543 Williams et al. Jun 2003 B2
6587912 Leddige et al. Jul 2003 B2
6590816 Perner Jul 2003 B2
6594713 Fuoco et al. Jul 2003 B1
6594722 Willke, II et al. Jul 2003 B1
6598154 Vaid et al. Jul 2003 B1
6599031 Li Jul 2003 B2
6615325 Mailloux et al. Sep 2003 B2
6622227 Zumkehr et al. Sep 2003 B2
6623177 Chilton Sep 2003 B1
6628294 Sadowsky et al. Sep 2003 B1
6629220 Dyer Sep 2003 B1
6631440 Jenne et al. Oct 2003 B2
6636110 Ooishi et al. Oct 2003 B1
6636957 Stevens et al. Oct 2003 B2
6643787 Zerbe et al. Nov 2003 B1
6646929 Moss et al. Nov 2003 B1
6651139 Ozeki et al. Nov 2003 B1
6658509 Bonella et al. Dec 2003 B1
6661943 Li Dec 2003 B2
6662304 Keeth et al. Dec 2003 B2
6667895 Jang et al. Dec 2003 B2
6681292 Creta et al. Jan 2004 B2
6697926 Johnson et al. Feb 2004 B2
6707726 Nishio et al. Mar 2004 B2
6715018 Farnworth et al. Mar 2004 B2
6718440 Maiyuran et al. Apr 2004 B2
6721187 Hall et al. Apr 2004 B2
6721195 Brunelle et al. Apr 2004 B2
6724685 Braun et al. Apr 2004 B2
6728800 Lee et al. Apr 2004 B1
6735679 Herbst et al. May 2004 B1
6735682 Segelken et al. May 2004 B2
6745275 Chang Jun 2004 B2
6751113 Bhakta et al. Jun 2004 B2
6751703 Chilton Jun 2004 B2
6751722 Mirsky et al. Jun 2004 B2
6752539 Colgan et al. Jun 2004 B2
6754117 Jeddeloh Jun 2004 B2
6754812 Abdallah et al. Jun 2004 B1
6756661 Tsuneda et al. Jun 2004 B2
6760833 Dowling Jul 2004 B1
6771538 Shukuri et al. Aug 2004 B2
6772261 D'Antonio et al. Aug 2004 B1
6775747 Venkatraman Aug 2004 B2
6789173 Tanaka et al. Sep 2004 B1
6792059 Yuan et al. Sep 2004 B2
6792496 Aboulenein et al. Sep 2004 B2
6793408 Levy et al. Sep 2004 B2
6795899 Dodd et al. Sep 2004 B2
6799246 Wise et al. Sep 2004 B1
6799268 Boggs et al. Sep 2004 B1
6804760 Wiliams Oct 2004 B2
6804764 LaBerge et al. Oct 2004 B2
6807630 Lay et al. Oct 2004 B2
6811320 Abbott Nov 2004 B1
6816931 Shih Nov 2004 B2
6816947 Huffman Nov 2004 B1
6820181 Jeddeloh et al. Nov 2004 B2
6821029 Grung et al. Nov 2004 B1
6823023 Hannah Nov 2004 B1
6829398 Ouchi Dec 2004 B2
6950956 Zerbe et al. Sep 2005 B2
6956996 Gordon et al. Oct 2005 B2
6961259 Lee et al. Nov 2005 B2
6980748 Leas Dec 2005 B2
6982892 Lee et al. Jan 2006 B2
7000062 Perego et al. Feb 2006 B2
7016213 Reeves et al. Mar 2006 B2
7016606 Cai et al. Mar 2006 B2
7024547 Kartoz Apr 2006 B2
7035212 Mittal et al. Apr 2006 B1
7047351 Jeddeloh May 2006 B2
7062595 Lindsay et al. Jun 2006 B2
7106973 Kube et al. Sep 2006 B2
20010023474 Kyozuka et al. Sep 2001 A1
20010034839 Karjoth et al. Oct 2001 A1
20010039612 Lee Nov 2001 A1
20020038412 Nizar et al. Mar 2002 A1
20020112119 Halbert et al. Aug 2002 A1
20020116588 Beckert et al. Aug 2002 A1
20020144064 Fanning Oct 2002 A1
20030005223 Coulson et al. Jan 2003 A1
20030043158 Wasserman et al. Mar 2003 A1
20030043426 Baker et al. Mar 2003 A1
20030093630 Richard et al. May 2003 A1
20030163649 Kapur et al. Aug 2003 A1
20030177320 Sah et al. Sep 2003 A1
20030193927 Hronik Oct 2003 A1
20030229734 Chang et al. Dec 2003 A1
20030229770 Jeddeloh Dec 2003 A1
20040015650 Zumkehr et al. Jan 2004 A1
20040022094 Radhakrishnan et al. Feb 2004 A1
20040044833 Ryan Mar 2004 A1
20040123088 Poisner et al. Jun 2004 A1
20040126115 Levy et al. Jul 2004 A1
20040128421 Forbes Jul 2004 A1
20040144994 Lee et al. Jul 2004 A1
20040148482 Grundy et al. Jul 2004 A1
20040230718 Polzin et al. Nov 2004 A1
20040268009 Shin et al. Dec 2004 A1
20050071542 Weber et al. Mar 2005 A1
20050105350 Zimmerman May 2005 A1
20050162882 Reeves et al. Jul 2005 A1
20050210185 Renick Sep 2005 A1
20060179203 Jeddeloh Aug 2006 A1
20060179208 Jeddeloh Aug 2006 A1
20060195647 Jeddeloh Aug 2006 A1
20060200598 Janzen Sep 2006 A1
20070025133 Taylor Feb 2007 A1
20070035980 Taylor Feb 2007 A1
Foreign Referenced Citations (5)
Number Date Country
0849685 Jun 1998 EP
2288066 Oct 1995 GB
2001265539 Sep 2001 JP
WO 9319422 Sep 1993 WO
WO 0227499 Apr 2002 WO
Related Publications (1)
Number Date Country
20060047891 A1 Mar 2006 US