System, method and storage medium for providing data caching and data compression in a memory subsystem

Information

  • Patent Grant
  • 7480759
  • Patent Number
    7,480,759
  • Date Filed
    Tuesday, July 3, 2007
    17 years ago
  • Date Issued
    Tuesday, January 20, 2009
    15 years ago
Abstract
A cascaded interconnect system including a memory controller, one or more memory modules, an upstream memory bus and a downstream memory bus. The one or more memory modules include a first memory module with cache data. The memory modules and the memory controller are interconnected by a packetized multi-transfer interface via the downstream memory bus and the upstream memory bus. The first memory module and the memory controller are in direct communication via the upstream memory bus and the downstream memory bus.
Description
BACKGROUND OF THE INVENTION

The invention relates to a memory subsystem and, in particular, to providing data caching and data compression in a memory subsystem.


Computer memory subsystems have evolved over the years, but continue to retain many consistent attributes. Computer memory subsystems from the early 1980's, such as the one disclosed in U.S. Pat. No. 4,475,194 to LaVallee et al., of common assignment herewith, included a memory controller, a memory assembly (contemporarily called a basic storage module (BSM) by the inventors) with array devices, buffers, terminators and ancillary timing and control functions, as well as several point-to-point busses to permit each memory assembly to communicate with the memory controller via its own point-to-point address and data bus. FIG. 1 depicts an example of this early 1980 computer memory subsystem with two BSMs, a memory controller, a maintenance console, and point-to-point address and data busses connecting the BSMs and the memory controller.



FIG. 2, from U.S. Pat. No. 5,513,135 to Dell et al., of common assignment herewith, depicts an early synchronous memory module, which includes synchronous dynamic random access memories (DRAMs) 8, buffer devices 12, an optimized pinout, an interconnect and a capacitive decoupling method to facilitate operation. The patent also describes the use of clock re-drive on the module, using such devices as phase lock loops (PLLs).



FIG. 3, from U.S. Pat. No. 6,510,100 to Grundon et al., of common assignment herewith, depicts a simplified diagram and description of a memory system 10 that includes up to four registered dual inline memory modules (DIMMs) 40 on a traditional multi-drop stub bus channel. The subsystem includes a memory controller 20, an external clock buffer 30, registered DIMMs 40, an address bus 50, a control bus 60 and a data bus 70 with terminators 95 on the address bus 50 and data bus 70.



FIG. 4 depicts a 1990's memory subsystem which evolved from the structure in FIG. 1 and includes a memory controller 402, one or more high speed point-to-point channels 404, each connected to a bus-to-bus converter chip 406, and each having a synchronous memory interface 408 that enables connection to one or more registered DIMMs 410. In this implementation, the high speed, point-to-point channel 404 operated at twice the DRAM data rate, allowing the bus-to-bus converter chip 406 to operate one or two registered DIMM memory channels at the full DRAM data rate. Each registered DIMM included a PLL, registers, DRAMs, an electrically erasable programmable read-only memory (EEPROM) and terminators, in addition to other passive components.


As shown in FIG. 5, memory subsystems were often constructed with a memory controller connected either to a single memory module, or to two or more memory modules interconnected on a ‘stub’ bus. FIG. 5 is a simplified example of a multi-drop stub bus memory structure, similar to the one shown in FIG. 3. This structure offers a reasonable tradeoff between cost, performance, reliability and upgrade capability, but has inherent limits on the number of modules that may be attached to the stub bus. The limit on the number of modules that may be attached to the stub bus is directly related to the data rate of the information transferred over the bus. As data rates increase, the number and length of the stubs must be reduced to ensure robust memory operation. Increasing the speed of the bus generally results in a reduction in modules on the bus with the optimal electrical interface being one in which a single module is directly connected to a single controller, or a point-to-point interface with few, if any, stubs that will result in reflections and impedance discontinuities. As most memory modules are sixty-four or seventy-two bits in data width, this structure also requires a large number of pins to transfer address, command, and data. One hundred and twenty pins are identified in FIG. 5 as being a representative pincount.



FIG. 6, from U.S. Pat. No. 4,723,120 to Petty, of common assignment herewith, is related to the application of a daisy chain structure in a multipoint communication structure that would otherwise require multiple ports, each connected via point-to-point interfaces to separate devices. By adopting a daisy chain structure, the controlling station can be produced with fewer ports (or channels), and each device on the channel can utilize standard upstream and downstream protocols, independent of their location in the daisy chain structure.



FIG. 7 represents a daisy chained memory bus, implemented consistent with the teachings in U.S. Pat. No. 4,723,120. A memory controller 111 is connected to a memory bus 315, which further connects to a module 310a. The information on bus 315 is re-driven by the buffer on module 310a to a next module, 310b, which further re-drives the bus 315 to module positions denoted as 310n. Each module 310a includes a DRAM 311a and a buffer 320a. The bus 315 may be described as having a daisy chain structure with each bus being point-to-point in nature.


One drawback to the use of a daisy chain bus is associated with providing enhanced capabilities such as data caching and data compression. Adding enhanced capabilities may result in an indeterminate read data latency because the amount of time required to read a particular item of data cannot be pre-determined by the memory controller. The read latency will depend on several varying factors such as whether the data is located in a cache and whether the data has to be decompressed before being returned to the memory controller. However, the ability to add data caching and/or data compression in a pluggable fashion to selected modules in a daisy chain bus is desirable because these enhanced capabilities may lead to improved performance and space savings within a memory subsystem.


BRIEF SUMMARY OF THE INVENTION

