US 7,636,813 B2Grant
Systems and methods for providing remote pre-fetch buffers
Issue Date:2009-12-22
•17 Claims
•10 Drawing Sheets
Abstract
Systems and methods for providing remote pre-fetch buffers. The systems include a computer memory system with a memory controller, one or more memory busses connected to the memory controller, and at least one memory subsystem in communication with the memory controller via the memory busses. The memory controller generates, receives and responds to memory access requests including unsolicited data transfers. The memory subsystem includes one or more memory devices and logic to initiate an unsolicited data transfer to the memory controller based on analysis performed at the memory subsystem of prior memory access requests received by the memory subsystem.
Metadata
Assignee
- International Business Machines Corporation
Inventor
- Robert B. Tremaine
Application Information
Application Number:US 11/419,586
Filing Date:2006-05-22
Priority Date:2006-05-22
Art Unit:2186
Classifications
IPC:
G06F13/18G06F13/374
Patent Drawings (10 sheets)
Description
Background of the Invention
[0001] This invention relates generally to computer memory, and more particularly to systems and methods for providing remote pre-fetch buffers.
[0002] 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).
[0003] 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-between-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).
[0004] 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).
[0005] 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.
[0006] Relative to U.S. Pat. Nos. 5,513,135, 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.
[0007] 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.
[0008] 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.
[0009] Contemporary computing systems may employ hub chip based memory systems, where memory devices (typically DRAM) are connected to memory hub devices. The memory hub devices are interconnected to the system memory controller(s) via a network of communication channels. To facilitate high frequency signaling, the channels are generally comprised of one or more unidirectional outputs (downstream) and a unidirectional input (upstream) point-to-point links. Processing and/or input/output (I/O) requests (including address, read/write indication and/or any other attributes) to access the system memory (referred to as access requests) are serviced by the system memory controller(s). The memory controller translates and regulates the access requests. The memory controller schedules and prioritizes the requests to the available memory banks for optimal system performance. The requests are specifically encoded according to the channel protocol (or associated interface protocol) and transmitted to the selected memory hub devices via the downstream link(s). Write requests include data associated with the write request, but not necessarily sent in the same packet. Read requests imply an expected data reply that will be transferred back to the memory controller via the one or more subsequent upstream packets. The targeted hub device(s) translate received requests and responsively control the attached memory devices to store write data from the hub, or provide read data to the hub.
[0010] The memory controller data read access latency can be mitigated by having a pre-fetch buffer associated with the memory controller. A pre-fetch buffer generally consists of a small associative cache, with one or more logical entries for storing data, associated address information, and other attributes. The memory controller can autonomously speculatively read and/or responsively read data from the memory devices for the purpose of storing the data into the pre-fetch buffer for lowest latency to anticipated future requests.
[0011] Hub based memory systems that employ pre-fetch buffers within a hub device to mitigate the latency associated with directly accessing the memory devices have been described (see, for example, U.S. Publication Number US2004/0260909 to Lee, et al.). However, this scheme incurs significant latency associated with the memory controller communicating with the hub device(s) to reference pre-fetch data stored within the hub. Having a pre-fetch data cache in the memory controller mitigates the access latency associated with implementing such buffers in the remote hub devices. However, both of these techniques require the use of critical output and input channel resources to transport data from the memory devices to the pre-fetch buffers, often during periods of high contention for these resources. Therefore, a need exists for a more efficient hub-based memory system to improve computing performance through lower memory latency and higher memory throughput.
Brief Summary of the Invention
[0012] Embodiments include a computer memory system with a memory controller, one or more memory busses connected to the memory controller, and at least one memory subsystem in communication with the memory controller via the memory busses. The memory controller generates, receives and responds to memory access requests including unsolicited data transfers. The memory subsystem includes one or more memory devices and logic to initiate an unsolicited data transfer to the memory controller based on analysis performed at the memory subsystem of prior memory access requests received by the memory subsystem.
[0013] Embodiments also include a computer memory subsystem including pre-fetch logic and a hub device. The pre-fetch logic performs an analysis of prior memory access requests to one or more memory devices in communication with the memory subsystem. The pre-fetch logic also initiates an unsolicited data read to one or more of the memory devices based on results of the analysis. The hub device is in communication with a memory bus for initiating an unsolicited data transfer to a memory controller. The unsolicited data transfer includes data returned by the unsolicited data read.
[0014] Embodiments also include a memory controller for generating, receiving, and responding to memory access requests. The memory controller includes a local pre-fetch data cache and unsolicited data transfer logic for facilitating processing of unsolicited data transfers from a memory subsystem. The processing includes receiving a data packet and identifying the data packet as an unsolicited data packet. The unsolicited data packet includes data from an address range. The processing also includes verifying that the data at the address range has not been overwritten by a subsequent write command to the address range. The contents of the unsolicited data packet are stored in the local pre-fetch data cache in response to verifying that the data at the address range has not been overwritten by a subsequent write command to the address range.
[0015] Embodiments further include a method for receiving and responding to memory access requests including receiving a data packet at a memory controller. The data packet is identified as being an unsolicited data packet and includes an address range. It is verified that the data at the address range has not been overwritten by a subsequent write command to the address range. The contents of the unsolicited data packet are stored in a local pre-fetch data cache in response to verifying that the data at the address range has not been overwritten by a subsequent write command to the address range.
[0016] Embodiments further include a method of driving unsolicited data packets in a memory system including analyzing prior memory access requests to one or more memory devices, the analyzing performed at a memory module. A data read command is initiated at an address range on one or more of the memory devices based on results of the analyzing. An unsolicited data packet is transmitted to a memory controller when an upstream bus is idle. The unsolicited data packet includes data returned by the data read command.
[0017] 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
[0018] Referring now to the drawings wherein like elements are numbered alike in the several FIGURES:
[0019] FIG. 1 depicts an exemplary early synchronous memory module;
[0020] FIG. 2 depicts an exemplary computer system with a fully buffered synchronous memory module that is directly connected to a memory controller;
[0021] FIG. 3 depicts an exemplary memory system, shown with a single, traditional multi-drop stub bus;
[0022] FIG. 4 depicts a fully buffered synchronous memory module and system structure, where the fully buffered synchronous memory module includes a repeater function;
[0023] FIG. 5 depicts a block diagram of multiple independent daisy-chained memory interface channels that operate in parallel to support data access requests;
[0024] FIG. 6 depicts a block diagram of multiple independent daisy-chained memory interface channels that operate in parallel to support data access requests;
[0025] FIG. 7 depicts a memory system having one or more memory channels and memory controllers interconnected by one or more cascade interconnect buses that may be implemented by exemplary embodiments;
[0026] FIG. 8 is a block diagram of a memory system that may be implemented by exemplary embodiments;
[0027] FIG. 9 is a process flow for operations performed at a hub device following the pre-fetching of unsolicited data that may be implemented by exemplary embodiments;
[0028] FIG. 10 is a process flow for operations performed at a memory controller following the receipt of an unsolicited read packet from a hub chip that may be implemented by exemplary embodiments; and
[0029] FIG. 11 depicts a packet structure that may be implemented by exemplary embodiments.
Detailed Description of Exemplary Embodiments
[0030] Exemplary embodiments include a computer memory system that includes one or more memory hub devices, with each hub device being connected to one or more memory devices. A memory controller directs requests to access the memory devices via channel(s) interconnecting the memory controller and the hub devices. Each hub device can pre-fetch data and send it to the memory controller as an unsolicited “read” reply. In exemplary embodiments, the sending of the pre-fetch data occurs on the channel during idle periods. The memory controller maintains a local set of “pre-fetch” data buffers (data cache) within the controller for storing the received pre-fetch data. Memory access requests are first compared to the local pre-fetch buffer contents, and are serviced directly from the local pre-fetch buffer when the address is valid, precluding the need to utilize the memory devices, hub devices and/or channels to access the data.
[0031] Exemplary embodiments include a computing system with a processor(s) and an I/O unit(s) (e.g., requestors) interconnected to a memory system that contains a memory controller and memory devices. The computer memory system includes a physical memory array with a plurality of memory devices for storing data and instructions. These memory devices may be connected directly to the memory controller and/or indirectly coupled to the memory controller through hub devices. In exemplary embodiments, the hub-based computer memory system has memory devices attached to a communication hub device that is connected to a memory control device (e.g., a memory controller). The hub device may be connected to the memory controller through a multi-drop or point-to-point bus structure (which may further include a cascade connection to one or more additional hubs). Memory access requests are transmitted by the memory controller through the bus structure to the selected hub(s). In response to receiving the memory access requests, the hub device translates the memory access requests to control the memory devices to store write data from the hub device or to provide read data to the hub device. Read data is encoded into one or more communication packet(s) and transmitted through the bus(ses) to the memory controller.
[0032] In exemplary embodiments, a pre-fetch data cache is contained within the memory controller, and/or may be logically partitioned from the cache hierarchy between the requestor(s) and the memory controller. The memory controller can autonomously (self-initiate accesses, without direction from the processor or another system element), speculatively (initiate an access based on a historical accesses and in response to a local algorithm) and/or responsively read data from the memory devices for the purpose of storing the data into the pre-fetch data cache for lowest latency to anticipated future requests. In any case, there is an implied data reply from the hub device with the data associated with the read request.
[0033] Exemplary embodiments include a new network packet and associated protocol for having an unsolicited data packet from the hub device received at the memory controller. An unsolicited data packet refers to a data packet that is not associated with a read request from the memory controller (i.e., is not a “solicited” data packet). An unsolicited data packet is used by the hub device to forward unsolicited pre-fetch data to the pre-fetch data cache in the memory controller.
[0034] FIG. 5 depicts a contemporary system composed of two processors 502 which share a common memory controller 504. The common memory controller is integrated into a “north bridge chip” 506. In the configuration depicted in FIG. 5 , multiple independent daisy-chained memory interface busses 508 are logically aggregated together to operate in unison to support a single independent access request at a higher bandwidth with data and error detection/correction information distributed or “striped” across the parallel busses and associated devices. The memory controller 504 attaches to four narrow/high speed point-to-point memory busses 508, with each bus 508 connecting one of the several unique memory controller interface channels to a daisy-chained memory subsystem 510 (or memory module) which includes at least a hub device and one or more memory devices. Some systems further enable operations when a subset of the memory busses 508 are populated with memory subsystems 510. In this case, the one or more populated memory busses 508 may operate in unison to support a single access request.
[0035] FIG. 6 depicts a contemporary system composed of an integrated processor chip 602, which contains one or more processor elements and an integrated memory controller 504. The operation of the system depicted in FIG. 6 is fundamentally identical to that of FIG. 5 , with the integrated processor chip 602 in FIG. 6 representing the two processors 502 and the north bridge chip 506 in FIG. 5 .
[0036] In alternate exemplary embodiments, the memory controller(s) 504 may be integrated together with one or more processor chips and supporting logic, packaged in a discrete chip (commonly called a “northbridge” chip), included in a multi-chip carrier with the one or more processors and/or supporting logic, or packaged in various alternative forms that best match the application/environment. Any of these solutions may or may not employ one or more narrow/high speed links to connect to one or more hub chips and/or memory devices.
[0037] Exemplary embodiments apply to memory systems constructed of one or more memory subsystems, generally in the form of memory modules with hub logic chips, or buffer devices, which are connected to a processor complex by a cascade interconnect bus 706 as depicted in FIG. 7 . In alternate exemplary embodiments, the memory modules 710 (also referred to as memory subsystems due to the inclusion of memory devices 716 and associated memory interface circuitry, in for example a hub logic chip 708) are connected to the processor complex 702 by one or more busses 706. The memory modules 710 depicted in FIG. 7 contain both a hub logic chip 708 that contains remote prefetch logic and a first interface to the memory controller 704 in the processor complex 702 (containing one or more processors) via a cascade-interconnect memory bus 706 (shown in the exemplary embodiment as including an upstream bus and a downstream bus). The memory modules 710 also include one or more memory devices 716 that are connected to the hub logic chip 708 via a second interface. A third interface may also exist on the hub logic chip 708, especially in the case of a cascade interconnect bus 706, to re-drive information such as address, command and data information to one or more memory modules 710 located downstream from the first memory module 710, as well as to receive and re-drive data and/or error, status and other operational information intended for an upstream memory module 710 or the main memory controller 704.
[0038] The memory modules 710 may be implemented in 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 DIMM depicted in FIG. 1 includes 168 pins in the exemplary embodiment, whereas subsequent DIMMs have been constructed with pincounts ranging from 100 pins to over 300 pins.
[0039] In exemplary embodiments, the memory bus 706 is constructed using multi-drop connections to the memory modules 710 and/or using point-to-point connections. The downstream portion of the controller interface (or memory bus 706), referred to as the downstream bus, may include command, address, data and other operational, initialization or status information being sent to the memory modules 710. Each memory module 710 may simply forward the information to the subsequent module(s) 710 via bypass circuitry; receive, interpret and re-drive the information if it is determined to be targeting a downstream memory module 710; 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.
[0040] The upstream portion of the memory bus 706, 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) 710 via bypass circuitry; be received, interpreted and re-driven if it is determined to be targeting an upstream memory module 710 and/or memory controller 704 in the processor complex 702; 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.
[0041] Exemplary embodiments may be utilized by a single level memory system having only a single memory module 710, or memory subsystem, which is directly connected (such as via one or more point-to-point interconnections) to the main memory controller 704, with or without additional memory subsystem positions connected in a cascade interconnect or multi-drop structure. In additional exemplary embodiments, the main memory controller 704 includes more than one memory channel (see for e.g., bus 712 in FIG. 7 ), with each memory channel often comprised of one or more upstream and downstream buses 706 and 712 operating in a like manner; with the memory controller 704 operating in a parallel or independent manner for each memory bus 706 and 712; and/or with each memory bus 706 and 712 including the same or a different number of installed memory modules 710.
[0042] In exemplary embodiments, the memory system includes more than one memory module 710, with subsequent memory modules 710 communicating to the controller 704 by way of and/or independent of the first memory module 710. In exemplary embodiments, such as the one depicted in FIG. 7 , the memory controller 704 is in communication with the first memory module 710 via a point-to-point bus, with the bus cascade-connected to a second (subsequent) memory module 710 via re-drive circuitry in the first memory module 710 (e.g., via circuitry in the hub logic chip 708). Third and fourth (and greater) memory modules 710 may be connected via a similar method, with the re-drive circuitry included in the memory module 710 located prior to that memory module 710 in the memory bus 706.
[0043] In alternate exemplary embodiments, the point-to-point bus includes a switch or bypass mechanism which results in the bus information being directed to one of two or more possible memory modules 710 during downstream communication (communication passing from the main memory controller 704 to a memory module 710), as well as directing upstream information (communication from a memory module 710 to the memory controller 704), often by way of one or more upstream memory modules 710. Further embodiments include the use of continuity modules, such as those recognized in the art, which, for example, can be placed between the memory controller and a first populated memory module, in a cascade interconnect memory system, such that any intermediate module positions between the memory controller and the first populated memory module include a means by which information passing between the memory controller and the first populated memory module position can be received even if the one or more intermediate module position(s) do not include a memory module. The continuity module(s) may be installed in any module position(s), subject to any bus restrictions, including the first position (closest to the main memory controller, the last position (prior to any included termination) or any intermediate position(s). The use of continuity modules may be especially beneficial in a multi-module cascade interconnect bus structure, where an intermediate memory module is removed and replaced by a continuity module, such that the system continues to operate after the removal of the intermediate memory module. In more common embodiments, the continuity module(s) would include either interconnect wires to transfer all required signals from the input(s) to the corresponding output(s), or be re-driven through a repeater device. The continuity module(s) might further include a non-volatile storage device (such as an EEPROM), but would not include main memory storage devices.
[0044] In exemplary embodiments, the memory system includes one or more memory modules 710 connected to the memory controller 704 via a cascade interconnect memory bus 706, however other memory structures may be implemented such as a point-to-point bus, a multi-drop memory bus or a shared bus. Depending on the signaling methods used, the target operating frequencies, space, power, cost, and other constraints, various alternate bus structures may be considered. A point-to-point bus may provide the optimal performance in systems produced with electrical interconnections, due to the reduced signal degradation that may occur as compared to bus structures having branched signal lines, switch devices, or stubs. However, when used in systems requiring communication with multiple devices or subsystems, this method will often result in significant added component cost and increased system power, and may reduce the potential memory density due to the need for intermediate buffering and/or re-drive.
[0045] Although not shown in FIG. 7 , the memory modules 710 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 module attributes (generally after power-up), the reporting of fault or status information to the system, the configuration of the memory subsystem(s) 710 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 module(s) 710 to the memory controller(s) 704, or the identification of failures occurring during the execution of the main memory controller requests.
[0046] Performances similar to those obtained from point-to-point bus structures can be obtained by adding switch devices. These and other solutions offer increased memory packaging density at lower power, while retaining many of the characteristics of a point-to-point bus. Multi-drop busses provide an alternate solution, albeit often limited to a lower operating frequency, but at a cost/performance point that may be advantageous for many applications. Optical bus solutions permit significantly increased frequency and bandwidth potential, either in point-to-point or multi-drop applications, but may incur cost and space impacts.
[0047] 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 708, as used herein, refers to a hub chip that includes logic (hardware and/or software) for performing memory functions.
[0048] 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).
[0049] 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.
[0050] 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.
[0051] 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.
[0052] Module support devices (such as buffers, hubs, 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.
[0053] FIG. 8 is a block diagram of a memory system that may be implemented by exemplary embodiments. The system depicted in FIG. 8 is similar to the system depicted in FIG. 7 , with FIG. 8 depicting elements in the hub device 708 and memory controller 704 that may be utilized to implement exemplary embodiments. The memory controller 704 includes a local pre-fetch data cache 810, although this cache may also be logically partitioned from the existing cache hierarchy between the requestors (e.g. processor(s)) and the memory controller. In exemplary embodiments, the local pre-fetch data cache 810 is managed according to policies established by the computing environment. In further embodiments, the local pre-fetch data cache is managed by the memory controller 704 according to the buffer replacement policy and coherency dependencies with respect to outstanding read and write requests.
[0054] The hub device 708 includes interface logic 808, pre-fetch logic 804 and a DRAM interface 802. The pre-fetch logic 804 is utilized to monitor accesses to the memory devices from the memory controller 704. Based on access patterns by the memory controller 704, the pre-fetch logic 804 determines if a pre-fetch should be performed at the hub device 708. In an exemplary embodiment, pre-fetch requests would include the next sequential address or stride address, based on the historical system access pattern—although other pre-fetch algorithms could be applied based on the system design and/or programming. As used herein, the term stride address implies that the next address will be a distance from the previous address that is consistent with historical address spacings and not necessarily an adjacent address. Any suitable pre-fetch algorithm may be implemented by the pre-fetch logic 804 on the hub device 708. In exemplary embodiments, if the pre-fetch logic 804 determines that data should be pre-fetched, then it directs the DRAM interface 802 to read the data. In alternate exemplary embodiments, the pre-fetch logic 804 directs the interface logic 808 to read the data and the interface logic requests the data from the DRAM interface 802.
[0055] The interface logic 808 includes standard interface logic functions in addition to logic that is utilized to transmit the unsolicited pre-fetch data to the memory controller 704 as described below in reference to FIG. 9 . In alternate exemplary embodiments, the pre-fetch logic includes the instructions that are utilized to transmit the unsolicited pre-fetch data to the memory controller 704 as described below in reference to FIG. 9 . In alternate exemplary embodiments, the memory devices 716 and/or hub devices 708 include a pre-fetch data cache for storing the pre-fetch data (also referred to herein as the data returned by the unsolicited data read) locally before transmitting it to the memory controller 704.
[0056] FIG. 9 is a process flow for operations performed at the hub device 708 following the pre-fetching of unsolicited data that is implemented by exemplary embodiments. The processing flow may be implemented by adding additional functions to the interface logic 808 in the hub device 708 or by adding separate pre-fetch logic 804 to the hub device 708. As used herein, the term “logic” refers to computer instructions that are implemented by hardware and/or software. At block 902, the hub device 708 (e.g., the pre-fetch logic 804) monitors accesses to the memory devices 716 by the memory controller 704. Based on an algorithm in the hub device 708 (e.g., the pre-fetch logic 804) and in response to prior accesses by the memory controller 704, data may be pre-fetched by the hub device 708 at block 902. Again, pre-fetch algorithms are well known in the art, and any suitable algorithm may be utilized by exemplary embodiments. Once the read operation to the memory device(s) 716 is completed, one or more packets are prepared for transmission to the memory controller 704. At block 904, it is determined if an access is complete and a packet is ready for transmission to the memory controller 704. In exemplary embodiments, a memory access will result in a cache line transfer (e.g. 64 bytes of 128 bytes) and the transmission of one or more packets to the memory controller is not initiated until data equal to the size of the cache line has been pre-fetched from the memory device(s) 716; however, other transfer and packet sizes may be utilized, depending on the application, and the transfer may be comprised of one or more packets. Block 902 is performed and the hub pre-fetches data until at least the minimum information associated with the first of one or more intended packet(s) is available. A variety of transfer or packet sizes can be used, based on the system design objectives, with FIG. 11 relating to an exemplary embodiment. The tag that accompanies the transfer identifies the type of transfer it is, and therefore the number of bits/bytes/packets associated with the transfer.
[0057] If a packet is ready for transmission to the memory controller 704, as determined at block 904, then block 906 is performed. At block 906, the activity on the upstream bus is monitored by the hub device 708 (e.g., by the interface logic 808). At block 908, it is determined if the upstream bus is available to enable transmission of the unsolicited data packet. Generally, the upstream bus is available if there is a period of inactivity on the upstream bus and there are no other higher priority packets to be sent upstream from the hub device 708. If the upstream bus is available, then block 916 is preformed and the hub device 708 transmits the data packet to the memory controller 704, in conjunction with a tag which identifies the data (e.g. the address range and module identification). In this manner, the unsolicited data is sent, typically at a low priority, to the memory controller 704. Processing then continues at block 902. In conventional cascade interconnect memory systems, interface logic 808 is responsible for the merging of local information onto the cascade interconnect bus, although the memory controller schedules accesses such that the bus will be idle at the time the information is prepared for transmission to the memory controller, for the duration of the transfer. In the exemplary embodiment, interface logic 808 will initiate an upstream transfer to the controller at a time based on the application settings and transfer priority, and may temporarily delay or otherwise interrupt transfers in flight from downstream modules.
[0058] If the upstream bus is not available, as determined at block 908, then block 910 is performed and the hub device 708 monitors accesses directed to that hub device 708 on the downstream bus to determine if any accesses are directed to the same address range as the unsolicited data packet(s) currently available and waiting to be sent to the memory controller 704 on the upstream bus. If it is determined, at block 912, that a read operation is received that matches the address range of the available unsolicited packet, then block 914 is performed. At block 914, the tag associated with the unsolicited packet is modified to indicate the packet is a response packet and the priority is raised commensurate with the new packet identification. Then, block 916 is performed to merge the packet onto the upstream data bus once any current transfers from that hub device 708 are completed, with the merge also being consistent with the read priority algorithm.
[0059] If it is determined, at block 918, that a write operation has been received that matches the address range of the available unsolicited packet, then block 922 is performed. At block 922, the packet is discarded because the pre-fetch data is no longer valid, and processing continues at block 902 where the hub device 708 continues to monitor accesses for optimal pre-fetches. Upon completion of an unsolicited pre-fetch from the memory device(s) 716, the timeout counter is set to a pre-defined time limit for retaining the packet(s) (e.g., twenty clock cycles, thirty clock cycles) and begins to count down to zero. Once the packet(s) have aged to the pre-defined time limit (or have reached a pre-defined age), as determined at block 920, the timeout counter raises a flag, and any packet(s) associated with that timeout period that are not currently in the process of being sent to the memory controller 704 are discarded at block 922. The pre-defined time limit is a programmable (e.g., modifiable) number that may differ between hub devices 708. Processing then continues at block 902. If the timeout period has not been reached, then processing continues at block 908 to determine if the upstream bus is available 908 to transmit the packet. Although the steps in block 908, 910, 912, 918 and 920 are shown in an exemplary process flow, other process flows may be utilized, including a parallel flow (where read, write and timeout events are monitored in parallel) or a combination of series and parallel process flows (such as monitoring the timeout block 920 in parallel with completing read block 912 followed by write block 918) without straying from the fundamental teachings.
[0060] FIG. 10 is an exemplary process flow for operations performed at the memory controller 704 following the receipt of one or more unsolicited read packets from one or more hub devices 708 resident in the memory system. At block 1002, the memory controller monitors all bus activity from the hub devices 708 on the memory modules 710 by interpreting the packets to determine if they contain header information identifying the packet as a solicited, status, unsolicited or other form of communication (e.g. one or more informational packets) from the one or more memory modules 710, or memory subsystems, resident in the memory system. At block 1004, it is determined if a valid packet has been received. In exemplary embodiments, the memory controller 704 looks at the first transfer(s) (or some number of bits) of the bus information (e.g., a header field) to determine if the information appears to include one or more valid packet(s). If the memory controller 704 does not identify the information on the bus 706 as comprising one or more valid data packet(s) at block 1004, then block 1002 is performed and the memory controller 704 continues to monitor activity on the upstream bus 706.
[0061] If the memory controller 704 identifies a transmission on the bus 706 as being some form of data packet(s) at block 1004, then block 1006 is performed to determine if the packet(s) are related to a reply to an access or other operation initiated by the controller. If the tag information attached to the packet(s) is decoded as a response to a solicited read request at block 1006, then block 1010 is preformed and the memory controller 704 compares the remaining tag information (e.g. address range and/or module identifier) to the pending read requests to verify the validity of the data. If the tag correlates to an outstanding read request, as determined at block 1010, then block 1012 is performed and the data is transferred to the requestor (e.g., to one or more processors) at the next available time, based on the priority assigned to the read request, and the pending read request is retired. Processing then continues at block 1002. If the tag does not correlate to an outstanding read request, as determined at block 1010, then block 1014 is performed and the packet(s) are discarded and an error flag is generated for servicing by the processor or alternate error recovery system. Block 1014 is performed when the packet(s) appears to be a valid response packet, but does not correlate to an outstanding read request (e.g., the address or module identifier does not match outstanding read requests). In this case, the memory controller 704 discards the packet and then attempts to figure out why the error occurred by performing error recovery (e.g., channel diagnostics). Upon resolution of the error condition, in parallel with the diagnostics or immediately upon discarding the invalid packet(s) (e.g. due to a decision to delay diagnostics until a later time), processing then continues at block 1002.
[0062] If the information on the bus 706 is identified as one or more valid packet(s) in block 1004, but does not correlate to an outstanding read or write request to that address range as determined at block 1006, then block 1008 is performed and the packet(s) are evaluated to determine if the packet(s) is an unsolicited data packet(s). If the packet(s) is determined to be an unsolicited read packet at block 1008, then block 1022 is performed and the memory controller 704 double checks and once again compares the tag information to determine if the request correlates to a recent read request. If the packet(s) is found to correlate to a read request at block 1022, then block 1028 is performed and the solicited read request is transmitted to the requestor in a manner that is functionally similar to the processing in block 1012. Processing then continues at block 1002.
[0063] If it is determined, at block 1022, that the packet(s) does not correlate to a read request, then block 1024 is performed. At block 1024 it is determined if the packet(s) relates to a recent write operation to that address range, and if the tag confirms that the data is older than the previous write to that address range, then block 1030 is performed and the packet(s) is discarded because the data is out of date. Updating the local cache with this data would result in out of date (or incorrect) data being stored in the local cache and thus a lack of data coherency. Processing then continues at block 1002. If no outstanding read or write request is identified for the address range, then block 1026 is performed and the packet(s) is added to the local pre-fetch data cache 810, in conjunction with the address information, consistent with a local pre-fetch data cache control algorithm. Processing then continues at block 1002.
[0064] If the packet(s) is determined not to be one or more unsolicited read packet(s) at block 1008, then the received packet(s) are neither solicited nor unsolicited read packet(s) and the packet(s) may consist of other valid communication(s) from one or more hub devices 708 to the memory controller 704. At block 1016, the packet(s) is evaluated to determine if the information in the data packet(s) is associated with status, failure recovery or other actions, in which case block 1020 is preformed and the memory controller 704 takes action consistent with the design or programming of the system. Alternatively, block 1018 is performed if the packet(s) is determined to be a valid packet(s), but the contents are indeterminate or otherwise invalid. In this case, the memory controller 704 discards the packet and then attempts to figure out why the error occurred by performing error recovery (e.g., channel diagnostics). Upon resolution of the error condition, in parallel with the diagnostics or immediately upon discarding the invalid packet(s) (e.g. due to a decision to delay diagnostics until a later time), processing then continues at block 1002
[0065] Upon responding to the received transmission, in parallel with the execution of a response to the current packet(s) or immediately after initiating operation in response to the current packet, the memory controller 704 continues to monitor the bus 706 for incoming solicited or unsolicited packets at block 1002. The processing depicted in FIGS. 9 and 10 represent a logical process flow. The actual physical implementation of the processes may be different (e.g., some process blocks performed in parallel) as long as the physical implementation achieves the same results as those depicted in FIGS. 9 and 10 .
[0066] FIG. 11 depicts an exemplary upstream data packet, which could be sent by one or more of the memory modules 710, via the cascade interconnect memory bus 706, to the memory controller 704. In exemplary embodiments, the unsolicited data transfer(s) from the hub device 708 to the memory controller 704 is formatted as a data packet. The exemplary data packet depicted in FIG. 11 includes nineteen bit lanes and one header and eight data transfers, yielding a total of one hundred and seventy one bit positions. Other exemplary packets may have more or less bit lanes and more or less transfers, and may include one or more spare bit lanes, based on the application requirements and/or conditions. The packet header is shown under the channel lane numbers, and defines the location of the tag (bits 0-5), command (CMD) bits (6-7), status (STS) bits (8-9), ECC bits (12-17), and other lanes which may be used for functions such as interrupts, spare bit lanes, CRC, data and other information that might apply to a given application. In exemplary embodiments, the tag is utilized, as described above in reference to FIG. 10 , by the memory controller 704 to identify reply packets, to identify unsolicited pre-fetch data packets and to identify other types of packets received at the memory controller 704. The subsequent transfers (identified as transfers 0-7) refer to the data transfers that follow the header, and in the exemplary embodiment include 18 bit lanes, identified as 0 through 17, and 8 transfers, identified as 0 through 7, comprising a total of 144 bit positions (e.g. 16 bytes of data plus the associated EDC check bits). An additional bit lane is shown (shown as column 18 of FIG. 11 ), which may be used for such purposes as a spare bit lane.
[0067] The locations, count and function of each of the defined bit positions may also vary from what is described. In one case, an upstream data transfer packet might consist exclusively of header and status information, comprising one or several transfers. This packet may be used to report completion of an operation such as a write command or refresh, report an error condition, report a status condition (such as module or device temperature) or provide other information that requires a limited number of bit positions/transfers. In another case, the full nine transfers may be included in the packet, which may provide data to the memory controller 704 associated with a read request initiated by the memory controller 704, data from a self-initiated read operation (initiated by the memory subsystem, or memory module 710), in conjunction with information such as ECC bits and/or CRC bits, status bits, tag bits and other information.
[0068] In many cases, one or more packet transfers will be required to provide the requested/required information to the memory controller 704 and/or processor(s) in the processor complex 702, with four or eight packets commonly used. The one or more packets may also include information associated with more than one requested operation. For example, a series of packets associated with a requested read to a second memory module 710 might be sent to the memory controller 704 by way of the upstream bus and a first memory module 710 located upstream from the second memory module 710 and prior to the memory controller 704. Upon receipt of the first of the one or more packets, the first memory module 710 might concatenate separate and independent tag and/or status information to the one or more packets traveling upstream, generally in locations pre-defined for this purpose, such that the resulting packets include information associated with two or more independent operations from one or more separate memory modules 710. In this manner, the utilization of the available bus bandwidth can be maximized by ensuring that all of the possible bit positions in the packet(s) are utilized. Examples of two independent operations might include the results of a read operation from a second memory module 710, to which status information is appended from a first memory module 710, such as a write operation completion status, a refresh completion status, a mode change status, environmental information such as temperature, or other information.
[0069] Although not shown in FIG. 11 , exemplary downstream packets are structured in a similar manner, with multiple bit lanes and one or more transfers involved in the communication of command, address, data, status, initialization, priority flag(s) and other information from the memory controller 704 to the one or more memory modules 710 on the memory bus(es) 706. The downstream packet will often be included as a portion of a multi-packet transfer, with the bit lanes in each packet having the same or different functions based on the specific transfer and/or the packet number (such as the first packet of four packets or the eighth packet of eight total packets). This is also true for the upstream packet.
[0070] Memory devices, hubs, buffers, registers, clock devices, passives and other memory support devices and/or components may be attached to the memory subsystem, or memory module 710, 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.
[0071] The one or more memory subsystem(s), or memory modules 710, 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.
[0072] 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. The memory modules 710 described herein may also be referred to as memory subsystems because they include one or more memory devices 716 and a hub device 708.
[0073] Additional functions that may reside local to the memory subsystem, or memory module 710, 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.
[0074] Memory subsystem support device(s) may be directly attached to the same substrate or assembly onto which the memory device(s) 716 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) 716 and/or to other elements of the memory or computer system.
[0075] Information transfers (e.g. packets) 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.
[0076] 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.
[0077] 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).
[0078] 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.
[0079] 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.
[0080] 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.
[0081] 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.
[0082] 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.
[0083] 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.
[0084] 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.
[0085] 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.
[0086] Technical effects and benefits of exemplary embodiments include the ability to implement a more efficient hub based memory system by to improving computing performance through lower memory latency and higher memory throughput. Exemplary embodiments include pre-fetch logic executing on the hub devices and the transmission of the pre-fetch data to the memory controller as unsolicited data packets with a tag identifying the packets as such. The memory controller then stores the unsolicited read data packet in its local cache, which results in the cache data being close to the processor for faster access (when compared with having to request it from the hub device). In exemplary embodiments, the data is transmitted to the memory controller as a low priority data packet when the bus is idle, thereby allowing for better utilization of the bus and for preventing the memory controller from having to utilize the downstream bus to request the pre-fetched data.
[0087] 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.
[0088] 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
I claim:
1. A computer memory system comprising:
a memory controller for generating memory access requests to read data from two or more memory subsystems, receiving and responding to unsolicited data transfers from the two or more memory subsystems, the memory controller including pre-fetch data cache for storing pre-fetch data in anticipation of future data references, thereby eliminating sending one or more of the memory access requests to one or more of the memory subsystems when requested data is available in the pre-fetch data cache;
one or more memory busses connected to the memory controller; and
the two or more memory subsystems remote from the memory controller and in communication with the memory controller via the memory busses, each of the memory subsystems including one or more memory devices and pre-fetch logic to initiate an unsolicited data transfer to the memory controller based on access pattern analysis performed at the memory subsystem of prior memory access requests received by the memory subsystem from the memory controller, wherein the unsolicited data transfer includes a tag identifying the unsolicited data transfer as unsolicited, and the two or more memory subsystems include logic to modify the tag as a response in response to determining that a read operation has received which matches an address range of the unsolicited data transfer.
2. The memory system of claim 1 wherein the pre-fetch logic in the memory subsystem autonomously performs the analysis and initiates the unsolicited data transfer.
3. The memory system of claim 1 wherein the unsolicited data transfer includes address information associated with the data transfer.
4. The memory system of claim 1 wherein the unsolicited data transfer is initiated at a lower priority than a solicited data transfer.
5. The memory system of claim 1 wherein the memory controller includes logic to identify the unsolicited data transfer.
6. The memory system of claim 1, wherein the pre-fetch data cache is a logical partition of one or more caches in a hierarchy between the memory controller and one or more requesting devices and the pre-fetch data cache is coherently managed according to policies established for a computing environment.
7. The memory system of claim 6, wherein the pre-fetch data cache includes instructions to service a memory access request from the pre-fetch data cache without initiating an access request to the memory controller.
8. The memory system of claim 1, wherein the pre-fetch data cache is integrated within the memory controller and independently managed by the memory controller for replacement and coherency with respect to request traffic.
9. The memory system of claim 8, wherein the memory controller includes instructions to service a memory access request using data from the pre-fetch data cache in lieu of accessing the memory subsystem.
10. A computer memory subsystem comprising:
pre-fetch logic to perform an analysis of prior memory access requests to one or more memory devices in communication with the memory subsystem and to initiate an unsolicited data read to one or more of the memory devices based on results of the analysis; and
a hub device in communication with memory bus for initiating an unsolicited data transfer to a memory controller, the unsolicited data transfer including data returned by the unsolicited data read, the pre-fetch logic external to the memory controller wherein the unsolicited data transfer includes a tag identifying the unsolicited data transfer as unsolicited, and the hub device further comprises logic to modify the tag as a response in response to determining that a read operation has been received which matches an address range of the unsolicited data transfer.
11. The subsystem of claim 10 wherein the unsolicited data transfer includes address information associated with the unsolicited data read.
12. The subsystem of claim 10 wherein the unsolicited data transfer is initiated at a lower priority than a solicited data transfer.
13. The subsystem of claim 10 wherein the unsolicited data transfer is initiated during an idle period on the memory bus.
14. A method of driving unsolicited data packets in a memory system, the method comprising:
analyzing prior memory access requests to one or more memory devices, the analyzing performed at a memory module;
initiating a data read command at an address range corresponding to one or more of the memory devices, the initiating responsive to results of the analyzing; and
modifying a tag in an unsolicited data packet to indicate that the unsolicited data packet is a response packet and raising a priority of the response packet;
transmitting the unsolicited data packet on an upstream bus connecting the memory module to a memory controller, the unsolicited data packet including data returned by the data read command to the memory controller when the upstream bus is idle.
15. The method of claim 14 further comprising discarding the unsolicited data packet if a pending write request specifies the address range.
16. The method of claim 14 further comprising discarding the unsolicited data packet if the unsolicited data packet has aged beyond a limit and the upstream bus is not idle.
17. The method of claim 14 further comprising monitoring activity on the upstream bus.
Patent Citations (339)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US2842682(A) | 1958-07-01 | Clapper | Applicant |
| US3333253(A) | 1967-07-01 | Sahulka | Applicant |
| US3395400(A) | 1968-07-01 | De Witt | Applicant |
| US3825904(A) | 1974-07-01 | Burk et al. | Applicant |
| US4028675(A) | 1977-06-01 | Frankenberg | Applicant |
| US4135240(A) | 1979-01-01 | Ritchie | Applicant |
| US4150428(A) | 1979-04-01 | Inrig et al. | Applicant |
| US4472780(A) | 1984-09-01 | Chenoweth et al. | Applicant |
| US4475194(A) | 1984-10-01 | LaVallee et al. | Applicant |
| US4486739(A) | 1984-12-01 | Franaszek et al. | Applicant |
| US4641263(A) | 1987-02-01 | Perlman et al. | Applicant |
| US4654857(A) | 1987-03-01 | Samson et al. | Applicant |
| US4723120(A) | 1988-02-01 | Petty, Jr. | Applicant |
| US4740916(A) | 1988-04-01 | Martin | Applicant |
| US4796231(A) | 1989-01-01 | Pinkham | Applicant |
| US4803485(A) | 1989-02-01 | Rypinkski | Applicant |
| US4833605(A) | 1989-05-01 | Terada et al. | Applicant |
| US4839534(A) | 1989-06-01 | Clasen | Applicant |
| US4943984(A) | 1990-07-01 | Pechanek et al. | Applicant |
| US4985828(A) | 1991-01-01 | Shimizu et al. | Applicant |
| US5053947(A) | 1991-10-01 | Heibel et al. | Applicant |
| US5177375(A) | 1993-01-01 | Ogawa et al. | Applicant |
| US5206946(A) | 1993-04-01 | Brunk | Applicant |
| US5214747(A) | 1993-05-01 | Cok | Applicant |
| US5265049(A) | 1993-11-01 | Takasugi | Applicant |
| US5265212(A) | 1993-11-01 | Bruce, II | Applicant |
| US5287531(A) | 1994-02-01 | Rogers, Jr. et al. | Applicant |
| US5347270(A) | 1994-09-01 | Matsuda et al. | Applicant |
| US5357621(A) | 1994-10-01 | Cox | Applicant |
| US5375127(A) | 1994-12-01 | Leak et al. | Applicant |
| US5387911(A) | 1995-02-01 | Gleichert et al. | Applicant |
| US5394535(A) | 1995-02-01 | Ohuchi | Applicant |
| US5454091(A) | 1995-09-01 | Sites et al. | Applicant |
| US5475690(A) | 1995-12-01 | Burns et al. | Applicant |
| US5513135(A) | 1996-04-01 | Dell et al. | Applicant |
| US5517626(A) | 1996-05-01 | Archer et al. | Applicant |
| US5522064(A) | 1996-05-01 | Aldereguia et al. | Applicant |
| US5544309(A) | 1996-08-01 | Chang et al. | Applicant |
| US5546023(A) | 1996-08-01 | Borkar et al. | Applicant |
| US5561826(A) | 1996-10-01 | Davies et al. | Applicant |
| US5592632(A) | 1997-01-01 | Leung et al. | Applicant |
| US5594925(A) | 1997-01-01 | Harder et al. | Applicant |
| US5611055(A) | 1997-03-01 | Krishan et al. | Applicant |
| US5613077(A) | 1997-03-01 | Leung et al. | Applicant |
| US5627963(A) | 1997-05-01 | Gabillard et al. | Applicant |
| US5629685(A) | 1997-05-01 | Allen et al. | Applicant |
| US5661677(A) | 1997-08-01 | Rondeau, II et al. | Applicant |
| US5666480(A) | 1997-09-01 | Leung et al. | Applicant |
| US5684418(A) | 1997-11-01 | Yanagiuchi | Applicant |
| US5706346(A) | 1998-01-01 | Katta et al. | Applicant |
| US5754804(A) | 1998-05-01 | Cheselka et al. | Applicant |
| US5764155(A) | 1998-06-01 | Kertesz et al. | Applicant |
| US5822749(A) | 1998-10-01 | Agarwal | Applicant |
| US5852617(A) | 1998-12-01 | Mote, Jr. | Applicant |
| US5870325(A) | 1999-02-01 | Nielsen et al. | Applicant |
| US5872996(A) | 1999-02-01 | Barth et al. | Applicant |
| US5917760(A) | 1999-06-01 | Millar | Applicant |
| US5926838(A) | 1999-07-01 | Jeddeloh | Applicant |
| US5928343(A) | 1999-07-01 | Farmwald et al. | Applicant |
| US5930273(A) | 1999-07-01 | Mukojima | Applicant |
| US5959914(A) | 1999-09-01 | Gates et al. | Applicant |
| US5973951(A) | 1999-10-01 | Bechtolsheim et al. | Applicant |
| US5974493(A) | 1999-10-01 | Okumura et al. | Applicant |
| US5995405(A) | 1999-11-01 | Trick | Applicant |
| US6003121(A) | 1999-12-01 | Wirt | Applicant |
| US6011732(A) | 2000-01-01 | Harrison et al. | Applicant |
| US6038132(A) | 2000-03-01 | Tokunaga et al. | Applicant |
| US6049476(A) | 2000-04-01 | Laudon et al. | Applicant |
| US6076158(A) | 2000-06-01 | Sites et al. | Applicant |
| US6078515(A) | 2000-06-01 | Nielsen et al. | Applicant |
| US6081868(A) | 2000-06-01 | Brooks | Applicant |
| US6085276(A) | 2000-07-01 | VanDoren et al. | Applicant |
| US6096091(A) | 2000-08-01 | Hartmann | Applicant |
| US6128746(A) | 2000-10-01 | Clark et al. | Applicant |
| US6145028(A) | 2000-11-01 | Shank et al. | Applicant |
| US6170047(B1) | 2001-01-01 | Dye | Applicant |
| US6170059(B1) | 2001-01-01 | Pruett et al. | Applicant |
| US6173382(B1) | 2001-01-01 | Dell et al. | Applicant |
| US6185718(B1) | 2001-02-01 | Dell et al. | Applicant |
| US6198304(B1) | 2001-03-01 | Sasaki | Applicant |
| US6215686(B1) | 2001-04-01 | Deneroff et al. | Applicant |
| US6219288(B1) | 2001-04-01 | Braceras et al. | Applicant |
| US6219760(B1) | 2001-04-01 | McMinn | Examiner |
| US6233639(B1) | 2001-05-01 | Dell et al. | Applicant |
| US6260127(B1) | 2001-07-01 | Olarig et al. | Applicant |
| US6262493(B1) | 2001-07-01 | Garnett | Applicant |
| US6285172(B1) | 2001-09-01 | Torbey | Applicant |
| US6292903(B1) | 2001-09-01 | Coteus et al. | Applicant |
| US6301636(B1) | 2001-10-01 | Schultz et al. | Applicant |
| US6308247(B1) | 2001-10-01 | Ackerman et al. | Applicant |
| US6317352(B1) | 2001-11-01 | Halbert et al. | Applicant |
| US6321343(B1) | 2001-11-01 | Toda | Applicant |
| US6338113(B1) | 2002-01-01 | Kubo et al. | Applicant |
| US6349390(B1) | 2002-02-01 | Dell et al. | Applicant |
| US6357018(B1) | 2002-03-01 | Stuewe et al. | Applicant |
| US6370631(B1) | 2002-04-01 | Dye | Applicant |
| US6378018(B1) | 2002-04-01 | Tsern et al. | Applicant |
| US6381685(B2) | 2002-04-01 | Dell et al. | Applicant |
| US6393512(B1) | 2002-05-01 | Chen et al. | Applicant |
| US6393528(B1) | 2002-05-01 | Arimilli et al. | Applicant |
| US6408398(B1) | 2002-06-01 | Frecker et al. | Applicant |
| US6425044(B1) | 2002-07-01 | Jeddeloh | Applicant |
| US6446174(B1) | 2002-09-01 | Dow | Applicant |
| US6467013(B1) | 2002-10-01 | Nizar | Applicant |
| US6473836(B1) | 2002-10-01 | Ikeda | Applicant |
| US6477614(B1) | 2002-11-01 | Leddige et al. | Applicant |
| US6483755(B2) | 2002-11-01 | Leung et al. | Applicant |
| US6484271(B1) | 2002-11-01 | Gray | Applicant |
| US6487102(B1) | 2002-11-01 | Halbert et al. | Applicant |
| US6487627(B1) | 2002-11-01 | Willke et al. | Applicant |
| US6493250(B2) | 2002-12-01 | Halbert et al. | Applicant |
| US6496540(B1) | 2002-12-01 | Widmer | Applicant |
| US6496910(B1) | 2002-12-01 | Baentsch et al. | Applicant |
| US6499070(B1) | 2002-12-01 | Whetsel | Applicant |
| US6502161(B1) | 2002-12-01 | Perego et al. | Applicant |
| US6507888(B2) | 2003-01-01 | Wu et al. | Applicant |
| US6510100(B2) | 2003-01-01 | Grundon et al. | Applicant |
| US6513091(B1) | 2003-01-01 | Blackmon et al. | Applicant |
| US6530007(B2) | 2003-03-01 | Olarig | Applicant |
| US6532525(B1) | 2003-03-01 | Aleksic et al. | Applicant |
| US6546359(B1) | 2003-04-01 | Week | Applicant |
| US6549971(B1) | 2003-04-01 | Cecchi et al. | Applicant |
| US6553450(B1) | 2003-04-01 | Dodd et al. | Applicant |
| US6557069(B1) | 2003-04-01 | Drehmel et al. | Applicant |
| US6564329(B1) | 2003-05-01 | Cheung et al. | Applicant |
| US6584576(B1) | 2003-06-01 | Co | Applicant |
| US6587912(B2) | 2003-07-01 | Leddige | Applicant |
| US6590827(B2) | 2003-07-01 | Chang et al. | Applicant |
| US6594713(B1) | 2003-07-01 | Fuocco et al. | Applicant |
| US6594748(B1) | 2003-07-01 | Lin | Applicant |
| US6601121(B2) | 2003-07-01 | Singh et al. | Applicant |
| US6601149(B1) | 2003-07-01 | Brock et al. | Applicant |
| US6604180(B2) | 2003-08-01 | Jeddeloh | Applicant |
| US6611902(B2) | 2003-08-01 | Kuroda et al. | Applicant |
| US6622217(B2) | 2003-09-01 | Barroso et al. | Applicant |
| US6622227(B2) | 2003-09-01 | Zumkehr et al. | Applicant |
| US6625687(B1) | 2003-09-01 | Halbert et al. | Applicant |
| US6625702(B2) | 2003-09-01 | Rentschler et al. | Applicant |
| US6628538(B2) | 2003-09-01 | Funaba et al. | Applicant |
| US6631439(B2) | 2003-10-01 | Saulsbury et al. | Applicant |
| US6636957(B2) | 2003-10-01 | Stevens et al. | Applicant |
| US6643745(B1) | 2003-11-01 | Palanca et al. | Applicant |
| US6671376(B1) | 2003-12-01 | Koto et al. | Applicant |
| US6678811(B2) | 2004-01-01 | Rentschler et al. | Applicant |
| US6681292(B2) | 2004-01-01 | Creta et al. | Applicant |
| US6684320(B2) | 2004-01-01 | Mohamed et al. | Applicant |
| US6697919(B2) | 2004-02-01 | Gharachorloo et al. | Applicant |
| US6704842(B1) | 2004-03-01 | Janakiraman et al. | Applicant |
| US6721185(B2) | 2004-04-01 | Dong et al. | Applicant |
| US6721944(B2) | 2004-04-01 | Chaudhry et al. | Applicant |
| US6738836(B1) | 2004-05-01 | Kessler et al. | Applicant |
| US6741096(B2) | 2004-05-01 | Moss | Applicant |
| US6748518(B1) | 2004-06-01 | Guthrie et al. | Applicant |
| US6754762(B1) | 2004-06-01 | Curley | Applicant |
| US6766389(B2) | 2004-07-01 | Hayter et al. | Applicant |
| US6775747(B2) | 2004-08-01 | Venkatraman | Applicant |
| US6791555(B1) | 2004-09-01 | Radke et al. | Applicant |
| US6792495(B1) | 2004-09-01 | Garney et al. | Applicant |
| US6799241(B2) | 2004-09-01 | Kahn et al. | Applicant |
| US6839393(B1) | 2005-01-01 | Sidiropoulos | Applicant |
| US6877076(B1) | 2005-04-01 | Cho et al. | Applicant |
| US6877078(B2) | 2005-04-01 | Fujiwara et al. | Applicant |
| US6882082(B2) | 2005-04-01 | Greeff et al. | Applicant |
| US6889284(B1) | 2005-05-01 | Nizar et al. | Applicant |
| US6898726(B1) | 2005-05-01 | Lee | Applicant |
| US6910146(B2) | 2005-06-01 | Dow | Applicant |
| US6918068(B2) | 2005-07-01 | Vail et al. | Applicant |
| US6938119(B2) | 2005-08-01 | Kohn et al. | Applicant |
| US6944084(B2) | 2005-09-01 | Wilcox | Applicant |
| US6948091(B2) | 2005-09-01 | Bartels et al. | Applicant |
| US6949950(B2) | 2005-09-01 | Takahashi et al. | Applicant |
| US6965952(B2) | 2005-11-01 | Echartea et al. | Applicant |
| US6977536(B2) | 2005-12-01 | Chin-Chieh et al. | Applicant |
| US6993612(B2) | 2006-01-01 | Porterfield | Applicant |
| US6996639(B2) | 2006-02-01 | Narad | Applicant |
| US7039755(B1) | 2006-05-01 | Helms | Applicant |
| US7047370(B1) | 2006-05-01 | Jeter et al. | Examiner |
| US7047371(B2) | 2006-05-01 | Dortu | Applicant |
| US7047384(B2) | 2006-05-01 | Bodas et al. | Applicant |
| US7076700(B2) | 2006-07-01 | Rieger | Applicant |
| US7103792(B2) | 2006-09-01 | Moon | Applicant |
| US7120743(B2) | 2006-10-01 | Meyer et al. | Applicant |
| US7133790(B2) | 2006-11-01 | Liou | Applicant |
| US7133972(B2) | 2006-11-01 | Jeddeloh | Applicant |
| US7177211(B2) | 2007-02-01 | Zimmerman | Applicant |
| US7194593(B2) | 2007-03-01 | Schnepper | Applicant |
| US7197594(B2) | 2007-03-01 | Raz et al. | Applicant |
| US7203318(B2) | 2007-04-01 | Collum et al. | Applicant |
| US7206887(B2) | 2007-04-01 | Jeddeloh | Applicant |
| US7206962(B2) | 2007-04-01 | Deegan | Applicant |
| US7210059(B2) | 2007-04-01 | Jeddeloh | Applicant |
| US7216196(B2) | 2007-05-01 | Jeddeloh | Applicant |
| US7216276(B1) | 2007-05-01 | Azimi et al. | Applicant |
| US7222213(B2) | 2007-05-01 | James | Applicant |
| US7227949(B2) | 2007-06-01 | Heegard et al. | Applicant |
| US7240145(B2) | 2007-07-01 | Holman | Examiner |
| US7260685(B2) | 2007-08-01 | Lee et al. | Applicant |
| US7266634(B2) | 2007-09-01 | Ware et al. | Applicant |
| US7296129(B2) | 2007-11-01 | Gower et al. | Applicant |
| US7313583(B2) | 2007-12-01 | Porten et al. | Applicant |
| US7321979(B2) | 2008-01-01 | Lee | Applicant |
| US7353316(B2) | 2008-04-01 | Erdmann | Applicant |
| US7363419(B2) | 2008-04-01 | Cronin et al. | Applicant |
| US7363436(B1) | 2008-04-01 | Yeh et al. | Applicant |
| US7370134(B2) | 2008-05-01 | Jeddeloh | Applicant |
| US7386575(B2) | 2008-06-01 | Bashant et al. | Applicant |
| US7418526(B2) | 2008-08-01 | Jeddeloh | Applicant |
| US7421525(B2) | 2008-09-01 | Polzin et al. | Applicant |
| US7433258(B2) | 2008-10-01 | Rao et al. | Applicant |
| US2001/0000822(A1) | 2001-05-01 | Dell et al. | Applicant |
| US2001/0003839(A1) | 2001-06-01 | Kondo | Applicant |
| US2001/0029566(A1) | 2001-10-01 | Shin | Applicant |
| US2002/0019926(A1) | 2002-02-01 | Huppenthal et al. | Applicant |
| US2002/0038405(A1) | 2002-03-01 | Leddige et al. | Applicant |
| US2002/0059439(A1) | 2002-05-01 | Arroyo et al. | Applicant |
| US2002/0083255(A1) | 2002-06-01 | Greeff et al. | Applicant |
| US2002/0103988(A1) | 2002-08-01 | Dornier | Applicant |
| US2002/0112119(A1) | 2002-08-01 | Halbert et al. | Applicant |
| US2002/0112194(A1) | 2002-08-01 | Uzelac | Applicant |
| US2002/0124195(A1) | 2002-09-01 | Nizar | Applicant |
| US2002/0124201(A1) | 2002-09-01 | Edwards et al. | Applicant |
| US2002/0147898(A1) | 2002-10-01 | Rentschler et al. | Applicant |
| US2002/0174274(A1) | 2002-11-01 | Wu et al. | Applicant |
| US2003/0009632(A1) | 2003-01-01 | Arimilli et al. | Applicant |
| US2003/0028701(A1) | 2003-02-01 | Rao et al. | Applicant |
| US2003/0033364(A1) | 2003-02-01 | Garnett et al. | Applicant |
| US2003/0051055(A1) | 2003-03-01 | Parrella et al. | Examiner |
| US2003/0056183(A1) | 2003-03-01 | Kobayashi | Applicant |
| US2003/0084309(A1) | 2003-05-01 | Kohn | Applicant |
| US2003/0090879(A1) | 2003-05-01 | Doblar et al. | Applicant |
| US2003/0105938(A1) | 2003-06-01 | Cooksey et al. | Examiner |
| US2003/0118044(A1) | 2003-06-01 | Blanc et al. | Applicant |
| US2003/0126354(A1) | 2003-07-01 | Kahn et al. | Applicant |
| US2003/0126355(A1) | 2003-07-01 | David | Examiner |
| US2003/0126363(A1) | 2003-07-01 | David | Applicant |
| US2003/0223303(A1) | 2003-12-01 | Lamb et al. | Applicant |
| US2003/0229770(A1) | 2003-12-01 | Jeddeloh | Applicant |
| US2003/0235222(A1) | 2003-12-01 | Bridges et al. | Applicant |
| US2003/0236959(A1) | 2003-12-01 | Johnson et al. | Applicant |
| US2004/0006674(A1) | 2004-01-01 | Hargis et al. | Applicant |
| US2004/0015650(A1) | 2004-01-01 | Zumkehr et al. | Applicant |
| US2004/0049723(A1) | 2004-03-01 | Obara | Applicant |
| US2004/0078615(A1) | 2004-04-01 | Martin et al. | Applicant |
| US2004/0098546(A1) | 2004-05-01 | Bashant et al. | Applicant |
| US2004/0098549(A1) | 2004-05-01 | Dorst | Applicant |
| US2004/0117588(A1) | 2004-06-01 | Arimilli et al. | Applicant |
| US2004/0123222(A1) | 2004-06-01 | Widmer | Applicant |
| US2004/0128474(A1) | 2004-07-01 | Vorbach | Applicant |
| US2004/0148482(A1) | 2004-07-01 | Grundy et al. | Applicant |
| US2004/0160832(A1) | 2004-08-01 | Janzen et al. | Applicant |
| US2004/0163028(A1) | 2004-08-01 | Olarig | Applicant |
| US2004/0165609(A1) | 2004-08-01 | Herbst et al. | Examiner |
| US2004/0199363(A1) | 2004-10-01 | Bohizic et al. | Examiner |
| US2004/0205433(A1) | 2004-10-01 | Gower et al. | Applicant |
| US2004/0230718(A1) | 2004-11-01 | Polzin et al. | Applicant |
| US2004/0246767(A1) | 2004-12-01 | Vogt | Applicant |
| US2004/0250153(A1) | 2004-12-01 | Vogt | Applicant |
| US2004/0260909(A1) | 2004-12-01 | Lee et al. | Applicant |
| US2004/0260957(A1) | 2004-12-01 | Jeddeloh et al. | Applicant |
| US2005/0023560(A1) | 2005-02-01 | Ahn et al. | Applicant |
| US2005/0027941(A1) | 2005-02-01 | Wang et al. | Examiner |
| US2005/0033906(A1) | 2005-02-01 | Mastronarde et al. | Applicant |
| US2005/0044305(A1) | 2005-02-01 | Jakobs et al. | Applicant |
| US2005/0050237(A1) | 2005-03-01 | Jeddeloh et al. | Applicant |
| US2005/0050255(A1) | 2005-03-01 | Jeddeloh | Applicant |
| US2005/0066136(A1) | 2005-03-01 | Schnepper | Applicant |
| US2005/0071542(A1) | 2005-03-01 | Weber et al. | Examiner |
| US2005/0071707(A1) | 2005-03-01 | Hampel | Applicant |
| US2005/0078506(A1) | 2005-04-01 | Rao et al. | Applicant |
| US2005/0080581(A1) | 2005-04-01 | Zimmerman et al. | Applicant |
| US2005/0081129(A1) | 2005-04-01 | Shah et al. | Applicant |
| US2005/0086424(A1) | 2005-04-01 | Oh et al. | Applicant |
| US2005/0086441(A1) | 2005-04-01 | Myer et al. | Applicant |
| US2005/0097249(A1) | 2005-05-01 | Oberlin et al. | Applicant |
| US2005/0105350(A1) | 2005-05-01 | Zimmerman et al. | Applicant |
| US2005/0120157(A1) | 2005-06-01 | Chen et al. | Applicant |
| US2005/0125702(A1) | 2005-06-01 | Huang et al. | Applicant |
| US2005/0125703(A1) | 2005-06-01 | Lefurgy et al. | Applicant |
| US2005/0138246(A1) | 2005-06-01 | Chen et al. | Applicant |
| US2005/0138267(A1) | 2005-06-01 | Bains et al. | Applicant |
| US2005/0144399(A1) | 2005-06-01 | Hosomi | Applicant |
| US2005/0149665(A1) | 2005-07-01 | Wolrich et al. | Examiner |
| US2005/0166006(A1) | 2005-07-01 | Talbot et al. | Applicant |
| US2005/0177677(A1) | 2005-08-01 | Jeddeloh | Applicant |
| US2005/0177690(A1) | 2005-08-01 | LaBerge | Applicant |
| US2005/0204216(A1) | 2005-09-01 | Daily et al. | Applicant |
| US2005/0216678(A1) | 2005-09-01 | Jeddeloh | Applicant |
| US2005/0220097(A1) | 2005-10-01 | Swami et al. | Applicant |
| US2005/0223196(A1) | 2005-10-01 | Knowles | Applicant |
| US2005/0229132(A1) | 2005-10-01 | Butt et al. | Applicant |
| US2005/0248997(A1) | 2005-11-01 | Lee | Applicant |
| US2005/0257005(A1) | 2005-11-01 | Jeddeloh | Applicant |
| US2005/0259496(A1) | 2005-11-01 | Hsu et al. | Applicant |
| US2005/0289292(A1) | 2005-12-01 | Morrow et al. | Applicant |
| US2005/0289377(A1) | 2005-12-01 | Luong | Applicant |
| US2006/0036826(A1) | 2006-02-01 | Dell et al. | Applicant |
| US2006/0036827(A1) | 2006-02-01 | Dell et al. | Applicant |
| US2006/0080584(A1) | 2006-04-01 | Hartnett et al. | Applicant |
| US2006/0085602(A1) | 2006-04-01 | Huggahalli et al. | Examiner |
| US2006/0095592(A1) | 2006-05-01 | Borkenhagen | Applicant |
| US2006/0095679(A1) | 2006-05-01 | Edirisooriya | Examiner |
| US2006/0107175(A1) | 2006-05-01 | Dell et al. | Applicant |
| US2006/0112238(A1) | 2006-05-01 | Jamil et al. | Examiner |
| US2006/0161733(A1) | 2006-07-01 | Beckett et al. | Examiner |
| US2006/0162882(A1) | 2006-07-01 | Ohara et al. | Applicant |
| US2006/0168407(A1) | 2006-07-01 | Stern | Applicant |
| US2006/0179208(A1) | 2006-08-01 | Jeddeloh | Applicant |
| US2006/0190674(A1) | 2006-08-01 | Poechmueller | Applicant |
| US2006/0195631(A1) | 2006-08-01 | Rajamani | Examiner |
| US2006/0206742(A1) | 2006-09-01 | James | Applicant |
| US2006/0212666(A1) | 2006-09-01 | Jeddeloh | Applicant |
| US2006/0224764(A1) | 2006-10-01 | Shinohara et al. | Applicant |
| US2006/0277365(A1) | 2006-12-01 | Pong | Applicant |
| US2006/0288172(A1) | 2006-12-01 | Lee et al. | Applicant |
| US2007/0005922(A1) | 2007-01-01 | Swaminathan et al. | Applicant |
| US2007/0025304(A1) | 2007-02-01 | Leelahakriengkrai et al. | Examiner |
| US2007/0038907(A1) | 2007-02-01 | Jeddeloh et al. | Applicant |
| US2007/0067382(A1) | 2007-03-01 | Sun | Examiner |
| US2007/0083701(A1) | 2007-04-01 | Kapil | Applicant |
| US2007/0160053(A1) | 2007-07-01 | Coteus | Applicant |
| US2008/0043808(A1) | 2008-02-01 | Hsu et al. | Applicant |
| US2008/0162807(A1) | 2008-07-01 | Rothman et al. | Applicant |
| US2008/0222379(A1) | 2008-09-01 | Jeddeloh | Applicant |
| EP229316(A2) | 1987-07-01 | Applicant | |
| EP470734(A1) | 1992-02-01 | Applicant | |
| EP899743(A2) | 1998-06-01 | Applicant | |
| EP1429340(A2) | 2004-06-01 | Applicant | |
| GB2396711(A) | 2004-06-01 | Applicant | |
| JP59153353(A) | 1984-09-01 | Applicant | |
| JP114140(A) | 1989-06-01 | Applicant | |
| JP432614 | 1992-11-01 | Applicant | |
| JP10011971 | 1998-01-01 | Applicant | |
| JP2004139552(A) | 2004-05-01 | Applicant | |
| JP2008003711(A) | 2008-01-01 | Applicant | |
| WO9621188 | 1996-07-01 | Applicant | |
| WO9812651 | 1998-03-01 | Applicant | |
| WO223353(A2) | 2002-03-01 | Applicant | |
| WO2005038660 | 2005-04-01 | Applicant | |
| WO2007109888 | 2007-10-01 | Applicant |
Non-Patent Literature (34)
- Boudon, et al., “Novel Bus Reconfiguration Scheme With Spare Lines”, IBM Technical Disclosure Bulletin, May 1987, vol. 29, No. 12, pp. 1-3.Applicant
- NB940259 (IBM Technical Disclosure Bulletin, Feb. 1994; vol. 37; pp. 59-64).Applicant
- Singh, S., et al., “Bus Sparing for Fault-Tolerant System Design”, IBM Technical Disclosure Bulletin, Dec. 1991, vol. 34, No. 71, pp. 117-118.Applicant
- U.S. Appl. No. 11/419,586, filed May 22, 2006. Robert Tremaine. “Systems and Methods for Providing Remote Pre-Fetch Buffers”.Applicant
- Wikipedia, Serial Communications, [online], [retrieved Apr. 10, 2007 from the Internet], http://en.wikipedia.org/wiki/Serial—communications, 3 pages.Applicant
- Sivencrona et al.; “RedCAN™: Simulations of two Fault Recovery Algorithms for CAN;” Proceedings for the 10th IEEE Pacific Rim International Symposium on Dependable Computing (PRDC'04); 2005.Applicant
- Jungjoon Kim et al.; “Performance and Architecture Features of Segmented Multiple Bus System;” IEEE Computer Society; 1999 International Conference on Parallel Processing (ICPP '99).Applicant
- Ghoneima et al.; “Optimum Positioning of Interleaved Repeaters in Bidirectional Buses;” IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems, vol. 25, No. 3, Mar. 2005, pp. 461-469.Applicant
- Seceleanu et al.; “Segment Arbiter as Action System;” IEEE 2003 pp. 249-252.Applicant
- Understanding System Memory and CPU Speeds: A Layman'S Guide to the Front Side Bus (FSB), [online]; [retrieved on Feb. 23, 2006]; retrieved from the Internet http://www.directron.com/fsbguide.html.Applicant
- JEDEC Solid State Technology Association, “JEDEC Standard: DDR2 SDRAM Specification”, Jan. 2004, JEDEC, Revision JESD79-2A, p. 10.Applicant
- Brown, et al “Compiler-Based I/O Prefetching for Out-of-Core Applications”, ACM Transactions on Computer Systems, vol. 19, No, 2, May 2001, pp. 111-170.Applicant
- Wang, et al., “Guided Region Prefetching: A Cooperative Hardware/Software Approach”, pp. 388-398.Applicant
- Natarajan, et al., “A Study of Performance Impact of Memory Controller Features in Multi-Processor Server Environment”, pp. 80-87.Applicant
- Nilsen, “High-Level Dynamic Memory Management for Object-Oriented Real-Time Systems”, pp. 86-93.Applicant
- Massoud Pedram, “Power Minimization in IC Design Principles and Applications”, ACM Transactions on Design Automation of Electronic Systems vol. 1, No. 1, Jan. 1996, pp. 3-56.Applicant
- P.R. Panda, “Data and Memory Optimization Techniques For Embedded Systems”, ACM Transactions on Design Automation of Electronic Systems, vol. 6, No. 2, Apr. 2001, pp. 149-206.Applicant
- Luca Benini, et al., “System-Level Powers Optimization: Techniques and Tools”, ACM Transactions on Design Automation of Electronic Systems, vol. 5, No. 2, Apr. 2000, pp. 115-192.Applicant
- IEEE, “IEEE Standard Test Access Port and Boundary-Scan Architecture”, Jul. 23, 2001, IEEE Std 1149-1-2001, pp. 11-13.Applicant
- Rosenberg, “Dictionary of Computers, Information Processing & Telecommuications”, Second Edition, John Wiley & Sons, Inc. 1987. 3 pgs.Applicant
- PCT Search Report. PCT/EP2007/057915. Mailed Nov. 7, 2007.Applicant
- International Search Report, International Application No. PCT/EP2007/054929, International Publication No. WO 2007/135144 A1, received Mar. 21, 2008.Applicant
- PCT International Search Report PCT/EP2006/068984. Mailed Feb. 16, 2007.Applicant
- PCT International Search Report PCT/EP2007/057916. Mailed Dec. 14, 2007.Applicant
- Yang, Q.; Bhuyan, L.N., “Analysis of packet-switched multiple-bus multiprocessor systems,” Computers, IEEE Transactions on, vol. 40, No. 3, pp. 352-357, Mar. 1991.Applicant
- Li, P; Martinez, J.; Tang, J.; Priore, S.,; Hubbard, K.; Jie Xue; Poh, E.; Ong MeiLin; Chok KengYin; Hallmark, C.; Mendez, D.; “Development and evaluation of a high performance fine pitch SODIMM socket package.” Electronic Components and Technology Conference, 2004. Proceedings. 54th, vol. 1, pp. 1161-1166, Jun. 1-4, 2004.Applicant
- International Search Report, International Patent Application No. PCT/US07/75944, mailed Sep. 23, 2008, 3 pages.Applicant
- European Search Report, European Patent Application No. 05106701.5, mailed Oct. 7, 2008, 5 pages.Applicant
- European Search Report, European Patent Application No. 05109837.4, mailed Oct. 7, 2008, 5 pages.Applicant
- Joe Jeddeloh, Fully Buffered DIMM (FB-DIMM), XP002490174, Advanced Systems Technology, Micron Technology, Inc. Apr. 16, 2008, 32 pages.Applicant
- Timothy J. Dell, “The RAS Implications of DIMM Connector Failure Rates in Large, Highly Available Server Systems”, The 53rd IEEE Holm Conference on Electrical Contacts, IEEE, Sep. 16-19, 2007, pp. 256-261.Applicant
- “Using Dual and Mappable Spare Bus”, XP000433763, IBM Technical Disclosure Bulletin, vol. 37, No. 2B, IBM Copr., NY, US, Feb. 1, 1994, pp. 59-63.Applicant
- “Novel Bus Reconfiguration Scheme With Spare Lines”, XP000676205, IBM Technical Disclosure Bulletin, vol. 29, No. 12, IBM Copr., NY, US, May 12, 1987, pp. 5590-5593.Applicant
- European Search Report, European Patent Application 05106700.7, received Aug. 11, 2008.Applicant