# Patent

## Title
Memory hub and access method having a sequencer and internal row caching

## Abstract

A computer system includes a controller coupled to a plurality of memory modules each of which includes a memory hub and a plurality of memory devices. The memory hub includes a row cache memory that stores data as they are read from the memory devices. When the memory module is not being accessed by the controller, a sequencer in the memory module generates requests to read data from a row of memory cells. The data read responsive to the generated read requests are also stored in the row cache memory. As a result, read data in the row being accessed may be stored in the row cache memory even though the data was not previously read from the memory device responsive to a memory request from the controller.

## Background
This application is a continuation of U.S. patent application No. 10/213,038, filed Aug. 5, 2002, U.S. Pat. No. 7,117,316.


TECHNICAL FIELD
This invention relates to computer systems, and, more particularly, to a computer system having a memory hub coupling several memory devices to a processor or other memory access device.
BACKGROUND OF THE INVENTION
Computer systems use memory devices, such as dynamic random access memory (“DRAM”) devices, to store instructions and 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. The memory controller is often part of a system controller, which also includes bus bridge circuitry for coupling the processor bus to an expansion bus, such as a PCI bus.
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 to several memory modules, each of which includes a memory hub coupled to several memory devices. The memory hub efficiently routes memory requests and responses between the controller and the memory devices. 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. Although computer systems using memory hubs may provide superior performance, they nevertheless often fail to operate at optimum speed for several reasons. For example, even though memory hubs can provide computer systems with a greater memory bandwidth, they still suffer from latency problems of the type described above. More specifically, although the processor may communicate with one memory device while another memory device is preparing to transfer data, it is sometimes necessary to receive data from one memory device before the data from another memory device can be used. In the event data must be received from one memory device before data received from another memory device can be used, the latency problem continues to slow the operating speed of such computer systems.
One technique that has been used to reduce latency in memory devices is a cache memory, which stores data recently accessed from system memory. The cache memory is generally in the form of a static random access memory (“SRAM”), which has a substantially shorter access time compared to dynamic random access memory (“DRAM”) typically used as system memory. Furthermore, the SRAM cache memory is generally coupled directly to the processor through a processor bus rather than through a system controller or the like as is typical with DRAM system memory. As a result of the faster speed of cache memory and the closer proximity of cache memory to the processor, the use of cache memory can greatly reduce the latency of memory read operations.
Although conventional cache memory has reduced memory access latencies in conventional computer systems, cache memory has not been used in a manner that provides optimum performance in computer systems using memory hubs. In particular, the limited storage capacity of typical cache memories compared to the vastly larger capacity of typical memory hub system memories makes cache memory of lesser value since a cache hit is less likely to occur. This problem is exacerbated by the difficulty in transferring data to cache memory that is likely to be the subject of subsequent memory requests. More specifically, it is difficult to couple the data that will subsequently be needed from all of the memory modules through the memory controller to the processor and then from the processor to the cache memory. Also, it can be difficult to maintain cache coherency in a computer system using memory hubs and a cache memory coupled to the processor through the processor bus, and it can require significant hardware resources to maintain cache coherency. Furthermore, the time required to maintain cache coherency can slow memory performance to the extent that much of the performance advantages of using cache memory can be lost.
There is therefore a need for a computer architecture that provides the advantages of a memory hub architecture and also minimize this latency problems common in such systems, thereby providing a memory devices with high bandwidth and low latency.
SUMMARY OF THE INVENTION
A plurality of memory modules are coupled to a controller in a computer system. Each of the memory modules includes a plurality of memory devices and a memory hub. The memory hub comprises a link interface coupled to the controller and a memory device interface coupled to the memory devices. The link interface receives memory requests from the controller for access to a row of memory cells in at least one of the memory devices. The link interface transfers the memory requests to the memory device interface, which then couples the memory requests to the memory devices for access to a row of memory cells in at least one of the memory devices. The memory device interface then receives the read data from the memory devices responsive to at least some of the memory requests. Each of the memory hubs also includes a row cache memory coupled to the memory device interface for receiving and storing read data responsive to at least one of the memory requests. A sequencer that is also included in the memory hub is coupled to the link interface, the memory device interface and the row cache memory. The sequencer generates and couples to the memory device interface memory requests to read data from memory cells in a row of memory cells being accessed responsive to a memory request transferred from the link interface to the memory device interface. The read data from the memory cells in the row of memory cells being accessed responsive to the generated memory requests are also stored in the row cache memory. The sequencer preferably generates the memory requests when memory requests are not being received from the controller.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of a computer system according to one example of the invention in which a memory hub is included in each of a plurality of memory modules.
FIG. 2 is a block diagram of a memory hub used in the computer system of FIG. 1.