Exemplary embodiments of the present invention include a cascaded interconnect system including a memory controller, one or more memory modules, an upstream memory bus and a downstream memory bus. The one or more memory modules include a first memory module with cache data. The memory modules and the memory controller are interconnected by a packetized multi-transfer interface via the downstream memory bus and the upstream memory bus. The first memory module and the memory controller are in direct communication via the upstream memory bus and the downstream memory bus.


Another exemplary embodiment of the present invention includes a memory controller, one or more memory modules, an upstream memory bus and a downstream memory bus. The one or more memory modules each include memory modules a plurality of corresponding memory devices. At least one of the memory modules includes cache data sourced from the corresponding memory devices on the memory module and a cache directory corresponding to the cache data. The memory modules and the memory controller are interconnected by a packetized multi-transfer interface via the downstream memory bus and the upstream memory bus. In addition, the memory controller utilizes a read data tag on data read requests sent via the downstream memory bus and the read data tag on data return results received via the upstream memory bus to match the data read requests with the data return results.


Another exemplary embodiment of the present invention includes a memory controller, one or more memory modules, an upstream memory bus and a downstream memory bus. The one or more memory modules include a first memory module with a data compression module for compressing and decompressing data stored on the memory modules. The memory modules and the memory controller are interconnected by a packetized multi-transfer interface via the downstream memory bus and the upstream memory bus. The first memory module and the memory controller are in direct communication via the upstream memory bus and the downstream memory bus.


A further exemplary embodiment of the present invention includes a cascaded interconnect system with a memory controller, one or more memory modules, an upstream memory bus and a downstream memory bus. The one or more memory modules each include a plurality of corresponding memory devices and at least one of the memory modules includes a data compression module. The memory modules and the memory controller are interconnected by a packetized multi-transfer interface via the downstream memory bus and the upstream memory bus. In addition, the memory controller utilizes a read data tag on data read requests sent via the downstream memory bus and the read data tag on data return results received via the upstream memory bus to match the data read requests with the data return results.


A further exemplary embodiment of the present invention includes a method for providing data caching in a memory system. The method includes receiving a request at a selected memory module to read data at a specified data address. The request is from a memory controller in a cascaded memory system and the selected memory module is one of one or more memory modules included in the cascaded memory system. A cache directory is searched for the data address. The data is read from cache data in response to locating the data address in the cache directory. The data is read from one of the memory devices in response to not locating the data address in the cache directory. The data is transmitted to the memory controller.


A further exemplary embodiment of the present invention includes a method for providing data compression in a memory system. The method includes receiving a request at a selected memory module to read data at a specified data address. The request comes from a memory controller in a cascaded memory system and the selected memory module is one of one or more memory modules included in the cascaded memory system. It is determined if the data is compressed and the data is decompressed if it is determined to be compressed. The data is then transmitted to the memory controller.


A further exemplary embodiment of the present invention includes a storage medium encoded with machine readable computer program code for providing data caching in a memory subsystem. The storage medium includes instructions for causing a computer to implement a method. The method includes receiving a request at a selected memory module to read data at a specified data address. The request is from a memory controller in a cascaded memory system and the selected memory module is one of one or more memory modules included in the cascaded memory system. A cache directory is searched for the data address. The data is read from cache data in response to locating the data address in the cache directory. The data is read from one of the memory devices in response to not locating the data address in the cache directory. The data is transmitted to the memory controller.


A further exemplary embodiment of the present invention includes a storage medium encoded with machine readable computer program code for providing data compression in a memory subsystem. The storage medium includes instructions for causing a computer to implement a method. The method includes receiving a request at a selected memory module to read data at a specified data address. The request comes from a memory controller in a cascaded memory system and the selected memory module is one of one or more memory modules included in the cascaded memory system. It is determined if the data is compressed and the data is decompressed if it is determined to be compressed. The data is then transmitted to the memory controller.





BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings wherein like elements are numbered alike in the several FIGURES:



FIG. 1 depicts a prior art memory controller connected to two buffered memory assemblies via separate point-to-point links;



FIG. 2 depicts a prior art synchronous memory module with a buffer device;



FIG. 3 depicts a prior art memory subsystem using registered DIMMs;



FIG. 4 depicts a prior art memory subsystem with point-to-point channels, registered DIMMs, and a 2:1 bus speed multiplier;



FIG. 5 depicts a prior art memory structure that utilizes a multidrop memory ‘stub’ bus;



FIG. 6 depicts a prior art daisy chain structure in a multipoint communication structure that would otherwise require multiple ports;



FIG. 7 depicts a prior art daisy chain connection between a memory controller and memory modules;



FIG. 8 depicts a cascaded memory structure that is utilized by exemplary embodiments of the present invention;



FIG. 9 depicts a memory structure with cascaded memory modules and unidirectional busses that is utilized by exemplary embodiments of the present invention;



FIG. 10 depicts a buffered module wiring system that is utilized by exemplary embodiments of the present invention;



FIG. 11 depicts a memory structure with cached data that may be utilized by exemplary embodiments of the present invention;



FIG. 12 depicts a memory structure with cached data that may be utilized by exemplary embodiments of the present invention;



FIG. 13 depicts a memory structure with data compression that may be utilized by exemplary embodiments of the present invention; and



FIG. 14 depicts a memory structure with cached data and data compression that may be utilized by exemplary embodiments of the present invention.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Exemplary embodiments of the present invention provide an enhanced memory subsystem (or memory channel) by including data caching capability in one or more memory modules within a cascaded memory subsystem. In embodiments where the memory controller has access to a cache directory for the memory subsystem, the deterministic nature of the controller interface protocol utilized by the memory subsystem is preserved. When the memory controller has access to the cache directory, reads to the cache data can be predetermined and specifically requested by the memory controller. Thus, the read data return from such reads to the cache data may be scheduled using standard mechanisms.


