# Patent

## Title
Systems and methods for providing data modification operations in memory subsystems

## Abstract

Systems and methods for providing data modification operations in memory subsystems. Systems include a plurality of memory devices, a memory controller, one or more memory busses connected to the memory controller and a memory hub device. The memory controller receives and responds to memory access requests including memory update requests from a processor. The memory controller also generates a memory update command in response to receiving a memory update request. The memory hub device includes a first port, a second port and a control unit. The first port is in communication with the memory controller via one or more of the memory busses for transferring data and control information between the memory hub device and the memory controller. The second port is in communication with one or more of the memory devices. The control unit decodes the memory update command from the data and control information and accesses the memory devices via the second port to perform the memory update command local to the memory hub devices as a logical read-modify-write sequence.

## Background
GOVERNMENT RIGHTS
This invention was made with Government support under subcontract NBCH3039004 awarded by the Defense Advanced Research Projects Agency (DARPA). The Government has certain rights in this invention.


BACKGROUND OF THE INVENTION
This invention relates generally to memory controllers and memory hub devices, and more particularly to systems and methods for providing data modification operations in memory hub devices.
Contemporary high performance computing main memory systems are generally composed of one or more dynamic random access memory (DRAM) devices, which are connected to one or more processors via one or more memory control elements. Overall computer system performance is affected by each of the key elements of the computer structure, including the performance/structure of the processor(s), any memory cache(s), the input/output (I/O) subsystem(s), the efficiency of the memory control function(s), the main memory device(s), and the type and structure of the memory interconnect interface(s).
Extensive research and development efforts are invested by the industry, on an ongoing basis, to create improved and/or innovative solutions to maximizing overall system performance and density by improving the memory system/subsystem design and/or structure. High-availability systems present further challenges as related to overall system reliability due to customer expectations that new computer systems will markedly surpass existing systems in regard to mean-time-before-failure (MTBF), in addition to offering additional functions, increased performance, increased storage, lower operating costs, etc. Other frequent customer requirements further exacerbate the memory system design challenges, and include such items as ease of upgrade and reduced system environmental impact (such as space, power and cooling).
FIG. 1 relates to U.S. Pat. No. 5,513,135 to Dell et al., of common assignment herewith, and depicts an early synchronous memory module. The memory module depicted in FIG. 1 is a dual in-line memory module (DIMM). This module is composed of synchronous DRAMs 8, buffer devices 12, an optimized pinout, and an interconnect and capacitive decoupling method to facilitate high performance operation. The patent also describes the use of clock re-drive on the module, using such devices as phase-locked loops (PLLs).
FIG. 2 relates to U.S. Pat. No. 6,173,382 to Dell et al., of common assignment herewith, and depicts a computer system 10 which includes a synchronous memory module 20 that is directly (i.e. point-to-point) connected to a memory controller 14 via a bus 40, and which further includes logic circuitry 24 (such as an application specific integrated circuit, or “ASIC”) that buffers, registers or otherwise acts on the address, data and control information that is received from the memory controller 14. The memory module 20 can be programmed to operate in a plurality of selectable or programmable modes by way of an independent bus, such as an inter-integrated circuit (I2C) control bus 34, either as part of the memory initialization process or during normal operation. When utilized in applications requiring more than a single memory module connected directly to a memory controller, the patent notes that the resulting stubs can be minimized through the use of field-effect transistor (FET) switches to electrically disconnect modules from the bus.
Relative to U.S. Pat. No. 5,513,135, U.S. Pat. No. 6,173,382 further demonstrates the capability of integrating all of the defined functions (address, command, data, presence detect, etc) into a single device. The integration of functions is a common industry practice that is enabled by technology improvements and, in this case, enables additional module density and/or functionality.
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 DIMMs 40 on a traditional multi-drop stub bus. 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 the data bus 70. Although only a single memory channel is shown in FIG. 3, systems produced with these modules often included more than one discrete memory channel from the memory controller, with each of the memory channels operated singly (when a single channel was populated with modules) or in parallel (when two or more channels where populated with modules) to achieve the desired system functionality and/or performance.
FIG. 4, from U.S. Pat. No. 6,587,912 to Bonella et al., depicts a synchronous memory module 210 and system structure in which the repeater hubs 320 include local re-drive of the address, command and data to the local memory devices 301 and 302 via buses 321 and 322; generation of a local clock (as described in other figures and the patent text); and the re-driving of the appropriate memory interface signals to the next module or component in the system via bus 300.
FIG. 5 illustrates a computing system comprised of: a processor chip 500 with an integrated memory controller 510 and a cache 512; and one or more memory subsystems (also referred to as memory modules) 503 that include one or more memory hub devices 504 each connected to one or more DRAM devices 509. Each memory subsystem 503 is associated with a memory channel that is connected to the integrated processor chip 500 through a cascade interconnect bus structure for the highest performance at the lowest cost. The memory controller(s) 510 are interconnected to memory hub devices 504 via one or more physical high speed bus(es) 506. Each hub device 504 provides one or more low speed independent connection(s) to groups of DRAM devices 509 following, for example, the fully buffered DIMM standard. Multiple (typically 2 or 4) identically configured physical networks 508 of memory modules are logically grouped together into module groups 501 and 502, and operated on in unison by the memory controller 510 to provide for optimal latency, bandwidth, and error correction effectiveness for system memory cache line transfer (typically 64B or 128B). However, a commonly assigned U.S. patent application Ser. No. 11/464,503, entitled SYSTEMS AND METHODS FOR PROGRAM DIRECTED MEMORY ACCESS PATTERNS, filed on Aug. 15, 2006, provides the means to have logical networks of hubs dynamically associated and de-associated for specific addresses based on software hints.
The memory controller 510 translates system requests for memory access into packets according to a memory hub communication protocol. Memory write packets contain at least a command, address, and associated data. Memory read packets contain at least a command and address. Memory read packets imply an expected packet will be returned which contains the requested data.
FIG. 6 depicts a block diagram of a memory hub device 504 including a link interface 604 for providing the means to re-synchronize, translate and re-drive high speed memory access information to associated DRAM devices 509 and/or to re-drive the information downstream on memory bus 506 as applicable based on the memory system protocol. The information is received by the links interface 604 from an upstream memory hub device 504 or from a memory controller 510 (directly or via an upstream memory hub device controller 504) via the memory bus 506. The memory device data interface 615 manages the technology-specific data interface with the memory devices 509 and controls the bidirectional memory data bus 608. The memory hub control 613 responds to access request packets by responsively driving the memory device 509 technology-specific address and control bus 614 and directing the read data flow 607 and write data flow 610 selectors. The link interface 604 decodes the packets and directs the address and command information directed to the local hub device 504 to the memory hub control 613. Memory write data from the link interface 604 can be temporarily stored in the write data queue 611 or directly driven to the memory devices 509 via the write data flow selector 610 and internal bus 612, and then sent via internal bus 609 and memory device data interface 615 to memory device data bus 608. Memory read data from memory device(s) 509 can be queued in the read data queue 606 or directly transferred to the link interface 604 via internal bus 605 and read data selector 607, to be transmitted on the upstream bus 506 as a read reply packet.
Processor updates to memory (write operations) at a granularity smaller than a cache line are merged in the cache 512, which is located in the integrated processor chip 500, requiring the processor to initiate a request access to the cache 512. Responsively, the cache 512 requests the memory controller 510 to read the cache line from main memory, and the memory controller 510 initiates a memory read command to the memory hub device(s), 504 and the memory hub device(s) 504 forward the read command to the memory devices 509. The memory devices 509 reply with the data comprising the cache line, and the data is propagated back to the cache 512 where the processor “write” data is then merged to complete the read-modify-write operation. In one caching convention, the updated cache line is eventually written back to the main memory after it is replaced by a higher value cache line, although the cache line may also be immediately written to the main memory or follow another caching convention. The throughput for this cache line data merge is limited by the number of pending cache line merges that can be supported by the processor chip 500/cache 512, among other factors. The described process works well when the cache line is referenced multiple times and/or when there are relatively few sub cache line granularity memory updates.
Certain computational algorithms result in significant volumes of memory updates at sub-cache line granularity. Moreover, these updates can be to random records in a large database, resulting in little or no reuse of the cache line. In this case, the computer system throughput can be limited to the number of pending merge buffers associated with the cache 512, leading to an effective main memory bandwidth utilization of only a few percent. Having processor sub-cache line granularity memory write requests bypass the caches 512 for execution by the main memory controller 510, by a process of reading the cache line from main memory, merging the write data and writing updated cache line data back to the main memory is also inefficient due to the transfer of un-needed data and commands through the bus(es) 506 to the memory subsystems 503 and associated hub devices 504. Therefore, a need exists for having sub-cache line memory updates executed efficiently and reliably in systems that employ memory hub devices 504.
BRIEF SUMMARY OF THE INVENTION
Embodiments include a memory system for storing and retrieving data for a processing system. The memory system includes a plurality of memory devices, a memory controller, one or more memory busses connected to the memory controller and a memory hub device. The memory controller receives and responds to memory access requests including memory update requests from a processor. The memory controller also generates a memory update command in response to receiving a memory update request. The memory hub device includes a first port, a second port and a control unit. The first port is in communication with the memory controller via one or more of the memory busses for transferring data and control information between the memory hub device and the memory controller. The second port is in communication with one or more of the memory devices. The control unit decodes the memory update command from the data and control information and accesses the memory devices via the second port to perform the memory update command local to the memory hub devices as a logical read-modify-write sequence.
Further embodiments include a memory subsystem for storing and retrieving data for a processing system. The memory subsystem includes a plurality of memory devices and a memory hub device. The memory hub device includes a first port, a second port and a control unit. The first port is in communication with a memory controller via one or more memory busses for transferring data and control information between the memory hub device and the memory controller. The second port is in communication with one or more of the memory devices. The control unit decodes the memory update command from the data and control information and accesses the memory devices via the second port to perform the memory update command local to the memory hub devices as a logical read-modify-write sequence.
Further embodiments include a memory hub device with a first port, a second port and a control unit. The first port is in communication with a memory controller via one or more memory busses for transferring data and control information between the memory hub device and the memory controller. The second port is in communication with one or more of the memory devices. The control unit decodes the memory update command from the data and control information and accesses the memory devices via the second port to perform the memory update command local to the memory hub device as a logical read-modify-write sequence.
Still further embodiments include a method for executing a memory command. The method includes receiving a memory update command including an address and update data from a memory controller. The memory update command is received via one or more memory busses at a memory hub device that includes two or more ports. One or more memory devices associated with the address is accessed. The memory update command is performed on the memory devices as a logical read-modify-write sequence. The memory update command is performed local to the memory hub device in response to the update data.
Other systems, methods, and/or computer program products according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, methods, and/or computer program products be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.