DETAILED DESCRIPTION OF THE INVENTION
A computer system 100 according to one example of the invention is shown in FIG. 1. The computer system 100 includes a processor 104 for performing various computing functions, such as executing specific software to perform specific calculations or tasks. The processor 104 includes a processor bus 106 that normally includes an address bus, a control bus, and a data bus. The processor bus 106 is typically coupled to cache memory 108, which, as previously mentioned, is usually static random access memory (“SRAM”). Finally, the processor bus 106 is coupled to a system controller 110, which is also sometimes referred to as a “North Bridge” or “memory controller.”
The system controller 110 serves as a communications path to the processor 104 for a variety of other components. More specifically, the system controller 110 includes a graphics port that is typically coupled to a graphics controller 112, which is, in turn, coupled to a video terminal 114. The system controller 110 is also coupled to one or more input devices 118, such as a keyboard or a mouse, to allow an operator to interface with the computer system 100. Typically, the computer system 100 also includes one or more output devices 120, such as a printer, coupled to the processor 104 through the system controller 110. One or more data storage devices 124 are also typically coupled to the processor 104 through the system controller 110 to allow the processor 104 to store data or retrieve data from internal or external storage media (not shown). Examples of typical storage devices 124 include hard and floppy disks, tape cassettes, and compact disk read-only memories (CD-ROMs).
The system controller 110 is coupled to several memory modules 130a,b . . . n, which serve as system memory for the computer system 100. The memory modules 130 are preferably coupled to the system controller 110 through a high-speed link 134, which may be an optical or electrical communication path or some other type of communications path. In the event the high-speed link 134 is implemented as an optical communication path, the optical communication path may be in the form of one or more optical fibers, for example. In such case, the system controller 110 and the memory modules will include an optical input/output port or separate input and output ports coupled to the optical communication path. The memory modules 130 are shown coupled to the system controller 110 in a multi-drop arrangement in which the single high-speed link 134 is coupled to all of the memory modules 130. However, it will be understood that other topologies may also be used, such as a point-to-point coupling arrangement in which a separate high-speed link (not shown) is used to couple each of the memory modules 130 to the system controller 110. A switching topology may also be used in which the system controller 110 is selectively coupled to each of the memory modules 130 through a switch (not shown). Other topologies that may be used will be apparent to one skilled in the art.
Each of the memory modules 130 includes a memory hub 140 for controlling access to 6 memory devices 148, which, in the example illustrated in FIG. 2, are synchronous dynamic random access memory (“SDRAM”) devices. However, a fewer or greater number of memory devices 148 may be used, and memory devices other than SDRAM devices may, of course, also be used. The memory hub 140 is coupled to each of the system memory devices 148 through a bus system 150, which normally includes a control bus, an address bus and a data bus.
One example of the memory hub 140 of FIG. 1 is shown in FIG. 2. The memory hub 140 includes a link interface 152 that is coupled to the high-speed link 134. The nature of the link interface 152 will depend upon the characteristics of the high-speed link 134. For example, in the event the high-speed link 134 is implemented using an optical communications path, the link interface 152 will include an optical input/output port and will convert optical signals coupled through the optical communications path into electrical signals. In any case, the link interface 152 preferably includes a buffer, such as a first-in, first-out buffer 154, for receiving and storing memory requests as they are received through the high-speed link 134. The memory requests are stored in the buffer 154 until they can be processed by the memory hub 140.
When the memory hub 140 is able to process a memory request, one of the memory requests stored in the buffer 154 is transferred to a memory sequencer 160. The memory sequencer 160 converts the memory requests from the format output from the system controller 110 into a memory request having a format that can be used by the memory devices 148. These re-formatted request signals will normally include memory command signals, which are derived from memory commands contained in the memory request received by the memory hub 140, and row and column address signals, which are derived from an address contained in the memory request received by the memory hub 140. In the event the memory request is a write memory request, the re-formatted request signals will normally include write data signals which are derived from write data contained in the memory request received by the memory hub 140. For example, where the memory devices 148 are conventional DRAM devices, the memory sequencer 160 will output row address signals, a row address strobe (“RAS”) signal, an active high write/active low read signal (“W/R*”), column address signals and a column address strobe (“CAS”) signal. The re-formatted memory requests are preferably output from the sequencer 160 in the order they will be used by the memory devices 148.
The memory sequencer 160 applies the re-formatted memory requests to a memory device interface 166. The nature of the memory device interface 166 will again depend upon the characteristics of the memory devices 148. In any case, the memory device interface 166 preferably includes a buffer, such as a FIFO buffer 168, for receiving and storing one or more memory requests as they are received from the link interface 152. The memory requests are stored in the buffer 168 until they can be processed by the memory devices 148. However, in the event the memory device interface 166 stores several memory requests, the memory device interface 166 may re-order the memory requests so that they are applied to the memory devices in some other order. For example, the memory requests may be stored in the interface 166 in a manner that causes one type of request, e.g., read requests to be processed before other types of requests, e.g., write requests.
The memory requests are described above as being received by the memory hub 140 in a format that is different from the format that the memory requests are applied to the memory devices 148. However, the system controller 110 may instead re-format memory requests from the processor 104 (FIG. 1) to a format that can be used by the memory devices 148. In such case, it is not necessary for the sequencer 160 to re-format the memory request. Instead, the sequencer 160 simply schedules the re-formatted memory request signals in the order needed for use by the memory devices 148. The memory request signals for one or more memory requests are then transferred to the memory device interface 166 so they can subsequently be applied to the memory devices 148.
As previously explained, one of the disadvantages of using memory hubs is the increased latency they can sometimes create. As also previously explained, a cache memory in the processor 104 or coupled to the processor bus 106 (FIG. 1), which is the traditional approach to reducing memory read latency, is not well suited to a memory system using memory hubs. The memory hub 140 example shown in FIG. 2 provides relatively low memory read latency by including a row cache memory 170 in each of the memory hubs 140. The row cache memory 170 may be similar in design to conventional cache systems including a data memory (not shown), a tag memory (not shown), and conventional address comparison logic (not shown). The row cache memory 170 stores data contained in one or more previously addressed rows of memory cells in one or more of the memory devices 148 in the module 140. The row cache memory 170 receives addresses forming part of a memory request from the link interface 152, which are compared to addresses of cached data. In the event of an address match, which indicates that the data being fetched by the memory request is stored in the row cache memory 170, the memory 170 outputs the requested data and a “ROW HIT” signal indicative of a cache hit. The ROW HIT signal is applied to a multiplexer 176 to cause the data from the cache memory 170 to be coupled to the link interface 152. In the event of a row cache miss, the multiplexer 176 couples data from the memory device interface 166 to the link interface 152. The ROW HIT signal is also applied to the memory sequencer 160 so that the sequencer will not couple the memory request to the memory device interface 166 in the event of a row hit since the data called for by the memory request has already been supplied by the row cache memory 170.
Although the row cache memory 170 may store data only from columns in a row that have been previously accessed, the memory 170 preferably pre-fetches data from many or all of the columns in the cached row when the memory hub 140 is not busy responding to memory requests from the system controller 110. More specifically, the memory sequencer 160 contains conventional circuitry to keep track of which columns of a row being accessed have had the data stored therein transferred to the row cache memory 170. When the sequencer 160 is not busy servicing memory requests from the link interface 152, the sequencer 160 generates memory requests, which are applied to the memory device interface 166, to cause data stored in the remaining columns of an addressed row to be transferred to the row cache memory 170. As a result, since memory accesses are typically to a series of memory locations in the same row, the row cache memory 170 is likely to be storing data that will be fetched in subsequent memory requests.
The memory hub 140 can process a subsequent memory request directed to a new row of memory cells in one of the memory devices 148 using a variety of procedures. For example, if the row cache memory 170 is capable of storing data from more than one row, the sequencer 160 can simply cause the data stored in the subsequently accessed row to be transferred to the row cache memory 170. If the row cache memory 170 is capable of storing data from only a single row of memory cells, or the cache memory 170 has otherwise reached its storage capacity, the data stored in the newly accessed row of memory cells can simply overwrite the previously stored data.
Although not shown in FIG. 2 or discussed above, the memory hub 140 preferably includes circuitry for maintaining cache consistency using conventional memory cache techniques. For example, the hub 140 may employ a “write through” mode of operation or a “write back” mode of operation in the event of a memory request for a write to a location followed by a memory request for a read from that same location.
From the foregoing it will be appreciated that, although specific embodiments of the invention have been described herein for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not limited except as by the appended claims.

