Memory module with memory stack and interface with enhanced capabilities

Abstract
A memory module, which includes at least one memory stack, comprises a plurality of DRAM integrated circuits and an interface circuit. The interface circuit interfaces the memory stack to a host system so as to operate the memory stack as a single DRAM integrated circuit. In other embodiments, a memory module includes at least one memory stack and a buffer integrated circuit. The buffer integrated circuit, coupled to a host system, interfaces the memory stack to the host system so to operate the memory stack as at least two DRAM integrated circuits. In yet other embodiments, the buffer circuit interfaces the memory stack to the host system for transforming one or more physical parameters between the DRAM integrated circuits and the host system.
Description
BACKGROUND

1. Field of the Invention


The present invention is directed toward the field of building custom memory systems cost-effectively for a wide range of markets.


2. Art Background


The memory capacity requirements of computers in general, and servers in particular, are increasing at a very rapid pace due to several key trends in the computing industry. The first trend is 64-bit computing, which enables processors to address more than 4 GB of physical memory. The second trend is multi-core CPUs, where each core runs an independent software thread. The third trend is server virtualization or consolidation, which allows multiple operating systems and software applications to run simultaneously on a common hardware platform. The fourth trend is web services, hosted applications, and on-demand software, where complex software applications are centrally run on servers instead of individual copies running on desktop and mobile computers. The intersection of all these trends has created a step function in the memory capacity requirements of servers.


However, the trends in the DRAM industry are not aligned with this step function. As the DRAM interface speeds increase, the number of loads (or ranks) on the traditional multi-drop memory bus decreases in order to facilitate high speed operation of the bus. In addition, the DRAM industry has historically had an exponential relationship between price and DRAM density, such that the highest density ICs or integrated circuits have a higher $/Mb ratio than the mainstream density integrated circuits. These two factors usually place an upper limit on the amount of memory (i.e. the memory capacity) that can be economically put into a server.


One solution to this memory capacity gap is to use a fully buffered DIMM (FB-DIMM), and this is currently being standardized by JEDEC. FIG. 1A illustrates a fully buffered DIMM. As shown in FIG. 1A, memory controller 100 communicates with FB-DIMMs (130 and 140) via advanced memory buffers (AMB) 110 and 120 to operate a plurality of DRAMs. As shown in FIG. 1B, the FB-DIMM approach uses a point-to-point, serial protocol link between the memory controller 100 and FB-DIMMs 150, 151, and 152. In order to read the DRAM devices on, say, the third FB-DIMM 152, the command has to travel through the AMBs on the first FB-DIMM 150 and second FB-DIMM 151 over the serial link segments 141, 142, and 143, and the data from the DRAM devices on the third FB-DIMM 152 must travel back to the memory controller 100 through the AMBs on the first and second FB-DIMMs over serial link segments 144, 145, and 146.


The FB-DIMM approach creates a direct correlation between maximum memory capacity and the printed circuit board (PCB) area. In other words, a larger PCB area is required to provide larger memory capacity. Since most of the growth in the server industry is in the smaller form factor servers like 1 U/2 U rack servers and blade servers, the FB-DIMM solution does not solve the memory capacity gap for small form factor servers. So, clearly there exists a need for dense memory technology that fits into the mechanical and thermal envelopes of current memory systems.


SUMMARY

A memory module comprises at least one memory stack. The memory stack includes a plurality of DRAM integrated circuits. A buffer circuit, which couples the memory module to a host system, interfaces the memory stack to the host system for transforming one or more physical parameters between the DRAM integrated circuits and the host system. In other embodiments, the buffer circuit interfaces the memory stack to the host system for configuring one or more of the DRAM integrated circuits in the memory stack.





BRIEF DESCRIPTION OF THE DRAWINGS


FIGS. 1A-1B illustrate a memory sub-system that uses fully buffered DIMMs.



FIGS. 2A-2C illustrate one embodiment of a DIMM with a plurality of DRAM stacks.



FIG. 3A illustrates a DIMM PCB with buffered DRAM stacks.



FIG. 3B illustrates a buffered DRAM stack that emulates a 4 Gbyte DRAM.



FIG. 4A illustrates an example of a DIMM that uses the buffer integrated circuit and DRAM stack.



FIG. 4B illustrates a physical stack of DRAMs in accordance with one embodiment.



FIGS. 5A and 5B illustrate another embodiment of a multi-rank buffer integrated circuit and DIMM.



FIGS. 6A and 6B illustrates one embodiment of a buffer that provides a number of ranks on a DIMM equal to the number of valid integrated circuit selects from a host system.



FIG. 6C illustrates one embodiment that provides a mapping between logical partitions of memory and physical partitions of memory.



FIG. 7A illustrates a configuration between a memory controller and DIMMs.



FIG. 7B illustrates the coupling of integrated circuit select lines to a buffer on a DIMM for configuring the number of ranks based on commands from the host system.



FIG. 8 illustrates one embodiment for a DIMM PCB with a connector or interposer with upgrade capability.



FIG. 9 illustrates an example of linear address mapping for use with a multi-rank buffer integrated circuit.



FIG. 10 illustrates an example of linear address mapping with a single rank buffer integrated circuit.



FIG. 11 illustrates an example of “bit slice” address mapping with a multi-rank buffer integrated circuit.



FIG. 12 illustrates an example of “bit slice” address mapping with a single rank buffer integrated circuit.



FIGS. 13A and 13B illustrate examples of buffered stacks that contain DRAM and non-volatile memory integrated circuits.



FIGS. 14A, 14B and 14C illustrate one embodiment of a buffered stack with power decoupling layers.





DETAILED DESCRIPTION

In one embodiment of this invention, multiple buffer integrated circuits are used to buffer the DRAM integrated circuits or devices on a DIMM as opposed to the FB-DIMM approach, where a single buffer integrated circuit is used to buffer all the DRAM integrated circuits on a DIMM. That is, a bit slice approach is used to buffer the DRAM integrated circuits. As an option, multiple DRAMs may be connected to each buffer integrated circuit. In other words, the DRAMs in a slice of multiple DIMMs may be collapsed or coalesced or stacked behind each buffer integrated circuit, such that the buffer integrated circuit is between the stack of DRAMs and the electronic host system. FIGS. 2A-2C illustrate one embodiment of a DIMM with multiple DRAM stacks, where each DRAM stack comprises a bit slice across multiple DIMMs. As an example, FIG. 2A shows four DIMMs (e.g., DIMM A, DIMM B, DIMM C and DIMM D). Also, in this example, there are 9 bit slices labeled DAO, . . . , DA6, . . . DA8 across the four DIMMs. Bit slice “6” is shown encapsulated in block 210. FIG. 2B illustrates a buffered DRAM stack. The buffered DRAM stack 230 comprises a buffer integrated circuit (220) and DRAM devices DA6, DB6, DC6 and DD6. Thus, bit slice 6 is generated from devices DA6, DB6, DC6 and DD6. FIG. 2C is a top view of a high density DIMM with a plurality of buffered DRAM stacks. A high density DIMM (240) comprises buffered DRAM stacks (250) in place of individual DRAMs.


Some exemplary embodiments include:

    • (a) a configuration with increased DIMM density, that allows the total memory capacity of the system to increase without requiring a larger PCB area. Thus, higher density DIMMs fit within the mechanical and space constraints of current DIMMs.
    • (b) a configuration with distributed power dissipation, which allows the higher density DIMM to fit within the thermal envelope of existing DIMMs. In an embodiment with multiple buffers on a single DIMM, the power dissipation of the buffering function is spread out across the DIMM.
    • (c) a configuration with non-cumulative latency to improve system performance. In a configuration with non-cumulative latency, the latency through the buffer integrated circuits on a DIMM is incurred only when that particular DIMM is being accessed.


In a buffered DRAM stack embodiment, the plurality of DRAM devices in a stack are electrically behind the buffer integrated circuit. In other words, the buffer integrated circuit sits electrically between the plurality of DRAM devices in the stack and the host electronic system and buffers some or all of the signals that pass between the stacked DRAM devices and the host system. Since the DRAM devices are standard, off-the-shelf, high speed devices (like DDR SDRAMs or DDR2 SDRAMs), the buffer integrated circuit may have to re-generate some of the signals (e.g. the clocks) while other signals (e.g. data signals) may have to be re-synchronized to the clocks or data strobes to minimize the jitter of these signals. Other signals (e.g. address signals) may be manipulated by logic circuits such as decoders. Some embodiments of the buffer integrated circuit may not re-generate or re-synchronize or logically manipulate some or all of the signals between the DRAM devices and host electronic system.


The buffer integrated circuit and the DRAM devices may be physically arranged in many different ways. In one embodiment, the buffer integrated circuit and the DRAM devices may all be in the same stack. In another embodiment, the buffer integrated circuit may be separate from the stack of DRAM integrated circuits (i.e. buffer integrated circuit may be outside the stack). In yet another embodiment, the DRAM integrated circuits that are electrically behind a buffer integrated circuit may be in multiple stacks (i.e. a buffer integrated circuit may interface with a plurality of stacks of DRAM integrated circuits).


In one embodiment, the buffer integrated circuit can be designed such that the DRAM devices that are electrically behind the buffer integrated circuit appear as a single DRAM integrated circuit to the host system, whose capacity is equal to the combined capacities of all the DRAM devices in the stack. So, for example, if the stack contains eight 512 Mb DRAM integrated circuits, the buffer integrated circuit of this embodiment is designed to make the stack appear as a single 4 Gb DRAM integrated circuit to the host system. An un-buffered DIMM, registered DIMM, S0-DIMM, or FB-DIMM can now be built using buffered stacks of DRAMs instead of individual DRAM devices. For example, a double rank registered DIMM that uses buffered DRAM stacks may have eighteen stacks, nine of which may be on one side of the DIMM PCB and controlled by a first integrated circuit select signal from the host electronic system, and nine may be on the other side of the DIMM PCB and controlled by a second integrated circuit select signal from the host electronic system. Each of these stacks may contain a plurality of DRAM devices and a buffer integrated circuit.



FIG. 3A illustrates a DIMM PCB with buffered DRAM stacks. As shown in FIG. 3A, both the top and bottom sides of the DIMM PCB comprise a plurality of buffered DRAM stacks (e.g., 310 and 320). Note that the register and clock PLL integrated circuits of a registered DIMM are not shown in this figure for simplicity's sake. FIG. 3B illustrates a buffered DRAM stack that emulates a 4 Gb DRAM.


In one embodiment, a buffered stack of DRAM devices may appear as or emulate a single DRAM device to the host system. In such a case, the number of memory banks that are exposed to the host system may be less than the number of banks that are available in the stack. To illustrate, if the stack contained eight 512 Mb DRAM integrated circuits, the buffer integrated circuit of this embodiment will make the stack look like a single 4 Gb DRAM integrated circuit to the host system. So, even though there are thirty two banks (four banks per 512 Mb integrated circuit*eight integrated circuits) in the stack, the buffer integrated circuit of this embodiment might only expose eight banks to the host system because a 4 Gb DRAM will nominally have only eight banks. The eight 512 Mb DRAM integrated circuits in this example may be referred to as physical DRAM devices while the single 4 Gb DRAM integrated circuit may be referred to as a virtual DRAM device. Similarly, the banks of a physical DRAM device may be referred to as a physical bank whereas the bank of a virtual DRAM device may be referred to as a virtual bank.


In another embodiment of this invention, the buffer integrated circuit is designed such that a stack of n DRAM devices appears to the host system as m ranks of DRAM devices (where n≧m, and m≧2). To illustrate, if the stack contained eight 512 Mb DRAM integrated circuits, the buffer integrated circuit of this embodiment may make the stack appear as two ranks of 2 Gb DRAM devices (for the case of m=2), or appear as four ranks of 1 Gb DRAM devices (for the case of m=4), or appear as eight ranks of 512 Mb DRAM devices (for the case of m=8). Consequently, the stack of eight 512 Mb DRAM devices may feature sixteen virtual banks (m=2; eight banks per 2 Gb virtual DRAM*two ranks), or thirty two virtual banks (m=4; eight banks per 1 Gb DRAM*four ranks), or thirty two banks (m=8; four banks per 512 Mb DRAM*eight ranks).


In one embodiment, the number of ranks may be determined by the number of integrated circuit select signals from the host system that are connected to the buffer integrated circuit. For example, the most widely used JEDEC approved pin out of a DIMM connector has two integrated circuit select signals. So, in this embodiment, each stack may be made to appear as two DRAM devices (where each integrated circuit belongs to a different rank) by routing the two integrated circuit select signals from the DIMM connector to each buffer integrated circuit on the DIMM. For the purpose of illustration, let us assume that each stack of DRAM devices has a dedicated buffer integrated circuit, and that the two integrated circuit select signals that are connected on the motherboard to a DIMM connector are labeled CS0# and CS1#. Let us also assume that each stack is 8-bits wide (i.e. has eight data pins), and that the stack contains a buffer integrated circuit and eight 8-bit wide 512 Mb DRAM integrated circuits. In this example, both CS0# and CS1# are connected to all the stacks on the DIMM. So, a single-sided registered DIMM with nine stacks (with CS0# and CS1# connected to all nine stacks) effectively features two 2 GB ranks, where each rank has eight banks.


In another embodiment, a double-sided registered DIMM may be built using eighteen stacks (nine on each side of the PCB), where each stack is 4-bits wide and contains a buffer integrated circuit and eight 4-bit wide 512 Mb DRAM devices. As above, if the two integrated circuit select signals CS0# and CS1# are connected to all the stacks, then this DIMM will effectively feature two 4 GB ranks, where each rank has eight banks. However, half of a rank's capacity is on one side of the DIMM PCB and the other half is on the other side. For example, let us number the stacks on the DIMM as S0 through S17, such that stacks S0 through S8 are on one side of the DIMM PCB while stacks S9 through S17 are on the other side of the PCB. Stack S0 may be connected to the host system's data lines DQ[3:0], stack S9 connected to the host system's data lines DQ[7:4], stack 51 to data lines DQ[11:8], stack S10 to data lines DQ[15:12], and so on. The eight 512 Mb DRAM devices in stack S0 may be labeled as S0_M0 through S0_M7 and the eight 512 Mb DRAM devices in stack S9 may be labeled as S9_M0 through S9_M7. In one example, integrated circuits S0_M0 through S0_M3 may be used by the buffer integrated circuit associated with stack S0 to emulate a 2 Gb DRAM integrated circuit that belongs to the first rank (i.e. controlled by integrated circuit select CS0#). Similarly, integrated circuits S0_M4 through S0_M7 may be used by the buffer integrated circuit associated with stack S0 to emulate a 2 Gb DRAM integrated circuit that belongs to the second rank (i.e. controlled by integrated circuit select CS1#). So, in general, integrated circuits Sn_M0 through Sn_M3 may be used to emulate a 2 Gb DRAM integrated circuit that belongs to the first rank while integrated circuits Sn_M4 through Sn_M7 may be used to emulate a 2 Gb DRAM integrated circuit that belongs to the second rank, where n represents the stack number (i.e. 0≦n≦17). It should be noted that the configuration described above is just for illustration. Other configurations may be used to achieve the same result without deviating from the spirit or scope of the claims. For example, integrated circuits S0_M0, S0_M2, S0_M4, and S0_M6 may be grouped together by the associated buffer integrated circuit to emulate a 2 Gb DRAM integrated circuit in the first rank while integrated circuits S0_M1, S0_M3, S0_M5, and S0_M7 may be grouped together by the associated buffer integrated circuit to emulate a 2 Gb DRAM integrated circuit in the second rank of the DIMM.



FIG. 4A illustrates an example of a registered DIMM that uses buffer integrated circuits and DRAM stacks. For simplicity sake, note that the register and clock PLL integrated circuits of a registered DIMM are not shown. The DIMM PCB 400 includes buffered DRAM stacks on the top side of DIMM PCB 400 (e.g., S5) as well as the bottom side of DIMM PCB 400 (e.g., S 15). Each buffered stack emulates two DRAMs. FIG. 4B illustrates a physical stack of DRAM devices in this embodiment. For example, stack 420 comprises eight 4-bit wide, 512 Mb DRAM devices and a buffer integrated circuit 430. As shown in FIG. 4B, a first group of devices, consisting of Sn_M0, Sn_M1, Sn_M2 and Sn_M3, is controlled by CS0#. A second group of devices, which consists of Sn_M4, Sn_M5, Sn_M6 and Sn_M7, is controlled by CS1#. It should be noted that the eight DRAM devices and the buffer integrated circuit are shown as belonging to one stack in FIG. 4B strictly as an example. Other implementations are possible. For example, the buffer integrated circuit 430 may be outside the stack of DRAM devices. Also, the eight DRAM devices may be arranged in multiple stacks.