BRIEF DESCRIPTION OF THE DRAWINGS
Referring now to the drawings wherein like elements are numbered alike in the several FIGURES:
FIG. 1 depicts an exemplary early synchronous memory module;
FIG. 2 depicts an exemplary computer system with a filly buffered synchronous memory module that is directly connected to a memory controller;
FIG. 3 depicts an exemplary memory system, shown with a single, traditional multi-drop stub bus;
FIG. 4 depicts a filly buffered synchronous memory module and system structure, where the filly buffered synchronous memory module includes a repeater function;
FIG. 5 depicts a block diagram of multiple independent daisy-chained memory interface channels that operate in parallel to support data access requests;
FIG. 6 depicts a memory hub device;
FIG. 7 depicts a memory hub device including circuitry to perform data modification operations that may be implemented by exemplary embodiments;
FIG. 8 is a block diagram of a sequence of operations associated with sub-cache line access that may be implemented by exemplary embodiments; and
FIG. 9 is a flow diagram of a process that may be implemented by exemplary embodiments.



DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS
The high speed memory bus that interconnects memory controller(s) with one or more hub devices in a cascade interconnect system often provides a lower access bandwidth to the array of memory devices than that which is afforded by the memory devices themselves. This may be due to bus contention with other module traffic, bus speed and signaling limitations, bus communication (i.e. packet) overhead, limited bus width and other affects. Exemplary embodiments provide the means to exploit the aggregate memory device bandwidth in a system for servicing memory accesses, specifically sub-cache line memory writes or updates (i.e., sub-cache line operations). Conventional hub devices serve as conduits for memory data and control traffic associated with operations such as cache line transfers to and from memory, and exemplary embodiments extend the capability of the hub device(s) to perform specific operations on memory data, local to the memory subsystem.
As used herein, the term sub-cache line access refers to a memory access (e.g., a write operation) having a granularity smaller than the smallest unit of memory that can be transferred between the main memory and the cache. From a memory system standpoint, the data width times the burst length is ideally the same as a cache line (e.g., a data width of 8 bytes times a burst of 8 equals 64 bytes of data, which might represent an ideal memory structure to support a cache line of 64 bytes) and/or the conventional memory system access granularity (e.g., 64 bytes, 128 bytes). A memory write operation to an 8 byte data field (e.g. one-eighth of a cache line) would therefore represent a ‘sub-cache line access’, in that the 8 byte access granularity would be smaller than the smallest unit of memory (in this example, 64 bytes) that can be transferred between the main memory and the cache.
FIG. 7 illustrates a memory hub device 504 that may be implemented by exemplary embodiments. In exemplary embodiments, the hub device 504 is located in a memory subsystem, or memory module. The hub device 504 depicted in FIG. 7 is similar to the hub device 504 depicted in FIG. 6 (and performs the functions described in reference to FIG. 6), but also includes a modify pipeline 721, an improved link interface 704 and an improved memory hub control 713. The improved link interface 704 decodes a command packet received from the bus 506 and the improved memory hub control 713 further decodes the command packet to determine the operation to be completed. In exemplary embodiments, one or more commands will identify specific operations to be applied to memory data. In exemplary embodiments, the bus 506 is implemented by a unidirectional upstream bus and a unidirectional downstream bus. In alternate exemplary embodiments, the bus is implemented by a single bidirectional bus. The functions performed by the memory hub device 504 depicted in FIG. 7 may be implemented by software and/or hardware.
The following two groups of memory update commands are examples of operations that can be completed within a memory subsystem produced with an exemplary memory hub control device 504. Memory update commands that do not imply reply data from the main memory to the processor may include, but are not limited to:

    
    
        Fetch and write operand
        Fetch and ADD operand
        Fetch and SUBTRACT operand
        Fetch and logical OR with operand
        Fetch and logical AND with operand
        Fetch and logical XOR with operand
        Fetch and logical NOT with operand
        Fetch and logical CLEAR to zero
        Fetch and logical bit SHIFT LEFT (0 or 1 fill) by operand
        Fetch and logical bit SHIFT RIGHT (0 or 1 fill) by operand
        Fetch and logical bit ROTATE by operand
    
    