## Claims

1. A memory module, comprising:
a plurality of memory devices; and
a memory hub, comprising:
a link interface receiving a memory request for access to a row of memory cells in at least one of the memory devices, wherein the memory request includes a read request to read data from a series of memory cells within the row of memory cells and wherein the series of memory cells in the row of memory cells comprises less than all the memory cells in the row of memory cells;
a memory device interface coupled to the memory devices, the memory device interface being operable to couple the memory request to the memory devices in an order different than an order the memory requests are received to access memory cells in the row of memory cells in at least one of the memory devices and to receive read data from the series of memory cells responsive to the read request included in the memory request;
a sequencer coupled to the link interface and the memory device interface, the sequencer configured to keep track of remaining memory cells in the row of memory cells not included in the series of memory cells in the row of memory cells read responsive to the received memory request, the sequencer further being configured to generate memory requests and couple to the memory device interface the generated memory requests to read data from the remaining memory cells in the same row of memory cells being accessed responsive to the memory request being coupled from the memory device interface to the at least one memory device, wherein the remaining memory cells in the same row of memory cells excludes the series of memory cells in the row of memory cells accessed responsive to the memory request, the sequencer being operable to generate and couple to the memory device the generated memory requests to read data only when memory requests are not being transferred from the link interface to the memory device interface, the read data read from the other memory cells in the same row of memory cells being accessed being stored in a row cache memory; and
the row cache memory coupled to the memory device interface and the sequencer configured to receive and store the read data from the remaining memory cells in the same row of memory cells being accessed responsive to the generated memory requests.