In an optional variation of the multi-rank embodiment, a single buffer integrated circuit may be associated with a plurality of stacks of DRAM integrated circuits. In the embodiment exemplified in FIGS. 5A and 5B, a buffer integrated circuit is dedicated to two stacks of DRAM integrated circuits. FIG. 5B shows two stacks, one on each side of the DIMM PCB, and one buffer integrated circuit B0 situated on one side of the DIMM PCB. However, this is strictly for the purpose of illustration. The stacks that are associated with a buffer integrated circuit may be on the same side of the DIMM PCB or may be on both sides of the PCB.


In the embodiment exemplified in FIGS. 5A and 5B, each stack of DRAM devices contains eight 512 Mb integrated circuits, the stacks are numbered S0 through S17, and within each stack, the integrated circuits are labeled Sn_M0 through Sn_M7 (where n is 0 through 17). Also, for this example, the buffer integrated circuit is 8-bits wide, and the buffer integrated circuits are numbered B0 through B8. The two integrated circuit select signals, CS0# and CS1#, are connected to buffer B0 as are the data lines DQ[7:0]. As shown, stacks S0 through S8 are the primary stacks and stacks S9 through S17 are optional stacks. The stack S9 is placed on the other side of the DIMM PCB, directly opposite stack S0 (and buffer B0). The integrated circuits in stack S9 are connected to buffer B0. In other words, the DRAM devices in stacks S0 and S9 are connected to buffer B0, which in turn, is connected to the host system. In the case where the DIMM contains only the primary stacks S0 through S8, the eight DRAM devices in stack S0 are emulated by the buffer integrated circuit B0 to appear to the host system as two 2 Gb devices, one of which is controlled by CS0# and the other is controlled by CS1#. In the case where the DIMM contains both the primary stacks S0 through S8 and the optional stacks S9 through S17, the sixteen 512 Mb DRAM devices in stacks S0 and S9 are together emulated by buffer integrated circuit B0 to appear to the host system as two 4 Gb DRAM devices, one of which is controlled by CS0# and the other is controlled by CS1#.


It should be clear from the above description that this architecture decouples the electrical loading on the memory bus from the number of ranks. So, a lower density DIMM can be built with nine stacks (S0 through S8) and nine buffer integrated circuits (B0 through B8), and a higher density DIMM can be built with eighteen stacks (S0 through S17) and nine buffer integrated circuits (B0 through B8). It should be noted that it is not necessary to connect both integrated circuit select signals CS0# and CS1# to each buffer integrated circuit on the DIMM. A single rank lower density DIMM may be built with nine stacks (S0 through S8) and nine buffer integrated circuits (B0 through B8), wherein CS0# is connected to each buffer integrated circuit on the DIMM. Similarly, a single rank higher density DIMM may be built with seventeen stacks (S0 through S17) and nine buffer integrated circuits, wherein CS0# is connected to each buffer integrated circuit on the DIMM.


A DIMM implementing a multi-rank embodiment using a multi-rank buffer is an optional feature for small form factor systems that have a limited number of DIMM slots. For example, consider a processor that has eight integrated circuit select signals, and thus supports up to eight ranks. Such a processor may be capable of supporting four dual-rank DIMMs or eight single-rank DIMMs or any other combination that provides eight ranks Assuming that each rank has y banks and that all the ranks are identical, this processor may keep up to 8*y memory pages open at any given time. In some cases, a small form factor server like a blade or 1 U server may have physical space for only two DIMM slots per processor. This means that the processor in such a small form factor server may have open a maximum of 4*y memory pages even though the processor is capable of maintaining 8*y pages open. For such systems, a DIMM that contains stacks of DRAM devices and multi-rank buffer integrated circuits may be designed such that the processor maintains 8*y memory pages open even though the number of DIMM slots in the system are fewer than the maximum number of slots that the processor may support. One way to accomplish this, is to apportion all the integrated circuit select signals of the host system across all the DIMM slots on the motherboard. For example, if the processor has only two dedicated DIMM slots, then four integrated circuit select signals may be connected to each DIMM connector. However, if the processor has four dedicated DIMM slots, then two integrated circuit select signals may be connected to each DIMM connector.


To illustrate the buffer and DIMM design, say that a buffer integrated circuit is designed to have up to eight integrated circuit select inputs that are accessible to the host system. Each of these integrated circuit select inputs may have a weak pull-up to a voltage between the logic high and logic low voltage levels of the integrated circuit select signals of the host system. For example, the pull-up resistors may be connected to a voltage (VTT) midway between VDDQ and GND (Ground). These pull-up resistors may be on the DIMM PCB. Depending on the design of the motherboard, two or more integrated circuit select signals from the host system may be connected to the DIMM connector, and hence to the integrated circuit select inputs of the buffer integrated circuit. On power up, the buffer integrated circuit may detect a valid low or high logic level on some of its integrated circuit select inputs and may detect VTT on some other integrated circuit select inputs. The buffer integrated circuit may now configure the DRAMs in the stacks such that the number of ranks in the stacks matches the number of valid integrated circuit select inputs.



FIG. 6A illustrates a memory controller that connects to two DIMMS. Memory controller (600) from the host system drives 8 integrated circuit select (CS) lines: CS0# through CS7#. The first four lines (CS0#-CS3#) are used to select memory ranks on a first DIMM (610), and the second four lines (CS4#-CS7#) are used to select memory ranks on a second DIMM (620). FIG. 6B illustrates a buffer and pull-up circuitry on a DIMM used to configure the number of ranks on a DIMM. For this example, buffer 630 includes eight (8) integrated circuits select inputs (CS0#-CS7#). A pull-up circuit on DIMM 610 pulls the voltage on the connected integrated circuit select lines to a midway voltage value (i.e., midway between VDDQ and GND, VTT). CS0#-CS3# are coupled to buffer 630 via the pull-up circuit. CS4#-CS7# are not connected to DIMM 610. Thus, for this example, DIMM 610 configures ranks based on the CS0#-CS3# lines.


Traditional motherboard designs hard wire a subset of the integrated circuit select signals to each DIMM connector. For example, if there are four DIMM connectors per processor, two integrated circuit select signals may be hard wired to each DIMM connector. However, for the case where only two of the four DIMM connectors are populated, only 4*y memory banks are available even though the processor supports 8*y banks because only two of the four DIMM connectors are populated with DIMMs. One method to provide dynamic memory bank availability is to configure a motherboard where all the integrated circuit select signals from the host system are connected to all the DIMM connectors on the motherboard. On power up, the host system queries the number of populated DIMM connectors in the system, and then apportions the integrated circuit selects across the populated connectors.