Additional memory update commands that do imply reply data from the main memory to the processor may include, but are not limited to:

    
    
        Fetch and ADD operand and reply with result
        Fetch and SUBTRACT operand and reply with result
        Fetch and SET with operand when clear and reply with read data
    
    


Both groups of memory update commands described above are also referred to herein as read-modify-write (RMW) commands. These RMW commands may be performed local to the hub device 504 (i.e., without requiring processor chip 500 or memory controller 510 intervention).
Referring to FIG. 7, the inclusion of an arithmetic logic unit (ALU) 717 in the modify pipeline 721 provides the means to operate on the memory read data for memory update commands such as those listed above.
Preserving data integrity through error correction and detection in the memory controller 510 is impractical when memory updates are completed in the memory hub device(s) 504, as the write data is developed local to the hub device 504, and is dependent on the read data associated with that address range. Exemplary embodiments incorporate in the memory hub device 504 an error detection and correction (EDC) check and correct block 716 to detect and correct data errors on read data based on EDC codes (also referred to as Error Correction codes (ECC)) incorporated with the read data. Further, an EDC code generation block 719 generates EDC codes for the write data. In exemplary embodiments, the EDC coding scheme is based on 8-byte data words in hub devices that support a single 8-byte wide memory device interface. In further exemplary embodiments, the EDC coding scheme is based on either 8-byte data words or 16-byte data words in hub devices 504 that support two 8-byte wide memory device interfaces. Any EDC coding algorithm may be utilized by exemplary embodiments, and several are currently known in the art. In a second mode of operation, the dataflow may selectively bypass the EDC check and correct block 716 and/or the EDC code generation block 719 when a latency advantage exists and/or when this level of data integrity is not required. In a third mode of operation, exemplary embodiments may include a parallel EDC data pipeline capable of detecting data errors late and responsively aborting a memory writeback and/or indicating error in a data reply packet and/or re-running one or more operation(s) responsive to detecting a data error late in the execution process. In addition to or instead of using EDC as a means of maximizing data integrity, other modes or combinations of modes such as parity, CRC (cyclic redundancy check), complement/re-complement, memory access re-try, etc may be utilized in the hub device, without departing from the scope of the invention.
The system is most effective when independent update command streams are directed to each hub device 504 such that each hub device 504 can have one or more independent memory update operation(s) pending to one or more independent address(es). Moreover, a commonly assigned U.S. patent application Ser. No. 11/464,503, entitled SYSTEMS AND METHODS FOR PROGRAM DIRECTED MEMORY ACCESS PATTERNS, filed on Aug. 15, 2006, provides the means for a memory system comprised of two or more memory channels to utilize one or more busses, on a cycle by cycle basis, based on access “hint” information. The referenced application provides a means by which a memory system can accommodate accesses to a subset of the available memory channels, which complements the exemplary embodiment by permitting simultaneous independent operations, such as data modification operations in a memory subsystem.
Memory update commands received from the link interface 704 will include data or an operand as data (except for operands such as a “fetch and logical clear”), and the data is stored in the write data queue 711 via data path 712, for subsequent transfer to the ALU 717. Alternative exemplary embodiments employ a separate update command data queue that is independent of the write data queue (shown as block 611 in FIG. 6). Referring to FIG. 7, new memory update commands are serviced by the memory hub control 713 to memory devices 509 as a sequence of operations that correlate to a RMW operation. If a RMW operation is not supported by a memory device technology being utilized, a sequence of read and write operations will be performed that provide the same function. In exemplary embodiments, a sub-cache line operation commences with a conventional read access to the memory devices 509, using the smallest ‘minimum burst length’ (typically 4 or 8 consecutive 8-byte transfers) supported by the memory devices 509. The read data stream from the memory devices 509 is received by the memory data interface 715 and is acted upon by the modify pipeline 721, with the updated data sent back to the memory devices 509 via memory device interface 715 as a burst write to the same address range.
Although not shown, alternative embodiments including having the data streamed through the modify pipeline 721 to the write data queue 711 (or an alternate temporary storage location), to delay or accumulate one or more write operation(s) before writing back to the memory devices 509. This method may further improve overall memory subsystem performance by grouping multiple reads and multiple write accesses to reduce the bidirectional data bus 708 turn-around overhead.
Referring to the embodiment depicted in FIG. 7, the read data stream from the memory devices 509 is received by the memory device data interface 715, and the information is passed to the EDC check and correct block 716, where the data is checked and may be corrected if one or more errors are identified. The read data is then directed to the ALU 717 and the read selector MUX 718, with the memory hub control 713 determining the correct path based on the decode of the command(s) that initiated the read operation as received by link interface 704. The read selector MUX 718 passes the updated data to the EDC code generation block 719. The updated data includes the output of the EDC check and correct block 716 merged with the sub-cache line data from the write data queue 711. Alternatively, the updated data includes the data from the EDC check and correct block 716 and the data from the write data queue 711, logically or arithmetically operated on by ALU 717 (based on the operand identified by memory hub control 713). At the EDC code generation block 719, a new series of check bits are developed based on the write data, and merged with this data consistent with the selected EDC algorithm. The resulting combination of data and check bits (heretofore referred to as ‘data’) is then coupled to the write data selector MUX 720, where it is then forwarded, under the control of memory hub control 713, to the memory device data interface 715 for subsequent transfer to the one or more memory devices 509.
As further clarification, burst data transfers other than those targeted for update, bypass the ALU 717 via read selector MUX 718 to have ECC check bits generated by the EDC code generation block 719. Update command data from the write data queue 711 is provided to the ALU 717 and, at the same relative time, specific read data targeted for update is provided to the ALU 717, where the selected memory read data is logically or arithmetically operated on with an update command and an associated data operand from memory hub control 713. As suggested by the exemplary embodiments, the sequence of operations and the specific operations themselves may be implemented in different sequences or combinations, with some functions bypassed in total, based on the application requirements, while still completing local data modification for sub-cache line address ranges.
FIG. 8 illustrates a sequence of operations associated with sub-cache line accesses using memory devices operating in a ‘burst 4’ mode (with two data transfers per cycle). The operations shown in FIG. 8 relate to activity on the memory address and control bus 714 (identified as “ary0 A”) and the memory device data bus 708 (identified as “ary0 D”), in response to four memory update commands (identified as 0 through 3). In this example, when servicing memory update commands, the memory hub control 713 maintains the DRAM row open or activated (denoted as “Rx”) throughout the RMW sequence—hence no closing (e.g. ‘precharge’) and re-opening of the memory device row is shown. For example; R0 in cycle 1 (as shown in row “ary 0 A”) activates the row address acted upon by the read associated with update command “0”, Cr0 in cycle 5 initiates the read for the same update command “0” with the column address, and the memory device responds with the 2 transfers of data (as shown in row “ary 0 D” as Dr0) in each of cycles 10 and 11 (consistent with a burst of 4 operation). The read data is processed through the memory data interface 715 and modify pipeline 721 during cycles 11 through 14, and the modified data is written back to the memory device(s) in cycles 15 and 16 (shown in row “ary 0 D” as Dw0). Other memory device accesses may occur concurrently or otherwise overlap with a scheduled RMW, but only when these operations are to device addresses that are not affected by those operations associated with the first scheduled read-modify-write operation(s). The subsequent operations (shown as “1”, “2” and “3”) are also included in the figure as overlapping operations, are illustrative of the memory device bus activity that could occur in normal operation, and following the same naming convention as the operation that is described.
FIG. 9 depicts a process flow for servicing sub-cache line RMW access requests at hub devices 504 that may be implemented by exemplary embodiments. As described previously, all the processing described in reference to FIG. 9 is performed within the memory subsystem by the memory hub device 504. At block 902 in FIG. 9, a memory update command is received at a hub device 504. As described above, the link interface 704 receives the memory update command via the bus 506 and stores the write data (which may also be an operand as data) in the write data queue 711 via the internal bus 712. At block 904 in FIG. 9, data at the address specified by the command is read. The memory hub control 713 requests the data from the memory devices 509 on the memory address and control bus 714. The data is received from the memory device data bus 708 into the memory device data interface 715. At block 906 in FIG. 9, a check is performed to determine that the read data is valid data. In exemplary embodiments, the read data is transmitted along an internal bus 705 to the EDC check and correct block 716. If the data is not valid, then block 908 in FIG. 9 is performed and the data is corrected with processing continuing at block 910 in FIG. 9 and/or the error is reported.
If the data is valid, as determined at block 906 in FIG. 9 or upon correction of the data in block 908, then block 910 in FIG. 9 is performed to modify the data. If the RMW command is a write command with no data modification (as determined by the memory hub control 713), then the data exits the EDC check and correct block 716 and directly enters the read selector MUX 718 along with the data in the write data queue 711. If the RMW command does require data modification (as determined by the memory hub control 713), then the data exits the EDC check and correct block 716 and enters the ALU 717 to perform the modification. The modified data is input to the read selector MUX 718. At block 912 in FIG. 9, the error correction bits are added to the data by the EDC code generation block 719. The data is then written to the memory devices 509 via the memory device data interface 715 at block 914 in FIG. 9. As described previously, the data being written is either the data modified by the ALU 717 with error correction bits added, or data from the write data queue 711 with error correction bits added. In this manner, the RMW command is contained within the memory hub device 504.
In alternate exemplary embodiments, the EDC check and correct block 716 generates an error alert that is transmitted to the memory controller 510 to alert the memory controller 510 of the error. In alternate exemplary embodiments, the error alert is transmitted to a service processor or other error reporting/recovery circuitry. In addition to or instead of reporting an error alert, the memory hub device 504 may generate a completion alert that is transmitted to the memory controller 510 to communicate the completion of the RMW, or memory update command. The transmission of the error alert and/or completion alert may be via the memory bus 506 and/or via another bus that communicates between the hub device 504 and the memory controller 510 and/or the appropriate system logic circuitry.
Memory subsystems, where the hub device 504 is located, may be implemented by a variety of technologies including a DIMM, a single in-line memory module (SIMM) and/or other memory module or card structures. In general, a DIMM refers to a small circuit board which is comprised primarily of random access memory (RAM) integrated circuits or die on one or both sides with signal and/or power pins on both sides of the board. This can be contrasted to a SIMM which is a small circuit board or substrate composed primarily of RAM integrated circuits or die on one or both sides and single row of pins along one long edge. The memory subsystems utilized by exemplary embodiments may have pincounts ranging from 100 pins to over 300 pins.
In exemplary embodiments, the memory bus 506 is constructed using multi-drop connections to the memory subsystems and/or using point-to-point connections. The downstream portion of the controller interface (or memory bus 506), referred to as the downstream bus, may include command, address, data and other operational, initialization or status information being sent to the memory modules. Each memory module, e.g., via the link interface 704, may simply forward the information to the subsequent (or downstream) module(s) via bypass circuitry; receive, interpret and re-drive the information if it is determined to be targeting a downstream memory module; re-drive some or all of the information without first interpreting the information to determine the intended recipient; or perform a subset or combination of these options.
The upstream portion of the memory bus 506, referred to as the upstream bus, returns requested read data and/or error, status or other operational information, and this information may be forwarded to the subsequent memory module(s) via bypass circuitry; be received, interpreted and re-driven if it is determined to be targeting an upstream memory module and/or memory controller in the processor complex; be re-driven in part or in total without first interpreting the information to determine the intended recipient; or perform a subset or combination of these options. In exemplary embodiments, the memory bus 506 is implemented as two unidirectional busses 506, in other embodiments the memory bus 506 is implemented as a single bidirectional bus 506.
Although not shown in FIG. 7, the hub device 504 may also include a separate bus, such as a ‘presence detect’ bus, an I2C bus and/or an SMBus which is used for one or more purposes including the determination of the memory subsystem attributes (generally after power-up), the reporting of fault or status information to the system, such as that defined in block 908, the configuration of the memory subsystem(s) after power-up or during normal operation or other purposes. Depending on the bus characteristics, this bus might also provide a means by which the valid completion of operations could be reported by the memory subsystem(s) to the memory controller(s), or the identification of failures occurring during the execution of the main memory controller requests.
As used herein the term “buffer” or “buffer device” refers to a temporary storage unit (as in a computer), especially one that accepts information at one rate and delivers it another. In exemplary embodiments, a buffer is an electronic device that provides compatibility between two signals (e.g., changing voltage levels or current capability). The term “hub” is sometimes used interchangeably with the term “buffer.” A hub is a device containing multiple ports that is connected to several other devices. A port is a portion of an interface that serves a congruent I/O functionality (e.g., a port may be utilized for sending and receiving data, address, and control information over one of the point-to-point links, or busses). A hub may be a central device that connects several systems, subsystems, or networks together. A passive hub may simply forward messages, while an active hub, or repeater, amplifies and refreshes the stream of data which otherwise would deteriorate over a distance. The term hub device 504, as used herein, refers to a hub chip that includes logic (hardware and/or software) for performing memory functions.
Also as used herein, the term “bus” refers to one of the sets of conductors (e.g., wires, and printed circuit board traces or connections in an integrated circuit) connecting two or more functional units in a computer. The data bus, address bus and control signals, despite their names, constitute a single bus since each are often useless without the others. A bus may include a plurality of signal lines, each signal line having two or more connection points that form a main transmission path that electrically connects two or more transceivers, transmitters and/or receivers. The term “bus” is contrasted with the term “channel” which is often used to describe the function of a “port” as related to a memory controller in a memory system, and which may include one or more busses or sets of busses. The term “channel” as used herein refers to a port on a memory controller. Note that this term is often used in conjunction with I/O or other peripheral equipment, however the term channel has been adopted by some to describe the interface between a processor or memory controller and one of one or more memory subsystem(s).
Further, as used herein, the term “daisy chain” refers to a bus wiring structure in which, for example, device A is wired to device B, device B is wired to device C, etc. The last device is typically wired to a resistor or terminator. All devices may receive identical signals or, in contrast to a simple bus, each device may modify one or more signals before passing them on. A “cascade” or cascade interconnect' as used herein refers to a succession of stages or units or a collection of interconnected networking devices, typically hubs, in which the hubs operate as a logical repeater, further permitting merging data to be concentrated into the existing data stream. Also as used herein, the term “point-to-point” bus and/or link refers to one or a plurality of signal lines that may each include one or more terminators. In a point-to-point bus and/or link, each signal line has two transceiver connection points, with each transceiver connection point coupled to transmitter circuitry, receiver circuitry or transceiver circuitry. A signal line refers to one or more electrical conductors or optical carriers, generally configured as a single carrier or as two or more carriers, in a twisted, parallel, or concentric arrangement, used to transport at least one logical signal.
Memory devices are generally defined as integrated circuits that are composed primarily of memory (storage) cells, such as DRAMs (Dynamic Random Access Memories), SRAMs (Static Random Access Memories), FeRAMs (Ferro-Electric RAMs), MRAMs (Magnetic Random Access Memories), Flash Memory and other forms of random access and related memories that store information in the form of electrical, optical, magnetic, biological or other means. Dynamic memory device types may include asynchronous memory devices such as FPM DRAMs (Fast Page Mode Dynamic Random Access Memories), EDO (Extended Data Out) DRAMs, BEDO (Burst EDO) DRAMs, SDR (Single Data Rate) Synchronous DRAMs, DDR (Double Data Rate) Synchronous DRAMs or any of the expected follow-on devices such as DDR2, DDR3, DDR4 and related technologies such as Graphics RAMs, Video RAMs, LP RAM (Low Power DRAMs) which are often based on the fundamental functions, features and/or interfaces found on related DRAMs.
Memory devices may be utilized in the form of chips (die) and/or single or multi-chip packages of various types and configurations. In multi-chip packages, the memory devices may be packaged with other device types such as other memory devices, logic chips, analog devices and programmable devices, and may also include passive devices such as resistors, capacitors and inductors. These packages may include an integrated heat sink or other cooling enhancements, which may be further attached to the immediate carrier or another nearby carrier or heat removal system.
Module support devices (such as buffers, hubs, hub devices, hub logic chips, registers, PLL's, DLL's, non-volatile memory, etc.) may be comprised of multiple separate chips and/or components, may be combined as multiple separate chips onto one or more substrates, may be combined onto a single package or even integrated onto a single device—based on technology, power, space, cost and other tradeoffs. In addition, one or more of the various passive devices such as resistors, capacitors may be integrated into the support chip packages, or into the substrate, board or raw card itself, based on technology, power, space, cost and other tradeoffs. These packages may include an integrated heat sink or other cooling enhancements, which may be further attached to the immediate carrier or another nearby carrier or heat removal system.
Memory devices, hub devices, buffers, registers, clock devices, passives and other memory support devices and/or components may be attached to the memory subsystem, via various methods including solder interconnects, conductive adhesives, socket structures, pressure contacts and other methods which enable communication between the two or more devices via electrical, optical or alternate means.
The memory subsystem(s) may be connected to the memory system, processor complex, computer system or other system environment via one or more methods such as soldered interconnects, connectors, pressure contacts, conductive adhesives, optical interconnects and other communication and power delivery methods. Connector systems may include mating connectors (male/female), conductive contacts and/or pins on one carrier mating with a male or female connector, optical connections, pressure contacts (often in conjunction with a retaining mechanism) and/or one or more of various other communication and power delivery methods. The interconnection(s) may be disposed along one or more edges of the memory assembly and/or placed a distance from an edge of the memory subsystem depending on such application requirements as ease-of-upgrade/repair, available space/volume, heat transfer, component size and shape and other related physical, electrical, optical, visual/physical access, etc.
As used herein, the term memory subsystem refers to, but is not limited to: one or more memory devices; one or more memory devices and associated interface and/or timing/control circuitry; and/or one or more memory devices in conjunction with a memory buffer, hub, and/or switch. The term memory subsystem may also refer to one or more memory devices, in addition to any associated interface and/or timing/control circuitry and/or a memory buffer, hub device or switch, assembled into a substrate, a card, a module or related assembly, which may also include a connector or similar means of electrically attaching the memory subsystem with other circuitry.
Additional functions that may reside local to the memory subsystem include write and/or read buffers, one or more levels of memory cache, local pre-fetch logic, data encryption/decryption, compression/decompression, protocol translation, command prioritization logic, voltage and/or level translation, error detection and/or correction circuitry, data scrubbing, local power management circuitry and/or reporting, operational and/or status registers, initialization circuitry, performance monitoring and/or control, one or more co-processors, search engine(s) and other functions that may have previously resided in other memory subsystems. By placing a function local to the memory subsystem, added performance may be obtained as related to the specific function, often while making use of unused circuits within the subsystem.
Memory subsystem support device(s) may be directly attached to the same substrate or assembly onto which the memory device(s) 509 are attached, or may be mounted to a separate interposer or substrate also produced using one or more of various plastic, silicon, ceramic or other materials which include electrical, optical or other communication paths to functionally interconnect the support device(s) to the memory device(s) 509 and/or to other elements of the memory or computer system.
Information transfers along a bus, channel, link or other naming convention applied to an interconnection method may be completed using one or more of many signaling options. These signaling options may include such methods as single-ended, differential, optical or other approaches, with electrical signaling further including such methods as voltage or current signaling using either single or multi-level approaches. Signals may also be modulated using such methods as time or frequency, non-return to zero, phase shift keying, amplitude modulation and others. Voltage levels are expected to continue to decrease, with 1.5V, 1.2V, 1V and lower signal voltages expected consistent with (but often independent of) the reduced power supply voltages required for the operation of the associated integrated circuits themselves.
One or more clocking methods may be utilized within the memory subsystem and the memory system itself, including global clocking, source-synchronous clocking, encoded clocking or combinations of these and other methods. The clock signaling may be identical to that of the signal lines themselves, or may utilize one of the listed or alternate methods that is more conducive to the planned clock frequency(ies), and the number of clocks planned within the various subsystems. A single clock may be associated with all communication to and from the memory, as well as all clocked functions within the memory subsystem, or multiple clocks may be sourced using one or more methods such as those described earlier. When multiple clocks are used, the functions within the memory subsystem may be associated with a clock that is uniquely sourced to the subsystem, or may be based on a clock that is derived from the clock related to the information being transferred to and from the memory subsystem (such as that associated with an encoded clock). Alternately, a unique clock may be used for the information transferred to the memory subsystem, and a separate clock for information sourced from one (or more) of the memory subsystems. The clocks themselves may operate at the same or frequency multiple of the communication or functional frequency, and may be edge-aligned, center-aligned or placed in an alternate timing position relative to the data, command or address information.
Information passing to the memory subsystem(s) will generally be composed of address, command and data, as well as other signals generally associated with requesting or reporting status or error conditions, resetting the memory, completing memory or logic initialization and other functional, configuration or related information. Information passing from the memory subsystem(s) may include any or all of the information passing to the memory subsystem(s), however generally will not include address and command information. This information may be communicated using communication methods that may be consistent with normal memory device interface specifications (generally parallel in nature), the information may be encoded into a ‘packet’ structure, which may be consistent with future memory interfaces or simply developed to increase communication bandwidth and/or enable the subsystem to operate independently of the memory technology by converting the received information into the format required by the receiving device(s).
Initialization of the memory subsystem may be completed via one or more methods, based on the available interface busses, the desired initialization speed, available space, cost/complexity objectives, subsystem interconnect structures, the use of alternate processors (such as a service processor) which may be used for this and other purposes, etc. In one embodiment, the high speed bus may be used to complete the initialization of the memory subsystem(s), generally by first completing a training process to establish reliable communication, then by interrogation of the attribute or ‘presence detect’ data associated the various components and/or characteristics associated with that subsystem, and ultimately by programming the appropriate devices with information associated with the intended operation within that system. In a cascaded system, communication with the first memory subsystem would generally be established, followed by subsequent (downstream) subsystems in the sequence consistent with their position along the cascade interconnect bus.
A second initialization method would include one in which the high speed bus is operated at one frequency during the initialization process, then at a second (and generally higher) frequency during the normal operation. In this embodiment, it may be possible to initiate communication with all of the memory subsystems on the cascade interconnect bus prior to completing the interrogation and/or programming of each subsystem, due to the increased timing margins associated with the lower frequency operation.
A third initialization method might include operation of the cascade interconnect bus at the normal operational frequency(ies), while increasing the number of cycles associated with each address, command and/or data transfer. In one embodiment, a packet containing all or a portion of the address, command and/or data information might be transferred in one clock cycle during normal operation, but the same amount and/or type of information might be transferred over two, three or more cycles during initialization. This initialization process would therefore be using a form of ‘slow’ commands, rather than ‘normal’ commands, and this mode might be automatically entered at some point after power-up and/or re-start by each of the subsystems and the memory controller by way of POR (power-on-reset) logic included in each of these subsystems.
A fourth initialization method might utilize a distinct bus, such as a presence detect bus (such as the one defined in U.S. Pat. No. 5,513,135 to Dell et al., of common assignment herewith), an I2C bus (such as defined in published JEDEC standards such as the 168 Pin DIMM family in publication 21-C revision 7R8) and/or the SMBUS, which has been widely utilized and documented in computer systems using such memory modules. This bus might be connected to one or more modules within a memory system in a daisy chain/cascade interconnect, multi-drop or alternate structure, providing an independent means of interrogating memory subsystems, programming each of the one or more memory subsystems to operate within the overall system environment, and adjusting the operational characteristics at other times during the normal system operation based on performance, thermal, configuration or other changes desired or detected in the system environment.
Other methods for initialization can also be used, in conjunction with or independent of those listed. The use of a separate bus, such as described in the fourth embodiment above, also offers the advantage of providing an independent means for both initialization and uses other than initialization (such as described in U.S. Pat. No. 6,381,685 to Dell et al., of common assignment herewith) including changes to the subsystem operational characteristics on-the-fly and for the reporting of and response to operational subsystem information such as utilization, temperature data, failure information or other purposes.
With improvements in lithography, better process controls, the use of materials with lower resistance, increased field sizes and other semiconductor processing improvements, increased device circuit density (often in conjunction with increased die sizes) will help facilitate increased function on integrated devices as well as the integration of functions previously implemented on separate devices. This integration will serve to improve overall performance of the intended function, as well as promote increased storage density, reduced power, reduced space requirements, lower cost and other manufacturer and customer benefits. This integration is a natural evolutionary process, and may result in the need for structural changes to the fundamental building blocks associated with systems.
The integrity of the communication path, the data storage contents and all functional operations associated with each element of a memory system or subsystem can be assured, to a high degree, with the use of one or more fault detection and/or correction methods. Any or all of the various elements may include error detection and/or correction methods such as CRC (Cyclic Redundancy Code), EDC (Error Detection and Correction), parity or other encoding/decoding methods suited for this purpose. Further reliability enhancements may include operation re-try (to overcome intermittent faults such as those associated with the transfer of information), the use of one or more alternate or replacement communication paths to replace failing paths and/or lines, complement-re-complement techniques or alternate methods used in computer, communication and related systems.
The use of bus termination, on busses as simple as point-to-point links or as complex as multi-drop structures, is becoming more common consistent with increased performance demands. A wide variety of termination methods can be identified and/or considered, and include the use of such devices as resistors, capacitors, inductors or any combination thereof, with these devices connected between the signal line and a power supply voltage or ground, a termination voltage or another signal. The termination device(s) may be part of a passive or active termination structure, and may reside in one or more positions along one or more of the signal lines, and/or as part of the transmitter and/or receiving device(s). The terminator may be selected to match the impedance of the transmission line, or selected via an alternate approach to maximize the useable frequency, operating margins and related attributes within the cost, space, power and other constraints.
Technical effects and benefits of exemplary embodiments include the ability to perform memory update commands locally in the memory subsystem (or hub device in the memory subsystem) without requiring information transfer to the memory controller. This will result in improved overall performance because the commands are serviced locally. In addition, this will result in less traffic on the memory bus(ses) between the hub device and the controller.
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 memory system for storing and retrieving data for a processing system, the memory system comprising:
a plurality of memory devices;
a memory controller for receiving and responding to memory access requests including memory update requests from a processor and for generating a memory update command in response to receiving a memory update request;
one or more memory busses connected to the memory controller; and
a memory hub device comprising:
a first port in communication with the memory controller via one or more of the memory busses for transferring data and control information between the memory hub device and the memory controller;
a second port in communication with one or more of the memory devices; and
a control unit for decoding the memory update command from the data and control information and for accessing the memory devices via the second port to perform the memory update command local to the memory hub device as a logical read-modify-write sequence.