2. The memory module of claim 1 wherein the memory device interface further comprises a first-in, first-out buffer that is operable to receive and to store memory requests received from the link interface and from the sequencer and to transfer the stored memory requests to the at least one memory device in the order in which they were received.

3. The memory module of claim 1 wherein the link interface comprises a first-in, first-out buffer that is operable to receive and store memory requests and to transfer the stored memory requests to the memory device interface in the order in which they were received.

4. The memory module of claim 3 wherein the memory device interface further comprises a first-in, first-out buffer that is operable to receive and store memory requests received from the link interface and from the sequencer and to transfer the stored memory requests to the at least one memory device in the order in which they were received.

5. The memory module of claim 1 wherein the link interface comprises an optical input/output port.

6. The memory module of claim 1 wherein the memory devices comprises dynamic random access memory devices.

7. The memory module of claim 1 wherein the sequencer is operable to output an address contained in each read memory request received from the link interface, and wherein the row cache memory is operable to receive the addresses from the sequencer to determine if data called for by the memory request is stored in the row cache memory, the row cache memory outputting the read data and generating a hit signal if the data called for by the memory request is stored in the row cache memory and generating a row miss signal if the data called for by the memory request is not stored in the row cache memory.

8. The memory module of claim 7 further comprising a multiplexer having data inputs coupled to the row cache memory and to the memory device interface, a data output coupled to the link interface and a control input coupled to receive the row cache hit and row cache miss signals from the row cache memory, the multiplexer coupling read data from the memory device interface responsive to the row cache miss signal and coupling read data from the row cache memory responsive to the row cache hit signal.