Additional embodiments of the present invention provide for a memory subsystem where the cache directory does not reside in the memory controller and is not accessible by the memory controller. In this case, the addition of cache to the memory subsystem results in indeterminate read data latencies. A tag signal is added to the upstream controller interface frame format so that returned read data may be identified by the memory controller. This read data identification removes the requirement that the memory controller be able to predict the exact return time of each read request. The ability to handle indeterminate read data latency allows the memory modules in the memory channel to utilize enhanced features (e.g., data caching and data compression) that modify the normally predictable read data return times.



FIG. 8 depicts a cascaded memory structure that may be utilized by exemplary embodiments of the present invention when buffered memory modules 806 (e.g., the buffer device is included within the memory module 806) are in communication with a memory controller 802. This memory structure includes the memory controller 802 in communication with one or more memory modules 806 via a high speed point-to-point bus 804. Each bus 804 in the exemplary embodiment depicted in FIG. 8 includes approximately fifty high speed wires for the transfer of address, command, data and clocks. By using point-to-point busses as described in the aforementioned prior art, it is possible to optimize the bus design to permit significantly increased data rates, as well as to reduce the bus pincount by transferring data over multiple cycles. Whereas FIG. 4 depicts a memory subsystem with a two to one ratio between the data rate on any one of the busses connecting the memory controller to one of the bus converters (e.g., to 1,066 Mb/s per pin) versus any one of the busses between the bus converter and one or more memory modules (e.g., to 533 Mb/s per pin), an exemplary embodiment of the present invention, as depicted in FIG. 8, provides a four to one bus speed ratio to maximize bus efficiency and to minimize pincount.


Although point-to-point interconnects permit higher data rates, overall memory subsystem efficiency must be achieved by maintaining a reasonable number of memory modules 806 and memory devices per channel (historically four memory modules with four to thirty-six chips per memory module, but as high as eight memory modules per channel and as few as one memory module per channel). Using a point-to-point bus necessitates a bus re-drive function on each memory module to permit memory modules to be cascaded such that each memory module is interconnected to other memory modules, as well as to the memory controller 802.



FIG. 9 depicts a memory structure with cascaded memory modules and unidirectional busses that is utilized by exemplary embodiments of the present invention. One of the functions provided by the memory modules 806 in the cascade structure is a re-drive function to send signals on the memory bus to other memory modules 806 or to the memory controller 802. FIG. 9 includes the memory controller 802 and four memory modules 806a, 806b, 806c and 806d, on each of two memory busses (a downstream memory bus 904 and an upstream memory bus 902), connected to the memory controller 802 in either a direct or cascaded manner. Memory module 806a is connected to the memory controller 802 in a direct manner. Memory modules 806b, 806c and 806d are connected to the memory controller 802 in a cascaded manner.