2. The memory system of claim 1, wherein the memory update command is a sub-cache line operation.

3. The memory system of claim 1, wherein the hub device further comprises one or more arithmetic logic units (ALUs) for altering memory data responsive to the memory update command from the memory controller.

4. The memory system of claim 3, wherein the hub device further comprises an error correction and detection (EDC) unit for detecting data errors in selected read data and for generating new error correction codes for data generated by the ALU.

5. The memory system of claim 4, wherein the EDC unit includes a software interface for independently disabling one or more of the detecting and the generating.

6. The memory system of claim 1, wherein the memory hub device further comprises a write data queue for holding data received at the memory hub device to be later written to the memory devices.

7. The memory system of claim 6, wherein the memory hub device stores write data associated with the read-modify-write sequence in the write data queue.

8. A memory subsystem for storing and retrieving data for a processing system, the memory subsystem comprising:
a plurality of memory devices; and
a memory hub device comprising:
a first port in communication with a memory controller via one or more memory busses for transferring data and control information between the memory hub device and the memory controller;
a second port in communication with one or more of the memory devices; and
a control unit for decoding the memory update command from the data and control information and for accessing the memory devices via the second port to perform the memory update command local to the memory hub device as a logical read-modify-write sequence.

9. The memory subsystem system of claim 8, wherein the memory update command is a sub-cache line operation.