9. A memory module, comprising:
a plurality of memory devices; and
a memory hub, comprising:
a link interface receiving memory requests, wherein each memory request is for access to a series of memory cells in a row of memory cells in at least one of the memory devices and the series of memory cells in a row of memory cells is less than all the memory cells in that row of memory cells;
a memory device interface coupled to the memory devices, the memory device interface configured to re-order how the memory requests are applied to the plurality of memory devices and further configured to couple each re-ordered memory request to the memory devices for access to a respective series of memory cells in a row of memory cells in at least one of the memory devices and to receive read data responsive to at least some of the memory requests, at least some of the memory requests coupled to the memory devices being responsive to memory requests transferred from the link interface to the memory device interface, wherein the memory device interface re-orders the memory requests to apply read requests before write requests;
a sequencer coupled to the link interface and the memory device interface and the row cache memory, the sequencer being operable to convert memory request received by the link interface into memory device memory requests provided to the memory device interface, the format of the memory device memory requests different than memory requests received by the link interface, the sequencer being operable to output an address contained in each read memory request received from the link interface, the sequencer further being operable to output an address other than an address contained in a read memory request received from the link interface, wherein the address other than the address contained in the read memory request received from the link interface includes an address for other memory cells in the row of memory cells not accessed by the address contained in the read memory request;
a row cache memory coupled to the memory device interface for receiving and storing read data from the other memory cells in the row of memory cells responsive to the address other than the address contained in one of the memory read requests being coupled from the memory device interface to the at least one memory device, device, the row cache memory further being operable to receive the addresses from the sequencer to determine if data called for by the memory request is stored in the row cache memory, the row cache memory outputting the read data and generating a hit signal if the data called for by the memory request is stored in the row cache memory and generating a row miss signal if the data called for by the memory request is not stored in the row cache memory; and
a multiplexer having data inputs coupled to the row cache memory and to the memory device interface, a data output coupled to the link interface and a control input coupled to receive the row cache hit and row cache miss signals from the row cache memory, the multiplexer coupling read data from the memory device interface responsive to the row cache miss signal and coupling read data from the row cache memory responsive to the row cache hit signal.

10. The memory module of claim 9 wherein the memory device interface further comprises a buffer that is operable to receive and store memory requests from the link interface and from the sequencer.

11. The memory module of claim 9 wherein the link interface comprises a first-in, first-out buffer that is operable to receive and store memory requests and to transfer the stored memory requests to the memory device interface in the order in which they were received.

12. The memory module of claim 11 wherein the memory device interface further comprises a buffer that is operable to receive and store memory requests received from the link interface and from the sequencer.

13. The memory module of claim 9 wherein the link interface comprises an optical input/output port.

14. The memory module of claim 9 wherein the memory devices comprises dynamic random access memory devices.