In one embodiment, the buffer integrated circuits may be programmed on each DIMM to respond only to certain integrated circuit select signals. Again, using the example above of a processor with four dedicated DIMM connectors, consider the case where only two of the four DIMM connectors are populated. The processor may be programmed to allocate the first four integrated circuit selects (e.g., CS0# through CS3#) to the first DIMM connector and allocate the remaining four integrated circuit selects (say, CS4# through CS7#) to the second DIMM connector. Then, the processor may instruct the buffer integrated circuits on the first DIMM to respond only to signals CS0# through CS3# and to ignore signals CS4# through CS7#. The processor may also instruct the buffer integrated circuits on the second DIMM to respond only to signals CS4# through CS7# and to ignore signals CS0# through CS3#. At a later time, if the remaining two DIMM connectors are populated, the processor may then re-program the buffer integrated circuits on the first DIMM to respond only to signals CS0# and CS1#, re-program the buffer integrated circuits on the second DIMM to respond only to signals CS2# and CS3#, program the buffer integrated circuits on the third DIMM to respond to signals CS4# and CS5#, and program the buffer integrated circuits on the fourth DIMM to respond to signals CS6# and CS7#. This approach ensures that the processor of this example is capable of maintaining 8*y pages open irrespective of the number of DIMM connectors that are populated (assuming that each DIMM has the ability to support up to 8 memory ranks). In essence, this approach de-couples the number of open memory pages from the number of DIMMs in the system.



FIGS. 7A and 7B illustrate a memory system that configures the number of ranks in a DIMM based on commands from a host system. FIG. 7A illustrates a configuration between a memory controller and DIMMs. For this embodiment, all the integrated circuit select lines (e.g., CS0#-CS7#) are coupled between memory controller 730 and DIMMs 710 and 720. FIG. 7B illustrates the coupling of integrated circuit select lines to a buffer on a DIMM for configuring the number of ranks based on commands from the host system. For this embodiment, all integrated circuit select lines (CS0#-CS7#) are coupled to buffer 740 on DIMM 710.


Virtualization and multi-core processors are enabling multiple operating systems and software threads to run concurrently on a common hardware platform. This means that multiple operating systems and threads must share the memory in the server, and the resultant context switches could result in increased transfers between the hard disk and memory.


In an embodiment enabling multiple operating systems and software threads to run concurrently on a common hardware platform, the buffer integrated circuit may allocate a set of one or more memory devices in a stack to a particular operating system or software thread, while another set of memory devices may be allocated to other operating systems or threads. In the example of FIG. 6C, the host system (not shown) may operate such that a first operating system is partitioned to a first logical address range 660, corresponding to physical partition 680, and all other operating systems are partitioned to a second logical address range 670, corresponding to a physical partition 690. On a context switch toward the first operating system or thread from another operating system or thread, the host system may notify the buffers on a DIMM or on multiple DIMMs of the nature of the context switch. This may be accomplished, for example, by the host system sending a command or control signal to the buffer integrated circuits either on the signal lines of the memory bus (i.e. in-band signaling) or on separate lines (i.e. side band signaling). An example of side band signaling would be to send a command to the buffer integrated circuits over an SMBus. The buffer integrated circuits may then place the memory integrated circuits allocated to the first operating system or thread 680 in an active state while placing all the other memory integrated circuits allocated to other operating systems or threads 690 (that are not currently being executed) in a low power or power down mode. This optional approach not only reduces the power dissipation in the memory stacks but also reduces accesses to the disk. For example, when the host system temporarily stops execution of an operating system or thread, the memory associated with the operating system or thread is placed in a low power mode but the contents are preserved. When the host system switches back to the operating system or thread at a later time, the buffer integrated circuits bring the associated memory out of the low power mode and into the active state and the operating system or thread may resume the execution from where it left off without having to access the disk for the relevant data. That is, each operating system or thread has a private main memory that is not accessible by other operating systems or threads. Note that this embodiment is applicable for both the single rank and the multi-rank buffer integrated circuits.


When users desire to increase the memory capacity of the host system, the normal method is to populate unused DIMM connectors with memory modules. However, when there are no more unpopulated connectors, users have traditionally removed the smaller capacity memory modules and replaced them with new, larger capacity memory modules. The smaller modules that were removed might be used on other host systems but typical practice is to discard them. It could be advantageous and cost-effective if users could increase the memory capacity of a system that has no unpopulated DIMM connectors without having to discard the modules being currently used.


In one embodiment employing a buffer integrated circuit, a connector or some other interposer is placed on the DIMM, either on the same side of the DIMM PCB as the buffer integrated circuits or on the opposite side of the DIMM PCB from the buffer integrated circuits. When a larger memory capacity is desired, the user may mechanically and electrically couple a PCB containing additional memory stacks to the DIMM PCB by means of the connector or interposer. To illustrate, an example multi-rank registered DIMM may have nine 8-bit wide stacks, where each stack contains a plurality of DRAM devices and a multi-rank buffer. For this example, the nine stacks may reside on one side of the DIMM PCB, and one or more connectors or interposers may reside on the other side of the DIMM PCB. The capacity of the DIMM may now be increased by mechanically and electrically coupling an additional PCB containing stacks of DRAM devices to the DIMM PCB using the connector(s) or interposer(s) on the DIMM PCB. For this embodiment, the multi-rank buffer integrated circuits on the DIMM PCB may detect the presence of the additional stacks and configure themselves to use the additional stacks in one or more configurations employing the additional stacks. It should be noted that it is not necessary for the stacks on the additional PCB to have the same memory capacity as the stacks on the DIMM PCB. In addition, if the stacks on the DIMM PCB may be connected to one integrated circuit select signal while the stacks on the additional PCB may be connected to another integrated circuit select signal. Alternately, the stacks on the DIMM PCB and the stacks on the additional PCB may be connected to the same set of integrated circuit select signals.



FIG. 8 illustrates one embodiment for a DIMM PCB with a connector or interposer with upgrade capability. A DIMM PCB 800 comprises a plurality of buffered stacks, such as buffered stack 830. As shown, buffered stack 830 includes buffer integrated circuit 840 and DRAM devices 850. An upgrade module PCB 810, which connects to DIMM PCB 800 via connector or interposer 880 and 870, includes stacks of DRAMs, such as DRAM stack 820. In this example and as shown in FIG. 8, the upgrade module PCB 810 contains nine 8-bit wide stacks, wherein each stack contains only DRAM integrated circuits 860. Each multi-rank buffer integrated circuit 840 on DIMM PCB 800, upon detection of the additional stack, re-configures itself such that it sits electrically between the host system and the two stacks of DRAM integrated circuits. That is, the buffer integrated circuit is now electrically between the host system and the stack on the DIMM PCB 800 as well as the corresponding stack on the upgrade module PCB 810. However, it should be noted that other embodiments of the buffer integrated circuit (840), the DRAM stacks (820), the DIMM PCB 800, and the upgrade module PCB 810 may be configured in various manners to achieve the same result, without deviating from the spirit or scope of the claims. For example, the stack 820 on the additional PCB may also contain a buffer integrated circuit. So, in this example, the upgrade module 810 may contain one or more buffer integrated circuits.


The buffer integrated circuits may map the addresses from the host system to the DRAM devices in the stacks in several ways. In one embodiment, the addresses may be mapped in a linear fashion, such that a bank of the virtual (or emulated) DRAM is mapped to a set of physical banks, and wherein each physical bank in the set is part of a different physical DRAM device. To illustrate, let us consider a stack containing eight 512 Mb DRAM integrated circuits (i.e. physical DRAM devices), each of which has four memory banks. Let us also assume that the buffer integrated circuit is the multi-rank embodiment such that the host system sees two 2 Gb DRAM devices (i.e. virtual DRAM devices), each of which has eight banks. If we label the physical DRAM devices M0 through M7, then a linear address map may be implemented as shown below.















Host System Address
DRAM Device



(Virtual Bank)
(Physical Bank)








Rank 0, Bank [0]
{(M4, Bank [0]), (M0, Bank [0])}



Rank 0, Bank [1]
{(M4, Bank [1]), (M0, Bank [1]))



Rank 0, Bank [2]
{(M4, Bank [2]), (M0, Bank [2])}



Rank 0, Bank [3]
{(M4, Bank [3]), (M0, Bank [3]))



Rank 0, Bank [4]
{(M6, Bank [0]), (M2, Bank [0]))



Rank 0, Bank [5]
{(M6, Bank [1]), (M2, Bank [1]))



Rank 0, Bank [6]
{(M6, Bank [2]), (M2, Bank [2]))



Rank 0, Bank [7]
{(M6, Bank [3]), (M2, Bank [3]))



Rank 1, Bank [0]
{(M5, Bank [0]), (M1, Bank [0]))



Rank 1, Bank [1]
{(M5, Bank [1]), (M1, Bank [1]))



Rank 1, Bank [2]
{(M5, Bank [2]), (M1, Bank [2]))



Rank 1, Bank [3]
{(M5, Bank [3]), (M1, Bank [3]))



Rank 1, Bank [4]
{(M7, Bank [0]), (M3, Bank [0]))



Rank 1, Bank [5]
{(M7, Bank [1]), (M3, Bank [1]))



Rank 1, Bank [6]
{(M7, Bank [2]), (M3, Bank [2]))



Rank 1, Bank [7]
{(M7, Bank [3]), (M3, Bank [3]))










FIG. 9 illustrates an example of linear address mapping for use with a multi-rank buffer integrated circuit.


An example of a linear address mapping with a single-rank buffer integrated circuit is shown below.













Host System Address
DRAM Device


(Virtual Bank)
(Physical Banks)







Rank 0, Bank [0]
{(M6, Bank [0]), (M4, Bank[0]), (M2, Bank [0]),



(M0, Bank [0])}


Rank 0, Bank [1]
{(M6, Bank [1]), (M4, Bank[1]), (M2, Bank [1]),



(M0, Bank [1])}


Rank 0, Bank [2]
{(M6, Bank [2]), (M4, Bank[2]), (M2, Bank [2]),



(M0, Bank [2])}


Rank 0, Bank [3]
{(M6, Bank [3]), (M4, Bank[3]), (M2, Bank [3]),



(M0, Bank [3])}


Rank 0, Bank [4]
{(M7, Bank [0]), (M5, Bank[0]), (M3, Bank [0]),



(M1, Bank [0])}


Rank 0, Bank [5]
{(M7, Bank [1]), (M5, Bank[1]), (M3, Bank [1]),



(M1, Bank [1])}


Rank 0, Bank [6]
{(M7, Bank [2]), (M5, Bank[2]), (M3, Bank [2]),



(M1, Bank [2])}


Rank 0, Bank [7]
{(M7, Bank [3]), (M5, Bank[3]), (M3, Bank [3]),



(M1, Bank [3])}










FIG. 10 illustrates an example of linear address mapping with a single rank buffer integrated circuit. Using this configuration, the stack of DRAM devices appears as a single 4 Gb integrated circuit with eight memory banks.


In another embodiment, the addresses from the host system may be mapped by the buffer integrated circuit such that one or more banks of the host system address (i.e. virtual banks) are mapped to a single physical DRAM integrated circuit in the stack (“bank slice” mapping). FIG. 11 illustrates an example of bank slice address mapping with a multi-rank buffer integrated circuit. Also, an example of a bank slice address mapping is shown below.















Host System Address
DRAM Device



(Virtual Bank)
(Physical Bank)








Rank 0, Bank [0]
M0, Bank [1:0]



Rank 0, Bank [1]
M0, Bank [3:2]



Rank 0, Bank [2]
M2, Bank [1:0]



Rank 0, Bank [3]
M2, Bank [3:2]



Rank 0, Bank [4]
M4, Bank [1:0]



Rank 0, Bank [5]
M4, Bank [3:2]



Rank 0, Bank [6]
M6, Bank [1:0]



Rank 0, Bank [7]
M6, Bank [3:2]



Rank 1, Bank [0]
M1, Bank [1:0]



Rank 1, Bank [1]
M1, Bank [3:2]



Rank 1, Bank [2]
M3, Bank [1:0]



Rank 1, Bank [3]
M3, Bank [3:2]



Rank 1, Bank [4]
M5, Bank [1:0]



Rank 1, Bank [5]
M5, Bank [3:2]



Rank 1, Bank [6]
M7, Bank [1:0]



Rank 1, Bank [7]
M7, Bank [3:2]









The stack of this example contains eight 512 Mb DRAM integrated circuits, each with four memory banks In this example, a multi-rank buffer integrated circuit is assumed, which means that the host system sees the stack as two 2 Gb DRAM devices, each having eight banks.



FIG. 12 illustrates an example of bank slice address mapping with a single rank buffer integrated circuit. The bank slice mapping with a single-rank buffer integrated circuit is shown below.















Host System Address
DRAM Device



(Virtual Bank)
(Physical Device)








Rank 0, Bank [0]
M0



Rank 0, Bank [1]
M1



Rank 0, Bank [2]
M2



Rank 0, Bank [3]
M3



Rank 0, Bank [4]
M4



Rank 0, Bank [5]
M5



Rank 0, Bank [6]
M6



Rank 0, Bank [7]
M7









The stack of this example contains eight 512 Mb DRAM devices so that the host system sees the stack as a single 4 Gb device with eight banks. The address mappings shown above are for illustrative purposes only. Other mappings may be implemented without deviating from the spirit and scope of the claims.


Bank slice address mapping enables the virtual DRAM to reduce or eliminate some timing constraints that are inherent in the underlying physical DRAM devices. For instance, the physical DRAM devices may have a tFAW (4 bank activate window) constraint that limits how frequently an activate operation may be targeted to a physical DRAM device. However, a virtual DRAM circuit that uses bank slice address mapping may not have this constraint. As an example, the address mapping in FIG. 11 maps two banks of the virtual DRAM device to a single physical DRAM device. So, the tFAW constraint is eliminated because the tRC timing parameter prevents the host system from issuing more than two consecutive activate commands to any given physical DRAM device within a tRC window (and tRC>tFAW). Similarly, a virtual DRAM device that uses the address mapping in FIG. 12 eliminates the tRRD constraint of the underlying physical DRAM devices.


In addition, a bank slice address mapping scheme enables the buffer integrated circuit or the host system to power manage the DRAM devices on a DIMM on a more granular level. To illustrate this, consider a virtual DRAM device that uses the address mapping shown in FIG. 12, where each bank of the virtual DRAM device corresponds to a single physical DRAM device. So, when bank 0 of the virtual DRAM device (i.e. virtual bank 0) is accessed, the corresponding physical DRAM device M0 may be in the active mode. However, when there is no outstanding access to virtual bank 0, the buffer integrated circuit or the host system (or any other entity in the system) may place DRAM device M0 in a low power (e.g. power down) mode. While it is possible to place a physical DRAM device in a low power mode, it is not possible to place a bank (or portion) of a physical DRAM device in a low power mode while the remaining banks (or portions) of the DRAM device are in the active mode. However, a bank or set of banks of a virtual DRAM circuit may be placed in a low power mode while other banks of the virtual DRAM circuit are in the active mode since a plurality of physical DRAM devices are used to emulate a virtual DRAM device. It can be seen from FIG. 12 and FIG. 10, for example, that fewer virtual banks are mapped to a physical DRAM device with bank slice mapping (FIG. 12) than with linear mapping (FIG. 10). Thus, the likelihood that all the (physical) banks in a physical DRAM device are in the precharge state at any given time is higher with bank slice mapping than with linear mapping. Therefore, the buffer integrated circuit or the host system (or some other entity in the system) has more opportunities to place various physical DRAM devices in a low power mode when bank slide mapping is used.


In several market segments, it may be desirable to preserve the contents of main memory (usually, DRAM) either periodically or when certain events occur. For example, in the supercomputer market, it is common for the host system to periodically write the contents of main memory to the hard drive. That is, the host system creates periodic checkpoints. This method of checkpointing enables the system to re-start program execution from the last checkpoint instead of from the beginning in the event of a system crash. In other markets, it may be desirable for the contents of one or more address ranges to be periodically stored in non-volatile memory to protect against power failures or system crashes. All these features may be optionally implemented in a buffer integrated circuit disclosed herein by integrating one or more non-volatile memory integrated circuits (e.g. flash memory) into the stack. In some embodiments, the buffer integrated circuit is designed to interface with one or more stacks containing DRAM devices and non-volatile memory integrated circuits. Note that each of these stacks may contain only DRAM devices or contain only non-volatile memory integrated circuits or contain a mixture of DRAM and non-volatile memory integrated circuits.



FIGS. 13A and 13B illustrate examples of buffered stacks that contain both DRAM and non-volatile memory integrated circuits. A DIMM PCB 1300 includes a buffered stack (buffer 1310 and DRAMs 1320) and flash 1330. In another embodiment shown in FIG. 13B, DIMM PCB 1340 includes a buffered stack (buffer 1350, DRAMs 1360 and flash 1370). An optional non-buffered stack includes at least one non-volatile memory device (e.g., flash 1390) or DRAM device 1380. All the stacks that connect to a buffer integrated circuit may be on the same PCB as the buffer integrated circuit or some of the stacks may be on the same PCB while other stacks may be on another PCB that is electrically and mechanically coupled by means of a connector or an interposer to the PCB containing the buffer integrated circuit.


In some embodiments, the buffer integrated circuit copies some or all of the contents of the DRAM devices in the stacks that it interfaces with to the non-volatile memory integrated circuits in the stacks that it interfaces with. This event may be triggered, for example, by a command or signal from the host system to the buffer integrated circuit, by an external signal to the buffer integrated circuit, or upon the detection (by the buffer integrated circuit) of an event or a catastrophic condition like a power failure. As an example, let us assume that a buffer integrated circuit interfaces with a plurality of stacks that contain 4 Gb of DRAM memory and 4 Gb of non-volatile memory. The host system may periodically issue a command to the buffer integrated circuit to copy the contents of the DRAM memory to the non-volatile memory. That is, the host system periodically checkpoints the contents of the DRAM memory. In the event of a system crash, the contents of the DRAM may be restored upon re-boot by copying the contents of the non-volatile memory back to the DRAM memory. This provides the host system with the ability to periodically check point the memory.


In another embodiment, the buffer integrated circuit may monitor the power supply rails (i.e. voltage rails or voltage planes) and detect a catastrophic event, for example, a power supply failure. Upon detection of this event, the buffer integrated circuit may copy some or all the contents of the DRAM memory to the non-volatile memory. The host system may also provide a non-interruptible source of power to the buffer integrated circuit and the memory stacks for at least some period of time after the power supply failure to allow the buffer integrated circuit to copy some or all the contents of the DRAM memory to the non-volatile memory. In other embodiments, the memory module may have a built-in backup source of power for the buffer integrated circuits and the memory stacks in the event of a host system power supply failure. For example, the memory module may have a battery or a large capacitor and an isolation switch on the module itself to provide backup power to the buffer integrated circuits and the memory stacks in the event of a host system power supply failure.


A memory module, as described above, with a plurality of buffers, each of which interfaces to one or more stacks containing DRAM and non-volatile memory integrated circuits, may also be configured to provide instant-on capability. This may be accomplished by storing the operating system, other key software, and frequently used data in the non-volatile memory.


In the event of a system crash, the memory controller of the host system may not be able to supply all the necessary signals needed to maintain the contents of main memory. For example, the memory controller may not send periodic refresh commands to the main memory, thus causing the loss of data in the memory. The buffer integrated circuit may be designed to prevent such loss of data in the event of a system crash. In one embodiment, the buffer integrated circuit may monitor the state of the signals from the memory controller of the host system to detect a system crash. As an example, the buffer integrated circuit may be designed to detect a system crash if there has been no activity on the memory bus for a pre-determined or programmable amount of time or if the buffer integrated circuit receives an illegal or invalid command from the memory controller. Alternately, the buffer integrated circuit may monitor one or more signals that are asserted when a system error or system halt or system crash has occurred. For example, the buffer integrated circuit may monitor the HT_SyncFlood signal in an Opteron processor based system to detect a system error. When the buffer integrated circuit detects this event, it may de-couple the memory bus of the host system from the memory integrated circuits in the stack and internally generate the signals needed to preserve the contents of the memory integrated circuits until such time as the host system is operational. So, for example, upon detection of a system crash, the buffer integrated circuit may ignore the signals from the memory controller of the host system and instead generate legal combinations of signals like CKE, CS#, RAS#, CAS#, and WE# to maintain the data stored in the DRAM devices in the stack, and also generate periodic refresh signals for the DRAM integrated circuits. Note that there are many ways for the buffer integrated circuit to detect a system crash, and all these variations fall within the scope of the claims.


Placing a buffer integrated circuit between one or more stacks of memory integrated circuits and the host system allows the buffer integrated circuit to compensate for any skews or timing variations in the signals from the host system to the memory integrated circuits and from the memory integrated circuits to the host system. For example, at higher speeds of operation of the memory bus, the trace lengths of signals between the memory controller of the host system and the memory integrated circuits are often matched. Trace length matching is challenging especially in small form factor systems. Also, DRAM processes do not readily lend themselves to the design of high speed I/O circuits. Consequently, it is often difficult to align the I/O signals of the DRAM integrated circuits with each other and with the associated data strobe and clock signals.


In one embodiment of a buffer integrated circuit, circuitry that adjusts the timing of the I/O signals may be incorporated. In other words, the buffer integrated circuit may have the ability to do per-pin timing calibration to compensate for skews or timing variations in the I/0 signals. For example, say that, the DQ[0] data signal between the buffer integrated circuit and the memory controller has a shorter trace length or has a smaller capacitive load than the other data signals, DQ[7:1]. This results in a skew in the data signals since not all the signals arrive at the buffer integrated circuit (during a memory write) or at the memory controller (during a memory read) at the same time. When left uncompensated, such skews tend to limit the maximum frequency of operation of the memory sub-system of the host system. By incorporating per-pin timing calibration and compensation circuits into the I/0 circuits of the buffer integrated circuit, the DQ[0] signal may be driven later than the other data signals by the buffer integrated circuit (during a memory read) to compensate for the shorter trace length of the DQ[O] signal. Similarly, the per-pin timing calibration and compensation circuits allow the buffer integrated circuit to delay the DQ[O] data signal such that all the data signals, DQ[7:0], are aligned for sampling during a memory write operation. The per-pin timing calibration and compensation circuits also allow the buffer integrated circuit to compensate for timing variations in the I/O pins of the DRAM devices. A specific pattern or sequence may be used by the buffer integrated circuit to perform the per-pin timing calibration of the signals that connect to the memory controller of the host system and the per-pin timing calibration of the signals that connect to the memory devices in the stack.


Incorporating per-pin timing calibration and compensation circuits into the buffer integrated circuit also enables the buffer integrated circuit to gang a plurality of slower DRAM devices to emulate a higher speed DRAM integrated circuit to the host system. That is, incorporating per-pin timing calibration and compensation circuits into the buffer integrated circuit also enables the buffer integrated circuit to gang a plurality of DRAM devices operating at a first clock speed and emulate to the host system one or more DRAM integrated circuits operating at a second clock speed, wherein the first clock speed is slower than the second clock speed.


For example, the buffer integrated circuit may operate two 8-bit wide DDR2 SDRAM devices-in parallel at a 533 MHz data rate such that the host system sees a single 8-bit wide DDR2 SDRAM integrated circuit that operates at a 1066 MHz data rate. Since, in this example, the two DRAM devices are DDR2 devices, they are designed to transmit or receive four data bits on each data pin for a memory read or write respectively (for a burst length of 4). So, the two DRAM devices operating in parallel may transmit or receive sixty four bits per data pin per memory read or write respectively in this example. Since the host system sees a single DDR2 integrated circuit behind the buffer, it will only receive or transmit thirty-two data bits per pin per memory read or write respectively. In order to accommodate for the different data widths, the buffer integrated circuit may make use of the DM signal (Data Mask). Say that the host system sends DA[7:0], DB[7:0], DC[7:0], and DD[7:0] to the buffer integrated circuit at a 1066 MHz data rate. The buffer integrated circuit may send DA[7:0], DC[7:0], XX, and XX to the first DDR2 SDRAM integrated circuit and send DB[7:0], DD[7:0], XX, and XX to the second DDR2 SDRAM integrated circuit, where XX denotes data that is masked by the assertion (by the buffer integrated circuit) of the DM inputs to the DDR2 SDRAM integrated circuits.


In another embodiment, the buffer integrated circuit operates two slower DRAM devices as a single, higher-speed, wider DRAM. To illustrate, the buffer integrated circuit may operate two 8-bit wide DDR2 SDRAM devices running at 533 MHz data rate such that the host system sees a single 16-bit wide DDR2 SDRAM integrated circuit operating at a 1066 MHz data rate. In this embodiment, the buffer integrated circuit may not use the DM signals. In another embodiment, the buffer integrated circuit may be designed to operate two DDR2 SDRAM devices (in this example, 8-bit wide, 533 MHz data rate integrated circuits) in parallel, such that the host system sees a single DDR3 SDRAM integrated circuit (in this example, an 8-bit wide, 1066 MHz data rate, DDR3 device). In another embodiment, the buffer integrated circuit may provide an interface to the host system that is narrower and faster than the interface to the DRAM integrated circuit. For example, the buffer integrated circuit may have a 16-bit wide, 533 MHz data rate interface to one or more DRAM devices but have an 8-bit wide, 1066 MHz data rate interface to the host system.


In addition to per-pin timing calibration and compensation capability, circuitry to control the slew rate (i.e. the rise and fall times), pull-up capability or strength, and pull-down capability or strength may be added to each I/O pin of the buffer integrated circuit or optionally, in common to a group of I/O pins of the buffer integrated circuit. The output drivers and the input receivers of the buffer integrated circuit may have the ability to do pre-emphasis in order to compensate for non-uniformities in the traces connecting the buffer integrated circuit to the host system and to the memory integrated circuits in the stack, as well as to compensate for the characteristics of the I/O pins of the host system and the memory integrated circuits in the stack.


Stacking a plurality of memory integrated circuits (both volatile and non-volatile) has associated thermal and power delivery characteristics. Since it is quite possible that all the memory integrated circuits in a stack may be in the active mode for extended periods of time, the power dissipated by all these integrated circuits may cause an increase in the ambient, case, and junction temperatures of the memory integrated circuits. Higher junction temperatures typically have negative impact on the operation of ICs in general and DRAMs in particular. Also, when a plurality of DRAM devices are stacked on top of each other such that they share voltage and ground rails (i.e. power and ground traces or planes), any simultaneous operation of the integrated circuits may cause large spikes in the voltage and ground rails. For example, a large current may be drawn from the voltage rail when all the DRAM devices in a stack are refreshed simultaneously, thus causing a significant disturbance (or spike) in the voltage and ground rails. Noisy voltage and ground rails affect the operation of the DRAM devices especially at high speeds. In order to address both these phenomena, several inventive techniques are disclosed below.


One embodiment uses a stacking technique wherein one or more layers of the stack have decoupling capacitors rather than memory integrated circuits. For example, every fifth layer in the stack may be a power supply decoupling layer (with the other four layers containing memory integrated circuits). The layers that contain memory integrated circuits are designed with more power and ground balls or pins than are present in the pin out of the memory integrated circuits. These extra power and ground balls are preferably disposed along all the edges of the layers of the stack.



FIGS. 14A, 14B and 14C illustrate one embodiment of a buffered stack with power decoupling layers. As shown in FIG. 14A, DIMM PCB 1400 includes a buffered stack of DRAMs including decoupling layers. Specifically, for this embodiment, the buffered stack includes buffer 1410, a first set of DRAM devices 1420, a first decoupling layer 1430, a second set of DRAM devices 1440, and an optional second decoupling layer 1450. The stack also has an optional heat sink or spreader 1455.



FIG. 14B illustrates top and side views of one embodiment for a DRAM die. A DRAM die 1460 includes a package (stack layer) 1466 with signal/power/GND balls 1462 and one or more extra power/GND balls 1464. The extra power/GND balls 1464 increase thermal conductivity.



FIG. 14C illustrates top and side views of one embodiment of a decoupling layer. A decoupling layer 1475 includes one or more decoupling capacitors 1470, signal/power/GND balls 1485, and one or more extra power/GND balls 1480. The extra power/GND balls 1480 increases thermal conductivity.


The extra power and ground balls, shown in FIGS. 14B and 14C, form thermal conductive paths between the memory integrated circuits and the PCB containing the stacks, and between the memory integrated circuits and optional heat sinks or heat spreaders. The decoupling capacitors in the power supply decoupling layer connect to the relevant power and ground pins in order to provide quiet voltage and ground rails to the memory devices in the stack. The stacking technique described above is one method of providing quiet power and ground rails to the memory integrated circuits of the stack and also to conduct heat away from the memory integrated circuits.


In another embodiment, the noise on the power and ground rails may be reduced by preventing the DRAM integrated circuits in the stack from performing an operation simultaneously. As mentioned previously, a large amount of current will be drawn from the power rails if all the DRAM integrated circuits in a stack perform a refresh operation simultaneously. The buffer integrated circuit may be designed to stagger or spread out the refresh commands to the DRAM integrated circuits in the stack such that the peak current drawn from the power rails is reduced. For example, consider a stack with four 1 Gb DDR2 SDRAM integrated circuits that are emulated by the buffer integrated circuit to appear as a single 4 Gb DDR2 SDRAM integrated circuit to the host system. The JEDEC specification provides for a refresh cycle time (i.e. tRFC) of 400 ns for a 4 Gb DRAM integrated circuit while a 1 Gb DRAM integrated circuit has a tRFC specification of 110 ns. So, when the host system issues a refresh command to the emulated 4 Gb DRAM integrated circuit, it expects the refresh to be done in 400 ns. However, since the stack contains four 1 Gb DRAM integrated circuits, the buffer integrated circuit may issue separate refresh commands to each of the 1 Gb DRAM integrated circuit in the stack at staggered intervals. As an example, upon receipt of the refresh command from the host system, the buffer integrated circuit may issue a refresh command to two of the four 1 Gb DRAM integrated circuits, and 200 ns later, issue a separate refresh command to the remaining two 1 Gb DRAM integrated circuits. Since the 1 Gb DRAM integrated circuits require 110 ns to perform the refresh operation, all four 1 Gb DRAM integrated circuits in the stack will have performed the refresh operation before the 400 ns refresh cycle time (of the 4 Gb DRAM integrated circuit) expires. This staggered refresh operation limits the maximum current that may be drawn from the power rails. It should be noted that other implementations that provide the same benefits are also possible, and are covered by the scope of the claims.


In one embodiment, a device for measuring the ambient, case, or junction temperature of the memory integrated circuits (e.g. a thermal diode) can be embedded into the stack. Optionally, the buffer integrated circuit associated with a given stack may monitor the temperature of the memory integrated circuits. When the temperature exceeds a limit, the buffer integrated circuit may take suitable action to prevent the overheating of and possible damage to the memory integrated circuits. The measured temperature may optionally be made available to the host system.


Other features may be added to the buffer integrated circuit so as to provide optional features. For example, the buffer integrated circuit may be designed to check for memory errors or faults either on power up or when the host system instructs it do so. During the memory check, the buffer integrated circuit may write one or more patterns to the memory integrated circuits in the stack, read the contents back, and compare the data read back with the written data to check for stuck-at faults or other memory faults.


Although the present invention has been described in terms of specific exemplary embodiments, it will be appreciated that various modifications and alterations might be made by those skilled in the art without departing from the spirit and scope of the claims.

Claims
  • 1. A memory module comprising: at least one memory stack that comprises a plurality of dynamic random access memory (DRAM) integrated circuits; anda buffer circuit, coupled to a host system, for interfacing the memory stack to the host system for providing at least one function to the host system;wherein the buffer circuit comprises a circuit for allocating at least one of the DRAM integrated circuits to a first operating system or thread in an active state and allocating at least one other of the DRAM integrated circuits to a second operating system or thread, which is not currently being executed, in a low power or power down mode.
  • 2. The memory module of claim 1, wherein: the memory module further comprises a DIMM, including a plurality of slots, for mounting the DRAM integrated circuits; andthe buffer circuit comprises a circuit to permit the host system to maintain open a maximum number of memory pages even though a number of DIMM slots are fewer than a maximum number of DIMM slots the host system is capable of supporting.
  • 3. The memory module of claim 1, wherein the buffer circuit interfaces the memory stack to the host system so to operate the memory stack as a single DRAM integrated circuit.
  • 4. The memory module of claim 3, wherein the buffer integrated circuit is incorporated as part of the memory stack.
  • 5. The memory module of claim 1, wherein the buffer circuit for mapping addresses for the host system to access data in the DRAM integrated circuits.
  • 6. The memory module of claim 5, wherein the addresses comprise linear addresses.
  • 7. The memory module of claim 5, wherein the addresses comprise bank-slice addresses.
  • 8. The memory module of claim 1, wherein the buffer integrated circuit, includes integrated circuits to enable the buffer integrated circuit to gang a plurality of DRAM devices operating at a first clock speed to emulate to the host system one or more DRAM integrated circuits operating at a second clock speed, the first clock speed slower than the second clock speed.
  • 9. A memory module comprising: at least one memory stack that comprises a plurality of dynamic random access memory (DRAM) integrated circuits;a DIMM, including a plurality of slots, for mounting the DRAM integrated circuits; anda buffer circuit, coupled to a host system, for interfacing the memory stack to the host system and for providing at least one function to the host system, wherein the buffer circuit comprises a circuit operable to permit the host system to maintain open a maximum number of memory pages even though a number of DIMM slots are fewer than a maximum number of DIMM slots the host system is capable of supporting.
  • 10. The memory module of claim 9, wherein the buffer circuit comprises a circuit for allocating at least one of the DRAM integrated circuits to a first operating system or thread in an active state and allocating at least one other of the DRAM integrated circuits to a second operating system or thread, which is not currently being executed, in a low power or power down mode.
  • 11. The memory module of claim 9, wherein the buffer integrated circuit includes integrated circuits to enable the buffer integrated circuit to gang a plurality of DRAM devices operating at a first clock speed to emulate to the host system one or more DRAM integrated circuits operating at a second clock speed, the first dock speed slower than the second dock speed.
  • 12. The memory module of claim 9, wherein the buffer circuit interfaces the memory stack to the host system so to operate the memory stack as a single DRAM integrated circuit.
  • 13. The memory module of claim 12, wherein the buffer integrated circuit is incorporated as part of the memory stack.
  • 14. A memory module comprising: at least one memory stack that comprises a plurality of dynamic random access memory (DRAM) integrated circuits; anda buffer circuit, coupled to a host system, for interfacing the memory stack to the host system for transforming one or more physical parameters between the DRAM integrated circuits and the host system; whereinthe memory module includes a dual rank DIMM for mounting the DRAM integrated circuits; andthe buffer circuit includes a circuit to transform the electrical loading of the dual rank DIMM into a single rank DIMM.
  • 15. The memory module of claim 14, wherein the buffer comprises a module to monitor the power supply rails and to detect a catastrophic event.
  • 16. The memory module as set forth in claim 14, wherein the power supply rails include voltage rails or voltage planes, and the catastrophic event includes a power supply failure.
  • 17. The memory module as set forth in claim 14, wherein the buffer circuit comprises a module to monitor the state of the signals from a memory controller of the host system to detect a system crash.
  • 18. The memory module as set forth in claim 14; wherein the buffer circuit further comprises a module to ignore signals from a memory controller of the host system, to generate legal combinations of signals to maintain data, stored in the DRAM integrated circuits, and to generate periodic refresh signals for the DRAM integrated circuits upon detection of a system crash.
  • 19. The memory module as set forth in claim 14, wherein the buffer circuit further comprises a module to compensate for any skews or timing variations in signals transferred between the host system and the DRAM memory integrated circuits.
  • 20. The memory module as set forth in claim 14, wherein the buffer circuit comprises: a plurality of I/0 pins; anda circuit to control a slew rate, pull-up capability or strength, and pull-down capability or strength to at least one of the I/0 pins.
CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a divisional application of, and claims priority to, U.S. patent application Ser. No. 11/702,981, entitled “Memory Module with Memory Stack and Interface with Enhanced Capabilities,” which was filed on Feb. 5, 2007. U.S. patent application Ser. No. 11/702,981 claims the benefit to U.S. Provisional Patent Application No. 60/772,414, entitled “Multi-Rank Memory Buffer and Memory Stack”, filed on Feb. 9, 2006. U.S. patent application Ser. No. 11/702,981 also claims the benefit to U.S. Provisional Patent Application No. 60/865,624, entitled “Memory Subsystem and Method,” filed on Nov. 13, 2006; and this application is a continuation-in-part and further claims the benefit to U.S. patent application Ser. No. 11/461,437, entitled “Memory Refresh System and Method”, filed on Jul. 31, 2006. The disclosures of the above-identified patent applications are expressly incorporated herein by reference.

US Referenced Citations (844)
Number Name Date Kind
3800292 Curley et al. Mar 1974 A
4069452 Conway et al. Jan 1978 A
4323965 Johnson et al. Apr 1982 A
4334307 Bourgeois et al. Jun 1982 A
4345319 Bernardini et al. Aug 1982 A
4392212 Miyasaka et al. Jul 1983 A
4525921 Carson et al. Jul 1985 A
4566082 Anderson Jan 1986 A
4592019 Huang et al. May 1986 A
4646128 Carson et al. Feb 1987 A
4698748 Juzswik et al. Oct 1987 A
4706166 Go Nov 1987 A
4710903 Hereth et al. Dec 1987 A
4764846 Go Aug 1988 A
4780843 Tietjen Oct 1988 A
4794597 Ooba et al. Dec 1988 A
4796232 House Jan 1989 A
4807191 Flannagan Feb 1989 A
4841440 Yonezu et al. Jun 1989 A
4862347 Rudy Aug 1989 A
4884237 Mueller et al. Nov 1989 A
4887240 Garverick et al. Dec 1989 A
4888687 Allison et al. Dec 1989 A
4899107 Corbett et al. Feb 1990 A
4912678 Mashiko Mar 1990 A
4922451 Lo et al. May 1990 A
4935734 Austin Jun 1990 A
4937791 Steele et al. Jun 1990 A
4956694 Eide Sep 1990 A
4982365 Ohtani et al. Jan 1991 A
4983533 Go Jan 1991 A
5025364 Zellmer Jun 1991 A
5072424 Brent et al. Dec 1991 A
5083266 Watanabe Jan 1992 A
5104820 Go et al. Apr 1992 A
5193072 Frenkil et al. Mar 1993 A
5212666 Takeda May 1993 A
5220672 Nakao et al. Jun 1993 A
5222014 Lin Jun 1993 A
5241266 Ahmad et al. Aug 1993 A
5252807 Chizinsky Oct 1993 A
5257233 Schaefer Oct 1993 A
5278796 Tillinghast et al. Jan 1994 A
5282177 McLaury Jan 1994 A
5332922 Oguchi et al. Jul 1994 A
5347428 Carson et al. Sep 1994 A
5369749 Baker et al. Nov 1994 A
5384745 Konishi et al. Jan 1995 A
5388265 Volk Feb 1995 A
5390334 Harrison Feb 1995 A
5392251 Manning Feb 1995 A
5408190 Wood et al. Apr 1995 A
5432729 Carson et al. Jul 1995 A
5448511 Paurus et al. Sep 1995 A
5453434 Albaugh et al. Sep 1995 A
5467455 Gay et al. Nov 1995 A
5483497 Mochizuki et al. Jan 1996 A
5498886 Hsu et al. Mar 1996 A
5502333 Bertin et al. Mar 1996 A
5502667 Bertin et al. Mar 1996 A
5513135 Dell et al. Apr 1996 A
5513339 Agrawal et al. Apr 1996 A
5519832 Warchol May 1996 A
5526320 Zagar et al. Jun 1996 A
5530836 Busch et al. Jun 1996 A
5550781 Sugawara et al. Aug 1996 A
5559990 Cheng et al. Sep 1996 A
5561622 Bertin et al. Oct 1996 A
5563086 Bertin et al. Oct 1996 A
5566344 Hall et al. Oct 1996 A
5581498 Ludwig et al. Dec 1996 A
5581779 Hall et al. Dec 1996 A
5590071 Kolor et al. Dec 1996 A
5598376 Merritt et al. Jan 1997 A
5604714 Manning et al. Feb 1997 A
5606710 Hall et al. Feb 1997 A
5608262 Degani et al. Mar 1997 A
5610864 Manning Mar 1997 A
5623686 Hall et al. Apr 1997 A
5627791 Wright et al. May 1997 A
5640337 Huang et al. Jun 1997 A
5640364 Merritt et al. Jun 1997 A
5652724 Manning Jul 1997 A
5654204 Anderson Aug 1997 A
5661677 Rondeau et al. Aug 1997 A
5661695 Zagar et al. Aug 1997 A
5668773 Zagar et al. Sep 1997 A
5675549 Ong et al. Oct 1997 A
5680342 Frankeny Oct 1997 A
5682354 Manning Oct 1997 A
5692121 Bozso et al. Nov 1997 A
5692202 Kardach et al. Nov 1997 A
5696732 Zagar et al. Dec 1997 A
5696929 Hasbun et al. Dec 1997 A
5702984 Bertin et al. Dec 1997 A
5703813 Manning et al. Dec 1997 A
5706247 Merritt et al. Jan 1998 A
RE35733 Hernandez et al. Feb 1998 E
5717654 Manning Feb 1998 A
5721859 Manning Feb 1998 A
5724288 Cloud et al. Mar 1998 A
5729503 Manning Mar 1998 A
5729504 Cowles Mar 1998 A
5742792 Yanai et al. Apr 1998 A
5748914 Barth et al. May 1998 A
5752045 Chen May 1998 A
5757703 Merritt et al. May 1998 A
5760478 Bozso et al. Jun 1998 A
5761703 Bolyn Jun 1998 A
5781766 Davis Jul 1998 A
5787457 Miller et al. Jul 1998 A
5798961 Heyden et al. Aug 1998 A
5802395 Connolly et al. Sep 1998 A
5802555 Shigeeda Sep 1998 A
5812488 Zagar et al. Sep 1998 A
5819065 Chilton et al. Oct 1998 A
5831833 Shirakawa et al. Nov 1998 A
5831931 Manning Nov 1998 A
5831932 Merritt et al. Nov 1998 A
5834838 Anderson Nov 1998 A
5835435 Bogin et al. Nov 1998 A
5838165 Chatter Nov 1998 A
5838177 Keeth Nov 1998 A
5841580 Farmwald et al. Nov 1998 A
5843799 Hsu et al. Dec 1998 A
5843807 Burns Dec 1998 A
5845108 Yoo et al. Dec 1998 A
5850368 Ong et al. Dec 1998 A
5859792 Rondeau et al. Jan 1999 A
5860106 Domen et al. Jan 1999 A
5870347 Keeth et al. Feb 1999 A
5870350 Bertin et al. Feb 1999 A
5872907 Griess et al. Feb 1999 A
5875142 Chevallier Feb 1999 A
5878279 Athenes Mar 1999 A
5884088 Kardach et al. Mar 1999 A
5901105 Ong et al. May 1999 A
5903500 Tsang et al. May 1999 A
5905688 Park May 1999 A
5907512 Parkinson et al. May 1999 A
5910010 Nishizawa et al. Jun 1999 A
5913072 Wierenga Jun 1999 A
5915105 Farmwald et al. Jun 1999 A
5915167 Leedy Jun 1999 A
5917758 Keeth Jun 1999 A
5923611 Ryan Jul 1999 A
5924111 Huang et al. Jul 1999 A
5926435 Park et al. Jul 1999 A
5929650 Pappert et al. Jul 1999 A
5943254 Bakeman, Jr. et al. Aug 1999 A
5946265 Cowles Aug 1999 A
5949254 Keeth Sep 1999 A
5953215 Karabatsos Sep 1999 A
5953263 Farmwald et al. Sep 1999 A
5954804 Farmwald et al. Sep 1999 A
5956233 Yew et al. Sep 1999 A
5962435 Mao et al. Oct 1999 A
5963429 Chen Oct 1999 A
5963463 Rondeau et al. Oct 1999 A
5963464 Dell et al. Oct 1999 A
5963504 Manning Oct 1999 A
5966724 Ryan Oct 1999 A
5966727 Nishino Oct 1999 A
5969996 Muranaka et al. Oct 1999 A
5973392 Senba et al. Oct 1999 A
5978304 Crafts Nov 1999 A
5995424 Lawrence et al. Nov 1999 A
5995443 Farmwald et al. Nov 1999 A
6001671 Fjelstad Dec 1999 A
6002613 Cloud et al. Dec 1999 A
6002627 Chevallier Dec 1999 A
6014339 Kobayashi et al. Jan 2000 A
6016282 Keeth Jan 2000 A
6026027 Terrell, II et al. Feb 2000 A
6026050 Baker et al. Feb 2000 A
6029250 Keeth Feb 2000 A
6032214 Farmwald et al. Feb 2000 A
6032215 Farmwald et al. Feb 2000 A
6034916 Lee Mar 2000 A
6034918 Farmwald et al. Mar 2000 A
6035365 Farmwald et al. Mar 2000 A
6038195 Farmwald et al. Mar 2000 A
6038673 Benn et al. Mar 2000 A
6044032 Li Mar 2000 A
6047073 Norris et al. Apr 2000 A
6047344 Kawasumi et al. Apr 2000 A
6047361 Ingenio et al. Apr 2000 A
6053948 Vaidyanathan et al. Apr 2000 A
6058451 Bermingham et al. May 2000 A
6065092 Roy May 2000 A
6069504 Keeth May 2000 A
6070217 Connolly et al. May 2000 A
6073223 McAllister et al. Jun 2000 A
6075730 Barth et al. Jun 2000 A
6075744 Tsern et al. Jun 2000 A
6078546 Lee Jun 2000 A
6079025 Fung Jun 2000 A
6084434 Keeth Jul 2000 A
6088290 Ohtake et al. Jul 2000 A
6091251 Wood et al. Jul 2000 A
RE36839 Simmons et al. Aug 2000 E
6101152 Farmwald et al. Aug 2000 A
6101564 Athenes et al. Aug 2000 A
6101612 Jeddeloh Aug 2000 A
6108795 Jeddeloh Aug 2000 A
6111812 Gans et al. Aug 2000 A
6134638 Olarig et al. Oct 2000 A
6154370 Degani et al. Nov 2000 A
6166991 Phelan Dec 2000 A
6181640 Kang Jan 2001 B1
6182184 Farmwald et al. Jan 2001 B1
6199151 Williams et al. Mar 2001 B1
6208168 Rhee Mar 2001 B1
6216246 Shau Apr 2001 B1
6222739 Bhakta et al. Apr 2001 B1
6226709 Goodwin et al. May 2001 B1
6226730 Murdoch et al. May 2001 B1
6233192 Tanaka May 2001 B1
6233650 Johnson et al. May 2001 B1
6240048 Matsubara May 2001 B1
6243282 Rondeau et al. Jun 2001 B1
6252807 Suzuki et al. Jun 2001 B1
6253278 Ryan Jun 2001 B1
6260097 Farmwald et al. Jul 2001 B1
6260154 Jeddeloh Jul 2001 B1
6262938 Lee et al. Jul 2001 B1
6266285 Farmwald et al. Jul 2001 B1
6266292 Tsern et al. Jul 2001 B1
6274395 Weber Aug 2001 B1
6279069 Robinson et al. Aug 2001 B1
6295572 Wu Sep 2001 B1
6298426 Ajanovic Oct 2001 B1
6304511 Gans et al. Oct 2001 B1
6307769 Nuxoll et al. Oct 2001 B1
6314051 Farmwald et al. Nov 2001 B1
6317352 Halbert et al. Nov 2001 B1
6317381 Gans et al. Nov 2001 B1
6324120 Farmwald et al. Nov 2001 B2
6326810 Keeth Dec 2001 B1
6327664 Dell et al. Dec 2001 B1
6330683 Jeddeloh Dec 2001 B1
6336174 Li et al. Jan 2002 B1
6338108 Motomura Jan 2002 B1
6338113 Kubo et al. Jan 2002 B1
6341347 Joy et al. Jan 2002 B1
6343019 Jiang et al. Jan 2002 B1
6343042 Tsern et al. Jan 2002 B1
6353561 Funyu et al. Mar 2002 B1
6356105 Volk Mar 2002 B1
6356500 Cloud et al. Mar 2002 B1
6362656 Rhee Mar 2002 B2
6363031 Phelan Mar 2002 B2
6378020 Farmwald et al. Apr 2002 B2
6381188 Choi et al. Apr 2002 B1
6381668 Lunteren Apr 2002 B1
6389514 Rokicki May 2002 B1
6392304 Butler May 2002 B1
6414868 Wong et al. Jul 2002 B1
6418034 Weber et al. Jul 2002 B1
6421754 Kau et al. Jul 2002 B1
6424532 Kawamura Jul 2002 B2
6426916 Farmwald et al. Jul 2002 B2
6429029 Eldridge et al. Aug 2002 B1
6430103 Nakayama et al. Aug 2002 B2
6434660 Lambert et al. Aug 2002 B1
6437600 Keeth Aug 2002 B1
6438057 Ruckerbauer Aug 2002 B1
6442698 Nizar Aug 2002 B2
6445591 Kwong Sep 2002 B1
6452826 Kim et al. Sep 2002 B1
6452863 Farmwald et al. Sep 2002 B2
6453400 Maesako et al. Sep 2002 B1
6453402 Jeddeloh Sep 2002 B1
6453434 Delp et al. Sep 2002 B2
6455348 Yamaguchi Sep 2002 B1
6457095 Volk Sep 2002 B1
6459651 Lee et al. Oct 2002 B1
6473831 Schade Oct 2002 B1
6476476 Glenn Nov 2002 B1
6480929 Gauthier et al. Nov 2002 B1
6487102 Halbert et al. Nov 2002 B1
6489669 Shimada et al. Dec 2002 B2
6490161 Johnson Dec 2002 B1
6492726 Quek et al. Dec 2002 B1
6493789 Ware et al. Dec 2002 B2
6496440 Manning Dec 2002 B2
6496897 Ware et al. Dec 2002 B2
6498766 Lee et al. Dec 2002 B2
6510097 Fukuyama Jan 2003 B2
6510503 Gillingham et al. Jan 2003 B2
6512392 Fleury et al. Jan 2003 B2
6521984 Matsuura Feb 2003 B2
6526471 Shimomura et al. Feb 2003 B1
6526473 Kim Feb 2003 B1
6526484 Stacovsky et al. Feb 2003 B1
6545895 Li et al. Apr 2003 B1
6546446 Farmwald et al. Apr 2003 B2
6553450 Dodd et al. Apr 2003 B1
6560158 Choi et al. May 2003 B2
6563337 Dour May 2003 B2
6563759 Yahata et al. May 2003 B2
6564281 Farmwald et al. May 2003 B2
6564285 Mills et al. May 2003 B1
6574150 Suyama et al. Jun 2003 B2
6584037 Farmwald et al. Jun 2003 B2
6587912 Leddige et al. Jul 2003 B2
6590822 Hwang et al. Jul 2003 B2
6594770 Sato et al. Jul 2003 B1
6597616 Tsern et al. Jul 2003 B2
6597617 Ooishi et al. Jul 2003 B2
6614700 Dietrich et al. Sep 2003 B2
6618267 Dulal et al. Sep 2003 B1
6618791 Dodd et al. Sep 2003 B1
6621760 Ahmad et al. Sep 2003 B1
6628538 Funaba et al. Sep 2003 B2
6630729 Huang Oct 2003 B2
6631086 Bill et al. Oct 2003 B1
6639820 Khandekar et al. Oct 2003 B1
6646939 Kwak Nov 2003 B2
6650588 Yamagata Nov 2003 B2
6650594 Lee et al. Nov 2003 B1
6657634 Sinclair et al. Dec 2003 B1
6657918 Foss et al. Dec 2003 B2
6657919 Foss et al. Dec 2003 B2
6658016 Dai et al. Dec 2003 B1
6658530 Robertson et al. Dec 2003 B1
6659512 Harper et al. Dec 2003 B1
6664625 Hiruma Dec 2003 B2
6665224 Lehmann et al. Dec 2003 B1
6665227 Fetzer Dec 2003 B2
6668242 Reynov et al. Dec 2003 B1
6674154 Minamio et al. Jan 2004 B2
6683372 Wong et al. Jan 2004 B1
6684292 Piccirillo et al. Jan 2004 B2
6690191 Wu et al. Feb 2004 B2
6697295 Farmwald et al. Feb 2004 B2
6701446 Tsern et al. Mar 2004 B2
6705877 Li et al. Mar 2004 B1
6708144 Merryman et al. Mar 2004 B1
6710430 Minamio et al. Mar 2004 B2
6711043 Friedman et al. Mar 2004 B2
6713856 Tsai et al. Mar 2004 B2
6714891 Dendinger Mar 2004 B2
6724684 Kim Apr 2004 B2
6730540 Siniaguine May 2004 B2
6731009 Jones et al. May 2004 B1
6731527 Brown May 2004 B2
6742098 Halbert et al. May 2004 B1
6744687 Koo et al. Jun 2004 B2
6747887 Halbert et al. Jun 2004 B2
6751113 Bhakta et al. Jun 2004 B2
6751696 Farmwald et al. Jun 2004 B2
6754129 Khateri et al. Jun 2004 B2
6754132 Kyung Jun 2004 B2
6757751 Gene Jun 2004 B1
6762948 Kyun et al. Jul 2004 B2
6765812 Anderson Jul 2004 B2
6766469 Larson et al. Jul 2004 B2
6771526 LaBerge Aug 2004 B2
6772359 Kwak et al. Aug 2004 B2
6779097 Gillingham et al. Aug 2004 B2
6785767 Coulson Aug 2004 B2
6791877 Miura et al. Sep 2004 B2
6795899 Dodd et al. Sep 2004 B2
6799241 Kahn et al. Sep 2004 B2
6801989 Johnson et al. Oct 2004 B2
6807598 Farmwald et al. Oct 2004 B2
6807650 Lamb et al. Oct 2004 B2
6807655 Rehani et al. Oct 2004 B1
6810475 Tardieux Oct 2004 B1
6816991 Sanghani Nov 2004 B2
6819602 Seo et al. Nov 2004 B2
6819617 Hwang et al. Nov 2004 B2
6820163 McCall et al. Nov 2004 B1
6820169 Wilcox et al. Nov 2004 B2
6826104 Kawaguchi et al. Nov 2004 B2
6839290 Ahmad et al. Jan 2005 B2
6845027 Mayer et al. Jan 2005 B2
6845055 Koga et al. Jan 2005 B1
6847582 Pan Jan 2005 B2
6850449 Takahashi Feb 2005 B2
6854043 Hargis et al. Feb 2005 B2
6862202 Schaefer Mar 2005 B2
6862249 Kyung Mar 2005 B2
6862653 Dodd et al. Mar 2005 B1
6873534 Bhakta et al. Mar 2005 B2
6878570 Lyu et al. Apr 2005 B2
6894933 Kuzmenka et al. May 2005 B2
6898683 Nakamura May 2005 B2
6908314 Brown Jun 2005 B2
6912778 Ahn et al. Jul 2005 B2
6914786 Paulsen et al. Jul 2005 B1
6917219 New Jul 2005 B2
6922371 Takahashi et al. Jul 2005 B2
6930900 Bhakta et al. Aug 2005 B2
6930903 Bhakta et al. Aug 2005 B2
6938119 Kohn et al. Aug 2005 B2
6943450 Fee et al. Sep 2005 B2
6944748 Sanches et al. Sep 2005 B2
6947341 Stubbs et al. Sep 2005 B2
6951982 Chye et al. Oct 2005 B2
6952794 Lu Oct 2005 B2
6961281 Wong et al. Nov 2005 B2
6968416 Moy Nov 2005 B2
6968419 Holman Nov 2005 B1
6970968 Holman Nov 2005 B1
6980021 Srivastava et al. Dec 2005 B1
6986118 Dickman Jan 2006 B2
6992501 Rapport Jan 2006 B2
6992950 Foss et al. Jan 2006 B2
7000062 Perego et al. Feb 2006 B2
7003618 Perego et al. Feb 2006 B2
7003639 Tsern et al. Feb 2006 B2
7007095 Chen et al. Feb 2006 B2
7007175 Chang et al. Feb 2006 B2
7010642 Perego et al. Mar 2006 B2
7010736 The et al. Mar 2006 B1
7024518 Halbert et al. Apr 2006 B2
7026708 Cady et al. Apr 2006 B2
7028215 Depew et al. Apr 2006 B2
7028234 Huckaby et al. Apr 2006 B2
7033861 Partridge et al. Apr 2006 B1
7035150 Streif et al. Apr 2006 B2
7043599 Ware et al. May 2006 B1
7043611 McClannahan et al. May 2006 B2
7045396 Crowley et al. May 2006 B2
7045901 Lin et al. May 2006 B2
7046538 Kinsley et al. May 2006 B2
7053470 Sellers et al. May 2006 B1
7053478 Roper et al. May 2006 B2
7058776 Lee Jun 2006 B2
7058863 Kouchi et al. Jun 2006 B2
7061784 Jakobs et al. Jun 2006 B2
7061823 Faue et al. Jun 2006 B2
7066741 Burns et al. Jun 2006 B2
7075175 Kazi et al. Jul 2006 B2
7079396 Gates et al. Jul 2006 B2
7079441 Partsch et al. Jul 2006 B1
7079446 Murtagh et al. Jul 2006 B2
7085152 Ellis et al. Aug 2006 B2
7085941 Li Aug 2006 B2
7089438 Raad Aug 2006 B2
7093101 Aasheim et al. Aug 2006 B2
7103730 Saxena et al. Sep 2006 B2
7111143 Walker Sep 2006 B2
7117309 Bearden Oct 2006 B2
7119428 Tanie et al. Oct 2006 B2
7120727 Lee et al. Oct 2006 B2
7126399 Lee Oct 2006 B1
7127567 Ramakrishnan et al. Oct 2006 B2
7133960 Thompson et al. Nov 2006 B1
7136978 Miura et al. Nov 2006 B2
7138823 Janzen et al. Nov 2006 B2
7149145 Kim et al. Dec 2006 B2
7149824 Johnson Dec 2006 B2
7173863 Conley et al. Feb 2007 B2
7200021 Raghuram Apr 2007 B2
7205789 Karabatsos Apr 2007 B1
7210059 Jeddeloh Apr 2007 B2
7215561 Park et al. May 2007 B2
7218566 Totolos, Jr. et al. May 2007 B1
7224595 Dreps et al. May 2007 B2
7228264 Barrenscheen et al. Jun 2007 B2
7231562 Ohlhoff et al. Jun 2007 B2
7233541 Yamamoto et al. Jun 2007 B2
7234081 Nguyen et al. Jun 2007 B2
7243185 See et al. Jul 2007 B2
7245541 Janzen Jul 2007 B2
7254036 Pauley et al. Aug 2007 B2
7266639 Raghuram Sep 2007 B2
7269042 Kinsley et al. Sep 2007 B2
7269708 Ware Sep 2007 B2
7274583 Park et al. Sep 2007 B2
7277333 Schaefer Oct 2007 B2
7286436 Bhakta et al. Oct 2007 B2
7289386 Bhakta et al. Oct 2007 B2
7296754 Nishizawa et al. Nov 2007 B2
7299330 Gillingham et al. Nov 2007 B2
7302598 Suzuki et al. Nov 2007 B2
7307863 Yen et al. Dec 2007 B2
7317250 Koh et al. Jan 2008 B2
7327613 Lee Feb 2008 B2
7337293 Brittain et al. Feb 2008 B2
7363422 Perego et al. Apr 2008 B2
7366947 Gower et al. Apr 2008 B2
7379316 Rajan May 2008 B2
7386656 Rajan et al. Jun 2008 B2
7392338 Rajan et al. Jun 2008 B2
7408393 Jain et al. Aug 2008 B1
7409492 Tanaka et al. Aug 2008 B2
7414917 Ruckerbauer et al. Aug 2008 B2
7428644 Jeddeloh et al. Sep 2008 B2
7437579 Jeddeloh et al. Oct 2008 B2
7441064 Gaskins Oct 2008 B2
7457122 Lai et al. Nov 2008 B2
7464225 Tsern Dec 2008 B2
7472220 Rajan et al. Dec 2008 B2
7474576 Co et al. Jan 2009 B2
7480147 Hoss et al. Jan 2009 B2
7480774 Ellis et al. Jan 2009 B2
7496777 Kapil Feb 2009 B2
7515453 Rajan Apr 2009 B2
7532537 Solomon et al. May 2009 B2
7539800 Dell et al. May 2009 B2
7573136 Jiang et al. Aug 2009 B2
7580312 Rajan et al. Aug 2009 B2
7581121 Barth et al. Aug 2009 B2
7590796 Rajan et al. Sep 2009 B2
7599205 Rajan Oct 2009 B2
7606245 Ma et al. Oct 2009 B2
7609567 Rajan et al. Oct 2009 B2
7613880 Miura et al. Nov 2009 B2
7619912 Bhakta et al. Nov 2009 B2
7724589 Rajan et al. May 2010 B2
7730338 Rajan et al. Jun 2010 B2
7761724 Rajan et al. Jul 2010 B2
7934070 Brittain et al. Apr 2011 B2
7990797 Moshayedi et al. Aug 2011 B2
8116144 Shaw et al. Feb 2012 B2
20010000822 Dell et al. May 2001 A1
20010003198 Wu Jun 2001 A1
20010011322 Stolt et al. Aug 2001 A1
20010019509 Aho et al. Sep 2001 A1
20010021106 Weber et al. Sep 2001 A1
20010021137 Kai et al. Sep 2001 A1
20010046129 Broglia et al. Nov 2001 A1
20010046163 Yaganawa Nov 2001 A1
20010052062 Lipovski Dec 2001 A1
20020002662 Olarig et al. Jan 2002 A1
20020004897 Kao et al. Jan 2002 A1
20020015340 Batinovich Feb 2002 A1
20020019961 Blodgett Feb 2002 A1
20020034068 Weber et al. Mar 2002 A1
20020038405 Leddige et al. Mar 2002 A1
20020041507 Woo et al. Apr 2002 A1
20020051398 Mizugaki May 2002 A1
20020060945 Ikeda May 2002 A1
20020060948 Chang et al. May 2002 A1
20020064073 Chien May 2002 A1
20020064083 Ryu et al. May 2002 A1
20020089831 Forthun Jul 2002 A1
20020089970 Asada et al. Jul 2002 A1
20020094671 Distefano et al. Jul 2002 A1
20020121650 Minamio et al. Sep 2002 A1
20020121670 Minamio et al. Sep 2002 A1
20020124195 Nizar Sep 2002 A1
20020129204 Leighnor et al. Sep 2002 A1
20020145900 Schaefer Oct 2002 A1
20020165706 Raynham Nov 2002 A1
20020167092 Fee et al. Nov 2002 A1
20020172024 Hui et al. Nov 2002 A1
20020174274 Wu et al. Nov 2002 A1
20020184438 Usui Dec 2002 A1
20030002262 Benisek et al. Jan 2003 A1
20030011993 Summers et al. Jan 2003 A1
20030016550 Yoo et al. Jan 2003 A1
20030021175 Tae Kwak Jan 2003 A1
20030026155 Yamagata Feb 2003 A1
20030026159 Frankowsky et al. Feb 2003 A1
20030035312 Halbert et al. Feb 2003 A1
20030039158 Horiguchi et al. Feb 2003 A1
20030041295 Hou et al. Feb 2003 A1
20030061458 Wilcox et al. Mar 2003 A1
20030061459 Aboulenein et al. Mar 2003 A1
20030083855 Fukuyama May 2003 A1
20030088743 Rader May 2003 A1
20030093614 Kohn et al. May 2003 A1
20030101392 Lee May 2003 A1
20030105932 David et al. Jun 2003 A1
20030110339 Calvignac et al. Jun 2003 A1
20030117875 Lee et al. Jun 2003 A1
20030123389 Russell et al. Jul 2003 A1
20030126338 Dodd et al. Jul 2003 A1
20030127737 Takahashi Jul 2003 A1
20030131160 Hampel et al. Jul 2003 A1
20030145163 Seo et al. Jul 2003 A1
20030158995 Lee et al. Aug 2003 A1
20030164539 Yau Sep 2003 A1
20030164543 Kheng Lee Sep 2003 A1
20030174569 Amidi Sep 2003 A1
20030182513 Dodd et al. Sep 2003 A1
20030183934 Barrett Oct 2003 A1
20030189868 Riesenman et al. Oct 2003 A1
20030189870 Wilcox Oct 2003 A1
20030191888 Klein Oct 2003 A1
20030191915 Saxena et al. Oct 2003 A1
20030200382 Wells et al. Oct 2003 A1
20030200474 Li Oct 2003 A1
20030205802 Segaram et al. Nov 2003 A1
20030206476 Joo Nov 2003 A1
20030217303 Chua-Eoan et al. Nov 2003 A1
20030223290 Park et al. Dec 2003 A1
20030227798 Pax Dec 2003 A1
20030229821 Ma Dec 2003 A1
20030230801 Jiang et al. Dec 2003 A1
20030231540 Lazar et al. Dec 2003 A1
20030231542 Zaharinova-Papazova et al. Dec 2003 A1
20030234664 Yamagata Dec 2003 A1
20040016994 Huang Jan 2004 A1
20040027902 Ooishi et al. Feb 2004 A1
20040034732 Valin et al. Feb 2004 A1
20040034755 LaBerge et al. Feb 2004 A1
20040037133 Park et al. Feb 2004 A1
20040042503 Shaeffer et al. Mar 2004 A1
20040044808 Salmon et al. Mar 2004 A1
20040047228 Chen Mar 2004 A1
20040049624 Salmonsen Mar 2004 A1
20040057317 Schaefer Mar 2004 A1
20040064647 DeWhitt et al. Apr 2004 A1
20040064767 Huckaby et al. Apr 2004 A1
20040083324 Rabinovitz et al. Apr 2004 A1
20040088475 Streif et al. May 2004 A1
20040100837 Lee May 2004 A1
20040117723 Foss Jun 2004 A1
20040123173 Emberling et al. Jun 2004 A1
20040125635 Kuzmenka Jul 2004 A1
20040133736 Kyung Jul 2004 A1
20040139359 Samson et al. Jul 2004 A1
20040145863 Byon Jul 2004 A1
20040151038 Ruckerbauer et al. Aug 2004 A1
20040174765 Seo et al. Sep 2004 A1
20040177079 Gluhovsky et al. Sep 2004 A1
20040178824 Pan Sep 2004 A1
20040184324 Pax Sep 2004 A1
20040186956 Perego et al. Sep 2004 A1
20040188704 Halbert et al. Sep 2004 A1
20040195682 Kimura Oct 2004 A1
20040196732 Lee Oct 2004 A1
20040205433 Gower et al. Oct 2004 A1
20040208173 Di Gregorio Oct 2004 A1
20040225858 Brueggen Nov 2004 A1
20040228166 Braun et al. Nov 2004 A1
20040228196 Kwak et al. Nov 2004 A1
20040228203 Koo Nov 2004 A1
20040230932 Dickmann Nov 2004 A1
20040236877 Burton Nov 2004 A1
20040250989 Im et al. Dec 2004 A1
20040256638 Perego et al. Dec 2004 A1
20040257847 Matsui et al. Dec 2004 A1
20040260957 Jeddeloh et al. Dec 2004 A1
20040264255 Royer Dec 2004 A1
20040268161 Ross Dec 2004 A1
20050018495 Bhakta et al. Jan 2005 A1
20050021874 Georgiou et al. Jan 2005 A1
20050024963 Jakobs et al. Feb 2005 A1
20050027928 Avraham et al. Feb 2005 A1
20050028038 Pomaranski et al. Feb 2005 A1
20050034004 Bunker et al. Feb 2005 A1
20050036350 So et al. Feb 2005 A1
20050041504 Perego et al. Feb 2005 A1
20050044302 Pauley et al. Feb 2005 A1
20050044303 Perego et al. Feb 2005 A1
20050044305 Jakobs et al. Feb 2005 A1
20050047192 Matsui et al. Mar 2005 A1
20050071543 Ellis et al. Mar 2005 A1
20050078532 Ruckerbauer et al. Apr 2005 A1
20050081085 Ellis et al. Apr 2005 A1
20050086548 Haid et al. Apr 2005 A1
20050099834 Funaba et al. May 2005 A1
20050102590 Norris et al. May 2005 A1
20050105318 Funaba et al. May 2005 A1
20050108460 David May 2005 A1
20050127531 Tay et al. Jun 2005 A1
20050132158 Hampel et al. Jun 2005 A1
20050135176 Ramakrishnan et al. Jun 2005 A1
20050138267 Bains et al. Jun 2005 A1
20050138304 Ramakrishnan et al. Jun 2005 A1
20050139977 Nishio et al. Jun 2005 A1
20050141199 Chiou et al. Jun 2005 A1
20050149662 Perego et al. Jul 2005 A1
20050152212 Yang et al. Jul 2005 A1
20050156934 Perego et al. Jul 2005 A1
20050166026 Ware et al. Jul 2005 A1
20050193163 Perego et al. Sep 2005 A1
20050193183 Barth et al. Sep 2005 A1
20050194676 Fukuda et al. Sep 2005 A1
20050194991 Dour et al. Sep 2005 A1
20050195629 Leddige et al. Sep 2005 A1
20050201063 Lee et al. Sep 2005 A1
20050204111 Natarajan Sep 2005 A1
20050207255 Perego et al. Sep 2005 A1
20050210196 Perego et al. Sep 2005 A1
20050223179 Perego et al. Oct 2005 A1
20050224948 Lee et al. Oct 2005 A1
20050232049 Park Oct 2005 A1
20050235119 Sechrest et al. Oct 2005 A1
20050235131 Ware Oct 2005 A1
20050237838 Kwak et al. Oct 2005 A1
20050243635 Schaefer Nov 2005 A1
20050246558 Ku Nov 2005 A1
20050249011 Maeda Nov 2005 A1
20050259504 Murtugh et al. Nov 2005 A1
20050263312 Bolken et al. Dec 2005 A1
20050265506 Foss et al. Dec 2005 A1
20050269715 Yoo Dec 2005 A1
20050278474 Perersen et al. Dec 2005 A1
20050281096 Bhakta et al. Dec 2005 A1
20050281123 Bell et al. Dec 2005 A1
20050283572 Ishihara Dec 2005 A1
20050285174 Saito et al. Dec 2005 A1
20050286334 Saito et al. Dec 2005 A1
20050289292 Morrow et al. Dec 2005 A1
20050289317 Liou et al. Dec 2005 A1
20060002201 Janzen Jan 2006 A1
20060010339 Klein Jan 2006 A1
20060026484 Hollums Feb 2006 A1
20060038597 Becker et al. Feb 2006 A1
20060039204 Cornelius Feb 2006 A1
20060039205 Cornelius Feb 2006 A1
20060041711 Miura et al. Feb 2006 A1
20060041730 Larson Feb 2006 A1
20060044909 Kinsley et al. Mar 2006 A1
20060044913 Klein et al. Mar 2006 A1
20060049502 Goodwin et al. Mar 2006 A1
20060050574 Streif et al. Mar 2006 A1
20060056244 Ware Mar 2006 A1
20060062047 Bhakta et al. Mar 2006 A1
20060067141 Perego et al. Mar 2006 A1
20060085616 Zeighami et al. Apr 2006 A1
20060087900 Bucksch et al. Apr 2006 A1
20060090031 Kirshenbaum et al. Apr 2006 A1
20060090054 Choi et al. Apr 2006 A1
20060106951 Bains May 2006 A1
20060112214 Yeh May 2006 A1
20060112219 Chawla et al. May 2006 A1
20060117152 Amidi et al. Jun 2006 A1
20060117160 Jackson et al. Jun 2006 A1
20060118933 Haba Jun 2006 A1
20060120193 Casper Jun 2006 A1
20060123265 Ruckerbauer et al. Jun 2006 A1
20060126369 Raghuram Jun 2006 A1
20060129712 Raghuram Jun 2006 A1
20060129740 Ruckerbauer et al. Jun 2006 A1
20060129755 Raghuram Jun 2006 A1
20060133173 Jain et al. Jun 2006 A1
20060136791 Nierle Jun 2006 A1
20060149857 Holman Jul 2006 A1
20060149982 Vogt Jul 2006 A1
20060174082 Bellows et al. Aug 2006 A1
20060176744 Stave Aug 2006 A1
20060179262 Brittain et al. Aug 2006 A1
20060179333 Brittain et al. Aug 2006 A1
20060179334 Brittain et al. Aug 2006 A1
20060180926 Mullen et al. Aug 2006 A1
20060181953 Rotenberg et al. Aug 2006 A1
20060195631 Rajamani Aug 2006 A1
20060198178 Kinsley et al. Sep 2006 A1
20060203590 Mori et al. Sep 2006 A1
20060206738 Jeddeloh et al. Sep 2006 A1
20060233012 Sekiguchi et al. Oct 2006 A1
20060236165 Cepulis et al. Oct 2006 A1
20060236201 Gower et al. Oct 2006 A1
20060248261 Jacob et al. Nov 2006 A1
20060248387 Nicholson et al. Nov 2006 A1
20060262586 Solomon et al. Nov 2006 A1
20060262587 Matsui et al. Nov 2006 A1
20060277355 Ellsberry et al. Dec 2006 A1
20060294295 Fukuzo Dec 2006 A1
20070005998 Jain et al. Jan 2007 A1
20070050530 Rajan Mar 2007 A1
20070058471 Rajan et al. Mar 2007 A1
20070070669 Tsern Mar 2007 A1
20070088995 Tsern et al. Apr 2007 A1
20070091696 Niggemeier et al. Apr 2007 A1
20070106860 Foster, Sr. et al. May 2007 A1
20070136537 Doblar et al. Jun 2007 A1
20070162700 Fortin et al. Jul 2007 A1
20070188997 Hockanson et al. Aug 2007 A1
20070192563 Rajan et al. Aug 2007 A1
20070195613 Rajan et al. Aug 2007 A1
20070204075 Rajan et al. Aug 2007 A1
20070216445 Raghavan et al. Sep 2007 A1
20070247194 Jain Oct 2007 A1
20070279084 Oh et al. Dec 2007 A1
20070288683 Panabaker et al. Dec 2007 A1
20070288686 Arcedera et al. Dec 2007 A1
20070288687 Panabaker et al. Dec 2007 A1
20080002447 Gulachenski et al. Jan 2008 A1
20080010435 Smith et al. Jan 2008 A1
20080025108 Rajan et al. Jan 2008 A1
20080025122 Schakel et al. Jan 2008 A1
20080025136 Rajan et al. Jan 2008 A1
20080025137 Rajan et al. Jan 2008 A1
20080027697 Rajan et al. Jan 2008 A1
20080027702 Rajan et al. Jan 2008 A1
20080027703 Rajan et al. Jan 2008 A1
20080028135 Rajan et al. Jan 2008 A1
20080028136 Schakel et al. Jan 2008 A1
20080028137 Schakel et al. Jan 2008 A1
20080031030 Rajan et al. Feb 2008 A1
20080031072 Rajan et al. Feb 2008 A1
20080034130 Perego et al. Feb 2008 A1
20080037353 Rajan et al. Feb 2008 A1
20080056014 Rajan et al. Mar 2008 A1
20080062773 Rajan et al. Mar 2008 A1
20080065820 Gillingham et al. Mar 2008 A1
20080082763 Rajan et al. Apr 2008 A1
20080086588 Danilak et al. Apr 2008 A1
20080089034 Hoss et al. Apr 2008 A1
20080098277 Hazelzet Apr 2008 A1
20080103753 Rajan et al. May 2008 A1
20080104314 Rajan et al. May 2008 A1
20080109206 Rajan et al. May 2008 A1
20080109595 Rajan et al. May 2008 A1
20080109597 Schakel et al. May 2008 A1
20080109598 Schakel et al. May 2008 A1
20080115006 Smith et al. May 2008 A1
20080120443 Rajan et al. May 2008 A1
20080120458 Gillingham et al. May 2008 A1
20080123459 Rajan et al. May 2008 A1
20080126624 Prete et al. May 2008 A1
20080126687 Rajan et al. May 2008 A1
20080126688 Rajan et al. May 2008 A1
20080126689 Rajan et al. May 2008 A1
20080126690 Rajan et al. May 2008 A1
20080126692 Rajan et al. May 2008 A1
20080130364 Guterman et al. Jun 2008 A1
20080133825 Rajan et al. Jun 2008 A1
20080155136 Hishino Jun 2008 A1
20080159027 Kim Jul 2008 A1
20080170425 Rajan Jul 2008 A1
20080195894 Schreck et al. Aug 2008 A1
20080215832 Allen et al. Sep 2008 A1
20080239857 Rajan et al. Oct 2008 A1
20080239858 Rajan et al. Oct 2008 A1
20080256282 Guo et al. Oct 2008 A1
20080282084 Hatakeyama Nov 2008 A1
20080282341 Hatakeyama Nov 2008 A1
20090024789 Rajan et al. Jan 2009 A1
20090024790 Rajan et al. Jan 2009 A1
20090049266 Kuhne Feb 2009 A1
20090063865 Berenbaum et al. Mar 2009 A1
20090063896 Lastras-Montano et al. Mar 2009 A1
20090070520 Mizushima Mar 2009 A1
20090089480 Wah et al. Apr 2009 A1
20090109613 Legen et al. Apr 2009 A1
20090216939 Smith et al. Aug 2009 A1
20090285031 Rajan et al. Nov 2009 A1
20090290442 Rajan Nov 2009 A1
20100005218 Gower et al. Jan 2010 A1
20100020585 Rajan Jan 2010 A1
20100257304 Rajan et al. Oct 2010 A1
20100271888 Rajan Oct 2010 A1
20100281280 Rajan et al. Nov 2010 A1
Foreign Referenced Citations (31)
Number Date Country
102004051345 May 2005 DE
102004053316 May 2006 DE
102005036528 Feb 2007 DE
0644547 Mar 1995 EP
62121978 Jun 1987 JP
01171047 Jul 1989 JP
03-029357 Feb 1991 JP
03286234 Dec 1991 JP
2005-298192 Nov 1993 JP
07-141870 Jun 1995 JP
08077097 Mar 1996 JP
11-149775 Jun 1999 JP
2002025255 Jan 2002 JP
3304893 May 2002 JP
2004-327474 Nov 2004 JP
2006236388 Sep 2006 JP
1020040062717 Jul 2004 KR
2005120344 Dec 2005 KR
9505676 Feb 1995 WO
WO 9725674 Jul 1997 WO
9900734 Jan 1999 WO
WO0045270 Aug 2000 WO
0190900 Nov 2001 WO
0197160 Dec 2001 WO
WO2004044754 May 2004 WO
WO2004051645 Jun 2004 WO
WO 2006072040 Jul 2006 WO
2007028109 Mar 2007 WO
2007038225 Apr 2007 WO
2007095080 Aug 2007 WO
2008063251 May 2008 WO
Non-Patent Literature Citations (271)
Entry
Non-Final Office Action from U.S. Appl. No. 12/508,496 Dated Oct. 11, 2011.
Non-Final Office Action from U.S. Appl. No. 11/588,739 Dated Oct. 13, 2011.
Notice of Allowance from U.S. Appl. No. 11/939,432 Dated Oct. 24, 2011.
Non-Final Office Action from U.S. Appl. No. 11/929,631 Dated Nov. 1, 2011.
Non-Final Office Action from U.S. Appl. No. 11/553,372 Dated Nov. 14, 2011.
Notice of Allowance from U.S. Appl. No. 11/515,223 Dated Nov. 29, 2011.
Notice of Allowance from U.S. Appl. No. 12/769,428 Dated Nov. 28, 2011.
Final Office Action from U.S. Appl. No. 11/939,440 Dated Dec. 12, 2011.
Notice of Allowance from U.S. Appl. No. 12/797,557 Dated Dec. 28, 2011.
Office Action, including English translation, from co-pending Japanese application No. 2008-529353, Dated Jan. 10, 2012.
Notice of Allowance from Application No. 12/838,896 Dated Jan. 18, 2012.
Final Office Action from U.S. Appl. No. 11/929,655 Dated Jan. 19, 2012.
Final Office Action from U.S. Appl. No. 12/378,328 Dated Feb. 3, 2012.
Final Office Action from U.S. Appl. No. 11/672,921 Dated Feb. 16, 2012.
Final Office Action from U.S. Appl. No. 11/672,924 Dated Feb. 16, 2012.
Final Office Action from U.S. Appl. No. 11/929,225 Dated Feb. 16, 2012.
International Search Report for Application No. EP12150807 Dated Feb. 16, 2012.
Final Office Action from U.S. Appl. No. 11/828,181 Dated Feb. 23, 2012.
Non-Final Office Action from U.S. Appl. No. 11/461,520 Dated Feb. 29, 2012.
Notice of Allowance from U.S. Appl. No. 12/574,628 Dated Mar. 6, 2012.
Non-Final Office Action from U.S. Appl. No. 13/276,212 Dated Mar. 15, 2012.
Non-Final Office Action from U.S. Appl. No. 13/343,612 Dated Mar. 29, 2012.
Notice of Allowance from U.S. Appl. No. 11/939,440 Dated Mar. 30, 2012.
European Search Report from co-pending European application No. 11194876.6-2212/2450798, Dated Apr. 12, 2012.
European Search Report from co-pending European application No. 11194862.6-2212/2450800, Dated Apr. 12, 2012.
Notice of Allowance from U.S. Appl. No. 11/929,636, Dated Apr. 17, 2012.
Final Office Action from U.S. Appl. No. 11/858,518, Dated Apr. 17, 2012.
European Search Report from co-pending European application No. 11194883.2-2212, Dated Apr. 27, 2012.
Non-Final Office Action from U.S. Appl. No. 11/553,372, Dated May 3, 2012.
Notice of Allowance from U.S. Appl. No. 11/929,631, Dated May 3, 2012.
Non-Final Office Action from U.S. Appl. No. 13/165,713, Dated May 22, 2012.
Non-Final Office Action from U.S. Appl. No. 12/144,396, Dated May 29, 2012.
Non-Final Office Action from U.S. Appl. No. 13/165,713, Dated May 31, 2012.
Non-Final Office Action from U.S. Appl. No. 13/280,251, Dated Jun. 12, 2012.
Final Office Action from U.S. Appl. No. 11/855,805, Dated Jun. 14, 2012.
Office Action, including English translation, from co-pending Japanese application No. 2008-529353, Dated Jul. 31, 2012.
Final Office Action from U.S. Appl. No. 13/315,933, Dated Aug. 24, 2012.
“BIOS and Kernel Developer's Guide (BKDG) for AMD Family 10h Processors,” AMD, 31116 Rev 3.00, Sep. 7, 2007.
Buffer Device for Memory Modules (DIMM), IP.com Prior Art Database: <URL: http://ip.com/IPCOM/000144850>, Feb. 10, 2007, 1 pg.
Final Office Action from U.S. Appl. No. 11/929,571 Dated Mar. 3, 2011.
Final Office Action from U.S. Appl. No. 11/461,240 Dated Jul. 20, 2011.
Final Office Action from U.S. Appl. No. 11/461,420 Mailed Apr. 28, 2010.
Final Office Action from U.S. Appl. No. 11/461,430 mailed on Sep. 8, 2008.
Final Office Action from U.S. Appl. No. 11/461,435 Dated May 13, 2010.
Final Office Action from U.S. Appl. No. 11/461,435 mailed on Jan. 28, 2009.
Final Office Action from U.S. Appl. No. 11/461,435 Mailed Jan. 28, 2009.
Final Office Action from U.S. Appl. No. 11/515,167 Dated Jun. 3, 2010.
Final Office Action from U.S. Appl. No. 11/553,390 Dated Jun. 24, 2010.
Final Office Action from U.S. Appl. No. 11/588,739 Dated Dec. 15, 2010.
Final Office Action from U.S. Appl. No. 11/672,921 Dated Jul. 23, 2010.
Final Office Action from U.S. Appl. No. 11/672,924 Dated Sep. 7, 2010.
Final Office Action from U.S. Appl. No. 11/702,960 Dated Jun. 21, 2010.
Final Office Action from U.S. Appl. No. 11/828,182 Dated Dec. 22, 2010.
Final Office Action from U.S. Appl. No. 11/855,805, Dated May 26, 2011.
Final Office Action from U.S. Appl. No. 11/858,518 Mailed Apr. 21, 2010.
Final Office Action from U.S. Appl. No. 11/929,225 Dated Aug. 27, 2010.
Final Office Action from U.S. Appl. No. 11/929,261 Dated Sep. 7, 2010.
Final Office Action from U.S. Appl. No. 11/929,286 Dated Aug. 20, 2010.
Final Office Action from U.S. Appl. No. 11/929,403 Dated Aug. 31, 2010.
Final Office Action from U.S. Appl. No. 11/929,417 Dated Aug. 31, 2010.
Final Office Action from U.S. Appl. No. 11/929,432 Dated Aug. 20, 2010.
Final Office Action from U.S. Appl. No. 11/929,450 Dated Aug. 20, 2010.
Final Office Action from U.S. Appl. No. 11/929,500 Dated Jun. 24, 2010.
Final Office Action from U.S. Appl. No. 11/929,631 Dated Nov. 18, 2010.
Final Office Action from U.S. Appl. No. 11/929,655 Dated Nov. 22, 2010.
Final Office Action from U.S. Appl. No. 11/939,440 Dated May 19, 2011.
Final Office Action from U.S. Appl. No. 12/057,306 Dated Jun. 15, 2011.
Final Office Action from U.S. Appl. No. 12/507,682 Dated Mar. 29, 2011.
Final Office Action from U.S. Appl. No. 12/574,628 Dated Mar. 3, 2011.
Final Office Action from U.S. Appl. No. 12/769,428 Dated Jun. 16,2011.
Final Rejection from U.S. Appl. No. 11/461,437 Mailed Nov. 10, 2009.
Final Rejection from U.S. Appl. No. 11/762,010 Mailed Dec. 4, 2009.
German Office Action From German Patent Application No. 11 2006 001 810.8-55 Mailed Apr. 20, 2009 (With Translation).
German Office Action from German Patent Application No. 11 2006 002 300.4-55 Dated May 11, 2009 (With Translation).
German Office Action from German Patent Application No. 11 2006 002 300.4-55 Mailed Jun. 5, 2009 (with Translation).
Great Britain Office Action from GB Patent Application No. GB0800734.6 Mailed Mar. 1, 2010.
Great Britain Office Action from GB Patent Application No. GB0803913.3 Mailed Mar. 1, 2010.
International Preliminary Examination Report From PCT Application No. PCT/US07/016385 Dated Feb. 3, 2009.
Non-final Office Action from U.S. Appl. No. 11/461,430 mailed on Feb. 19, 2009.
Non-final Office Action from U.S. Appl. No. 11/461,437 mailed on Jan. 26, 2009.
Non-final Office Action from U.S. Appl. No. 11/939,432 mailed on Feb. 6, 2009.
Non-Final Office Action from U.S. Appl. No. 11/461,420 Dated Jul. 23, 2009.
Non-Final Office Action from U.S. Appl. No. 11/461,430 Mailed Feb. 19, 2009.
Non-Final Office Action from U.S. Appl. No. 11/461,435 Dated Aug. 5, 2009.
Non-Final Office Action from U.S. Appl. No. 11/461,437 Mailed Jan. 26 2009.
Non-Final Office Action from U.S. Appl. No. 11/461,441 Mailed Apr. 2, 2009.
Non-Final Office Action from U.S. Appl. No. 11/515,167 Dated Sep. 25, 2009.
Non-Final Office Action from U.S. Appl. No. 11/515,223 Dated Sep. 22, 2009.
Non-Final Office Action from U.S. Appl. No. 11/538,041 Dated Jun. 10, 2009.
Non-Final Office Action from U.S. Appl. No. 11/553,372 Dated Jun. 25, 2009.
Non-Final Office Action from U.S. Appl. No. 11/553,372 Dated Jan. 5, 2011.
Non-Final Office Action from U.S. Appl. No. 11/553,390 Dated Sep. 9, 2009.
Non-Final Office Action from U.S. Appl. No. 11/553,399 Dated Jul. 7, 2009.
Non-Final Office Action from U.S. Appl. No. 11/588,739 Mailed Dec. 29, 2009.
Non-Final Office Action from U.S. Appl. No. 11/611,374 Mailed Mar. 23, 2009.
Non-Final Office Action from U.S. Appl. No. 11/672,921 Dated May 27, 2011.
Non-Final Office Action from U.S. Appl. No. 11/672,924 Dated Jun. 8, 2011.
Non-Final Office Action from U.S. Appl. No. 11/702,960 Dated Sep. 25, 2009.
Non-Final Office Action from U.S. Appl. No. 11/702,960 Dated Jun. 23, 2011.
Non-Final Office Action from U.S. Appl. No. 11/702,981 Dated Aug. 19, 2009.
Non-Final Office Action from U.S. Appl. No. 11/702,981 Dated Mar. 11, 2009.
Non-Final Office Action from U.S. Appl. No. 11/762,010 Mailed Mar. 20, 2009.
Non-Final Office Action from U.S. Appl. No. 11/762,013 Dated Jun. 5, 2009.
Non-Final Office Action from U.S. Appl. No. 11/763,365 Dated Oct. 28, 2009.
Non-Final Office Action from U.S. Appl. No. 11/828,181 Dated Jun. 27, 2011.
Non-Final Office Action from U.S. Appl. No. 11/828,181 Mailed Mar. 2, 2010.
Non-Final Office Action from U.S. Appl. No. 11/828,182 Dated Jun. 27, 2011.
Non-Final Office Action from U.S. Appl. No. 11/828,182 Mailed Mar. 29, 2010.
Non-Final Office Action from U.S. Appl. No. 11/855,805 Dated Sep. 21, 2010.
Non-Final Office Action from U.S. Appl. No. 11/855,826 Dated Jan. 13, 2011.
Non-Final Office Action from U.S. Appl. No. 11/858,518 Dated Aug. 14, 2009.
Non-Final Office Action from U.S. Appl. No. 11/858,518 Dated Sep. 8, 2010.
Non-Final Office Action from U.S. Appl. No. 11/858,518 Dated Sep. 27, 2011.
Non-Final Office Action from U.S. Appl. No. 11/929,225 Dated Jun. 8, 2011.
Non-Final Office Action from U.S. Appl. No. 11/929,403 Dated Mar. 31, 2011.
Non-Final Office Action from U.S. Appl. No. 11/929,417 Dated Mar. 31, 2011.
Non-Final Office Action from U.S. Appl. No. 11/929,432 Mailed Jan. 14, 2010.
Non-Final Office Action from U.S. Appl. No. 11/929,500 Dated Oct. 13, 2009.
Non-Final Office Action from U.S. Appl. No. 11/929,571 Mailed Mar. 3, 2010.
Non-Final Office Action from U.S. Appl. No. 11/929,631 Mailed Mar. 3, 2010.
Non-Final Office Action from U.S. Appl. No. 11/929,636 Mailed Mar. 9, 2010.
Non-Final Office Action from U.S. Appl. No. 11/929,655 Dated Jun. 24, 2011.
Non-Final Office Action from U.S. Appl. No. 11/929,655 Mailed Mar. 3, 2010.
Non-Final Office Action from U.S. Appl. No. 11/939,432 Mailed Apr. 12, 2010.
Non-Final Office Action from U.S. Appl. No. 11/939,432 Mailed Feb. 6, 2009.
Non-Final Office Action from U.S. Appl. No. 11/939,440 Dated Sep. 17, 2010.
Non-Final Office Action from U.S. Appl. No. 11/941,589 Dated Oct. 1, 2009.
Non-Final Office Action from U.S. Appl. No. 12/057,306 Dated Oct. 8, 2010.
Non-Final Office Action from U.S. Appl. No. 12/111,819 Mailed Apr. 27, 2009.
Non-Final Office Action from U.S. Appl. No. 12/111,828 Mailed Apr. 17, 2009.
Non-Final Office Action from U.S. Appl. No. 12/203,100 Dated Dec. 1, 2010.
Non-Final Office Action from U.S. Appl. No. 12/378,328 Dated Jul. 15, 2011.
Non-Final Office Action from U.S. Appl. No. 12/507,682 Mailed Mar. 8, 2010.
Non-Final Office Action from U.S. Appl. No. 12/574,628 Dated Sep. 20, 2011.
Non-Final Office Action from U.S. Appl. No. 12/769,428 Dated Nov. 8, 2010.
Non-Final Office Action from U.S. Appl. No. 12/797,557 Dated Jun. 21, 2011.
Non-Final Office Action from U.S. Appl. No. 12/816,756 Dated Feb. 7, 2011.
Non-Final Office Action from U.S. Appl. No. 12/838,896 Mailed Dec. 8, 2009.
Non-Final Rejection from U.S. Appl. No. 11/672,921 Mailed Dec. 8, 2009.
Non-Final Rejection from U.S. Appl. No. 11/672,924 Mailed Dec. 14, 2009.
Non-Final Rejection from U.S. Appl. No. 11/929,225 Mailed Dec. 14, 2009.
Non-Final Rejection from U.S. Appl. No. 11/929,261 Mailed Dec. 14, 2009.
Notice of Allowability from U.S. Appl. No. 11/855,826 Dated Aug. 15, 2011.
Notice of Allowance from U.S. Appl. No. 11/641,430 Dated Sep. 10, 2009.
Notice of Allowance from U.S. Appl. No. 11/461,437 Dated Jul. 25, 2011.
Notice of Allowance from U.S. Appl. No. 11/474,075 mailed on Nov. 26, 2008.
Notice of Allowance from U.S. Appl. No. 11/515,223 Dated Feb. 4, 2011.
Notice of Allowance from U.S. Appl. No. 11/553,372 Dated Sep. 30, 2009.
Notice of Allowance from U.S. Appl. No. 11/553,372 Dated Aug. 4, 2010.
Notice of Allowance from U.S. Appl. No. 11/553,399 Dated Oct. 13, 2009.
Notice of Allowance from U.S. Appl. No. 11/553,399 Dated Dec. 3, 2010.
Notice of Allowance from U.S. Appl. No. 11/553,399 Dated Mar. 18, 2011.
Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Sep. 15, 2009.
Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Oct. 29, 2010.
Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Mar. 4, 2011.
Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Jun. 24, 2011.
Notice of Allowance from U.S. Appl. No. 11/611,374 Mailed Nov. 30, 2009.
Notice of Allowance from U.S. Appl. No. 11/702,981 Dated Apr. 25, 2011.
Notice of Allowance from U.S. Appl. No. 11/702,981 Dated Aug. 5, 2011.
Notice of Allowance from U.S. Appl. No. 11/762,010 Dated Oct. 22, 2010.
Notice of Allowance from U.S. Appl. No. 11/762,010 Dated Feb. 18, 2011.
Notice of Allowance from U.S. Appl. No. 11/762,010 Dated Jun. 8, 2011.
Notice of Allowance from U.S. Appl. No. 11/762,013 Dated Aug. 17, 2010.
Notice of Allowance from U.S. Appl. No. 11/762,013 Dated Dec. 7, 2010.
Notice of Allowance from U.S. Appl. No. 11/762,013 Dated Feb. 22, 2011.
Notice of Allowance from U.S. Appl. No. 11/762,013 Dated Jun. 20, 2011.
Notice of Allowance from U.S. Appl. No. 11/763,365 Dated Oct. 20, 2010.
Notice of Allowance from U.S. Appl. No. 11/763,365 Dated Mar. 1, 2011.
Notice of Allowance from U.S. Appl. No. 11/763,365 Dated Jun. 24, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,320 Dated Sep. 29, 2010.
Notice of Allowance from U.S. Appl. No. 11/929,320 Dated May 5, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,483 Dated Oct. 7, 2010.
Notice of Allowance from U.S. Appl. No. 11/929,483 Dated Mar. 4, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,483 Dated Jun. 23, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,500 Dated Feb. 24, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,500 Dated Jun. 13, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,500 Dated Sep. 27, 2011.
Notice of Allowance from U.S. Appl. No. 11/929,571 Dated Sep. 27, 2011.
Notice of Allowance from U.S. Appl. No. 11/939,432 Dated Sep. 24, 2009.
Notice of Allowance from U.S. Appl. No. 11/939,432 Dated Feb. 18, 2011.
Notice of Allowance from U.S. Appl. No. 11/939,432 Mailed Dec. 1, 2009.
Notice of Allowance from U.S. Appl. No. 11/941,589 Dated Oct. 25, 2010.
Notice of Allowance from U.S. Appl. No. 11/941,589 Dated Jun. 15, 2011.
Notice of Allowance from U.S. Appl. No. 11/941,589 Dated Sep. 30, 2011.
Notice of Allowance from U.S. Appl. No. 12/111,819 Mailed Nov. 20, 2009.
Notice of Allowance from U.S. Appl. No. 12/111,828 Mailed Dec. 15 2009.
Notice of Allowance from U.S. Appl. No. 12/144,396 Dated Feb. 1, 2011.
Notice of Allowance from U.S. Appl. No. 12/203,100 Dated Jun. 17, 2011.
Notice of Allowance from U.S. Appl. No. 12/816,756 Dated Oct. 3, 2011.
Notice of Allowance from U.S. Appl. No. 12/838,896 Dated Apr. 19, 2011.
Office Action from U.S. Appl. No. 11/461,427 mailed on Sep. 5, 2008.
Office Action from U.S. Appl. No. 11/474,076 mailed on Nov. 3, 2008.
Office Action from U.S. Appl. No. 11/524,811 mailed on Sep. 17, 2008.
Office Action from U.S. Appl. No. 12/574,628 Dated Jun. 10, 2010.
Preliminary Report on Patentability From PCT Application No. PCT/US06/24360 mailed on Jan. 10, 2008.
Search Report and Written Opinion From PCT Application No. PCT/US07/03460 Dated on Feb. 14, 2008.
Search Report From International PCT Application No. PCT/US06/34390 mailed on Nov. 21, 2007.
Search Report From PCT Application No. PCT/US10/038041 Dated Aug. 23, 2010.
Supplemental European Search Report and Search Opinion issued Sep. 21, 2009 in European Application No. 07870726.2, 8 pp.
Written Opinion From International PCT Application No. PCT/US06/34390 mailed on Nov. 21, 2007.
Written Opinion From PCT Application No. PCT/US06/24360 mailed on Jan. 8, 2007.
Fang et al., W. Power Complexity Analysis of Adiabatic SRAM, 6th Int. Conference on ASIC, vol. 1, Oct. 2005, pp. 334-337.
Kellerbauer “Die Schnelle Million,” with translation, “The quick million.” [online] [Retrieved on Apr. 1, 2008]: Retrieved from the Internet URL: http://et.coremelt.net/html/91/12/276/art.htm; 8 pages.
Notice of Allowance from U.S. Appl. No. 11/515,223 Dated Jul. 30, 2010.
Notice of Allowance from U.S. Appl. No. 11/553,372 Mailed Mar. 12, 2010.
Notice of Allowance from U.S. Appl. No. 11/553,399 Mailed Mar. 22, 2010.
Notice of Allowance from U.S. Appl. No. 11/611,374 Dated Jul. 19, 2010.
Notice of Allowance from U.S. Appl. No. 11/611,374 Mailed Apr. 5, 2010.
Notice of Allowance from U.S. Appl. No. 11/762,010 Dated Jul. 2, 2010.
Notice of Allowance from U.S. Appl. No. 11/763,365 Dated Jun. 29, 2010.
Notice of Allowance from U.S. Appl. No. 12/111,819 Mailed Mar. 10, 2010.
Pavan et al., P. A Complete Model of E2PROM Memory Cells for Circuit Simulations, IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems, vol. 22, No. 8, Aug. 2003, pp. 1072-1079.
Skerlj et al., “Buffer Device for Memory Modules (DIMM),” Qimonda 2006, p. 1.
“Using Two Chip Selects to Enable Quad Rank,” IP.com PriorArtDatabase, copyright IP.com, Inc. 2004.
Wu et al., “eNVy: A Non-Volatile, Main Memory Storage System”, Rice Univeristy, ASPLOS-VI Proceedings—Sixth International Conference on Architectural Support for Programming Languages and Operating Systems, San Jose, California, Oct. 4-7, 1994. SIGARCH Computer Architecture News 23(Special Issue Oct. 1994) pp. 86-97; downloaded Nov. 1994.
Final Office Action from U.S. Appl. No. 13/276,212, Dated Aug. 30, 2012.
Non-Final Office Action from U.S. Appl. No. 13/367,182, Dated Aug. 31, 2012.
Notice of Allowance from U.S. Appl. No. 11/461,420, Dated Sep. 5, 2012.
Final Office Action from U.S. Appl. No. 13/280,251, Dated Sep. 12, 2012.
Non-Final Office Action from U.S. Appl. No. 11/929,225, Dated Sep. 17, 2012.
Notice of Allowance from U.S. Appl. No. 12/508,496, Dated Sep. 17, 2012.
Non-Final Office Action from U.S. Appl. No. 11/672,921, Dated Oct. 1, 2012.
Notice of Allowance from U.S. Appl. No. 12/057,306, Dated Oct. 10, 2012.
Notice of Allowance from U.S. Appl. No. 12/144,396, Dated Oct. 11, 2012.
Non-Final Office Action from U.S. Appl. No. 13/411,489, Dated Oct. 17, 2012.
Non-Final Office Action from U.S. Appl. No. 13/471,283, Dated Dec. 7, 2012.
English translation of Office Action from co-pending Korean patent application No. KR1020087005172, dated Dec. 20, 2012.
Office Action, including English translation, from co-pending Japanese application No. 2008-529353, Dated Dec. 27, 2012.
Office Action from co-pending European patent application No. EP12150798, Dated Jan. 3, 2013.
Final Office Action from U.S. Appl. No. 11/672,924, Dated Feb. 1, 2013.
Non-Final Office Action from U.S. Appl. No. 13/260,650, Dated Feb. 1, 2013.
Notice of Allowance from U.S. Appl. No. 13/141,844, Dated Feb. 5, 2013.
Notice of Allowance from U.S. Appl. No. 13/473,827, Dated Feb. 15, 2013.
Notice of Allowance from U.S. Appl. No. 12/378,328, Dated Feb. 27, 2013.
Non-Final Office Action from U.S. Appl. No. 13/536,093, Dated Mar. 1, 2013.
Office Action from co-pending Japanese patent application No. 2012-132119, Dated Mar. 6, 2013.
Notice of Allowance from U.S. Appl. No. 11/461,435, Dated Mar. 6, 2013.
Notice of Allowance from U.S. Appl. No. 11/515,223, Dated Mar. 18, 2013.
Notice of Allowance from U.S. Appl. No. 13/471,283, Dated Mar. 21, 2013.
Extended European Search Report for co-pending European patent application No. EP12150807.1, dated Feb. 1, 2013, mailed Mar. 22, 2013.
Notice of Allowance from U.S. Appl. No. 13/181,716, Dated Apr. 3, 2013.
English translation of Office Action from co-pending Korean patent application No. KR1020087019582, Dated Mar. 13, 2013.
Notice of Allowance from U.S. Appl. No. 13/618,246, Dated Apr. 23, 2013.
Notice of Allowance from U.S. Appl. No. 13/182,234, Dated May 1, 2013.
Final Office Action from U.S. Appl. No. 13/315,933, Dated May 3, 2013.
English Translation of Office Action from co-pending Korean patent application No. 10-2013-7004006, Dated Apr. 12, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,793, Dated May 6, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,565, Dated May 24, 2013.
Final Office Action from U.S. Appl. No. 11/929,225, Dated May 24, 2013.
Final Office Action from U.S. Appl. No. 11/672,921, Dated May 24, 2013.
Notice of Allowance from U.S. Appl. No. 11/929,631, Dated May 28, 2013.
Notice of Allowance from U.S. Appl. No. 13/620,424, Dated May 29, 2013.
Non-Final Office Action from U.S. Appl. No. 13/455,691, Dated Jun. 4, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,199, Dated Jun. 17, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,207, Dated Jun. 20, 2013.
Non-Final Office Action from U.S. Appl. No. 11/828,182, Dated Jun. 20, 2013.
Final Office Action from U.S. Appl. No. 11/828,181, Dated Jun. 20, 2013.
Notice of Allowance from U.S. Appl. No. 13/597,895, Dated Jun. 25, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,645, Dated Jun. 26, 2013.
Notice of Allowance from U.S. Appl. No. 13/471,283, Dated Jun. 28, 2013.
Notice of Allowance from U.S. Appl. No. 13/181,747, Dated Jul. 9, 2013.
Notice of Allowance from U.S. Appl. No. 11/515,223, Dated Jul. 18, 2013.
Notice of Allowance from U.S. Appl. No. 13/182,234, Dated Jul. 22, 2013.
Notice of Allowance from U.S. Appl. No. 13/181,716, Dated Jul. 22, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,233, Dated Aug. 2, 2013.
Final Office Action from U.S. Appl. No. 13/367,182, Dated Aug. 8, 2013.
Notice of Allowance from U.S. Appl. No. 13/620,425, Dated Aug. 20, 2013.
Notice of Allowance from U.S. Appl. No. 13/615,008, Dated Aug. 15, 2013.
Non-Final Office Action from U.S. Appl. No. 13/620,601, Dated Aug. 23, 2013.
Non-Final Office Action from U.S. Appl. No. 12/507,683, Dated Aug. 27, 2013.
Non-Final Office Action from U.S. Appl. No. 13/315,933, Dated Aug. 27, 2013.
Related Publications (1)
Number Date Country
20120102292 A1 Apr 2012 US
Provisional Applications (2)
Number Date Country
60772414 Feb 2006 US
60865624 Nov 2006 US
Divisions (1)
Number Date Country
Parent 11702981 Feb 2007 US
Child 13341844 US
Continuation in Parts (1)
Number Date Country
Parent 11461437 Jul 2006 US
Child 11702981 US