10. The memory subsystem of claim 8, wherein the hub device further comprises one or more arithmetic logic units (ALUs) for altering memory data responsive to the memory update command from the memory controller.

11. The memory subsystem of claim 10, wherein the hub device further comprises an error correction and detection (EDC) unit for detecting data errors in selected read data and for generating new error correction codes for data generated by the ALU.

12. The memory subsystem of claim 11, wherein the EDC unit includes a software interface for independently disabling one or more of the detecting and the generating.

13. The memory subsystem of claim 10, wherein the memory hub device further comprises a write data queue for holding data received at the memory hub device to be later written to the memory devices.

14. The memory subsystem of claim 13, wherein the memory hub device stores write data associated with the read-modify-write sequence in the write data queue.

15. A memory hub device comprising:
a first port in communication with a memory controller via one or more memory busses for transferring data and control information between the memory hub device and the memory controller;
a second port in communication with one or more memory devices; and
a control unit for decoding the memory update command from the data and control information and for accessing the memory devices via the second port to perform the memory update command local to the memory hub device as a logical read-modify-write sequence.

16. The memory hub device of claim 15, wherein the memory update command is a sub-cache line operation.

17. The memory hub device of claim 15, further comprising one or more arithmetic logic units (ALUs) for altering memory data responsive to the memory update command from the memory controller.