15. A memory hub, comprising:
a link interface receiving memory requests, at least some of the memory requests including an address for a series of memory cells in a row of memory cells, wherein the series of memory cells in the row of memory cells is less than all of the memory cells in the row of memory cells;
a memory device interface operable to re-order formatted memory requests and apply the re-ordered formatted memory requests to the memory devices and to receive read data responsive to at least some of the formatted memory requests, at least some of the formatted memory requests output by the memory device interface being responsive to memory requests transferred from the link interface to the memory device interface;
a row cache memory coupled to the memory device interface for receiving and storing read data received from the memory device interface based on at least one of the formatted memory requests being output from the memory device interface; and
a sequencer coupled to the link interface and the memory device interface and the row cache memory, the sequencer being operable to format memory requests received by the link interface into a different format to provide formatted memory requests to the memory device interface generated memory requests to read data from memory cells in the row of memory cells not included in a respective received memory request, the sequencer being operable to generate and couple to the memory device interface the generated memory requests to read data when memory requests are not being transferred from the link interface, the read data read responsive to the generated memory requests from the sequencer being stored in the row cache memory.

16. The memory hub of claim 15 wherein the memory device interface further comprises a buffer that is operable to receive and store memory requests received from the link interface and from the sequencer.

17. The memory hub of claim 15 wherein the link interface comprises a first-in, first-out buffer that is operable to receive and store memory requests and to transfer the stored memory requests to the memory device interface in the order in which they were received.

18. The memory hub of claim 17 wherein the memory device interface further comprises a buffer that is operable to receive and store memory requests received from the link interface and from the sequencer.

19. The memory hub of claim 15 wherein the link interface comprises an optical input/output port.

20. The memory hub of claim 15 wherein the sequencer is operable to output an address contained in each read memory request received from the link interface, and wherein the row cache memory is operable to receive the addresses from the sequencer to determine if data called for by the memory request is stored in the row cache memory, the row cache memory outputting the read data and generating a hit signal if the data called for by the memory request is stored in the row cache memory and generating a row miss signal if the data called for by the memory request is not stored in the row cache memory.

21. The memory hub of claim 20 further comprising a multiplexer having data inputs coupled to the row cache memory and to the memory device interface, a data output coupled to the link interface and a control input coupled to receive the row cache hit and row cache miss signals from the row cache memory, the multiplexer coupling read data from the memory device interface responsive to the row cache miss signal and coupling read data from the row cache memory responsive to the row cache hit signal.

22. A method of reading data in each of a plurality of memory modules using a controller coupled to the memory modules, the method comprising:
receiving, by a memory hub, memory requests from the controller by a first one of the memory modules, at least one of the memory requests being a request to access a series of memory cells in a row of memory cells of at least one memory device in a plurality of memory devices included in the first memory module, wherein the series of memory cells in the row of memory cells includes less than all of the memory cells in the row of memory cells;
re-ordering, by a memory device interface in the memory hub, the received memory requests;
coupling, by the memory hub, re-ordered memory requests to the at least one memory device in the first memory module;
generating, by a sequencer in the memory hub, requests to read data from other memory cells in the same row of memory cells accessed responsive to the at least one of the memory requests being a request to access the series of memory cells in the row of memory cells of the at least one memory device, the requests being generated when memory requests from the controller are not being coupled to the at least one memory device;
re-ordering, by a memory device interface in the memory hub, the received and generated memory requests;
coupling, by the memory hub, the generated memory requests to the at least one memory device; and
storing in cache memory in the first memory module read data responsive to the generated memory requests.

23. The method of claim 22, further comprising, in response to a memory request from the controller to read data from the first memory module:
determining if the read data are stored in the cache memory;
if the read data are stored in the cache memory, transferring the requested read data from the cache memory to the controller; and
if the read data are not stored in the cache memory, transferring the requested read data from the at least one memory device to the controller.

24. The method of claim 22 wherein the act of receiving memory requests from the controller by a first one of the memory modules comprises receiving optical signals corresponding to the received memory requests.

25. The method of claim 22 wherein the memory devices included in the first memory module comprises dynamic random access memory devices.