An exemplary embodiment of the present invention includes two unidirectional busses between the memory controller 802 and memory module 806a (“DIMM #1”), as well as between each successive memory module 806b-d (“DIMM #2”, “DIMM #3” and “DIMM #4”) in the cascaded memory structure. The downstream memory bus 904 is comprised of twenty-two single-ended signals and a differential clock pair. The downstream memory bus 904 is used to transfer address, control, write data and bus-level error code correction (ECC) bits downstream from the memory controller 802, over several clock cycles, to one or more of the memory modules 806 installed on the cascaded memory channel. The upstream memory bus 902 is comprised of twenty-three single-ended signals and a differential clock pair, and is used to transfer read data and bus-level ECC bits upstream from the sourcing memory module 806 to the memory controller 802. Because the upstream memory bus 902 and the downstream memory bus 904 are unidirectional and operate independently, read data, write data and memory commands may be transmitted simultaneously. This increases effective memory subsystem bandwidth and may result in higher system performance. Using this memory structure, and a four to one data rate multiplier between the DRAM data rate (e.g., 400 to 800 Mb/s per pin) and the unidirectional memory bus data rate (e.g., 1.6 to 3.2 Gb/s per pin), the memory controller 802 signal pincount, per memory channel, is reduced from approximately one hundred and twenty pins to about fifty pins.



FIG. 10 depicts a buffered module wiring system that is utilized by exemplary embodiments of the present invention. FIG. 10 is a pictorial representation of a memory module with shaded arrows representing the primary signal flows. The signal flows include the upstream memory bus 902, the downstream memory bus 904, memory device address and command busses 1010 and 1006, and memory device data busses 1012 and 1008. In an exemplary embodiment of the present invention, a buffer device 1002, also referred to as a memory interface chip, provides two copies of the address and command signals to the SDRAMs 1004 with the right memory device address and command bus 1006 exiting from the right side of the buffer device 1002 for the SDRAMs 1004 located to the right side and behind the buffer device 1002 on the right. The left memory device address and command bus 1010 exits from the left side of the buffer device 1002 and connects to the SDRAMs 1004 to the left side and behind the buffer device 1002 on the left. Similarly, the data bits intended for SDRAMs 1004 to the right of the buffer device 1002 exit from the right of the buffer device 1002 on the right memory device data bus 1008. The data bits intended for the left side of the buffer device 1002 exit from the left of the buffer device 1002 on the left memory device data bus 1012. The high speed upstream memory bus 902 and downstream memory bus 904 exit from the lower portion of the buffer device 1002, and connect to a memory controller or other memory modules either upstream or downstream of this memory module 806, depending on the application. The buffer device 1002 receives signals that are four times the memory module data rate and converts them into signals at the memory module data rate.


The memory controller 802 interfaces to the memory modules 806 via a pair of high speed busses (or channels). The downstream memory bus 904 (outbound from the memory controller 802) interface has twenty-four pins and the upstream memory bus 902 (inbound to the memory controller 802) interface has twenty-five pins. The high speed channels each include a clock pair (differential), a spare bit lane, ECC syndrome bits and the remainder of the bits pass information (based on the operation underway). Due to the cascaded memory structure, all nets are point-to-point, allowing reliable high-speed communication that is independent of the number of memory modules 806 installed. Whenever a memory module 806 receives a packet on either bus, it re-synchronizes the command to the internal clock and re-drives the command to the next memory module 806 in the chain (if one exists).


As described previously, the memory controller 802 interfaces to the memory module 806 via a pair of high speed channels (i.e., the downstream memory bus 904 and the upstream memory bus 902). The downstream (outbound from the memory controller 802) interface has twenty-four pins and the upstream (inbound to the memory controller 802) has twenty-five pins. The high speed channels each consist of a clock pair (differential), as well as single ended signals. Due to the cascade memory structure, all nets are point to point, allowing reliable high-speed communication that is independent of the number of memory modules 806 installed. The differential clock received from the downstream interface is used as the reference clock for the buffer device PLL and is therefore the source of all local buffer device 1002 clocks. Whenever the memory module 806 receives a packet on either bus, it re-synchronizes it to the local clock and drives it to the next memory module 806 or memory controller 802, in the chain (if one exists).



FIG. 11 depicts a memory subsystem with cached data that may be utilized by exemplary embodiments of the present invention. The memory subsystem includes a memory controller 1108 with a cache directory 1106. The first memory module 806 (labeled in FIG. 11 as “first”) connected to the memory controller 1108 includes a cache buffer device 1102 with cache data 1104. The second memory module 806 (labeled in FIG. 11 as “second”) in the chain includes a buffer device 1002 as described previously herein. The cache buffer device 1102 operates in the same manner as the previously described buffer device 1002 with the addition of cache functions. Similarly, the memory controller 1108 depicted in FIG. 1 operates in the same manner as the previously described memory controller 802 with the addition of cache functions.


In the configuration depicted in FIG. 11, the cache directory 1106 is separately accessible by the memory controller 1108 because it is contained within the memory controller 802. Alternatively, the cache directory 1106 may be located externally to the memory controller 1108 but accessible by the memory controller 1108. Accesses to the cache data 1104 (also referred to in the art as “level 3 data” or “L3 data”) are explicitly addressed by the memory controller 1108. As is known in the art, the latency of the cache reads will be less than the latency of reads to the memory devices 1004. In the exemplary configuration depicted in FIG. 11, the cache read latency is deterministically predetermined. The memory controller 1108 utilizes the information in the cache directory 1106 and the cache read latency to schedule collision free read traffic in the memory subsystem.


The cache buffer device 1102 may be located on one or more of the memory modules 806 within the memory subsystem depicted in FIG. 11. It may be located on the first memory module 806 and/or the second memory module 806. If the cache buffer device 1102 is set to “global” and located in the first memory module 806, then data from any of the memory modules 806 in the memory subsystem may be contained in the cache data 1104 and therefore referenced in the cache directory 1106. Alternatively, the cache buffer device 1104 may be located in the first memory module 806 and set to “local”, which indicates that only data within the first memory module 806 will be contained in the cache data 1104 and referenced by the cache directory 1106. Both the first and second memory modules 806 may contain “local” cache buffer devices 1102 with cached data 1104 contents being reflected in the cache directory 1106. Further, the first and second memory modules 806 may contain cache buffer devices 1104 that are set to “global” and cache data from any of the memory modules 806 in the memory subsystem may be contained in either of the cache buffer devices 1102. The previous examples refer to a memory subsystem that contains two memory modules 806, the same principles may be applied to memory subsystems with any number of memory modules 806 (e.g., one, four, eight, etc.).



FIG. 12 depicts an alternate memory subsystem with cached data that may be utilized by exemplary embodiments of the present invention. The first memory module 806 (labeled in FIG. 12 as “first”) includes a cache buffer device 1102 set to “global” that contains cached data 1104 and the cache directory 1106. Because the memory controller 802 does not know the contents of the cache data 1104, it cannot predict the return time of the data associated with the read request (i.e., there is indeterminate read data latency). To support indeterminate read data latency, the first memory module 806 includes a read data tag signal on the upstream memory bus 906 that will tie a memory read request from the memory controller 802 to result data sent to the memory controller 802. An extra wire may be added to the upstream memory bus 906 between the first memory module 806 and the memory controller 802 to contain a bit associated with the read data tag signal. Alternatively, one or more existing wires on the upstream memory bus 906 may be utilized to support the read data tag signal. In an exemplary embodiment of the present invention, the read data tag signal is sent to the first memory module 806 on the downstream memory bus 904 via one or more existing wires in the downstream memory bus 904. For example, the read data tag signal for the downstream memory bus 904 may be created by combining the position of the memory module 806 in the chain with a sequence number.


If a cache buffer device 1102 is plugged into the memory module 806 in the first position of the memory channel (or memory subsystem) and the cache buffer device 1102 is set to “global”, then the read data tag signal is utilized to identify which read request corresponds to the returning data. Memory read requests are issued by the memory controller 802 to the memory channel without knowledge of the cached status of the data at the requested address. If the requested address is found to be cached, then the data at the requested address will be returned immediately by the cache buffer device 1102, thus improving read data latency and system performance. If the requested address is not found in the cache, it will be returned from the main memory devices (e.g., SDRAMS 1004) with the standard read data latency. All memory addressable in the channel are potentially cached by the cache buffer device 1102 when the cache buffer device 1102 is located on a memory module 806 in the first position in the memory channel and the cache buffer device 1102 is set to “global.”


In an alternate exemplary embodiment of the present invention, all memory modules 806 include the optional read data tag signal on their upstream controller interfaces (i.e., the upstream memory bus 906). Each segment (i.e., between each of the memory modules 806 and between the first memory module 806 and the memory controller 802) of the upstream memory bus 906 includes an extra bit for the read data tag signal or utilize an existing bit for the read data tag signal. Each segment will contain a read data tag in cases where the cache buffer device 1102 is set to “local” and will only operate on the memory addresses that reside on the local memory module 806. In addition, the read data tag may be utilized to perform data merging between data local to the memory module 806 and data being received via the upstream memory bus 906. The decoding of the read data tag and local data arbitration at each memory module 806 in the memory channel may add appreciable latency to all memory read operations. The added latency associated with this embodiment is more than the added latency associated with the previous embodiment where the read data tag signal is limited to the first memory module 806 in the chain.



FIG. 13 depicts a memory structure with data compression that may be utilized by exemplary embodiments of the present invention. Data compression is another enhanced feature that may be optionally added to the memory subsystems described herein. The compression buffer device 1302 includes logic macros that encode write data into a format that requires less space in the main memory devices (e.g., the SDRAMS 1004). A memory channel, or memory subsystem, with data compression will appear to have a much higher capacity than an uncompressed memory channel. When leveraged by the system, this additional effective capacity will result in increased performance as fewer pieces of data will need to be stored in the slower levels of system memory such as the hard disk drive. During read operations, memory data locations that have been compressed will typically take longer to retrieve from the memory channel due to the decompression time.


In exemplary embodiments, such as the one depicted in FIG. 13, the first memory module 806 includes an optional read data tag signal on the upstream controller interface (i.e., the upstream memory bus 906) to allow for indeterminate read data latency. If a compression buffer device 1302 is included in the first memory module 806 in the chain (i.e., the memory module labeled “first” in FIG. 13) and the compression buffer device 1302 is set to “global”, then read data tag signal will be utilized. Memory read requests are issued to the memory channel by the memory controller 802 without knowledge of the compression status of the requested address. If the data at the requested address is determined to be compressed, the data at that address will be returned after decompression. The compression of data will result in improving effective channel memory capacity and system performance. If the data at the requested address is not compressed, the data at the requested address will be returned from the main memory devices (e.g., the SDRAMS 1004) with the standard read data latency. All data at memory addresses in the channel are potentially compressed when the compression buffer device 1302 is located in the first memory module 806 in the channel and the compression buffer device 1302 is set to “global.”


In alternate exemplary embodiments of the present invention, the compression buffer device 1302 is located on one or more of the memory modules 806 and set to “local.” In this case, all memory modules 806 include the optional read data tag signal on their upstream controller interfaces (i.e., the upstream memory bus 906). Each segment of the upstream memory bus 906 (i.e., between each of the memory modules 806 and between the first memory module 806 and the memory controller 802) includes an extra bit for the read data tag signal. Here, the compression buffer device 1302 will only operate on the memory addresses that reside on the local memory module 806. Decoding of the read data tag and local data arbitration at each memory module 806 in the memory channel may add appreciable latency to all memory read operations. The added latency associated with this embodiment is more than the added latency associated with the previous embodiment where the read data tag signal is limited to the first memory module 806 in the chain.


An alternate exemplary embodiment of the present invention includes a buffer device 1002 with the cache functions of the cache buffer device 1102 and the compression functions of the compression buffer device 1302. One, both or none of the cache functions and the compression functions may be activated for each memory module in the memory subsystem, thereby allowing for flexibility in memory subsystem configuration. Further, one or both of the cache buffer device 1102 and the compression buffer device 1302 may be located included on the first memory module and set to “global.”



FIG. 14 depicts a memory structure with cached data (on the memory module 806 labeled “second”) and data compression (on the memory module 806 labeled “third”) that may be utilized by exemplary embodiments of the present invention. Because the cache buffer device 1102 and compression buffer device 1302 are not located in the first memory module 806 (i.e., they are set to “local”), the read data tag is added to all segments of the upstream memory bus 906 to track the read commands in the memory subsystem. The caching performed by the cache buffer device is limited to data stored on memory devices (e.g., SDRAMS 1004) accessible by the second memory module 806. Similarly, the compression performed by the compression buffer device 1302 is limited to data stored on memory devices accessible by the third memory module 806.


Exemplary embodiments of the present invention may be utilized to improve the performance of the entire memory subsystem. Cache and/or data compression may be included in a buffer device 1002 in the first memory module 806 in the chain and apply to all data in the memory subsystem. If global caching is activated, then the cache buffer device 1102 in the first memory module 806 includes cache data for data that may be addressed by any of the memory modules 806 in the memory subsystem. Similarly, if global data compression is activated, then the compression buffer device 1302 in the first memory module provides data compression (and decompression) for data that may be addressed by any of the memory modules 806 in the memory subsystem


Alternate exemplary embodiments of the present invention may be utilized to improve the performance of particular memory modules 806 within the memory subsystem. Local cache and/or data compression may be included in a buffer device 1002 in a selected memory module 806 and apply to data accessible by the selected memory module 806. In this manner, the performance for selected memory modules 806 may be improved by utilizing exemplary embodiments of the present invention.


As described above, the embodiments of the invention may be embodied in the form of computer-implemented processes and apparatuses for practicing those processes. Embodiments of the invention may also be embodied in the form of computer program code containing instructions embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. The present invention can also be embodied in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.


While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another.

Claims
  • 1. A cascaded interconnect system comprising: a memory controller for generating data read requests, the controller operable with indeterminate data response times;one or more memory modules for processing the data read requests, each memory module including one or more memory devices, wherein at least one of the memory modules includes a data compression module for compressing and decompressing at least a subset of the data read from and written to at least a subset of the one or more memory devices;an upstream memory bus; anda downstream memory bus, wherein the memory modules and the memory controller are interconnected by a packetized multi-transfer interface via the downstream memory bus and the upstream memory bus, and data responses to the data read requests accessed via the data compression module include tag information to correlate the data responses to the data read requests.
  • 2. The system of claim 1 wherein the upstream memory bus includes one or more wires for the tag information.
  • 3. The system of claim 1 wherein the data compression module is located on a first memory module in the one or more memory modules and at least a subset of the data accessed via the data compression module is sourced from a memory device located on a second memory module in the one or more memory modules, the first memory module and the second memory module being different memory modules.
  • 4. The system of claim 1 wherein at least one of the memory modules includes a cache.
  • 5. A cascaded interconnect system comprising: a memory controller for generating read data requests, the controller operable with indeterminate data response times;one or more memory modules each including a plurality of corresponding memory devices, wherein at least one of the memory modules includes a data compression module for compressing and decompressing at least a subset of the data stored on the corresponding memory devices on the memory module;an upstream memory bus; anda downstream memory bus, wherein the memory modules and the memory controller are interconnected by a packetized multi-transfer interface via the downstream memory bus and the upstream memory bus, and the memory controller utilizes a read data tag on data read requests sent via the downstream memory bus and the read data tag on data return results received via the upstream memory bus to match the data read requests with the data return results.
  • 6. The system of claim 5 wherein at least one of the one or more memory modules includes a data cache.
  • 7. A method for providing data compression in a memory system, the method comprising: receiving a request at a selected memory module to read data at a specified data address, the request from a memory controller in a cascaded memory system and the selected memory module one of one or more memory modules included in the cascaded memory system;determining if the data is compressed;decompressing the data if it is determined to be compressed; andtransmitting tag information along with the data to correlate the data to the request if the data was determined to be compressed.
  • 8. The method of claim 7 wherein a data compression module for performing the decompressing is located on the selected memory module, the receiving a request includes receiving a read data tag associated with the request and the transmitting the data includes transmitting the read data tag.
  • 9. The method of claim 7 wherein the selected memory module is in direct communication with the memory controller and data is sourced from the one or more memory modules.
  • 10. The method of claim 7 wherein data in the data is sourced from the selected memory module.
  • 11. The method of claim 7 wherein the selected memory module further includes a cache.
  • 12. A storage medium encoded with machine readable computer program code for providing data caching in a memory subsystem, the storage medium including instructions for causing a computer to implement a method comprising: receiving a request at a selected memory module to read data at a specified data address, the request from a memory controller in a cascaded memory system and the selected memory module one of one or more memory modules included in the cascaded memory system;determining if the data is compressed;decompressing the data if it is determined to be compressed; andtransmitting tag information along with the data to correlate the data to the request if the data was determined to be compressed.
  • 13. The storage medium of claim 12 wherein a data compression module for performing the decompressing is located on the selected memory module, the receiving a request includes receiving a read data tag associated with the request and the transmitting the data includes transmitting the read data tag.
  • 14. The storage medium of claim 12 wherein the selected memory module is in direct communication with the memory controller and data is sourced from the one or more memory modules.
  • 15. The storage medium of claim 12 wherein data in the data is sourced from the selected memory module.
  • 16. The storage medium of claim 12 wherein the selected memory module further includes a cache.
CROSS REFERENCE TO RELATED APPLICATION

This application is a divisional application of U.S. Ser. No. 10/977,846 filed Oct. 29, 2004, now U.S. Pat. No. 7,277,988, the contents of which are incorporated by reference herein in their entirety.

US Referenced Citations (249)
Number Name Date Kind
2842682 Clapper Jul 1958 A
3333253 Sahulka Jul 1967 A
3395400 De Witt Jul 1968 A
3825904 Burk et al. Jul 1974 A
4028675 Frankenberg Jun 1977 A
4135240 Ritchie Jan 1979 A
4472780 Chenoweth et al. Sep 1984 A
4475194 LaVallee et al. Oct 1984 A
4486739 Franaszek et al. Dec 1984 A
4641263 Perlman et al. Feb 1987 A
4654857 Samson et al. Mar 1987 A
4723120 Petty, Jr. Feb 1988 A
4740916 Martin Apr 1988 A
4796231 Pinkham Jan 1989 A
4803485 Rypinkski Feb 1989 A
4833605 Terada et al. May 1989 A
4839534 Clasen Jun 1989 A
4943984 Pechanek et al. Jul 1990 A
4985828 Shimizu et al. Jan 1991 A
5053947 Heibel et al. Oct 1991 A
5177375 Ogawa et al. Jan 1993 A
5206946 Brunk Apr 1993 A
5214747 Cok May 1993 A
5265212 Bruce, II Nov 1993 A
5287531 Rogers, Jr. et al. Feb 1994 A
5347270 Matsuda et al. Sep 1994 A
5357621 Cox Oct 1994 A
5375127 Leak Dec 1994 A
5387911 Gleichert et al. Feb 1995 A
5394535 Ohuchi Feb 1995 A
5454091 Sites et al. Sep 1995 A
5475690 Burns et al. Dec 1995 A
5513135 Dell et al. Apr 1996 A
5517626 Archer et al. May 1996 A
5522064 Aldereguia et al. May 1996 A
5544309 Chang et al. Aug 1996 A
5546023 Borkar et al. Aug 1996 A
5561826 Davies et al. Oct 1996 A
5592632 Leung et al. Jan 1997 A
5594925 Harder et al. Jan 1997 A
5611055 Krishan et al. Mar 1997 A
5613077 Leung et al. Mar 1997 A
5627963 Gabillard et al. May 1997 A
5629685 Allen et al. May 1997 A
5661677 Rondeau, II et al. Aug 1997 A
5666480 Leung et al. Sep 1997 A
5684418 Yanagiuchi Nov 1997 A
5706346 Katta et al. Jan 1998 A
5764155 Kertesz et al. Jun 1998 A
5822749 Agarwal Oct 1998 A
5852617 Mote, Jr. Dec 1998 A
5870325 Nielsen et al. Feb 1999 A
5872996 Barth et al. Feb 1999 A
5917780 Millar Jun 1999 A
5926838 Jeddeloh Jul 1999 A
5928343 Farmwald et al. Jul 1999 A
5930273 Mukojima Jul 1999 A
5959914 Gates et al. Sep 1999 A
5973951 Bechtolsheim et al. Oct 1999 A
5974493 Okumura et al. Oct 1999 A
5995405 Trick Nov 1999 A
6003121 Wirt Dec 1999 A
6011732 Harrison et al. Jan 2000 A
6038132 Tokunaga et al. Mar 2000 A
6049476 Laudon et al. Apr 2000 A
6076158 Sites et al. Jun 2000 A
6078515 Nielsen et al. Jun 2000 A
6081868 Brooks Jun 2000 A
6085276 VanDoren et al. Jul 2000 A
6096091 Hartmann Aug 2000 A
6128746 Clark et al. Oct 2000 A
6145028 Shank et al. Nov 2000 A
6170047 Dye Jan 2001 B1
6170059 Pruett et al. Jan 2001 B1
6173382 Dell et al. Jan 2001 B1
6185718 Dell et al. Feb 2001 B1
6215686 Deneroff et al. Apr 2001 B1
6219288 Braceras et al. Apr 2001 B1
6219760 McMinn Apr 2001 B1
6260127 Olarig et al. Jul 2001 B1
6262493 Garnett Jul 2001 B1
6292903 Coteus et al. Sep 2001 B1
6301636 Schultz et al. Oct 2001 B1
6317352 Halbert et al. Nov 2001 B1
6321343 Toda Nov 2001 B1
6338113 Kubo et al. Jan 2002 B1
6357018 Stuewe et al. Mar 2002 B1
6370631 Dye Apr 2002 B1
6378018 Tsern et al. Apr 2002 B1
6381685 Dell et al. Apr 2002 B2
6393528 Arimilli et al. May 2002 B1
6408398 Frecker et al. Jun 2002 B1
6446174 Dow Sep 2002 B1
6467013 Nizar Oct 2002 B1
6473836 Ikeda Oct 2002 B1
6483755 Leung et al. Nov 2002 B2
6487102 Halbert et al. Nov 2002 B1
6487627 Willke et al. Nov 2002 B1
6493250 Halbert et al. Dec 2002 B2
6496540 Widmer Dec 2002 B1
6496910 Baentsch et al. Dec 2002 B1
6499070 Whetsel Dec 2002 B1
6502161 Perego et al. Dec 2002 B1
6507888 Wu et al. Jan 2003 B2
6510100 Grundon et al. Jan 2003 B2
6513091 Blackmon et al. Jan 2003 B1
6530007 Olarig Mar 2003 B2
6532525 Aleksic et al. Mar 2003 B1
6546359 Week Apr 2003 B1
6549971 Cecchi et al. Apr 2003 B1
6553450 Dodd et al. Apr 2003 B1
6557069 Drehmel et al. Apr 2003 B1
6564329 Cheung et al. May 2003 B1
6584576 Co Jun 2003 B1
6587912 Leddige et al. Jul 2003 B2
6590827 Chang et al. Jul 2003 B2
6594748 Lin Jul 2003 B1
6601121 Singh et al. Jul 2003 B2
6601149 Brock et al. Jul 2003 B1
6604180 Jeddeloh Aug 2003 B2
6611905 Grundon et al. Aug 2003 B1
6622217 Gharacorloo et al. Sep 2003 B2
6625687 Halber et al. Sep 2003 B1
6625702 Rentscler et al. Sep 2003 B2
6628538 Funaba et al. Sep 2003 B2
6631439 Saulsbury et al. Oct 2003 B2
6671376 Koto et al. Dec 2003 B1
6678811 Rentschler et al. Jan 2004 B2
6684320 Mohamed et al. Jan 2004 B2
6697919 Gharachorloo et al. Feb 2004 B2
6704842 Janakiraman et al. Mar 2004 B1
6721185 Dong et al. Apr 2004 B2
6721944 Chaudhry et al. Apr 2004 B2
6738836 Kessler et al. May 2004 B1
6741096 Moss May 2004 B2
6754762 Curley Jun 2004 B1
6766389 Hayter et al. Jul 2004 B2
6775747 Venkatraman Aug 2004 B2
6791555 Radke et al. Sep 2004 B1
6792495 Garney et al. Sep 2004 B1
6839393 Sidiropoulos Jan 2005 B1
6877076 Cho et al. Apr 2005 B1
6877078 Fujiwara et al. Apr 2005 B2
6882082 Greeff et al. Apr 2005 B2
6889284 Nizar et al. May 2005 B1
6898726 Lee May 2005 B1
6918068 Vail et al. Jul 2005 B2
6938119 Kohn et al. Aug 2005 B2
6944084 Wilcox Sep 2005 B2
6948091 Bartels et al. Sep 2005 B2
6949950 Takahashi et al. Sep 2005 B2
6977536 Chin-Chieh et al. Dec 2005 B2
6993612 Porterfield Jan 2006 B2
7039755 Helms May 2006 B1
7047384 Bodas et al. May 2006 B2
7076700 Rieger Jul 2006 B2
7103792 Moon Sep 2006 B2
7133790 Liou Nov 2006 B2
7133972 Jeddeloh Nov 2006 B2
7177211 Zimmerman Feb 2007 B2
7194593 Schnepper Mar 2007 B2
7197594 Raz et al. Mar 2007 B2
7206962 Deegan et al. Apr 2007 B2
7216196 Jeddeloh May 2007 B2
7227949 Heegard et al. Jun 2007 B2
7240145 Holman Jul 2007 B2
7266634 Ware et al. Sep 2007 B2
7313583 Porten et al. Dec 2007 B2
7321979 Lee Jan 2008 B2
20010000822 Dell et al. May 2001 A1
20010003839 Kondo Jun 2001 A1
20010029566 Woo Oct 2001 A1
20020019926 Huppenthal et al. Feb 2002 A1
20020038405 Leddige et al. Mar 2002 A1
20020059439 Arroyo et al. May 2002 A1
20020083255 Greeff et al. Jun 2002 A1
20020103988 Dornier Aug 2002 A1
20020112119 Halbert et al. Aug 2002 A1
20020112194 Uzelac Aug 2002 A1
20020124195 Nizar Sep 2002 A1
20020124201 Edwards et al. Sep 2002 A1
20020147898 Rentschler et al. Oct 2002 A1
20020174274 Wu et al. Nov 2002 A1
20030009632 Arimilli et al. Jan 2003 A1
20030028701 Rao et al. Feb 2003 A1
20030033364 Garnett et al. Feb 2003 A1
20030051055 Parrella et al. Mar 2003 A1
20030056183 Kobayashi Mar 2003 A1
20030084309 Kohn May 2003 A1
20030090879 Doblar et al. May 2003 A1
20030105938 Cooksey et al. Jun 2003 A1
20030126363 David Jul 2003 A1
20030223303 Lamb et al. Dec 2003 A1
20030236959 Johnson et al. Dec 2003 A1
20040006674 Hargis et al. Jan 2004 A1
20040049723 Obara Mar 2004 A1
20040098459 Dorst May 2004 A1
20040098549 Dorst May 2004 A1
20040117588 Arimilli et al. Jun 2004 A1
20040128474 Vorbach Jul 2004 A1
20040163028 Olarig Aug 2004 A1
20040165609 Herbst et al. Aug 2004 A1
20040199363 Bohizic et al. Oct 2004 A1
20040205433 Gower et al. Oct 2004 A1
20040230718 Polzin et al. Nov 2004 A1
20040246767 Vogt Dec 2004 A1
20040250153 Vogt Dec 2004 A1
20040260909 Lee et al. Dec 2004 A1
20040260957 Jeddeloh et al. Dec 2004 A1
20050023560 Ahn et al. Feb 2005 A1
20050033906 Mastronarde et al. Feb 2005 A1
20050044305 Jakobs et al. Feb 2005 A1
20050050237 Jeddeloh et al. Mar 2005 A1
20050050255 Jeddeloh Mar 2005 A1
20050066136 Schnepper Mar 2005 A1
20050071542 Weber et al. Mar 2005 A1
20050080581 Zimmerman et al. Apr 2005 A1
20050086411 Myer et al. Apr 2005 A1
20050097249 Oberlin et al. May 2005 A1
20050120157 Chen et al. Jun 2005 A1
20050125702 Huang et al. Jun 2005 A1
20050125703 Lefurgy et al. Jun 2005 A1
20050138246 Chen et al. Jun 2005 A1
20050138267 Bains et al. Jun 2005 A1
20050144399 Hosomi Jun 2005 A1
20050149665 Wolrich et al. Jul 2005 A1
20050166006 Talbot et al. Jul 2005 A1
20050177677 Jeddeloh Aug 2005 A1
20050177690 LaBerge Aug 2005 A1
20050204216 Daily et al. Sep 2005 A1
20050223196 Knowles Oct 2005 A1
20050229132 Butt et al. Oct 2005 A1
20050248997 Lee Nov 2005 A1
20050257005 Jeddeloh et al. Nov 2005 A1
20050259496 Hsu et al. Nov 2005 A1
20050289377 Luong Dec 2005 A1
20060036826 Dell et al. Feb 2006 A1
20060036827 Dell et al. Feb 2006 A1
20060080584 Hartnett et al. Apr 2006 A1
20060085602 Huggahalli et al. Apr 2006 A1
20060095592 Borkenhagen May 2006 A1
20060095679 Edirisooriya May 2006 A1
20060107175 Dell et al. May 2006 A1
20060112238 Jamil et al. May 2006 A1
20060161733 Beckett et al. Jul 2006 A1
20060195631 Rajamani Aug 2006 A1
20060288172 Lee et al. Dec 2006 A1
20070025304 Leelahakriengkrai et al. Feb 2007 A1
20070160053 Coteus Jul 2007 A1
Foreign Referenced Citations (7)
Number Date Country
0470734 Feb 1992 EP
2396711 Jun 2004 GB
59153353 Sep 1984 JP
59153353 Sep 1984 JP
0432614 Nov 1992 JP
10011971 Jan 1998 JP
WO2005038660 Apr 2005 WO
Related Publications (1)
Number Date Country
20080016280 A1 Jan 2008 US
Divisions (1)
Number Date Country
Parent 10977846 Oct 2004 US
Child 11772922 US