18. The memory hub device of claim 17, further comprising an error correction and detection (EDC) unit for detecting data errors in selected read data and for generating new error correction codes for data generated by the ALU.

19. The memory hub device of claim 18, wherein the EDC unit includes a software interface for independently disabling one or more of the detecting and the generating.

20. The memory hub device of claim 18 wherein the memory hub device generates an error alert in response to one or more of the EDC unit detecting an error and the memory hub device detecting an update error.

21. The memory hub device of claim 15, further comprising a write data queue for holding data received at the memory hub device to be later written to the memory devices.

22. The memory hub device of claim 21, wherein the memory hub device stores write data associated with the read-modify-write sequence in the write data queue.

23. The memory hub device of claim 15 wherein the memory hub device generates a completion alert in response to the memory update command being completed.

24. A method for executing a memory command, the method comprising:
receiving a memory update command including an address and update data from a memory controller, the receiving via one or more memory busses at a memory hub device that includes two or more ports;
accessing one or more memory devices associated with the address; and
performing the memory update command on the memory devices as a logical read-modify-write sequence, the performing responsive to the update data and the performing local to the memory hub device.

25. The method of claim 24 wherein the memory update command is a sub-cache line operation.

26. The method of claim 24 wherein the performing includes:
reading current data associated with the address from the one or more memory devices;
modifying the current data in response to the update data and the memory update command resulting in modified data; and
writing the modified data to the one or more memory devices at the address.

27. The method of claim 26 wherein the modifying is performed by one or more ALUs.

28. The method of claim 26 wherein the modifying includes replacing the current data with the update data.

29. The method of claim 26 wherein the reading includes using an EDC unit to detect any errors in the current data.

30. The method of claim 29 wherein if the EDC unit detects any errors then the reading further includes one or more of using the EDC unit to correct the errors and generating an error alert.

31. The method of claim 26 the modifying writing includes using an EDC unit to generate new error correction codes for the modified data.

32. The method of claim 26 wherein the writing includes holding the modified data in a write data queue to be written later to the one or more memory devices.

33. The method of claim 26 further comprising generating a completion alert in response to the memory update command being completed by the hub device.