US20050166006A1 - System including a host connected serially in a chain to one or more memory modules that include a cache - Google Patents
System including a host connected serially in a chain to one or more memory modules that include a cache Download PDFInfo
- Publication number
- US20050166006A1 US20050166006A1 US10/842,298 US84229804A US2005166006A1 US 20050166006 A1 US20050166006 A1 US 20050166006A1 US 84229804 A US84229804 A US 84229804A US 2005166006 A1 US2005166006 A1 US 2005166006A1
- Authority
- US
- United States
- Prior art keywords
- memory
- cache
- recited
- controller
- address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4204—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus
- G06F13/4234—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being a memory bus
- G06F13/4243—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being a memory bus with synchronous protocol
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0215—Addressing or allocation; Relocation with look ahead addressing means
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
- G06F13/1605—Handling requests for interconnection or transfer for access to memory bus based on arbitration
- G06F13/161—Handling requests for interconnection or transfer for access to memory bus based on arbitration with latency improvement
- G06F13/1626—Handling requests for interconnection or transfer for access to memory bus based on arbitration with latency improvement by reordering requests
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
- G06F13/1668—Details of memory controller
- G06F13/1684—Details of memory controller using multiple buses
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4247—Bus transfer protocol, e.g. handshake; Synchronisation on a daisy chain bus
- G06F13/4256—Bus transfer protocol, e.g. handshake; Synchronisation on a daisy chain bus using a clocked protocol
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0862—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches with prefetch
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/60—Details of cache memory
- G06F2212/6022—Using a prefetch buffer or dedicated prefetch cache
Definitions
- This invention relates to computer system memory and, more particularly, to memory module configurations and the memory subsystem topology.
- a motherboard or system board may include a number of memory expansion sockets.
- One or more small circuit boards, referred to as memory modules, may be inserted into the sockets as needed to increase the memory capacity of the computer system.
- Each of the memory modules typically includes multiple memory devices that provide a given amount of memory capacity.
- the memory devices are usually implemented using some type of dynamic random access memory (DRAM).
- DRAM types include synchronous DRAM (SDRAM) as well as the various types of double data rate SDRAM (DDR SDRAM).
- the memory modules are connected to a memory/DRAM controller via a memory bus that includes address, control (including clock signals), and data signals.
- the address, control and data signals may be multiplexed and thus share the same sets of wires.
- the address, control and data signals may use separate wires.
- each of the address and control signals are routed to each expansion socket such that the memory modules, when inserted, are connected in parallel to the memory/DRAM controller.
- parallel bus arrangements For example, depending on the topology of the interconnect, the maximum memory bus speed may be limited due to transmission line effects such as signal reflections.
- the memory/DRAM controller may reside on the same integrated circuit (IC) chip as the system processor, while in other systems the memory/DRAM controller may reside in one IC (e.g., a Northbridge) of a chipset.
- a host is coupled to a serially connected chain of memory modules.
- At least one memory module includes a cache for storing data stored in a system memory.
- system memory may include a respective plurality of memory chips mounted on each memory module.
- each memory module may include a memory control hub including a controller configured to determine whether data associated with a received memory request is stored within the cache.
- a given cache may include a storage for storing cache tags corresponding to the data stored within the given cache.
- the controller is configured to access the cache in response to determining that the data associated with the received memory request is stored within the cache.
- the host includes a memory controller configured to generate memory requests to the memory modules.
- the memory controller may include a storage for storing cache tags corresponding to data stored within each cache.
- the memory control hub includes a controller that may be configured to access the memory chips in response to receiving a memory command having a memory address that matches a memory address associated with the memory chips.
- the controller may be configured to access the cache in response to receiving a memory command having a memory address that matches a memory address associated with the cache.
- FIG. 1 is a block diagram of one embodiment of a system including a serially connected chain of system memory modules.
- FIG. 2 is a block diagram of one embodiment of a memory module of FIG. 1 including one cache implementation.
- FIG. 3 is a block diagram of another embodiment of a memory module of FIG. 1 including another cache implementation.
- FIG. 4 is a block diagram of one embodiment of a system including a serially connected chain of cache memory modules.
- FIG. 5 is a diagram of one embodiment of a memory read packet.
- FIG. 6 is a diagram of one embodiment of a cache memory read packet.
- FIG. 7 is a block diagram of one embodiment of a computer system.
- System 50 includes a host 100 coupled to a system memory 125 via a memory link 1 I A.
- System 50 may be configured to operate as part of a computing device such as a computer system or server system, for example.
- System memory 125 includes a memory module 150 A coupled to a memory module 150 B via a memory link 110 B.
- Memory module 150 B is shown coupled to a memory link 110 C, which may be coupled to an additional memory module (not shown) as desired to form a serially connected chain of memory modules that is coupled to host 100 .
- a memory link 110 C which may be coupled to an additional memory module (not shown) as desired to form a serially connected chain of memory modules that is coupled to host 100 .
- components including a reference number followed by a reference letter may be referred to generally by the reference number alone. For example, when referring generally to all memory modules, reference may be made to memory module 150 .
- memory module 150 A includes a memory control hub 160 A, which is coupled to a plurality of memory devices that are designated memory chip 171 A through 171 N, where N may be any number, as desired.
- memory control hub 160 A may be coupled to the memory chips via any type of memory interconnect.
- the memory interconnect may be a typical address, control and data bus configuration.
- memory module 150 B includes a memory control hub 160 B, which is coupled to a plurality of memory devices that are designated memory chip 181 A through 181 N, where N may be any number, as desired.
- memory control hub 160 B may be coupled to the memory chips via any type of memory interconnect as described above. It is noted that each of memory chips 171 A through 171 N and 181 A through 181 N may be any type of memory device such as a memory device in the DRAM family of memory devices, for example.
- memory links 110 A- 110 C form a memory interconnect.
- each of memory links 110 A- 110 C forms a point-to-point memory interconnect that is implemented as two sets of unidirectional lines.
- One set of unidirectional lines is referred to as a downlink and is configured to convey transactions away from host 100 in a downstream direction.
- the other set of unidirectional lines is referred to as an uplink and is configured to convey transactions toward host 100 in an upstream direction.
- each set of unidirectional lines may be implemented using a plurality of differential signal pairs.
- each memory link 110 includes an 18-bit downlink and a 16-bit uplink, where each bit is a differential signal pair.
- the memory interconnect formed by memory links 110 may be configured to convey packets.
- each of memory links 110 may form a point-to-point memory interconnect that is implemented as one set of bi-directional lines. As such, transactions may flow both upstream and downstream on the set of bi-directional wires.
- the bi-directional lines may be implemented using a plurality of differential signal pairs. It is noted that in other embodiments, other signaling schemes may be used, such as multi-level signaling, for example.
- all transactions from host 100 flow downstream through all memory modules 150 on the downlink and all response transactions flow upstream from the responding memory module 150 through each upstream memory module 150 on the uplink. More particularly, in one embodiment, host 100 may request to retrieve or store data within system memory 125 .
- memory controller 105 initiates a corresponding transaction such as a memory read transaction or a memory write transaction, for example.
- Memory controller 105 transmits the transaction to system memory 125 via memory link 110 A.
- the transaction is received by memory control hub 160 A of memory module 150 A.
- memory control hub 160 A In response to receiving the transaction, memory control hub 160 A is configured to transmit the received transaction to memory module 150 B via memory link 110 B without decoding or modifying the transaction. This is referred to as forwarding the transaction downstream.
- each transaction received on a downlink by a given memory control hub 160 of a given memory module 150 is forwarded to the next memory module 150 in the chain that is coupled to the downlink without decoding the transaction.
- decoding of the transaction may occur in parallel with the forwarding of the transaction. In other embodiments, the decoding of the transaction may occur after the transaction has been forwarded.
- memory controller 105 initiates a read request transaction
- the memory module 150 having the memory location corresponding to the address in the request will respond with the requested data.
- the response will be transmitted on the memory module's uplink toward host 100 .
- the intervening memory module will forward the response transaction on its uplink to either host 100 or the next memory module in the chain in an upstream direction.
- the responding memory module may inject the response into a sequence of transactions that are being forwarded upstream on the uplink.
- memory controller 105 may be configured to make requests to system memory 125 without knowledge of which of memory modules 150 A and 150 B a particular address is associated. For example, each of memory modules 150 may be assigned a range of memory addresses during a system configuration sequence.
- Each memory control hub 160 may include logic (not shown in FIG. 1 ) that may decode the address of an incoming request. Thus, a memory control hub 160 of a given memory module 150 may initiate a memory read cycle or memory write cycle to the memory chips on the given memory module 150 in response to decoding a memory request having an address that is in the address range assigned to the given memory module 150 .
- each memory control hub 160 may include a DRAM controller (not shown in FIG. 1 ) for initiating memory cycles to the memory chips to which it is connected.
- memory controller 105 may initiate a subsequent memory access request prior to receiving a response to a previous memory access request. In such an embodiment, memory controller 105 may keep track of outstanding requests and may thus process the responses in a different order than they were sent.
- memory control hubs 160 A and 160 B include a cache memory designated 175 A and 175 B, respectively.
- Cache memories 175 A-B may each serve as a cache memory for data stored elsewhere in the computing system.
- cache memories 175 A-B may each serve as a cache memory for data stored within the respective memory chips of each memory module.
- cache memories 175 A-B may each serve as a cache memory for data stored within other memory modules in the chain that may be further from the host and thus have longer latencies.
- cache memories 175 A-B may serve as a cache memory for data stored in a remote processor node. In the embodiment described in conjunction with the description of FIG.
- cache 175 includes storage for cache tags. However, in the embodiment described in conjunction with the description of FIG. 2 , cache 175 does not include storage for cache tags. In such an embodiment, memory controller 105 may include cache tag storage (not shown). It is noted that although cache memories 175 are shown as part of memory control hub 160 (e.g., on the same device), it is contemplated that in other embodiments, cache memories 175 may be implemented on different devices than memory control hub 160 .
- the memory interconnect includes one or more high-speed point-to-point memory links such as memory links 110 A- 110 C each including an uplink such as uplink 111 A and a downlink such as downlink 112 A, for example.
- downlinks may be 18-bit links while uplinks may be 16-bit links.
- an 18-bit downlink may include 16 control, address and data (CAD) signals, a busy signal and a Control (CTL) signal.
- a given uplink may include 16 control, address and data (CAD) signals.
- an uplink such as uplink 211 A may also include a CTL signal.
- each memory module 150 may be provided to each memory module 150 .
- a reset signal, a power OK signal and a reference clock may be provided to each memory module 150 from host 100 .
- other signals may be provided between each memory module. For example, as described above, a next memory module present signal may be provided between memory modules.
- configuration and control transactions may be used to configure memory control hub 160 .
- configuration and control transactions may be used to access configuration registers, assign a memory address range to a memory module or to assign a hub address to a memory control hub.
- Memory transactions may be used to access the memory locations within the memory chips (e.g., 171 A- 171 N . . . 181 A- 181 N).
- certain memory transactions may be used to directly access cache 175 .
- hub addressing there are two types of addressing supported: hub addressing and memory addressing.
- hub addressing eight hub bits identify the specific memory control hub being accessed.
- a hub address of FFh may be indicative of a broadcast to all memory control hubs.
- memory addressing each hub decodes the upper portion of the address bits to determine which hub should accept the request and the lower portion to determine the memory location to be accessed.
- the additional memory addressing type may be used to specifically access a cache memory located on a given memory module.
- the last four entries of table 1, below, illustrate some exemplary cache access command codes.
- each of the memory links is configured to convey the transactions using one or more packets.
- the packets include control and configuration packets and memory access packets, each of which may include a data payload depending on the type of command the packet carries.
- the sets of wires that make up memory links 110 may be used to convey control, address and data.
- the packets may be generally characterized by the following: Each packet includes a number of bit positions which convey a single bit of information. Each packet is divided into several bit times and during a given bit time, all of the bit positions of the packet are sampled. As such, the control information and data share the same wires of a given link (e.g., CAD wires). As will be described in greater detail below, in one embodiment, packets are multiples of bit pairs and the first bit-time of every packet is sampled at an even bit-time. Packets begin with a control header that may be either one or two bit-pairs in length. In one embodiment, the first five bits of the control header is the command code. Table 1 below illustrates the various types of packets and their associated command codes.
- packets are transmitted with an error detecting code (EDC).
- EDC error detecting code
- the EDC is a 32-bit cyclic redundancy code (CRC), although other embodiments may employ other EDC's as desired.
- addresses are sent most significant bit-time first to speed decode within memory control hub 160 while data is sent least significant byte first. It is noted however, that other embodiments are contemplated in which the addresses may be sent least significant bit-time first and data my be sent most significant byte first.
- Packets may carry a payload of byte enables and/or data. Packets with no payload are referred to as header-only packets.
- the size of the data short reads may be up to one half of a programmed cache line size.
- the size of the data for long reads and block writes may be up to the programmed cache line size.
- the size of the data for byte writes may be a maximum of 64 bytes regardless of the cache line size setting.
- the CTL signal may be used to convey information about each packet. As illustrated in Table 2 below, some exemplary CTL encodings are shown. TABLE 2 CTL encodings for downstream use Even Odd Content of CAD 0 0 Data or Byte Enable Payload 1 1 Control Header 0 1 CRC for a Packet with Payload 1 0 CRC for a Header-Only Packet
- Different values of CTL for the header and payload portions of a packet may provide enough information to allow header-only packets to be inserted within the payload of another packet. This may be useful for reducing the latency of read commands by allowing them to issue while a write packet is still being sent on the link.
- Table 3 illustrates an exemplary packet including a payload in tabular format. The packet in table 3 also shows that a header-only packet is inserted in the payload during bit times 4 - 7 . It is noted however, that other packet encodings are possible and contemplated. For example, in other embodiments, a portion of the CRC bits may be transmitted during each bit time.
- Memory module 150 includes a memory control hub 160 coupled to memory chips 261 A through 261 N via z memory bus 265 .
- Memory control hub 160 includes a control unit 240 coupled to a DRAM controller 250 .
- DRAM controller 250 is coupled to memory chips 261 A- 261 N and to a cache memory 175 .
- Control unit 240 includes an uplink control 241 and a downlink control 242 .
- memory bus 265 may be any type of memory interconnect.
- memory control hub 160 is coupled to a memory link 110 A in an upstream direction and a memory link 110 B in a downstream direction. It is further noted that the frequency of operation of memory bus 265 may be independent of the frequency of operation of memory links 110 .
- cache memory 175 is shown as part of memory control hub 160 , in other embodiments, cache memory 175 may be separate from memory control hub 160 , but may still be included on the same memory module.
- uplink control unit 241 may be configured to receive and forward packets received from another memory module downstream. The receiving and forwarding of the upstream packets creates an upstream transaction sequence. In addition, uplink control unit 241 may be configured to inject packets that originate within memory module 150 into the transaction stream.
- downlink control unit 242 may be configured to receive packets that originate at the host and if a memory module is connected downstream, to forward those packets to the downstream memory module. In addition, downlink control unit 242 may be configured to copy and decode the packets. In one embodiment, if the packets include an address that is within the range of addresses assigned to memory module 150 and the packet is a memory access request, downlink control unit 242 may pass the command associated with the packet to DRAM controller 250 . However, if the packet is not a memory request, but is instead a configuration packet, downlink control unit 242 may pass the configuration command associated with the packet to the core logic of control unit 240 (not shown) for processing. It is noted that in one embodiment, if the packet does not include an address that is within the range of addresses assigned to memory module 150 , memory control hub 160 may drop or discard the packet if memory module 150 is the last memory module in the chain.
- memory control hub 160 is configured to receive a module present signal (not shown), which when activated by a downstream memory module, indicates to an upstream memory module that there is a downstream memory module present. In such an embodiment, if memory control hub 160 receives a transaction and no downstream memory module is determined to be present, memory control hub 160 may drop the transaction. In addition, if no downstream memory module is determined to be present, a memory control hub 160 may power down the downstream transmit and receive circuits; thereby reducing power consumption and possibly radiated emissions.
- a module present signal not shown
- cache memory 175 of FIG. 2 is configured to cache frequently accessed data, whether that data is stored within memory chips 261 A-N or some other place within the system.
- DRAM controller 250 is configured to initiate memory cycles to either to cache memory 175 or to memory chips 261 A- 261 N in response to memory commands received by memory control hub 160 .
- DRAM controller 250 may respond with a cache miss which may initiate a request to another memory in response to memory commands received by memory control hub 160 .
- cache memory 175 may be implemented using memory devices that are typically used for cache memory in a processor.
- the memory devices may be in the static RAM (SRAM) or fast SRAM (FSRAM) family of devices.
- cache memory 175 is configured to store cache data while memory controller 105 includes storage for cache tags corresponding to the cache data stored within cache memory 175 .
- memory controller 105 is configured to perform a tag lookup within a tag storage (not shown) prior to initiating a memory access request to system memory 125 . In doing so, memory controller 105 determines whether the data is located in cache memory 175 or not. In either case, the access times associated with the request may be planned for and the responses scheduled accordingly.
- each memory module may be associated with a particular address space.
- DRAM controller 250 is configured to generate read or write cycles to either cache 175 or memory chips 261 A-N.
- the address space associated with memory chips 261 A-N may be different than the address space associated with cache memory 175 .
- the address space associated with memory chips 261 A-N of all memory modules may be 00000000h through FFFFFFFFh, while the address space associated with of all cache memories may be 00000h through FFFFFh.
- a memory access command code is used and to access the address space associated with cache memory 175 , a cache access command code is used. Exemplary memory and cache read packets are described below in conjunction with the descriptions of FIG. 5 and FIG. 6 , respectively. Since the memory controller 105 has determined whether the data resides in cache memory 175 or in DRAM chips 261 A-N, memory controller 105 sends the access request using the correct addressing type.
- the memory space associated with memory module 150 may include addresses associated with memory chips 261 A-N as well as addresses associated with cache memory 175 .
- the address space associated with memory module 150 includes addresses in the range 00000000h through 3FFFFFFF
- the address space associated with cache memory 175 may be allocated to addresses 00000000h through 000FFFFFh and the remaining addresses may be allocated to memory chips 261 A-N.
- DRAM controller 250 may access memory chips 261 A-N.
- the type of packet may be a standard memory read or write packet including the requested address.
- DRAM controller 250 may include memory control logic (not shown) that may provide support for ensuring that cached data is written back to memory chips 261 A-N.
- DRAM controller 250 may provide a write back buffer and/or an eviction/victim buffer and support logic (not shown) for cache memory 175 .
- DRAM controller 250 may implement an eviction algorithm such as a least recently used (LRU) algorithm, for example, for evicting data from cache memory 175 .
- LRU least recently used
- memory controller 105 may provide explicit write back instructions to DRAM controller 250 .
- cache memory 175 of FIG. 2 may also be configured to cache frequently accessed data stored within a remote processor node (not shown in FIG. 2 ) or the memory chips of another downstream memory module.
- memory controller 105 may explicitly write data to cache memory 175 rather than writing to cache memory 175 as an artifact of writing to memory chips 261 A-N.
- FIG. 3 a block diagram of another embodiment of a memory module such as the memory module of FIG. 1 is shown. Components that correspond to those shown in FIG. 1 are numbered identically for clarity and simplicity.
- Memory module 150 of FIG. 3 includes a memory control hub 160 coupled to memory chips 261 A through 261 N via a memory bus 265 .
- Memory control hub 160 includes a control unit 240 coupled to a DRAM controller 250 .
- DRAM controller 250 is coupled to memory chips 261 A- 261 N and to a cache memory 175 .
- the operation of the memory interconnect and aspects of the operation of the DRAM controller 250 of memory module 150 of FIG. 3 are similar to the operation of memory module 150 Of FIG. 2 .
- memory control hub 160 of FIG. 3 includes a cache memory 175 that includes a cache tag storage 175 A and a cache data storage 175 B. Differences in functionality are described further below.
- cache data storage 175 B is configured to cache frequently accessed data stored within memory chips 261 A-N.
- cache tag storage 175 A is configured to store address tags corresponding to the data stored within cache data storage 175 B. Accordingly, data written to and read from memory chips 261 A-N may be stored within cache data storage 175 B.
- DRAM controller 250 is configured to initiate memory cycles to either memory chips 261 A- 261 N or to cache data storage 175 B in response to memory commands received by memory control hub 160 .
- cache memory 175 A and 175 B may be implemented using memory devices that are typically used for cache memory in a processor.
- the memory devices may be in the static RAM (SRAM) or fast SRAM (FSRAM) family of devices.
- SRAM static RAM
- FSRAM fast SRAM
- cache memory 175 A-B is shown as part of memory control hub 160 (e.g., on the same device), it is contemplated that in other embodiments, cache memory 175 A-B may be implemented as a separate device (e.g., on a different IC).
- memory controller 105 is configured to initiate a memory access request to system memory 125 .
- each memory module may be associated with a particular address space.
- DRAM controller 250 is configured to determine whether the requested data is stored within cache data storage 175 B. In the case of a read request, if the data is stored within cache data storage 175 B (cache hit), DRAM controller 250 is configured to generate read cycles to cache data storage 175 B. If, on the other hand, if the data is not stored within cache data storage 175 B (cache miss), DRAM controller 250 is configured to generate read cycles to memory chips 261 A-N.
- memory controller 105 may not have any a priori knowledge of whether a given read request will hit in the cache or not. Since read response latencies for cache hits and misses is typically different, the latency of a given read request is unknown to memory controller 105 . To handle the unknown read response latency, memory controller 105 may include logic (not shown) that handles out-of-order read responses by tracking outstanding read responses.
- write data e.g., data that may be posted to cache data storage 175 B
- this functionality may be implemented in memory controller 105 while in other embodiments this functionality may be implemented in DRAM controller 250 .
- DRAM controller 250 is configured to determine whether the requested data is stored within cache data storage 175 B. In one embodiment, if the data is not stored within cache data storage 175 B (cache miss), DRAM controller 250 may allocate a location within cache data storage 175 B for the write data and possibly evict data already present. As described above, DRAM controller may include logic (not shown), such as write back buffers or eviction/victim buffers to support operation of cache data storage 175 A and tag storage 175 B.
- DRAM controller 250 may write the received data into cache data storage 175 B.
- the evicted data and the newly written data may be written back to memory chips 261 A-N as determined by DRAM controller 250 . If the write data is stored within cache data storage 175 B (cache hit) and has not been flushed to memory chips 261 A-N, DRAM controller 250 may simply overwrite the data within cache data storage 175 B.
- DRAM controller 250 may write the data back to memory chips 261 A-N. DRAM controller 250 may then write the received data into the locations within cache data storage 250 . Alternatively, DRAM controller 250 may move the dirty data already in cache data storage 175 B into a write back buffer to be written back to memory chips 261 A-N at some later point in time.
- a memory access command code is used to access the address space associated with memory chips 261 A-N .
- An exemplary memory read packet is described below in conjunction with the description of FIG. 5 .
- System 400 includes a host processor 410 coupled to a cache memory module 450 A and a cache memory module 450 B via a memory link 110 A and a memory link 110 B, respectively.
- Host processor 410 is also coupled to a system memory 425 via a memory interconnect 430 .
- Cache memory module 450 B is shown coupled to a memory link 110 C, which may be coupled to an additional cache memory module (not shown) as desired to form a serially connected chain of cache memory modules that is coupled to processor host 410 .
- cache memory module 450 may be connected in this manner. It is further noted that components including a reference number followed by a reference letter may be referred to generally by the reference number alone. For example, when referring generally to all cache memory modules, reference may be made to cache memory module 450 .
- memory links 110 A-B and cache memory modules 450 A-B provide any level of external cache capability to processor 410 .
- cache memory modules 45 GA-B may be an external L3 or L4 cache and may provide a means of providing a very large external cache memory.
- Each cache memory module includes a cache memory control hub 460 which includes a cache memory 475 .
- Processor 410 may include cache control logic (not shown) configured to generate cache transactions and to maintain cache coherency.
- the external cache memory provided by cache memory modules 450 A-B may be used to cache frequently used data. That data may be stored within system memory 425 or any other storage.
- system memory 425 may be representative of any type of system memory such as the system memory including the memory modules described above in conjunction with the descriptions of FIG. 1-3 , for example.
- additional memory modules may be connected downstream from memory module 450 B.
- the additional memory modules may be representative of the memory modules illustrated in FIG. 1 through FIG. 3 and may include memory chips.
- the additional memory modules may not include cache memories.
- Cache memory transactions that are conveyed upon memory links 110 A-C may be representative of the transactions described above in conjunction with the description of FIG. 1 , above.
- FIG. 5 and FIG. 6 illustrate exemplary memory access packets that may be conveyed on memory links 110 A through 110 C of FIG. 1 .
- FIG. 5 a diagram of one embodiment of a memory read packet is shown.
- memory read packet 525 is 16 bits wide and includes six bit times or three bit-pairs.
- the five-bit command code e.g., 10h or 11h
- bit positions 0 - 4 are reserved.
- An eight-bit tag is conveyed in bit positions 8 - 15 .
- bit time one the length of the data that should be returned conveyed in bit positions 0 - 5 .
- a value of 00h indicates no data
- a value of 01h indicates two bit-pairs of data
- a value of 02h indicates four bit-pairs of data
- a zero length read results in an acknowledge packet (Ack) being returned to the requester.
- Ack acknowledge packet
- a read of a half cache line or less may result in a short RdResp and a read of more than a half cache line may result in either a single long RdResp or two short RdResp.
- the cache line size may be programmed by software into the configuration registers of host 100 and each memory control hub 160 . Bit positions 6 - 7 are reserved. Address bits 39 - 32 of the requested location in DRAM are conveyed in bit positions 8 - 15 .
- bit time two the address bits 31 - 16 of the requested location in DRAM are conveyed in bit positions 0 - 15 and during bit time 3 , the address bits 3 - 15 of the requested location in DRAM are conveyed in bit positions 3 - 15 .
- the packet priority is conveyed in bit positions 0 - 1 .
- the priority may be indicative of the priority of the packet relative to other requests. For example, one priority may be to delay all requests with lower priority even if they are already in progress and to execute this request ahead of them.
- Bit position 2 is reserved.
- bits 0 - 15 and 16 - 31 , respectively, of a CRC are conveyed in bit positions 0 - 15 .
- cache read packet 525 is 16 bits wide and includes 4 bit times or two bit-pairs.
- the five-bit command code e.g., 15h or 16h
- bit positions 0 - 4 are reserved.
- An eight-bit tag is conveyed in bit positions 8 - 15 .
- bit time one the length of the data that should be returned is conveyed in bit positions 0 - 5 .
- a value of 00h indicates no data
- a value of 01h indicates two bit-pairs of data
- a value of 02h indicates four bit-pairs of data
- a zero length read results in an acknowledge packet (Ack) being returned to the requestor.
- Ack acknowledge packet
- a read of a half cache line or less may result in a short RdResp and a read of more than a half cache line may result in either a single long RdResp or two short RdResp.
- the cache line size may be programmed by software into the configuration registers of host 100 and each memory control hub 160 . Address bits 25 - 16 of the requested location in cache are conveyed in bit positions 6 - 15 .
- bit time two the address bits 15 - 0 of the requested location in cache 175 are conveyed in bit positions 7 - 16 .
- bit times three and four bits 0 - 15 and 16 - 31 , respectively, of a CRC are conveyed in bit positions 0 - 15 .
- FIG. 7 is a block diagram of one embodiment of a computer system.
- Computer system 700 includes processor nodes 612 A- 612 D each interconnected by coherent packet interface links 615 A-D. Each link of coherent packet interface 615 may form a high-speed point-to-point link.
- Processor nodes 612 A-D may each include one or more processors.
- Computer system 700 also includes an I/O node 620 which is coupled to processor node 612 A via a non-coherent packet interface 650 A. I/O node 620 may be connected to another I/O node (not shown) in a chain topology for example, by non-coherent packet interface 650 B.
- Processor nodes 612 A is illustrated as a host node and may include a host bridge for communicating with I/O node 620 via NC packet interface 650 A. Processor nodes 612 B-D may also include host bridges for communication with other I/O nodes (not shown).
- the non-coherent packet interface links formed by NC packet interface 650 A-B may also be referred to as point-to-point links.
- I/O node 620 is connected to a pair of peripheral buses 625 A-B.
- FIG. 7 further illustrates respective system memories (e.g., 617 A and 617 B) coupled to processor nodes 612 A and 612 B.
- processor node 612 A and 612 B are each illustrative of a host as shown in FIG. 1 , and each system memory 617 may be implemented in the configuration described in conjunction with the descriptions of FIG. 2 and FIG. 3 above.
- the interconnects between each of processor nodes 612 A and 612 B and their respective system memories 617 may be reflective of the memory interconnect including memory link 110 C described above in FIG. 1 through FIG. 6 . It is noted that in other embodiments, other numbers of processor nodes may be used.
- each of processor nodes 612 C and 612 D may be similarly connected to a respective system memory such as system memory 617 , for example.
- a cache memory of a memory control hub located within system memory 617 A may cache data stored within either of system memories 617 A or 617 B, for example.
- each link of coherent packet interface 615 is implemented as sets of unidirectional lines (e.g. lines 615 A are used to transmit packets from processing node 612 A to processing node 612 B and lines 615 B are used to transmit packets from processing node 612 B to processing node 612 C). Other sets of lines 615 C-D are used to transmit packets between other processing nodes as illustrated in FIG. 7 .
- the coherent packet interface 615 may be operated in a cache coherent fashion for communication between processing nodes (“the coherent link”).
- non-coherent packet interface 650 may be operated in a non-coherent fashion for communication between I/O nodes and between I/O nodes and a host bridge such as the host bridge of processor node 612 A (“the non-coherent link”).
- the interconnection of two or more nodes via coherent links may be referred to as a “coherent fabric”.
- the interconnection of two or more nodes via non-coherent links may be referred to as a “non-coherent fabric”. It is noted that a packet to be transmitted from one processing node to another may pass through one or more intermediate nodes.
- a packet transmitted by processing node 612 A to processing node 612 C may pass through either processing node 612 B or processing node 612 D as shown in FIG. 7 .
- Any suitable routing algorithm may be used.
- Other embodiments of computer system 700 may include more or fewer processing nodes than the embodiment shown in FIG. 6 .
- Peripheral buses 625 A and 625 B are illustrative of a common peripheral bus such as a peripheral component interconnect (PCI) bus. It is understood, however, that other types of buses may be used.
- PCI peripheral component interconnect
- system memory configuration described above may be used in conjunction with a computer system employing a processor chipset that includes a Northbridge.
- a memory controller within the Northbridge may serve as the host.
Abstract
A system including a host coupled to a serially connected chain of memory modules. In one embodiment, at least one of the memory modules includes a cache for storing data stored in a system memory.
Description
- This application claims the benefit of U.S. Provisional Application No. 60/470,078 filed May 13, 2003.
- 1. Field of the Invention
- This invention relates to computer system memory and, more particularly, to memory module configurations and the memory subsystem topology.
- 2. Description of the Related Art
- Many computer systems employ a main system memory that may be configured dependent upon the needs of an end user. In such systems, a motherboard or system board may include a number of memory expansion sockets. One or more small circuit boards, referred to as memory modules, may be inserted into the sockets as needed to increase the memory capacity of the computer system. Each of the memory modules typically includes multiple memory devices that provide a given amount of memory capacity. The memory devices are usually implemented using some type of dynamic random access memory (DRAM). Some examples of DRAM types include synchronous DRAM (SDRAM) as well as the various types of double data rate SDRAM (DDR SDRAM).
- In conventional computer systems, the memory modules are connected to a memory/DRAM controller via a memory bus that includes address, control (including clock signals), and data signals. In some computer systems, the address, control and data signals may be multiplexed and thus share the same sets of wires. In other computer systems, the address, control and data signals may use separate wires. In either case, each of the address and control signals are routed to each expansion socket such that the memory modules, when inserted, are connected in parallel to the memory/DRAM controller. There are several drawbacks to parallel bus arrangements. For example, depending on the topology of the interconnect, the maximum memory bus speed may be limited due to transmission line effects such as signal reflections. In some systems, the memory/DRAM controller may reside on the same integrated circuit (IC) chip as the system processor, while in other systems the memory/DRAM controller may reside in one IC (e.g., a Northbridge) of a chipset.
- In addition, many conventional computers systems employ processors that use an external cache memory. In many such systems, the external cache memory interface uses a large number of address and data pins. Furthermore, increasing the size of the external cache may require a system redesign and so the external cache may not be configurable by an end user.
- Although the operating speed of computer system processors continues to increase, the relative performance of the main system memory has not increased at the same rate. This may be due, at least in part, to the incremental improvement in the bandwidth of the memory bus architectures described above.
- Various embodiments of a system including one or more memory modules are disclosed. In one embodiment, a host is coupled to a serially connected chain of memory modules. At least one memory module includes a cache for storing data stored in a system memory.
- In one specific implementation, the system memory may include a respective plurality of memory chips mounted on each memory module. In addition, each memory module may include a memory control hub including a controller configured to determine whether data associated with a received memory request is stored within the cache.
- In another specific implementation, a given cache may include a storage for storing cache tags corresponding to the data stored within the given cache. In such an implementation, the controller is configured to access the cache in response to determining that the data associated with the received memory request is stored within the cache.
- In another specific implementation, the host includes a memory controller configured to generate memory requests to the memory modules. The memory controller may include a storage for storing cache tags corresponding to data stored within each cache.
- In yet another implementation, the memory control hub includes a controller that may be configured to access the memory chips in response to receiving a memory command having a memory address that matches a memory address associated with the memory chips. In addition, the controller may be configured to access the cache in response to receiving a memory command having a memory address that matches a memory address associated with the cache.
-
FIG. 1 is a block diagram of one embodiment of a system including a serially connected chain of system memory modules. -
FIG. 2 is a block diagram of one embodiment of a memory module ofFIG. 1 including one cache implementation. -
FIG. 3 is a block diagram of another embodiment of a memory module ofFIG. 1 including another cache implementation. -
FIG. 4 is a block diagram of one embodiment of a system including a serially connected chain of cache memory modules. -
FIG. 5 is a diagram of one embodiment of a memory read packet. -
FIG. 6 is a diagram of one embodiment of a cache memory read packet. -
FIG. 7 is a block diagram of one embodiment of a computer system. - While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present invention as defined by the appended claims. Note, the headings are for organizational purposes only and are not meant to be used to limit or interpret the description or claims. Furthermore, note that the word “may” is used throughout this application in a permissive sense (i.e., having the potential to, being able to), not a mandatory sense (i.e., must). The term “include” and derivations thereof mean “including, but not limited to.” The term “connected” means “directly or indirectly connected,” and the term “coupled” means “directly or indirectly coupled.”
- Turning now to
FIG. 1 , a block diagram of one embodiment of a system including a serially connected chain of memory modules is shown.System 50 includes ahost 100 coupled to asystem memory 125 via a memory link 1I A.System 50 may be configured to operate as part of a computing device such as a computer system or server system, for example.System memory 125 includes amemory module 150A coupled to amemory module 150B via amemory link 110B.Memory module 150B is shown coupled to amemory link 110C, which may be coupled to an additional memory module (not shown) as desired to form a serially connected chain of memory modules that is coupled tohost 100. It is noted that although two memory modules are shown in the chain, it is contemplated that one or more memory modules may be connected in this manner. It is further noted that components including a reference number followed by a reference letter may be referred to generally by the reference number alone. For example, when referring generally to all memory modules, reference may be made tomemory module 150. - In the illustrated embodiment,
memory module 150A includes amemory control hub 160A, which is coupled to a plurality of memory devices that are designatedmemory chip 171A through 171N, where N may be any number, as desired. In one embodiment,memory control hub 160A may be coupled to the memory chips via any type of memory interconnect. For example, in one embodiment, the memory interconnect may be a typical address, control and data bus configuration. - Similarly,
memory module 150B includes amemory control hub 160B, which is coupled to a plurality of memory devices that are designatedmemory chip 181A through 181N, where N may be any number, as desired. In one embodiment,memory control hub 160B may be coupled to the memory chips via any type of memory interconnect as described above. It is noted that each ofmemory chips 171A through 171N and 181A through 181N may be any type of memory device such as a memory device in the DRAM family of memory devices, for example. - In the illustrated embodiment,
memory links 110A-110C form a memory interconnect. In one embodiment, each ofmemory links 110A-110C forms a point-to-point memory interconnect that is implemented as two sets of unidirectional lines. One set of unidirectional lines is referred to as a downlink and is configured to convey transactions away fromhost 100 in a downstream direction. The other set of unidirectional lines is referred to as an uplink and is configured to convey transactions towardhost 100 in an upstream direction. In addition, in one embodiment, each set of unidirectional lines may be implemented using a plurality of differential signal pairs. In one embodiment, each memory link 110 includes an 18-bit downlink and a 16-bit uplink, where each bit is a differential signal pair. As will be described in greater detail below in conjunction with the descriptions ofFIG. 4 andFIG. 5 , the memory interconnect formed by memory links 110 may be configured to convey packets. - In an alternative embodiment, each of memory links 110 may form a point-to-point memory interconnect that is implemented as one set of bi-directional lines. As such, transactions may flow both upstream and downstream on the set of bi-directional wires. In such an embodiment, the bi-directional lines may be implemented using a plurality of differential signal pairs. It is noted that in other embodiments, other signaling schemes may be used, such as multi-level signaling, for example.
- Generally speaking, all transactions from
host 100 flow downstream through allmemory modules 150 on the downlink and all response transactions flow upstream from the respondingmemory module 150 through eachupstream memory module 150 on the uplink. More particularly, in one embodiment, host 100 may request to retrieve or store data withinsystem memory 125. In response to host 100 making a request,memory controller 105 initiates a corresponding transaction such as a memory read transaction or a memory write transaction, for example.Memory controller 105 transmits the transaction tosystem memory 125 viamemory link 110A. In the illustrated embodiment, the transaction is received bymemory control hub 160A ofmemory module 150A. - In response to receiving the transaction,
memory control hub 160A is configured to transmit the received transaction tomemory module 150B viamemory link 110B without decoding or modifying the transaction. This is referred to as forwarding the transaction downstream. Thus, each transaction received on a downlink by a givenmemory control hub 160 of a givenmemory module 150 is forwarded to thenext memory module 150 in the chain that is coupled to the downlink without decoding the transaction. In one embodiment, decoding of the transaction may occur in parallel with the forwarding of the transaction. In other embodiments, the decoding of the transaction may occur after the transaction has been forwarded. - Likewise, if
memory controller 105 initiates a read request transaction, for example, thememory module 150 having the memory location corresponding to the address in the request will respond with the requested data. The response will be transmitted on the memory module's uplink towardhost 100. If there are any intervening memory modules between the sending memory module andhost 100, the intervening memory module will forward the response transaction on its uplink to either host 100 or the next memory module in the chain in an upstream direction. In addition, when the responding memory module is ready to send the response, it may inject the response into a sequence of transactions that are being forwarded upstream on the uplink. - In one embodiment,
memory controller 105 may be configured to make requests tosystem memory 125 without knowledge of which ofmemory modules memory modules 150 may be assigned a range of memory addresses during a system configuration sequence. Eachmemory control hub 160 may include logic (not shown inFIG. 1 ) that may decode the address of an incoming request. Thus, amemory control hub 160 of a givenmemory module 150 may initiate a memory read cycle or memory write cycle to the memory chips on the givenmemory module 150 in response to decoding a memory request having an address that is in the address range assigned to the givenmemory module 150. As will be described in greater detail below in conjunction with the descriptions ofFIG. 2 andFIG. 3 , eachmemory control hub 160 may include a DRAM controller (not shown inFIG. 1 ) for initiating memory cycles to the memory chips to which it is connected. - In addition, in one embodiment,
memory controller 105 may initiate a subsequent memory access request prior to receiving a response to a previous memory access request. In such an embodiment,memory controller 105 may keep track of outstanding requests and may thus process the responses in a different order than they were sent. - Further, in the illustrated embodiment,
memory control hubs Cache memories 175A-B may each serve as a cache memory for data stored elsewhere in the computing system. For example, as will be described in greater detail below,cache memories 175A-B may each serve as a cache memory for data stored within the respective memory chips of each memory module. Alternatively,cache memories 175A-B may each serve as a cache memory for data stored within other memory modules in the chain that may be further from the host and thus have longer latencies. Likewise, in computing systems having multiple processor nodes,cache memories 175A-B may serve as a cache memory for data stored in a remote processor node. In the embodiment described in conjunction with the description ofFIG. 3 ,cache 175 includes storage for cache tags. However, in the embodiment described in conjunction with the description ofFIG. 2 ,cache 175 does not include storage for cache tags. In such an embodiment,memory controller 105 may include cache tag storage (not shown). It is noted that althoughcache memories 175 are shown as part of memory control hub 160 (e.g., on the same device), it is contemplated that in other embodiments,cache memories 175 may be implemented on different devices thanmemory control hub 160. - The Memory Interconnect
- The memory interconnect includes one or more high-speed point-to-point memory links such as
memory links 110A-110C each including an uplink such asuplink 111A and a downlink such asdownlink 112A, for example. As noted above, in one embodiment downlinks may be 18-bit links while uplinks may be 16-bit links. As such, an 18-bit downlink may include 16 control, address and data (CAD) signals, a busy signal and a Control (CTL) signal. A given uplink may include 16 control, address and data (CAD) signals. It is contemplated however, that in an alternative embodiment, an uplink such asuplink 211A may also include a CTL signal. - In addition to the high-speed links, other signals may be provided to each
memory module 150. For example, in one embodiment, a reset signal, a power OK signal and a reference clock may be provided to eachmemory module 150 fromhost 100. Further, other signals may be provided between each memory module. For example, as described above, a next memory module present signal may be provided between memory modules. - Generally speaking, the types of transactions conveyed on memory links 110 may be categorized into configuration and control transactions and memory transactions. In one embodiment, configuration and control transactions may be used to configure
memory control hub 160. For example, configuration and control transactions may be used to access configuration registers, assign a memory address range to a memory module or to assign a hub address to a memory control hub. Memory transactions may be used to access the memory locations within the memory chips (e.g., 171A-171N . . . 181A-181N). In addition, as described further below, certain memory transactions may be used to directly accesscache 175. - Accordingly, in one embodiment, there are two types of addressing supported: hub addressing and memory addressing. Using hub addressing, eight hub bits identify the specific memory control hub being accessed. In one embodiment, a hub address of FFh may be indicative of a broadcast to all memory control hubs. Using memory addressing, each hub decodes the upper portion of the address bits to determine which hub should accept the request and the lower portion to determine the memory location to be accessed. In one embodiment, there are 40 address bits, although it is contemplated that other numbers of address bits may be used as desired.
- As described further below, in certain embodiments, there may be an additional memory addressing type supported. The additional memory addressing type may be used to specifically access a cache memory located on a given memory module. For example, the last four entries of table 1, below, illustrate some exemplary cache access command codes.
- In one embodiment, each of the memory links is configured to convey the transactions using one or more packets. The packets include control and configuration packets and memory access packets, each of which may include a data payload depending on the type of command the packet carries. As such, the sets of wires that make up memory links 110 may be used to convey control, address and data.
- The packets may be generally characterized by the following: Each packet includes a number of bit positions which convey a single bit of information. Each packet is divided into several bit times and during a given bit time, all of the bit positions of the packet are sampled. As such, the control information and data share the same wires of a given link (e.g., CAD wires). As will be described in greater detail below, in one embodiment, packets are multiples of bit pairs and the first bit-time of every packet is sampled at an even bit-time. Packets begin with a control header that may be either one or two bit-pairs in length. In one embodiment, the first five bits of the control header is the command code. Table 1 below illustrates the various types of packets and their associated command codes. It is noted however, that the actual codes shown in column one are for illustrative purposes and that other codes may be used for each given command. It is further noted that other commands and encodings may be used.
TABLE 1 Packet types and command codes Header Length (bit- Normal Address Code times) Command Description Direction Response Type 00h — NOP Null Operation/Idle State Both — — 04h 2 AddrSet Address Set Down AddrAck Hub 05h 2 AddrAck Address Acknowledge Up — — 06h 2 Ack Acknowledge Up — — 07h 2 Nak Not Acknowledge/Error Up — — 08h 2 SRdResp Short Read Response Up — — 09h 2 LRdResp Long Read Response Up — — 0Ah 2 ConfigRd Configuration Read Down RdResp Hub 0Ch 2 ConfigWr Configuration Write Down Ack Hub 0Eh 2 DIMMCt1 DIMM Control Down Ack Hub 10h 4 SMemRd Short Memory Read Down RdResp/ Ack Memory 11h 4 LMemRd Long Memory Read Down RdResp Memory 12h 4 BlkMemWr Block Memory Write Down Ack Memory 13h 4 SbytMemWr Short Byte Memory Write Down Ack Memory 14h 4 LbytMemWr Long Byte Memory Write Down Ack Memory 15h 4 CacheDataRd Cache Read Down RdResp M/ Cache 16h 4 CacheDataWr Cache Write Down Ack M/ Cache 17h 4 CacheTagRd Cache Tag Read Down RdResp M/ Cache 18h 4 CacheTagWr Cache Tag Write Down Ack M/Cache - Further, in one embodiment, packets (except NOP packets) are transmitted with an error detecting code (EDC). It is noted that in one embodiment, the EDC is a 32-bit cyclic redundancy code (CRC), although other embodiments may employ other EDC's as desired. Additionally, addresses are sent most significant bit-time first to speed decode within
memory control hub 160 while data is sent least significant byte first. It is noted however, that other embodiments are contemplated in which the addresses may be sent least significant bit-time first and data my be sent most significant byte first. Packets may carry a payload of byte enables and/or data. Packets with no payload are referred to as header-only packets. In one embodiment, the size of the data short reads may be up to one half of a programmed cache line size. In addition, the size of the data for long reads and block writes may be up to the programmed cache line size. Further, the size of the data for byte writes may be a maximum of 64 bytes regardless of the cache line size setting. - In addition to the control header and command code information included within a packet, the CTL signal may be used to convey information about each packet. As illustrated in Table 2 below, some exemplary CTL encodings are shown.
TABLE 2 CTL encodings for downstream use Even Odd Content of CAD 0 0 Data or Byte Enable Payload 1 1 Control Header 0 1 CRC for a Packet with Payload 1 0 CRC for a Header-Only Packet - Different values of CTL for the header and payload portions of a packet may provide enough information to allow header-only packets to be inserted within the payload of another packet. This may be useful for reducing the latency of read commands by allowing them to issue while a write packet is still being sent on the link. Table 3 illustrates an exemplary packet including a payload in tabular format. The packet in table 3 also shows that a header-only packet is inserted in the payload during bit times 4-7. It is noted however, that other packet encodings are possible and contemplated. For example, in other embodiments, a portion of the CRC bits may be transmitted during each bit time.
TABLE 3 Packet with payload and header-only packet inserted within payload Bit- time CTL CAD 0 1 Headerl bits [15:0] 1 1 Headeri bits [31:16] 2 0 Databits [15:0] 3 0 Databits [31:16] 4 1 Header2 bits [15:0] 5 1 Header2 bits [31:16] 6 1 CRC2 bits [15:0] 7 0 CRC2 bits [31:16] 8 0 Data bits [47:32] 9 0 Data bits [64:48] 10 0 CRC1 bits [15:0] 11 1 CRC1 bits [31:16] - Referring to
FIG. 2 , a block diagram of one embodiment of a memory module such as the memory module illustrated inFIG. 1 is shown. Components that correspond to those shown inFIG. 1 are numbered identically for clarity and simplicity.Memory module 150 includes amemory control hub 160 coupled tomemory chips 261A through 261N via z memory bus 265. -
Memory control hub 160 includes acontrol unit 240 coupled to aDRAM controller 250.DRAM controller 250 is coupled tomemory chips 261A-261N and to acache memory 175.Control unit 240 includes anuplink control 241 and adownlink control 242. As noted above, memory bus 265 may be any type of memory interconnect. In the illustrated embodiment,memory control hub 160 is coupled to amemory link 110A in an upstream direction and amemory link 110B in a downstream direction. It is further noted that the frequency of operation of memory bus 265 may be independent of the frequency of operation of memory links 110. It is noted that althoughcache memory 175 is shown as part ofmemory control hub 160, in other embodiments,cache memory 175 may be separate frommemory control hub 160, but may still be included on the same memory module. - In the illustrated embodiment,
uplink control unit 241 may be configured to receive and forward packets received from another memory module downstream. The receiving and forwarding of the upstream packets creates an upstream transaction sequence. In addition,uplink control unit 241 may be configured to inject packets that originate withinmemory module 150 into the transaction stream. - In the illustrated embodiment,
downlink control unit 242 may be configured to receive packets that originate at the host and if a memory module is connected downstream, to forward those packets to the downstream memory module. In addition,downlink control unit 242 may be configured to copy and decode the packets. In one embodiment, if the packets include an address that is within the range of addresses assigned tomemory module 150 and the packet is a memory access request,downlink control unit 242 may pass the command associated with the packet toDRAM controller 250. However, if the packet is not a memory request, but is instead a configuration packet,downlink control unit 242 may pass the configuration command associated with the packet to the core logic of control unit 240 (not shown) for processing. It is noted that in one embodiment, if the packet does not include an address that is within the range of addresses assigned tomemory module 150,memory control hub 160 may drop or discard the packet ifmemory module 150 is the last memory module in the chain. - In one embodiment,
memory control hub 160 is configured to receive a module present signal (not shown), which when activated by a downstream memory module, indicates to an upstream memory module that there is a downstream memory module present. In such an embodiment, ifmemory control hub 160 receives a transaction and no downstream memory module is determined to be present,memory control hub 160 may drop the transaction. In addition, if no downstream memory module is determined to be present, amemory control hub 160 may power down the downstream transmit and receive circuits; thereby reducing power consumption and possibly radiated emissions. - As mentioned above, in one implementation,
cache memory 175 ofFIG. 2 is configured to cache frequently accessed data, whether that data is stored withinmemory chips 261A-N or some other place within the system. Thus, depending on whether the requested data is stored withincache memory 175,DRAM controller 250 is configured to initiate memory cycles to either tocache memory 175 or tomemory chips 261A-261N in response to memory commands received bymemory control hub 160. Alternatively,DRAM controller 250 may respond with a cache miss which may initiate a request to another memory in response to memory commands received bymemory control hub 160. In one embodiment,cache memory 175 may be implemented using memory devices that are typically used for cache memory in a processor. For example, the memory devices may be in the static RAM (SRAM) or fast SRAM (FSRAM) family of devices. - In the illustrated embodiment,
cache memory 175 is configured to store cache data whilememory controller 105 includes storage for cache tags corresponding to the cache data stored withincache memory 175. In one implementation,memory controller 105 is configured to perform a tag lookup within a tag storage (not shown) prior to initiating a memory access request tosystem memory 125. In doing so,memory controller 105 determines whether the data is located incache memory 175 or not. In either case, the access times associated with the request may be planned for and the responses scheduled accordingly. - As described above, each memory module may be associated with a particular address space. Thus, when a memory request is received that has an address associated with
memory module 150,DRAM controller 250 is configured to generate read or write cycles to eithercache 175 ormemory chips 261A-N. In one embodiment, the address space associated withmemory chips 261A-N may be different than the address space associated withcache memory 175. For example, the address space associated withmemory chips 261A-N of all memory modules may be 00000000h through FFFFFFFFh, while the address space associated with of all cache memories may be 00000h through FFFFFh. To access the address space associated withmemory chips 261A-N a memory access command code is used and to access the address space associated withcache memory 175, a cache access command code is used. Exemplary memory and cache read packets are described below in conjunction with the descriptions ofFIG. 5 andFIG. 6 , respectively. Since thememory controller 105 has determined whether the data resides incache memory 175 or inDRAM chips 261A-N,memory controller 105 sends the access request using the correct addressing type. - In an alternative embodiment, the memory space associated with
memory module 150 may include addresses associated withmemory chips 261A-N as well as addresses associated withcache memory 175. For example, if the address space associated withmemory module 150 includes addresses in the range 00000000h through 3FFFFFFF, the address space associated withcache memory 175 may be allocated to addresses 00000000h through 000FFFFFh and the remaining addresses may be allocated tomemory chips 261A-N. Thus, if a memory request having an address in the DRAM range is received,DRAM controller 250 may accessmemory chips 261A-N. Conversely, if the received memory request has an address in the cache address range,DRAM controller 250 may accesscache 175. In such an alternative embodiment, the type of packet may be a standard memory read or write packet including the requested address. - In one embodiment,
DRAM controller 250 may include memory control logic (not shown) that may provide support for ensuring that cached data is written back tomemory chips 261A-N. For example,DRAM controller 250 may provide a write back buffer and/or an eviction/victim buffer and support logic (not shown) forcache memory 175. In such an embodiment,DRAM controller 250 may implement an eviction algorithm such as a least recently used (LRU) algorithm, for example, for evicting data fromcache memory 175. In one implementation,memory controller 105 may provide explicit write back instructions toDRAM controller 250. - As noted above in the description of
FIG. 1 ,cache memory 175 ofFIG. 2 may also be configured to cache frequently accessed data stored within a remote processor node (not shown inFIG. 2 ) or the memory chips of another downstream memory module. In such implementations,memory controller 105 may explicitly write data tocache memory 175 rather than writing tocache memory 175 as an artifact of writing tomemory chips 261A-N. - Turning to
FIG. 3 , a block diagram of another embodiment of a memory module such as the memory module ofFIG. 1 is shown. Components that correspond to those shown inFIG. 1 are numbered identically for clarity and simplicity.Memory module 150 ofFIG. 3 includes amemory control hub 160 coupled tomemory chips 261A through 261N via a memory bus 265. -
Memory control hub 160 includes acontrol unit 240 coupled to aDRAM controller 250.DRAM controller 250 is coupled tomemory chips 261A-261N and to acache memory 175. The operation of the memory interconnect and aspects of the operation of theDRAM controller 250 ofmemory module 150 ofFIG. 3 are similar to the operation ofmemory module 150 OfFIG. 2 . However, in contrast tomemory control hub 160 ofFIG. 2 ,memory control hub 160 ofFIG. 3 includes acache memory 175 that includes acache tag storage 175A and acache data storage 175B. Differences in functionality are described further below. - In the illustrated embodiment,
cache data storage 175B is configured to cache frequently accessed data stored withinmemory chips 261A-N. Likewise,cache tag storage 175A is configured to store address tags corresponding to the data stored withincache data storage 175B. Accordingly, data written to and read frommemory chips 261A-N may be stored withincache data storage 175B. Thus, depending on whether the requested data is stored withincache memory 175,DRAM controller 250 is configured to initiate memory cycles to eithermemory chips 261A-261N or tocache data storage 175B in response to memory commands received bymemory control hub 160. In one embodiment,cache memory cache memory 175A-B is shown as part of memory control hub 160 (e.g., on the same device), it is contemplated that in other embodiments,cache memory 175A-B may be implemented as a separate device (e.g., on a different IC). - In one implementation,
memory controller 105 is configured to initiate a memory access request tosystem memory 125. As described above, each memory module may be associated with a particular address space. Thus, when a memory request is received that has an address associated withmemory module 150, using the tags stored withincache tag storage 175A,DRAM controller 250 is configured to determine whether the requested data is stored withincache data storage 175B. In the case of a read request, if the data is stored withincache data storage 175B (cache hit),DRAM controller 250 is configured to generate read cycles tocache data storage 175B. If, on the other hand, if the data is not stored withincache data storage 175B (cache miss),DRAM controller 250 is configured to generate read cycles tomemory chips 261A-N. - Since the tags are stored within
cache tag storage 175A,memory controller 105 may not have any a priori knowledge of whether a given read request will hit in the cache or not. Since read response latencies for cache hits and misses is typically different, the latency of a given read request is unknown tomemory controller 105. To handle the unknown read response latency,memory controller 105 may include logic (not shown) that handles out-of-order read responses by tracking outstanding read responses. - It is noted that depending on the implementation, it may be necessary to ensure the correct ordering of other transactions. For example, it is important to ensure that write data (e.g., data that may be posted to
cache data storage 175B) followed by a read of that data is not overwritten by a subsequent write to the same location prior to the read. In one embodiment, this functionality may be implemented inmemory controller 105 while in other embodiments this functionality may be implemented inDRAM controller 250. - There are various ways to implement cache policies with respect to writing data. Thus, assuming that such transaction ordering protection is in place, irrespective of the location, if a write request is received that has an address associated with
memory module 150, using the tags stored withincache tag storage 175A,DRAM controller 250 is configured to determine whether the requested data is stored withincache data storage 175B. In one embodiment, if the data is not stored withincache data storage 175B (cache miss),DRAM controller 250 may allocate a location withincache data storage 175B for the write data and possibly evict data already present. As described above, DRAM controller may include logic (not shown), such as write back buffers or eviction/victim buffers to support operation of cache data storage175A andtag storage 175B.DRAM controller 250 may write the received data intocache data storage 175B. The evicted data and the newly written data may be written back tomemory chips 261A-N as determined byDRAM controller 250. If the write data is stored withincache data storage 175B (cache hit) and has not been flushed tomemory chips 261A-N,DRAM controller 250 may simply overwrite the data withincache data storage 175B. - However, if the write ordering protection is not in place, and if the write data is stored within
cache data storage 175B (cache hit) and has not been flushed tomemory chips 261A-N,DRAM controller 250 may write the data back tomemory chips 261A-N. DRAM controller 250 may then write the received data into the locations withincache data storage 250. Alternatively,DRAM controller 250 may move the dirty data already incache data storage 175B into a write back buffer to be written back tomemory chips 261A-N at some later point in time. - It is noted that to access the address space associated with
memory chips 261A-N a memory access command code is used. An exemplary memory read packet is described below in conjunction with the description ofFIG. 5 . - Turning now to
FIG. 4 , a block diagram of one embodiment of a system including a serially connected chain of cache memory modules is shown. Components that correspond to those shown inFIG. 1 are numbered identically for clarity and simplicity.System 400 includes ahost processor 410 coupled to acache memory module 450A and acache memory module 450B via amemory link 110A and amemory link 110B, respectively.Host processor 410 is also coupled to asystem memory 425 via amemory interconnect 430.Cache memory module 450B is shown coupled to amemory link 110C, which may be coupled to an additional cache memory module (not shown) as desired to form a serially connected chain of cache memory modules that is coupled toprocessor host 410. It is noted that although two cache memory modules are shown in the chain, it is contemplated that any number of cache memory modules may be connected in this manner. It is further noted that components including a reference number followed by a reference letter may be referred to generally by the reference number alone. For example, when referring generally to all cache memory modules, reference may be made to cache memory module 450. - In the illustrated embodiment,
memory links 110A-B andcache memory modules 450A-B provide any level of external cache capability toprocessor 410. For example, cache memory modules 45GA-B may be an external L3 or L4 cache and may provide a means of providing a very large external cache memory. Each cache memory module includes a cache memory control hub 460 which includes a cache memory 475.Processor 410 may include cache control logic (not shown) configured to generate cache transactions and to maintain cache coherency. Thus, the external cache memory provided bycache memory modules 450A-B may be used to cache frequently used data. That data may be stored withinsystem memory 425 or any other storage. It is noted thatsystem memory 425 may be representative of any type of system memory such as the system memory including the memory modules described above in conjunction with the descriptions ofFIG. 1-3 , for example. - It is further noted that additional memory modules (not shown in
FIG. 4 ) may be connected downstream frommemory module 450B. In such an implementation, the additional memory modules may be representative of the memory modules illustrated inFIG. 1 throughFIG. 3 and may include memory chips. In one implementation, the additional memory modules may not include cache memories. - Cache memory transactions that are conveyed upon
memory links 110A-C may be representative of the transactions described above in conjunction with the description ofFIG. 1 , above. -
FIG. 5 andFIG. 6 illustrate exemplary memory access packets that may be conveyed onmemory links 110A through 110C ofFIG. 1 . Turning now toFIG. 5 , a diagram of one embodiment of a memory read packet is shown. In the illustrated embodiment, memory readpacket 525 is 16 bits wide and includes six bit times or three bit-pairs. During bit time zero, the five-bit command code (e.g., 10h or 11h) is conveyed in bit positions 0-4. Bit positions 5-7 are reserved. An eight-bit tag is conveyed in bit positions 8-15. - During bit time one, the length of the data that should be returned conveyed in bit positions 0-5. In one embodiment, a value of 00h indicates no data, a value of 01h indicates two bit-pairs of data, a value of 02h indicates four bit-pairs of data, and so on. A zero length read results in an acknowledge packet (Ack) being returned to the requester. In one embodiment, a read of a half cache line or less may result in a short RdResp and a read of more than a half cache line may result in either a single long RdResp or two short RdResp. The cache line size may be programmed by software into the configuration registers of
host 100 and each memory control hub160. Bit positions 6-7 are reserved. Address bits 39-32 of the requested location in DRAM are conveyed in bit positions 8-15. - During bit time two, the address bits 31-16 of the requested location in DRAM are conveyed in bit positions 0-15 and during
bit time 3, the address bits 3-15 of the requested location in DRAM are conveyed in bit positions 3-15. Also duringbit time 3, the packet priority is conveyed in bit positions 0-1. In one embodiment, the priority may be indicative of the priority of the packet relative to other requests. For example, one priority may be to delay all requests with lower priority even if they are already in progress and to execute this request ahead of them.Bit position 2 is reserved. During bit times four and five, bits 0-15 and 16-31, respectively, of a CRC are conveyed in bit positions 0-15. - Referring to
FIG. 6 , a diagram of one embodiment of a cache read packet is shown. In the illustrated embodiment, cache readpacket 525 is 16 bits wide and includes 4 bit times or two bit-pairs. During bit time zero, the five-bit command code (e.g., 15h or 16h) is conveyed in bit positions 0-4. Bit positions 5-7 are reserved. An eight-bit tag is conveyed in bit positions 8-15. - During bit time one, the length of the data that should be returned is conveyed in bit positions 0-5. In one embodiment, a value of 00h indicates no data, a value of 01h indicates two bit-pairs of data, a value of 02h indicates four bit-pairs of data, and so on. A zero length read results in an acknowledge packet (Ack) being returned to the requestor. In one embodiment, a read of a half cache line or less may result in a short RdResp and a read of more than a half cache line may result in either a single long RdResp or two short RdResp. The cache line size may be programmed by software into the configuration registers of
host 100 and each memory control hub160. Address bits 25-16 of the requested location in cache are conveyed in bit positions 6-15. - During bit time two, the address bits 15-0 of the requested location in
cache 175 are conveyed in bit positions 7-16. During bit times three and four, bits 0-15 and 16-31, respectively, of a CRC are conveyed in bit positions 0-15. - It is noted that although only two types of packets were shown, other types of packets, which may correspond to the command codes listed in table 3 are contemplated. It is further noted that the illustrated packets are for discussion purposes only and that although the various fields of the exemplary packets are shown having a particular number of bits, it is contemplated that in other embodiments, the various fields of the each packet may include other numbers of bits as desired.
-
FIG. 7 is a block diagram of one embodiment of a computer system.Computer system 700 includesprocessor nodes 612A-612D each interconnected by coherentpacket interface links 615A-D. Each link of coherent packet interface 615 may form a high-speed point-to-point link.Processor nodes 612A-D may each include one or more processors.Computer system 700 also includes an I/O node 620 which is coupled toprocessor node 612A via anon-coherent packet interface 650A. I/O node 620 may be connected to another I/O node (not shown) in a chain topology for example, bynon-coherent packet interface 650B.Processor nodes 612A is illustrated as a host node and may include a host bridge for communicating with I/O node 620 viaNC packet interface 650A.Processor nodes 612B-D may also include host bridges for communication with other I/O nodes (not shown). The non-coherent packet interface links formed byNC packet interface 650A-B may also be referred to as point-to-point links. I/O node 620 is connected to a pair of peripheral buses 625A-B. -
FIG. 7 further illustrates respective system memories (e.g., 617A and 617B) coupled toprocessor nodes processor node FIG. 1 , and each system memory 617 may be implemented in the configuration described in conjunction with the descriptions ofFIG. 2 andFIG. 3 above. Further, the interconnects between each ofprocessor nodes memory link 110C described above inFIG. 1 throughFIG. 6 . It is noted that in other embodiments, other numbers of processor nodes may be used. Further, it is contemplated that each ofprocessor nodes system memory 617A may cache data stored within either ofsystem memories - In the illustrated embodiment, each link of coherent packet interface 615 is implemented as sets of unidirectional lines (
e.g. lines 615A are used to transmit packets from processingnode 612A toprocessing node 612B andlines 615B are used to transmit packets from processingnode 612B toprocessing node 612C). Other sets oflines 615C-D are used to transmit packets between other processing nodes as illustrated inFIG. 7 . The coherent packet interface 615 may be operated in a cache coherent fashion for communication between processing nodes (“the coherent link”). Further, non-coherent packet interface 650 may be operated in a non-coherent fashion for communication between I/O nodes and between I/O nodes and a host bridge such as the host bridge ofprocessor node 612A (“the non-coherent link”). The interconnection of two or more nodes via coherent links may be referred to as a “coherent fabric”. Similarly, the interconnection of two or more nodes via non-coherent links may be referred to as a “non-coherent fabric”. It is noted that a packet to be transmitted from one processing node to another may pass through one or more intermediate nodes. For example, a packet transmitted by processingnode 612A toprocessing node 612C may pass through eitherprocessing node 612B orprocessing node 612D as shown inFIG. 7 . Any suitable routing algorithm may be used. Other embodiments ofcomputer system 700 may include more or fewer processing nodes than the embodiment shown inFIG. 6 . - One example of a packet interface such as non-coherent packet interface 650 may be compatible with HyperTransport™ technology. Peripheral buses 625A and 625B are illustrative of a common peripheral bus such as a peripheral component interconnect (PCI) bus. It is understood, however, that other types of buses may be used.
- It is further noted that other computer system configurations are possible and contemplated. For example, it is contemplated that the system memory configuration described above may be used in conjunction with a computer system employing a processor chipset that includes a Northbridge. In such an embodiment, a memory controller within the Northbridge may serve as the host.
- Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
Claims (23)
1. A system comprising:
a host; and
one or more memory modules coupled serially in a chain to said host;
wherein at least one of said memory modules includes a cache for storing data stored in a system memory.
2. The system as recited in claim 1 , wherein said system memory includes a respective plurality of memory chips mounted on given memory modules of said one or more memory modules.
3. The system as recited in claim 2 , wherein each memory module includes a memory control hub including a controller configured to determine whether data associated with a received memory request is stored within said cache.
4. The system as recited in claim 3 , wherein a given cache includes a storage for storing cache tags corresponding to said data stored within said given cache.
5. The system as recited in claim 4 , wherein said controller is configured to access said cache in response to determining that said data associated with a received memory request is stored within said cache.
6. The system as recited in claim 2 , wherein said host includes a memory controller configured to generate memory requests to said one or more memory modules.
7. The system as recited in claim 6 , wherein said memory controller includes a storage for storing cache tags corresponding to said data stored within each cache.
8. The system as recited in claim 7 , wherein said memory control hub includes a controller configured to access said plurality of memory chips in response to receiving a memory command having a memory address that matches a memory address associated with said plurality of memory chips.
9. The system as recited in claim 8 , wherein said controller is further configured to access said cache in response to receiving a memory command having a memory address that matches a memory address associated with said cache.
10. The system as recited in claim 6 , wherein said memory controller is further configured to issue a memory read request transaction prior to receiving a response to a previous memory read request transaction.
11. The system as recited in claim 1 , wherein said one or more memory modules is coupled serially in a chain to said host via a plurality of memory links, wherein each memory link includes an uplink for conveying transactions toward said host and a downlink for conveying transactions originating at said host to a next memory module in said chain.
12. The system as recited in claim 11 , wherein said uplink and said downlink are each a unidirectional link including a plurality of signals configured to convey transactions using packets that include control and configuration packets and memory access packets, wherein at least a portion of packets include control, address and data information, and wherein said control, address and data information share the same wires of a given link.
13. The system as recited in claim 12 , wherein each of said plurality of signals of each of said unidirectional links uses differential signaling.
14. The system as recited in claim 13 , wherein said packets are conveyed on said uplink and said downlink using 16 bit positions to convey said control, address and data information.
15. A memory module comprising:
a cache configured to store data stored in a system memory;
a memory control hub coupled to control access to said storage;
wherein said memory control hub is configured to receive memory transactions originating at a processor via a first downlink and to transmit said memory transactions via a second downlink to another memory module independent of decoding said transactions.
16. The memory module as recited in claim 15 , wherein said system memory includes a respective plurality of memory chips mounted said memory module.
17. The memory module as recited in claim 16 , wherein said memory control hub includes a controller configured to determine whether data associated with a received memory request is stored within said cache.
18. The memory module as recited in claim 17 , wherein said cache is further configured to store cache tags corresponding to said data stored within said cache.
19. The memory module as recited in claim 18 , wherein said controller is configured to access said cache in response to determining that said data associated with a received memory request is stored within said cache.
20. The memory module as recited in claim 16 , wherein said processor includes a memory controller configured to generate memory requests to said memory module.
21. The memory module as recited in claim 20 , wherein said memory controller includes a storage for storing cache tags corresponding to data stored within said cache.
22. The memory module as recited in claim 21 , wherein said memory control hub includes a controller configured to access said plurality of memory chips in response to receiving a memory command having a memory address that matches a memory address associated with said plurality of memory chips.
23. The memory module as recited in claim 22 , wherein said controller is further configured to access said cache in response to receiving a memory command having a memory address that matches a memory address associated with said cache.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/842,298 US20050166006A1 (en) | 2003-05-13 | 2004-05-10 | System including a host connected serially in a chain to one or more memory modules that include a cache |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US47007803P | 2003-05-13 | 2003-05-13 | |
US10/842,298 US20050166006A1 (en) | 2003-05-13 | 2004-05-10 | System including a host connected serially in a chain to one or more memory modules that include a cache |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050166006A1 true US20050166006A1 (en) | 2005-07-28 |
Family
ID=33452363
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/842,297 Expired - Fee Related US7016213B2 (en) | 2003-05-13 | 2004-05-10 | Method for initializing a system including a host and plurality of memory modules connected via a serial memory interconnect |
US10/842,298 Abandoned US20050166006A1 (en) | 2003-05-13 | 2004-05-10 | System including a host connected serially in a chain to one or more memory modules that include a cache |
US10/842,296 Active 2024-11-26 US7421525B2 (en) | 2003-05-13 | 2004-05-10 | System including a host connected to a plurality of memory modules via a serial memory interconnect |
US10/842,339 Abandoned US20050071542A1 (en) | 2003-05-13 | 2004-05-10 | Prefetch mechanism for use in a system including a host connected to a plurality of memory modules via a serial memory interconnect |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/842,297 Expired - Fee Related US7016213B2 (en) | 2003-05-13 | 2004-05-10 | Method for initializing a system including a host and plurality of memory modules connected via a serial memory interconnect |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/842,296 Active 2024-11-26 US7421525B2 (en) | 2003-05-13 | 2004-05-10 | System including a host connected to a plurality of memory modules via a serial memory interconnect |
US10/842,339 Abandoned US20050071542A1 (en) | 2003-05-13 | 2004-05-10 | Prefetch mechanism for use in a system including a host connected to a plurality of memory modules via a serial memory interconnect |
Country Status (8)
Country | Link |
---|---|
US (4) | US7016213B2 (en) |
JP (1) | JP4836794B2 (en) |
KR (1) | KR101095025B1 (en) |
CN (1) | CN100444141C (en) |
DE (1) | DE112004000821B4 (en) |
GB (1) | GB2416056B (en) |
TW (1) | TWI351613B (en) |
WO (1) | WO2004102403A2 (en) |
Cited By (59)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040264256A1 (en) * | 2003-06-26 | 2004-12-30 | Mauritz Karl H | Electrical solution to enable high-speed interfaces |
US20050086441A1 (en) * | 2003-10-20 | 2005-04-21 | Meyer James W. | Arbitration system and method for memory responses in a hub-based memory system |
US20050132159A1 (en) * | 2002-08-16 | 2005-06-16 | Jeddeloh Joseph M. | Memory hub bypass circuit and method |
US20050223165A1 (en) * | 2004-03-31 | 2005-10-06 | Microsoft Corporation | Strategies for reading information from a mass storage medium using a cache memory |
US20060095671A1 (en) * | 2004-10-29 | 2006-05-04 | International Business Machines Corporation | System, method and storage medium for providing data caching and data compression in a memory subsystem |
US20060095646A1 (en) * | 2004-10-29 | 2006-05-04 | International Business Machines Corporation | System, method and storage medium for a memory subsystem command interface |
US20060156102A1 (en) * | 2005-01-11 | 2006-07-13 | Johnson Tyler J | System and method to control data capture |
US20060156290A1 (en) * | 2005-01-11 | 2006-07-13 | Johnson Tyler J | System and method to qualify data capture |
US20060155516A1 (en) * | 2005-01-11 | 2006-07-13 | Johnson Tyler J | System and method for data analysis |
US20060190674A1 (en) * | 2003-08-06 | 2006-08-24 | Peter Poechmueller | Hub chip for connecting one or more memory chips |
US20060200602A1 (en) * | 2003-08-20 | 2006-09-07 | Ralph James | Method and system for capturing and bypassing memory transactions in a hub-based memory system |
US20070153576A1 (en) * | 2005-09-30 | 2007-07-05 | Hakjune Oh | Memory with output control |
US20070165457A1 (en) * | 2005-09-30 | 2007-07-19 | Jin-Ki Kim | Nonvolatile memory system |
US20070233939A1 (en) * | 2006-03-31 | 2007-10-04 | Mosaid Technologies Incorporated | Flash memory system control scheme |
US20070288707A1 (en) * | 2006-06-08 | 2007-12-13 | International Business Machines Corporation | Systems and methods for providing data modification operations in memory subsystems |
US20070300129A1 (en) * | 2004-10-29 | 2007-12-27 | International Business Machines Corporation | System, method and storage medium for providing fault detection and correction in a memory subsystem |
US20080137467A1 (en) * | 2006-12-06 | 2008-06-12 | Mosaid Technologies Incorporated | Apparatus and method for capturing serial input data |
US20080183977A1 (en) * | 2007-01-29 | 2008-07-31 | International Business Machines Corporation | Systems and methods for providing a dynamic memory bank page policy |
US20080201588A1 (en) * | 2007-02-16 | 2008-08-21 | Mosaid Technologies Incorporated | Semiconductor device and method for reducing power consumption in a system having interconnected devices |
US20080201496A1 (en) * | 2007-02-16 | 2008-08-21 | Peter Gillingham | Reduced pin count interface |
US20080205187A1 (en) * | 2007-02-22 | 2008-08-28 | Mosaid Technologies Incorporated | Data flow control in multiple independent port |
US20100011174A1 (en) * | 2008-07-08 | 2010-01-14 | Mosaid Technologies Incorporated | Mixed data rates in memory devices and systems |
US7652922B2 (en) | 2005-09-30 | 2010-01-26 | Mosaid Technologies Incorporated | Multiple independent serial link memory |
US7669086B2 (en) | 2006-08-02 | 2010-02-23 | International Business Machines Corporation | Systems and methods for providing collision detection in a memory system |
US7685392B2 (en) | 2005-11-28 | 2010-03-23 | International Business Machines Corporation | Providing indeterminate read data latency in a memory system |
US7721140B2 (en) | 2007-01-02 | 2010-05-18 | International Business Machines Corporation | Systems and methods for improving serviceability of a memory system |
US7765368B2 (en) | 2004-07-30 | 2010-07-27 | International Business Machines Corporation | System, method and storage medium for providing a serialized memory interface with a bus repeater |
US20100199057A1 (en) * | 2005-09-30 | 2010-08-05 | Mosaid Technologies Incorporated | Independent link and bank selection |
US7774559B2 (en) | 2004-05-28 | 2010-08-10 | Micron Technology, Inc. | Method and system for terminating write commands in a hub-based memory system |
US7788451B2 (en) | 2004-02-05 | 2010-08-31 | Micron Technology, Inc. | Apparatus and method for data bypass for a bi-directional data bus in a hub-based memory sub-system |
US7805586B2 (en) | 2002-08-29 | 2010-09-28 | Micron Technology, Inc. | System and method for optimizing interconnections of memory devices in a multichip module |
US7818712B2 (en) | 2003-06-19 | 2010-10-19 | Round Rock Research, Llc | Reconfigurable memory module and method |
US7870459B2 (en) | 2006-10-23 | 2011-01-11 | International Business Machines Corporation | High density high reliability memory module with power gating and a fault tolerant address and command bus |
US7873775B2 (en) | 2003-08-28 | 2011-01-18 | Round Rock Research, Llc | Multiple processor system and method including multiple memory hub modules |
US20110016279A1 (en) * | 2009-07-16 | 2011-01-20 | Mosaid Technologies Incorporated | Simultaneous read and write data transfer |
US7904639B2 (en) | 2006-08-22 | 2011-03-08 | Mosaid Technologies Incorporated | Modular command structure for memory and memory system |
US20110078387A1 (en) * | 2009-09-28 | 2011-03-31 | International Business Machines Corporation | Writing to memory using shared address buses |
US20110078392A1 (en) * | 2009-09-28 | 2011-03-31 | International Business Machines Corporation | Writing to memory using adaptive write techniques |
US7934115B2 (en) | 2005-10-31 | 2011-04-26 | International Business Machines Corporation | Deriving clocks in a memory system |
US20110228600A1 (en) * | 2009-02-24 | 2011-09-22 | International Business Machines Corporation | Memory programming |
US8082404B2 (en) | 2004-03-24 | 2011-12-20 | Micron Technology, Inc. | Memory arbitration system and method having an arbitration packet protocol |
US8127081B2 (en) | 2003-06-20 | 2012-02-28 | Round Rock Research, Llc | Memory hub and access method having internal prefetch buffers |
US8164375B2 (en) | 2004-04-05 | 2012-04-24 | Round Rock Research, Llc | Delay line synchronizer apparatus and method |
US8296541B2 (en) | 2004-10-29 | 2012-10-23 | International Business Machines Corporation | Memory subsystem with positional read data latency |
US8463985B2 (en) | 2010-03-31 | 2013-06-11 | International Business Machines Corporation | Constrained coding to reduce floating gate coupling in non-volatile memories |
US8594110B2 (en) | 2008-01-11 | 2013-11-26 | Mosaid Technologies Incorporated | Ring-of-clusters network topologies |
US8825967B2 (en) | 2011-12-08 | 2014-09-02 | Conversant Intellectual Property Management Inc. | Independent write and read control in serially-connected devices |
US8843694B2 (en) | 2007-02-22 | 2014-09-23 | Conversant Intellectual Property Management Inc. | System and method of page buffer operation for memory devices |
US8880780B2 (en) | 2007-02-22 | 2014-11-04 | Conversant Intellectual Property Management Incorporated | Apparatus and method for using a page buffer of a memory device as a temporary cache |
US20150026394A1 (en) * | 2013-07-18 | 2015-01-22 | Postech Academy-Industry Foundation | Memory system and method of operating the same |
US9141541B2 (en) | 2013-09-20 | 2015-09-22 | Advanced Micro Devices, Inc. | Nested channel address interleaving |
US9240227B2 (en) | 2005-09-30 | 2016-01-19 | Conversant Intellectual Property Management Inc. | Daisy chain cascading devices |
US9389808B2 (en) | 2013-08-22 | 2016-07-12 | Kabushiki Kaisha Toshiba | Storage device and data processing method |
US9442877B2 (en) | 2013-01-10 | 2016-09-13 | Kabushiki Kaisha Toshiba | Storage device |
US20170286010A1 (en) * | 2016-03-29 | 2017-10-05 | Samsung Electronics Co., Ltd. | Method and apparatus for enabling larger memory capacity than physical memory size |
US10095421B2 (en) | 2016-10-21 | 2018-10-09 | Advanced Micro Devices, Inc. | Hybrid memory module bridge network and buffers |
US10496543B2 (en) | 2016-03-31 | 2019-12-03 | Samsung Electronics Co., Ltd. | Virtual bucket multiple hash tables for efficient memory in-line deduplication application |
US10678704B2 (en) | 2016-03-29 | 2020-06-09 | Samsung Electronics Co., Ltd. | Method and apparatus for enabling larger memory capacity than physical memory size |
US11948629B2 (en) | 2005-09-30 | 2024-04-02 | Mosaid Technologies Incorporated | Non-volatile memory device with concurrent bank operations |
Families Citing this family (162)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6464628B1 (en) | 1999-08-12 | 2002-10-15 | Obtech Medical Ag | Mechanical anal incontinence |
US6471635B1 (en) | 2000-02-10 | 2002-10-29 | Obtech Medical Ag | Anal incontinence disease treatment with controlled wireless energy supply |
AU759363B2 (en) | 2000-02-10 | 2003-04-10 | Implantica Patent Ltd. | Controlled urinary incontinence treatment |
EP1253877B1 (en) | 2000-02-10 | 2005-05-11 | Potencia Medical AG | Mechanical impotence treatment apparatus |
AU778406B2 (en) | 2000-02-11 | 2004-12-02 | Potentica Ag | Controlled impotence treatment |
EP1255514B1 (en) | 2000-02-14 | 2006-04-26 | Potencia Medical AG | Male impotence prosthesis apparatus with wireless energy supply |
DE60111019T2 (en) | 2000-02-14 | 2006-05-11 | Potencia Medical Ag | PROSTHESIS |
US7565326B2 (en) * | 2000-05-25 | 2009-07-21 | Randle William M | Dialect independent multi-dimensional integrator using a normalized language platform and secure controlled access |
US6791555B1 (en) * | 2000-06-23 | 2004-09-14 | Micron Technology, Inc. | Apparatus and method for distributed memory control in a graphics processing system |
US20030101312A1 (en) * | 2001-11-26 | 2003-05-29 | Doan Trung T. | Machine state storage apparatus and method |
US7133972B2 (en) | 2002-06-07 | 2006-11-07 | Micron Technology, Inc. | Memory hub with internal cache and/or memory access prediction |
US7200024B2 (en) * | 2002-08-02 | 2007-04-03 | Micron Technology, Inc. | System and method for optically interconnecting memory devices |
US7117316B2 (en) * | 2002-08-05 | 2006-10-03 | Micron Technology, Inc. | Memory hub and access method having internal row caching |
US7254331B2 (en) * | 2002-08-09 | 2007-08-07 | Micron Technology, Inc. | System and method for multiple bit optical data transmission in memory systems |
US6820181B2 (en) | 2002-08-29 | 2004-11-16 | Micron Technology, Inc. | Method and system for controlling memory accesses to memory modules having a memory hub architecture |
US7102907B2 (en) * | 2002-09-09 | 2006-09-05 | Micron Technology, Inc. | Wavelength division multiplexed memory module, memory system and method |
US7083420B2 (en) * | 2003-02-10 | 2006-08-01 | Leapfrog Enterprises, Inc. | Interactive handheld apparatus with stylus |
US7194581B2 (en) * | 2003-06-03 | 2007-03-20 | Intel Corporation | Memory channel with hot add/remove |
US7200787B2 (en) * | 2003-06-03 | 2007-04-03 | Intel Corporation | Memory channel utilizing permuting status patterns |
US7340537B2 (en) | 2003-06-04 | 2008-03-04 | Intel Corporation | Memory channel with redundant presence detect |
US7165153B2 (en) | 2003-06-04 | 2007-01-16 | Intel Corporation | Memory channel with unidirectional links |
US8171331B2 (en) * | 2003-06-04 | 2012-05-01 | Intel Corporation | Memory channel having deskew separate from redrive |
US7386768B2 (en) * | 2003-06-05 | 2008-06-10 | Intel Corporation | Memory channel with bit lane fail-over |
US7245145B2 (en) * | 2003-06-11 | 2007-07-17 | Micron Technology, Inc. | Memory module and method having improved signal routing topology |
US7428644B2 (en) * | 2003-06-20 | 2008-09-23 | Micron Technology, Inc. | System and method for selective memory module power management |
US7107415B2 (en) * | 2003-06-20 | 2006-09-12 | Micron Technology, Inc. | Posted write buffers and methods of posting write requests in memory modules |
US7389364B2 (en) | 2003-07-22 | 2008-06-17 | Micron Technology, Inc. | Apparatus and method for direct memory access in a hub-based memory system |
US7210059B2 (en) * | 2003-08-19 | 2007-04-24 | Micron Technology, Inc. | System and method for on-board diagnostics of memory modules |
US20050050237A1 (en) * | 2003-08-28 | 2005-03-03 | Jeddeloh Joseph M. | Memory module and method having on-board data search capabilities and processor-based system using such memory modules |
US7194593B2 (en) * | 2003-09-18 | 2007-03-20 | Micron Technology, Inc. | Memory hub with integrated non-volatile memory |
US7234070B2 (en) * | 2003-10-27 | 2007-06-19 | Micron Technology, Inc. | System and method for using a learning sequence to establish communications on a high-speed nonsynchronous interface in the absence of clock forwarding |
US7721060B2 (en) * | 2003-11-13 | 2010-05-18 | Intel Corporation | Method and apparatus for maintaining data density for derived clocking |
US7533218B2 (en) * | 2003-11-17 | 2009-05-12 | Sun Microsystems, Inc. | Memory system topology |
US20050138267A1 (en) * | 2003-12-23 | 2005-06-23 | Bains Kuljit S. | Integral memory buffer and serial presence detect capability for fully-buffered memory modules |
US7330992B2 (en) * | 2003-12-29 | 2008-02-12 | Micron Technology, Inc. | System and method for read synchronization of memory modules |
US7188219B2 (en) * | 2004-01-30 | 2007-03-06 | Micron Technology, Inc. | Buffer control system and method for a memory system having outstanding read and write request buffers |
US7181584B2 (en) * | 2004-02-05 | 2007-02-20 | Micron Technology, Inc. | Dynamic command and/or address mirroring system and method for memory modules |
US7412574B2 (en) * | 2004-02-05 | 2008-08-12 | Micron Technology, Inc. | System and method for arbitration of memory responses in a hub-based memory system |
US7366864B2 (en) | 2004-03-08 | 2008-04-29 | Micron Technology, Inc. | Memory hub architecture having programmable lane widths |
US20050210185A1 (en) * | 2004-03-18 | 2005-09-22 | Kirsten Renick | System and method for organizing data transfers with memory hub memory modules |
US7120723B2 (en) | 2004-03-25 | 2006-10-10 | Micron Technology, Inc. | System and method for memory hub-based expansion bus |
US7447240B2 (en) * | 2004-03-29 | 2008-11-04 | Micron Technology, Inc. | Method and system for synchronizing communications links in a hub-based memory system |
US7228442B2 (en) * | 2004-03-30 | 2007-06-05 | The Boeing Company | Method and systems for a radiation tolerant bus interface circuit |
US8050176B2 (en) * | 2004-03-30 | 2011-11-01 | The Boeing Company | Methods and systems for a data processing system having radiation tolerant bus |
US7590797B2 (en) * | 2004-04-08 | 2009-09-15 | Micron Technology, Inc. | System and method for optimizing interconnections of components in a multichip memory module |
US20050240574A1 (en) * | 2004-04-27 | 2005-10-27 | International Business Machines Corporation | Pre-fetching resources based on a resource lookup query |
US7162567B2 (en) * | 2004-05-14 | 2007-01-09 | Micron Technology, Inc. | Memory hub and method for memory sequencing |
US7222213B2 (en) * | 2004-05-17 | 2007-05-22 | Micron Technology, Inc. | System and method for communicating the synchronization status of memory modules during initialization of the memory modules |
US7212423B2 (en) | 2004-05-31 | 2007-05-01 | Intel Corporation | Memory agent core clock aligned to lane |
US7519788B2 (en) | 2004-06-04 | 2009-04-14 | Micron Technology, Inc. | System and method for an asynchronous data buffer having buffer write and read pointers |
US7310748B2 (en) * | 2004-06-04 | 2007-12-18 | Micron Technology, Inc. | Memory hub tester interface and method for use thereof |
US8122187B2 (en) * | 2004-07-02 | 2012-02-21 | Qualcomm Incorporated | Refreshing dynamic volatile memory |
US20060015450A1 (en) * | 2004-07-13 | 2006-01-19 | Wells Fargo Bank, N.A. | Financial services network and associated processes |
US7254663B2 (en) * | 2004-07-22 | 2007-08-07 | International Business Machines Corporation | Multi-node architecture with daisy chain communication link configurable to operate in unidirectional and bidirectional modes |
US7389375B2 (en) * | 2004-07-30 | 2008-06-17 | International Business Machines Corporation | System, method and storage medium for a multi-mode memory buffer device |
US20060036826A1 (en) * | 2004-07-30 | 2006-02-16 | International Business Machines Corporation | System, method and storage medium for providing a bus speed multiplier |
US7224595B2 (en) | 2004-07-30 | 2007-05-29 | International Business Machines Corporation | 276-Pin buffered memory module with enhanced fault tolerance |
US7392331B2 (en) * | 2004-08-31 | 2008-06-24 | Micron Technology, Inc. | System and method for transmitting data packets in a computer system having a memory hub architecture |
US7742438B1 (en) * | 2004-10-21 | 2010-06-22 | Owlink Technology, Inc. | HDCP data transmission over a single communication channel |
US20060095620A1 (en) * | 2004-10-29 | 2006-05-04 | International Business Machines Corporation | System, method and storage medium for merging bus data in a memory subsystem |
US7395476B2 (en) * | 2004-10-29 | 2008-07-01 | International Business Machines Corporation | System, method and storage medium for providing a high speed test interface to a memory subsystem |
US7356737B2 (en) * | 2004-10-29 | 2008-04-08 | International Business Machines Corporation | System, method and storage medium for testing a memory module |
US7305574B2 (en) * | 2004-10-29 | 2007-12-04 | International Business Machines Corporation | System, method and storage medium for bus calibration in a memory subsystem |
US7441060B2 (en) * | 2004-10-29 | 2008-10-21 | International Business Machines Corporation | System, method and storage medium for providing a service interface to a memory system |
US20070005902A1 (en) * | 2004-12-07 | 2007-01-04 | Ocz Technology Group, Inc. | Integrated sram cache for a memory module and method therefor |
US20060168407A1 (en) * | 2005-01-26 | 2006-07-27 | Micron Technology, Inc. | Memory hub system and method having large virtual page size |
US20060195631A1 (en) | 2005-01-31 | 2006-08-31 | Ramasubramanian Rajamani | Memory buffers for merging local data from memory modules |
US7620783B2 (en) * | 2005-02-14 | 2009-11-17 | Qualcomm Incorporated | Method and apparatus for obtaining memory status information cross-reference to related applications |
US7640392B2 (en) * | 2005-06-23 | 2009-12-29 | Qualcomm Incorporated | Non-DRAM indicator and method of accessing data not stored in DRAM array |
JP2006259906A (en) * | 2005-03-15 | 2006-09-28 | Ricoh Co Ltd | Communication control device, communication control system, power saving control method, power saving control program and recording medium recording program |
JP4274140B2 (en) | 2005-03-24 | 2009-06-03 | 日本電気株式会社 | Memory system with hot swap function and replacement method of faulty memory module |
US7827462B2 (en) | 2005-03-31 | 2010-11-02 | Intel Corporation | Combined command and data code |
US8112655B2 (en) | 2005-04-21 | 2012-02-07 | Violin Memory, Inc. | Mesosynchronous data bus apparatus and method of data transmission |
US9384818B2 (en) | 2005-04-21 | 2016-07-05 | Violin Memory | Memory power management |
US9286198B2 (en) | 2005-04-21 | 2016-03-15 | Violin Memory | Method and system for storage of data in non-volatile media |
US9582449B2 (en) | 2005-04-21 | 2017-02-28 | Violin Memory, Inc. | Interconnection system |
KR101331569B1 (en) * | 2005-04-21 | 2013-11-21 | 바이올린 메모리 인코포레이티드 | Interconnection System |
US8452929B2 (en) | 2005-04-21 | 2013-05-28 | Violin Memory Inc. | Method and system for storage of data in non-volatile media |
US20060288132A1 (en) * | 2005-05-31 | 2006-12-21 | Mccall James A | Memory single-to-multi load repeater architecture |
TWI285839B (en) * | 2005-06-22 | 2007-08-21 | Via Tech Inc | Selectively prefetch method and bridge module |
US20070016698A1 (en) * | 2005-06-22 | 2007-01-18 | Vogt Pete D | Memory channel response scheduling |
US7966446B2 (en) * | 2005-09-12 | 2011-06-21 | Samsung Electronics Co., Ltd. | Memory system and method having point-to-point link |
US7930492B2 (en) * | 2005-09-12 | 2011-04-19 | Samsung Electronics Co., Ltd. | Memory system having low power consumption |
US7496777B2 (en) | 2005-10-12 | 2009-02-24 | Sun Microsystems, Inc. | Power throttling in a memory system |
US7533212B1 (en) | 2005-10-20 | 2009-05-12 | Sun Microsystems, Inc. | System memory board subsystem using DRAM with integrated high speed point to point links |
US7523282B1 (en) | 2005-10-27 | 2009-04-21 | Sun Microsystems, Inc. | Clock enable throttling for power savings in a memory subsystem |
KR100818298B1 (en) | 2005-12-08 | 2008-03-31 | 한국전자통신연구원 | Memory with flexible serial interfaces and Method for accessing to Memory threreof |
US7409491B2 (en) | 2005-12-14 | 2008-08-05 | Sun Microsystems, Inc. | System memory board subsystem using DRAM with stacked dedicated high speed point to point links |
US7516349B2 (en) | 2005-12-29 | 2009-04-07 | Intel Corporation | Synchronized memory channels with unidirectional links |
KR100656814B1 (en) * | 2006-01-17 | 2006-12-14 | 신잔토개발 주식회사 | Separating and washing device for construction waste |
KR100801709B1 (en) * | 2006-05-16 | 2008-02-11 | 삼성전자주식회사 | Memory module and memory system comprising the same |
US8185711B2 (en) | 2006-05-16 | 2012-05-22 | Samsung Electronics Co., Ltd. | Memory module, a memory system including a memory controller and a memory module and methods thereof |
US7636813B2 (en) * | 2006-05-22 | 2009-12-22 | International Business Machines Corporation | Systems and methods for providing remote pre-fetch buffers |
US7640386B2 (en) * | 2006-05-24 | 2009-12-29 | International Business Machines Corporation | Systems and methods for providing memory modules with multiple hub devices |
US7430139B2 (en) * | 2006-06-12 | 2008-09-30 | Via Technologies, Inc. | Shared memory synchronization systems and methods |
US9262326B2 (en) * | 2006-08-14 | 2016-02-16 | Qualcomm Incorporated | Method and apparatus to enable the cooperative signaling of a shared bus interrupt in a multi-rank memory subsystem |
US7539842B2 (en) * | 2006-08-15 | 2009-05-26 | International Business Machines Corporation | Computer memory system for selecting memory buses according to physical memory organization information stored in virtual address translation tables |
US7757064B2 (en) * | 2006-09-07 | 2010-07-13 | Infineon Technologies Ag | Method and apparatus for sending data from a memory |
US8028186B2 (en) | 2006-10-23 | 2011-09-27 | Violin Memory, Inc. | Skew management in an interconnection system |
US20080104352A1 (en) * | 2006-10-31 | 2008-05-01 | Advanced Micro Devices, Inc. | Memory system including a high-speed serial buffer |
US7694031B2 (en) | 2006-10-31 | 2010-04-06 | Globalfoundries Inc. | Memory controller including a dual-mode memory interconnect |
US7861140B2 (en) * | 2006-10-31 | 2010-12-28 | Globalfoundries Inc. | Memory system including asymmetric high-speed differential memory interconnect |
US7949794B2 (en) * | 2006-11-02 | 2011-05-24 | Intel Corporation | PCI express enhancements and extensions |
US20080133864A1 (en) * | 2006-12-01 | 2008-06-05 | Jonathan Randall Hinkle | Apparatus, system, and method for caching fully buffered memory |
US7881303B2 (en) * | 2006-12-13 | 2011-02-01 | GlobalFoundries, Inc. | Command packet packing to mitigate CRC overhead |
US8032711B2 (en) * | 2006-12-22 | 2011-10-04 | Intel Corporation | Prefetching from dynamic random access memory to a static random access memory |
US7603526B2 (en) * | 2007-01-29 | 2009-10-13 | International Business Machines Corporation | Systems and methods for providing dynamic memory pre-fetch |
US7783918B2 (en) * | 2007-02-15 | 2010-08-24 | Inventec Corporation | Data protection method of storage device |
JP5669338B2 (en) * | 2007-04-26 | 2015-02-12 | 株式会社日立製作所 | Semiconductor device |
TW200901042A (en) * | 2007-06-23 | 2009-01-01 | Jmicron Technology Corp | Storage device and circuit element switching method thereof |
US7890788B2 (en) * | 2007-07-09 | 2011-02-15 | John Yin | Clock data recovery and synchronization in interconnected devices |
WO2009027802A1 (en) * | 2007-08-28 | 2009-03-05 | Nokia Corporation | Method for bus testing and addressing in mass memory components |
US20090063786A1 (en) * | 2007-08-29 | 2009-03-05 | Hakjune Oh | Daisy-chain memory configuration and usage |
KR100934227B1 (en) | 2007-09-21 | 2009-12-29 | 한국전자통신연구원 | Memory switching control device using open serial matching, its operation method and data storage device applied thereto |
US8503678B2 (en) | 2007-09-28 | 2013-08-06 | Intel Corporation | Suppressing power supply noise using data scrambling in double data rate memory systems |
JP2011502293A (en) * | 2007-10-05 | 2011-01-20 | ヴァイオリン メモリー インコーポレイテッド | Meso-synchronous data bus device and data transmission method |
EP2244662B1 (en) | 2008-01-28 | 2021-09-29 | Implantica Patent Ltd. | Blood clot removal device and system |
WO2009096861A1 (en) | 2008-01-29 | 2009-08-06 | Milux Holding Sa | Methods and instruments for treating obesity and gastroesophageal reflux disease |
US8131913B2 (en) * | 2008-02-04 | 2012-03-06 | Mosaid Technologies Incorporated | Selective broadcasting of data in series connected devices |
US8516185B2 (en) * | 2009-07-16 | 2013-08-20 | Netlist, Inc. | System and method utilizing distributed byte-wise buffers on a memory module |
US20100005206A1 (en) * | 2008-07-01 | 2010-01-07 | International Business Machines Corporation | Automatic read data flow control in a cascade interconnect memory system |
US8122421B2 (en) * | 2008-08-14 | 2012-02-21 | Omnivision Technologies, Inc. | System, and method, and computer readable medium for designing a scalable clustered storage integrated circuit for multi-media processing |
US8560735B2 (en) * | 2008-08-15 | 2013-10-15 | Micron Technology, Inc. | Chained bus method and device |
EP4282462A3 (en) | 2008-10-10 | 2024-02-21 | MedicalTree Patent Ltd. | Heart help device, system, and method |
WO2010042019A1 (en) | 2008-10-10 | 2010-04-15 | Milux Holding Sa | Heart help device, system, and method |
ES2962384T3 (en) | 2008-10-10 | 2024-03-18 | Implantica Patent Ltd | Device for the treatment of female sexual dysfunction |
US8874215B2 (en) | 2008-10-10 | 2014-10-28 | Peter Forsell | System, an apparatus, and a method for treating a sexual dysfunctional female patient |
WO2010042058A1 (en) | 2008-10-10 | 2010-04-15 | Milux Holding S.A. | An improved artificial valve |
EP2349078A4 (en) | 2008-10-10 | 2018-02-07 | Kirk Promotion LTD. | Fastening means for implantable medcial control assembly |
DE102009004565B4 (en) * | 2009-01-14 | 2015-04-02 | Texas Instruments Deutschland Gmbh | Apparatus and method for caching data between memory controller and DRAM |
CN101872308A (en) * | 2009-04-25 | 2010-10-27 | 鸿富锦精密工业(深圳)有限公司 | Memory bar control system and control method thereof |
US8046628B2 (en) * | 2009-06-05 | 2011-10-25 | Micron Technology, Inc. | Failure recovery memory devices and methods |
US10952836B2 (en) | 2009-07-17 | 2021-03-23 | Peter Forsell | Vaginal operation method for the treatment of urinary incontinence in women |
US9949812B2 (en) | 2009-07-17 | 2018-04-24 | Peter Forsell | Vaginal operation method for the treatment of anal incontinence in women |
US8923405B1 (en) * | 2010-01-25 | 2014-12-30 | Ambarella, Inc. | Memory access ordering for a transformation |
US20120079313A1 (en) * | 2010-09-24 | 2012-03-29 | Honeywell International Inc. | Distributed memory array supporting random access and file storage operations |
US11048410B2 (en) | 2011-08-24 | 2021-06-29 | Rambus Inc. | Distributed procedure execution and file systems on a memory interface |
WO2013028854A1 (en) | 2011-08-24 | 2013-02-28 | Rambus Inc. | Methods and systems for mapping a peripheral function onto a legacy memory interface |
US9098209B2 (en) | 2011-08-24 | 2015-08-04 | Rambus Inc. | Communication via a memory interface |
US8495440B2 (en) | 2011-08-30 | 2013-07-23 | Advanced Micro Devices, Inc. | Fully programmable parallel PRBS generator |
CN103959300A (en) | 2012-03-21 | 2014-07-30 | 三星Sds株式会社 | Anti-malware system and method for processing data in system |
CN102693337B (en) * | 2012-05-11 | 2014-04-30 | 江苏中科梦兰电子科技有限公司 | Method for designing memory device compatible with 8-bit and 16-bit memory chips |
US9285865B2 (en) | 2012-06-29 | 2016-03-15 | Oracle International Corporation | Dynamic link scaling based on bandwidth utilization |
US9390018B2 (en) * | 2012-08-17 | 2016-07-12 | Advanced Micro Devices, Inc. | Data cache prefetch hints |
US9348753B2 (en) | 2012-10-10 | 2016-05-24 | Advanced Micro Devices, Inc. | Controlling prefetch aggressiveness based on thrash events |
WO2014056178A1 (en) * | 2012-10-12 | 2014-04-17 | 华为技术有限公司 | Memory system, memory module, memory module access method and computer system |
JP6005533B2 (en) | 2013-01-17 | 2016-10-12 | 株式会社東芝 | Storage device and storage method |
CN104461727A (en) * | 2013-09-16 | 2015-03-25 | 华为技术有限公司 | Memory module access method and device |
JP2015152949A (en) | 2014-02-10 | 2015-08-24 | 株式会社東芝 | storage system |
US9558143B2 (en) | 2014-05-09 | 2017-01-31 | Micron Technology, Inc. | Interconnect systems and methods using hybrid memory cube links to send packetized data over different endpoints of a data handling device |
US9396065B2 (en) * | 2014-06-25 | 2016-07-19 | Intel Corporation | Extensible memory hub |
US9336047B2 (en) | 2014-06-30 | 2016-05-10 | International Business Machines Corporation | Prefetching of discontiguous storage locations in anticipation of transactional execution |
US9448939B2 (en) | 2014-06-30 | 2016-09-20 | International Business Machines Corporation | Collecting memory operand access characteristics during transactional execution |
US9348643B2 (en) | 2014-06-30 | 2016-05-24 | International Business Machines Corporation | Prefetching of discontiguous storage locations as part of transactional execution |
US9710271B2 (en) | 2014-06-30 | 2017-07-18 | International Business Machines Corporation | Collecting transactional execution characteristics during transactional execution |
US9600286B2 (en) | 2014-06-30 | 2017-03-21 | International Business Machines Corporation | Latent modification instruction for transactional execution |
US9792246B2 (en) | 2014-12-27 | 2017-10-17 | Intel Corporation | Lower-power scrambling with improved signal integrity |
US10573354B2 (en) * | 2016-09-22 | 2020-02-25 | Smart Modular Technologies, Inc. | High density memory module system |
US11373691B2 (en) | 2019-12-20 | 2022-06-28 | Micron Technology Inc. | Clock locking for packet based communications of memory devices |
US11513976B2 (en) * | 2020-03-31 | 2022-11-29 | Western Digital Technologies, Inc. | Advanced CE encoding for bus multiplexer grid for SSD |
TWI756810B (en) * | 2020-09-02 | 2022-03-01 | 瑞昱半導體股份有限公司 | Chip and associated chip system |
TWI802065B (en) * | 2021-10-29 | 2023-05-11 | 飛捷科技股份有限公司 | Communication interface adapter capable of controlling power and signals of peripheral devices, method for dynamically assigning identification codes of communication interface adapter, and method for automatically diagnosing peripheral devices and repairing problems |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5434861A (en) * | 1989-02-02 | 1995-07-18 | Pritty; David | Deterministic timed bus access method |
US5983323A (en) * | 1993-07-15 | 1999-11-09 | Bull, S.A. | Processor node |
US6249840B1 (en) * | 1998-10-23 | 2001-06-19 | Enhanced Memory Systems, Inc. | Multi-bank ESDRAM with cross-coupled SRAM cache registers |
US6553446B1 (en) * | 1999-09-29 | 2003-04-22 | Silicon Graphics Inc. | Modular input/output controller capable of routing packets over busses operating at different speeds |
US20040024978A1 (en) * | 2002-08-05 | 2004-02-05 | Jeddeloh Joseph M. | Memory hub and access method having internal row caching |
US20050021884A1 (en) * | 2003-07-22 | 2005-01-27 | Jeddeloh Joseph M. | Apparatus and method for direct memory access in a hub-based memory system |
US20050210216A1 (en) * | 2004-03-08 | 2005-09-22 | Jobs Jeffrey R | Memory hub architecture having programmable lane widths |
Family Cites Families (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4604689A (en) * | 1983-04-15 | 1986-08-05 | Convergent Technologies, Inc. | Bus repeater |
JPH0740225B2 (en) * | 1985-12-25 | 1995-05-01 | 日本電気株式会社 | Program skip operation control method |
GB2234372A (en) | 1989-07-18 | 1991-01-30 | Anamartic Ltd | Mass memory device |
IL96808A (en) * | 1990-04-18 | 1996-03-31 | Rambus Inc | Integrated circuit i/o using a high performance bus interface |
JP3548616B2 (en) * | 1995-01-20 | 2004-07-28 | 株式会社日立製作所 | Information processing equipment |
US6226723B1 (en) * | 1996-09-20 | 2001-05-01 | Advanced Memory International, Inc. | Bifurcated data and command/address communication bus architecture for random access memories employing synchronous communication protocols |
US5822766A (en) * | 1997-01-09 | 1998-10-13 | Unisys Corporation | Main memory interface for high speed data transfer |
JP3189727B2 (en) * | 1997-04-15 | 2001-07-16 | 日本電気株式会社 | Packet-type memory LSI with built-in coprocessor, memory system using the same, and control method therefor |
US6442644B1 (en) * | 1997-08-11 | 2002-08-27 | Advanced Memory International, Inc. | Memory system having synchronous-link DRAM (SLDRAM) devices and controller |
US6970968B1 (en) * | 1998-02-13 | 2005-11-29 | Intel Corporation | Memory module controller for providing an interface between a system memory controller and a plurality of memory devices on a memory module |
US6154821A (en) * | 1998-03-10 | 2000-11-28 | Rambus Inc. | Method and apparatus for initializing dynamic random access memory (DRAM) devices by levelizing a read domain |
US6643745B1 (en) * | 1998-03-31 | 2003-11-04 | Intel Corporation | Method and apparatus for prefetching data into cache |
US6587912B2 (en) * | 1998-09-30 | 2003-07-01 | Intel Corporation | Method and apparatus for implementing multiple memory buses on a memory module |
US6272601B1 (en) * | 1999-05-20 | 2001-08-07 | International Business Machines Corporation | Critical word forwarding in a multiprocessor system |
JP3892655B2 (en) * | 1999-09-17 | 2007-03-14 | 株式会社東芝 | Semiconductor integrated circuit device |
US6567023B1 (en) * | 1999-09-17 | 2003-05-20 | Kabushiki Kaisha Toshiba | Analog to digital to analog converter for multi-valued current data using internal binary voltage |
US6430648B1 (en) * | 2000-01-05 | 2002-08-06 | International Business Machines Corporation | Arranging address space to access multiple memory banks |
US6502161B1 (en) * | 2000-01-05 | 2002-12-31 | Rambus Inc. | Memory system including a point-to-point linked memory subsystem |
KR100335501B1 (en) * | 2000-06-09 | 2002-05-08 | 윤종용 | Memory modules with improved data bus performance |
US6625687B1 (en) | 2000-09-18 | 2003-09-23 | Intel Corporation | Memory module employing a junction circuit for point-to-point connection isolation, voltage translation, data synchronization, and multiplexing/demultiplexing |
US6658509B1 (en) * | 2000-10-03 | 2003-12-02 | Intel Corporation | Multi-tier point-to-point ring memory interface |
US6493250B2 (en) * | 2000-12-28 | 2002-12-10 | Intel Corporation | Multi-tier point-to-point buffered memory interface |
US6665742B2 (en) * | 2001-01-31 | 2003-12-16 | Advanced Micro Devices, Inc. | System for reconfiguring a first device and/or a second device to use a maximum compatible communication parameters based on transmitting a communication to the first and second devices of a point-to-point link |
US6571318B1 (en) * | 2001-03-02 | 2003-05-27 | Advanced Micro Devices, Inc. | Stride based prefetcher with confidence counter and dynamic prefetch-ahead mechanism |
US6877079B2 (en) | 2001-03-06 | 2005-04-05 | Samsung Electronics Co., Ltd. | Memory system having point-to-point bus configuration |
JP2002278825A (en) * | 2001-03-19 | 2002-09-27 | Ricoh Co Ltd | Memory control unit |
US6675272B2 (en) * | 2001-04-24 | 2004-01-06 | Rambus Inc. | Method and apparatus for coordinating memory operations among diversely-located memory components |
US6760817B2 (en) * | 2001-06-21 | 2004-07-06 | International Business Machines Corporation | Method and system for prefetching utilizing memory initiated prefetch write operations |
US7184408B2 (en) * | 2001-07-31 | 2007-02-27 | Denton I Claude | Method and apparatus for programmable generation of traffic streams |
DE10146491B4 (en) * | 2001-09-21 | 2006-04-13 | Infineon Technologies Ag | Electronic circuit with a driver circuit |
US6781911B2 (en) * | 2002-04-09 | 2004-08-24 | Intel Corporation | Early power-down digital memory device and method |
TW569096B (en) * | 2002-09-17 | 2004-01-01 | Integrated Technology Express | The cache/prefetch frame of serial data system and its method of operation |
US6996639B2 (en) * | 2002-12-10 | 2006-02-07 | Intel Corporation | Configurably prefetching head-of-queue from ring buffers |
-
2004
- 2004-05-10 US US10/842,297 patent/US7016213B2/en not_active Expired - Fee Related
- 2004-05-10 WO PCT/US2004/014441 patent/WO2004102403A2/en active Application Filing
- 2004-05-10 JP JP2006532883A patent/JP4836794B2/en active Active
- 2004-05-10 DE DE112004000821.2T patent/DE112004000821B4/en active Active
- 2004-05-10 US US10/842,298 patent/US20050166006A1/en not_active Abandoned
- 2004-05-10 KR KR1020057021598A patent/KR101095025B1/en active IP Right Grant
- 2004-05-10 CN CNB2004800131820A patent/CN100444141C/en active Active
- 2004-05-10 US US10/842,296 patent/US7421525B2/en active Active
- 2004-05-10 GB GB0521694A patent/GB2416056B/en active Active
- 2004-05-10 US US10/842,339 patent/US20050071542A1/en not_active Abandoned
- 2004-05-12 TW TW093113296A patent/TWI351613B/en active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5434861A (en) * | 1989-02-02 | 1995-07-18 | Pritty; David | Deterministic timed bus access method |
US5983323A (en) * | 1993-07-15 | 1999-11-09 | Bull, S.A. | Processor node |
US6249840B1 (en) * | 1998-10-23 | 2001-06-19 | Enhanced Memory Systems, Inc. | Multi-bank ESDRAM with cross-coupled SRAM cache registers |
US6553446B1 (en) * | 1999-09-29 | 2003-04-22 | Silicon Graphics Inc. | Modular input/output controller capable of routing packets over busses operating at different speeds |
US20040024978A1 (en) * | 2002-08-05 | 2004-02-05 | Jeddeloh Joseph M. | Memory hub and access method having internal row caching |
US20050021884A1 (en) * | 2003-07-22 | 2005-01-27 | Jeddeloh Joseph M. | Apparatus and method for direct memory access in a hub-based memory system |
US20050210216A1 (en) * | 2004-03-08 | 2005-09-22 | Jobs Jeffrey R | Memory hub architecture having programmable lane widths |
Cited By (131)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050132159A1 (en) * | 2002-08-16 | 2005-06-16 | Jeddeloh Joseph M. | Memory hub bypass circuit and method |
US7805586B2 (en) | 2002-08-29 | 2010-09-28 | Micron Technology, Inc. | System and method for optimizing interconnections of memory devices in a multichip module |
US7836252B2 (en) | 2002-08-29 | 2010-11-16 | Micron Technology, Inc. | System and method for optimizing interconnections of memory devices in a multichip module |
US8190819B2 (en) | 2002-08-29 | 2012-05-29 | Micron Technology, Inc. | System and method for optimizing interconnections of memory devices in a multichip module |
US7818712B2 (en) | 2003-06-19 | 2010-10-19 | Round Rock Research, Llc | Reconfigurable memory module and method |
US8732383B2 (en) | 2003-06-19 | 2014-05-20 | Round Rock Research, Llc | Reconfigurable memory module and method |
US7966444B2 (en) | 2003-06-19 | 2011-06-21 | Round Rock Research, Llc | Reconfigurable memory module and method |
US8200884B2 (en) | 2003-06-19 | 2012-06-12 | Round Rock Research, Llc | Reconfigurable memory module and method |
US8127081B2 (en) | 2003-06-20 | 2012-02-28 | Round Rock Research, Llc | Memory hub and access method having internal prefetch buffers |
US20040264256A1 (en) * | 2003-06-26 | 2004-12-30 | Mauritz Karl H | Electrical solution to enable high-speed interfaces |
US20060190674A1 (en) * | 2003-08-06 | 2006-08-24 | Peter Poechmueller | Hub chip for connecting one or more memory chips |
US20060200602A1 (en) * | 2003-08-20 | 2006-09-07 | Ralph James | Method and system for capturing and bypassing memory transactions in a hub-based memory system |
US7873775B2 (en) | 2003-08-28 | 2011-01-18 | Round Rock Research, Llc | Multiple processor system and method including multiple memory hub modules |
US9082461B2 (en) | 2003-08-28 | 2015-07-14 | Round Rock Research, Llc | Multiple processor system and method including multiple memory hub modules |
US8244952B2 (en) | 2003-08-28 | 2012-08-14 | Round Rock Research, Llc | Multiple processor system and method including multiple memory hub modules |
US7120743B2 (en) * | 2003-10-20 | 2006-10-10 | Micron Technology, Inc. | Arbitration system and method for memory responses in a hub-based memory system |
US20060136683A1 (en) * | 2003-10-20 | 2006-06-22 | Meyer James W | Arbitration system and method for memory responses in a hub-based memory system |
US8589643B2 (en) | 2003-10-20 | 2013-11-19 | Round Rock Research, Llc | Arbitration system and method for memory responses in a hub-based memory system |
US20050086441A1 (en) * | 2003-10-20 | 2005-04-21 | Meyer James W. | Arbitration system and method for memory responses in a hub-based memory system |
US7788451B2 (en) | 2004-02-05 | 2010-08-31 | Micron Technology, Inc. | Apparatus and method for data bypass for a bi-directional data bus in a hub-based memory sub-system |
US9164937B2 (en) | 2004-02-05 | 2015-10-20 | Micron Technology, Inc. | Apparatus and method for data bypass for a bi-directional data bus in a hub-based memory sub-system |
US8291173B2 (en) | 2004-02-05 | 2012-10-16 | Micron Technology, Inc. | Apparatus and method for data bypass for a bi-directional data bus in a hub-based memory sub-system |
US8694735B2 (en) | 2004-02-05 | 2014-04-08 | Micron Technology, Inc. | Apparatus and method for data bypass for a bi-directional data bus in a hub-based memory sub-system |
US8555006B2 (en) | 2004-03-24 | 2013-10-08 | Micron Technology, Inc. | Memory arbitration system and method having an arbitration packet protocol |
US8082404B2 (en) | 2004-03-24 | 2011-12-20 | Micron Technology, Inc. | Memory arbitration system and method having an arbitration packet protocol |
US9032166B2 (en) | 2004-03-24 | 2015-05-12 | Micron Technology, Inc. | Memory arbitration system and method having an arbitration packet protocol |
US7747823B2 (en) | 2004-03-31 | 2010-06-29 | Microsoft Corporation | Strategies for reading information from a mass storage medium using a cache memory |
US7337273B2 (en) * | 2004-03-31 | 2008-02-26 | Microsoft Corporation | Strategies for reading information from a mass storage medium using a cache memory |
US20050223165A1 (en) * | 2004-03-31 | 2005-10-06 | Microsoft Corporation | Strategies for reading information from a mass storage medium using a cache memory |
US8164375B2 (en) | 2004-04-05 | 2012-04-24 | Round Rock Research, Llc | Delay line synchronizer apparatus and method |
US7774559B2 (en) | 2004-05-28 | 2010-08-10 | Micron Technology, Inc. | Method and system for terminating write commands in a hub-based memory system |
US7765368B2 (en) | 2004-07-30 | 2010-07-27 | International Business Machines Corporation | System, method and storage medium for providing a serialized memory interface with a bus repeater |
US8589769B2 (en) | 2004-10-29 | 2013-11-19 | International Business Machines Corporation | System, method and storage medium for providing fault detection and correction in a memory subsystem |
US20070300129A1 (en) * | 2004-10-29 | 2007-12-27 | International Business Machines Corporation | System, method and storage medium for providing fault detection and correction in a memory subsystem |
US7299313B2 (en) * | 2004-10-29 | 2007-11-20 | International Business Machines Corporation | System, method and storage medium for a memory subsystem command interface |
US7844771B2 (en) | 2004-10-29 | 2010-11-30 | International Business Machines Corporation | System, method and storage medium for a memory subsystem command interface |
US8140942B2 (en) | 2004-10-29 | 2012-03-20 | International Business Machines Corporation | System, method and storage medium for providing fault detection and correction in a memory subsystem |
US20080016280A1 (en) * | 2004-10-29 | 2008-01-17 | International Business Machines Corporation | System, method and storage medium for providing data caching and data compression in a memory subsystem |
US20060095646A1 (en) * | 2004-10-29 | 2006-05-04 | International Business Machines Corporation | System, method and storage medium for a memory subsystem command interface |
US8296541B2 (en) | 2004-10-29 | 2012-10-23 | International Business Machines Corporation | Memory subsystem with positional read data latency |
US20070294466A1 (en) * | 2004-10-29 | 2007-12-20 | International Business Machines Corporation | System, method and storage medium for a memory subsystem command interface |
US20060095671A1 (en) * | 2004-10-29 | 2006-05-04 | International Business Machines Corporation | System, method and storage medium for providing data caching and data compression in a memory subsystem |
US7752016B2 (en) | 2005-01-11 | 2010-07-06 | Hewlett-Packard Development Company, L.P. | System and method for data analysis |
US20060156290A1 (en) * | 2005-01-11 | 2006-07-13 | Johnson Tyler J | System and method to qualify data capture |
US20060156102A1 (en) * | 2005-01-11 | 2006-07-13 | Johnson Tyler J | System and method to control data capture |
US7228472B2 (en) * | 2005-01-11 | 2007-06-05 | Hewlett-Packard Development Company, L.P. | System and method to control data capture |
US20060155516A1 (en) * | 2005-01-11 | 2006-07-13 | Johnson Tyler J | System and method for data analysis |
US7809991B2 (en) | 2005-01-11 | 2010-10-05 | Hewlett-Packard Development Company, L.P. | System and method to qualify data capture |
US11948629B2 (en) | 2005-09-30 | 2024-04-02 | Mosaid Technologies Incorporated | Non-volatile memory device with concurrent bank operations |
US8427897B2 (en) | 2005-09-30 | 2013-04-23 | Mosaid Technologies Incorporated | Memory with output control |
US20100199057A1 (en) * | 2005-09-30 | 2010-08-05 | Mosaid Technologies Incorporated | Independent link and bank selection |
US7719892B2 (en) | 2005-09-30 | 2010-05-18 | Mosaid Technologies Incorproated | Flash memory device with data output control |
US7826294B2 (en) | 2005-09-30 | 2010-11-02 | Mosaid Technologies Incorporated | Memory with output control |
US8654601B2 (en) | 2005-09-30 | 2014-02-18 | Mosaid Technologies Incorporated | Memory with output control |
US20100030951A1 (en) * | 2005-09-30 | 2010-02-04 | Mosaid Technologies Incorporated | Nonvolatile memory system |
US7652922B2 (en) | 2005-09-30 | 2010-01-26 | Mosaid Technologies Incorporated | Multiple independent serial link memory |
US8285960B2 (en) | 2005-09-30 | 2012-10-09 | Mosaid Technologies Incorporated | Independent link and bank selection |
US20110002171A1 (en) * | 2005-09-30 | 2011-01-06 | Mosaid Technologies Incorporated | Memory with output control |
US8738879B2 (en) | 2005-09-30 | 2014-05-27 | Conversant Intellectual Property Managament Inc. | Independent link and bank selection |
US20090073768A1 (en) * | 2005-09-30 | 2009-03-19 | Mosaid Technologies Incorporated | Memory with output control |
US8743610B2 (en) | 2005-09-30 | 2014-06-03 | Conversant Intellectual Property Management Inc. | Method and system for accessing a flash memory device |
US8199598B2 (en) | 2005-09-30 | 2012-06-12 | Mosaid Technologies Incorporated | Memory with output control |
TWI449048B (en) * | 2005-09-30 | 2014-08-11 | Mosaid Technologies Inc | Multiple independent serial link memory |
US9230654B2 (en) | 2005-09-30 | 2016-01-05 | Conversant Intellectual Property Management Inc. | Method and system for accessing a flash memory device |
US9240227B2 (en) | 2005-09-30 | 2016-01-19 | Conversant Intellectual Property Management Inc. | Daisy chain cascading devices |
US7945755B2 (en) | 2005-09-30 | 2011-05-17 | Mosaid Technologies Incorporated | Independent link and bank selection |
US11600323B2 (en) | 2005-09-30 | 2023-03-07 | Mosaid Technologies Incorporated | Non-volatile memory device with concurrent bank operations |
US20110179245A1 (en) * | 2005-09-30 | 2011-07-21 | Mosaid Technologies Incorporated | Independent link and bank selection |
US8000144B2 (en) | 2005-09-30 | 2011-08-16 | Mosaid Technologies Incorporated | Method and system for accessing a flash memory device |
US20070165457A1 (en) * | 2005-09-30 | 2007-07-19 | Jin-Ki Kim | Nonvolatile memory system |
US20070153576A1 (en) * | 2005-09-30 | 2007-07-05 | Hakjune Oh | Memory with output control |
US7934115B2 (en) | 2005-10-31 | 2011-04-26 | International Business Machines Corporation | Deriving clocks in a memory system |
US8145868B2 (en) | 2005-11-28 | 2012-03-27 | International Business Machines Corporation | Method and system for providing frame start indication in a memory system having indeterminate read data latency |
US8151042B2 (en) | 2005-11-28 | 2012-04-03 | International Business Machines Corporation | Method and system for providing identification tags in a memory system having indeterminate data response times |
US7685392B2 (en) | 2005-11-28 | 2010-03-23 | International Business Machines Corporation | Providing indeterminate read data latency in a memory system |
US8495328B2 (en) | 2005-11-28 | 2013-07-23 | International Business Machines Corporation | Providing frame start indication in a memory system having indeterminate read data latency |
US8327105B2 (en) | 2005-11-28 | 2012-12-04 | International Business Machines Corporation | Providing frame start indication in a memory system having indeterminate read data latency |
US20100325353A1 (en) * | 2006-03-31 | 2010-12-23 | Mosaid Technologies Incorporated | Flash memory system control scheme |
US20070233939A1 (en) * | 2006-03-31 | 2007-10-04 | Mosaid Technologies Incorporated | Flash memory system control scheme |
WO2007112555A1 (en) * | 2006-03-31 | 2007-10-11 | Mosaid Technologies Incorporated | Flash memory system control scheme |
TWI456582B (en) * | 2006-03-31 | 2014-10-11 | Mosaid Technologies Inc | Flash memory system control scheme |
EP2002442A1 (en) * | 2006-03-31 | 2008-12-17 | Mosaid Technologies Incorporated | Flash memory system control scheme |
EP2002442A4 (en) * | 2006-03-31 | 2009-05-06 | Mosaid Technologies Inc | Flash memory system control scheme |
US7802064B2 (en) | 2006-03-31 | 2010-09-21 | Mosaid Technologies Incorporated | Flash memory system control scheme |
US7584336B2 (en) * | 2006-06-08 | 2009-09-01 | International Business Machines Corporation | Systems and methods for providing data modification operations in memory subsystems |
US20070288707A1 (en) * | 2006-06-08 | 2007-12-13 | International Business Machines Corporation | Systems and methods for providing data modification operations in memory subsystems |
US7669086B2 (en) | 2006-08-02 | 2010-02-23 | International Business Machines Corporation | Systems and methods for providing collision detection in a memory system |
US7904639B2 (en) | 2006-08-22 | 2011-03-08 | Mosaid Technologies Incorporated | Modular command structure for memory and memory system |
US7870459B2 (en) | 2006-10-23 | 2011-01-11 | International Business Machines Corporation | High density high reliability memory module with power gating and a fault tolerant address and command bus |
US8904046B2 (en) | 2006-12-06 | 2014-12-02 | Conversant Intellectual Property Management Inc. | Apparatus and method for capturing serial input data |
TWI470437B (en) * | 2006-12-06 | 2015-01-21 | Conversant Intellectual Property Man Inc | Apparatus and method for capturing serial input data |
US20080137467A1 (en) * | 2006-12-06 | 2008-06-12 | Mosaid Technologies Incorporated | Apparatus and method for capturing serial input data |
US20100332685A1 (en) * | 2006-12-06 | 2010-12-30 | Mosaid Technologies Incorporated | Apparatus and method for capturing serial input data |
US7818464B2 (en) * | 2006-12-06 | 2010-10-19 | Mosaid Technologies Incorporated | Apparatus and method for capturing serial input data |
US7721140B2 (en) | 2007-01-02 | 2010-05-18 | International Business Machines Corporation | Systems and methods for improving serviceability of a memory system |
US20080183977A1 (en) * | 2007-01-29 | 2008-07-31 | International Business Machines Corporation | Systems and methods for providing a dynamic memory bank page policy |
US20080201588A1 (en) * | 2007-02-16 | 2008-08-21 | Mosaid Technologies Incorporated | Semiconductor device and method for reducing power consumption in a system having interconnected devices |
US20080201496A1 (en) * | 2007-02-16 | 2008-08-21 | Peter Gillingham | Reduced pin count interface |
US8122202B2 (en) | 2007-02-16 | 2012-02-21 | Peter Gillingham | Reduced pin count interface |
US8159893B2 (en) | 2007-02-22 | 2012-04-17 | Mosaid Technologies Incorporated | Data flow control in multiple independent port |
US8843694B2 (en) | 2007-02-22 | 2014-09-23 | Conversant Intellectual Property Management Inc. | System and method of page buffer operation for memory devices |
US7796462B2 (en) | 2007-02-22 | 2010-09-14 | Mosaid Technologies Incorporated | Data flow control in multiple independent port |
US8886871B2 (en) | 2007-02-22 | 2014-11-11 | Conversant Intellectual Property Management Incorporated | Apparatus and method of page program operation for memory devices with mirror back-up of data |
US20080205187A1 (en) * | 2007-02-22 | 2008-08-28 | Mosaid Technologies Incorporated | Data flow control in multiple independent port |
US8493808B2 (en) | 2007-02-22 | 2013-07-23 | Mosaid Technologies Incorporated | Data flow control in multiple independent port |
US8880780B2 (en) | 2007-02-22 | 2014-11-04 | Conversant Intellectual Property Management Incorporated | Apparatus and method for using a page buffer of a memory device as a temporary cache |
US8825966B2 (en) | 2007-08-22 | 2014-09-02 | Mosaid Technologies Incorporated | Reduced pin count interface |
US8902910B2 (en) | 2008-01-11 | 2014-12-02 | Conversant Intellectual Property Management Inc. | Ring-of-clusters network topologies |
US8594110B2 (en) | 2008-01-11 | 2013-11-26 | Mosaid Technologies Incorporated | Ring-of-clusters network topologies |
US8139390B2 (en) | 2008-07-08 | 2012-03-20 | Mosaid Technologies Incorporated | Mixed data rates in memory devices and systems |
US20100011174A1 (en) * | 2008-07-08 | 2010-01-14 | Mosaid Technologies Incorporated | Mixed data rates in memory devices and systems |
US8897062B2 (en) | 2009-02-24 | 2014-11-25 | International Business Machines Corporation | Memory programming for a phase change memory cell |
US20110228600A1 (en) * | 2009-02-24 | 2011-09-22 | International Business Machines Corporation | Memory programming |
US8521980B2 (en) | 2009-07-16 | 2013-08-27 | Mosaid Technologies Incorporated | Simultaneous read and write data transfer |
US20110016279A1 (en) * | 2009-07-16 | 2011-01-20 | Mosaid Technologies Incorporated | Simultaneous read and write data transfer |
US8898415B2 (en) | 2009-07-16 | 2014-11-25 | Conversant Intellectual Property Management Inc. | Simultaneous read and write data transfer |
US20110078392A1 (en) * | 2009-09-28 | 2011-03-31 | International Business Machines Corporation | Writing to memory using adaptive write techniques |
US8230276B2 (en) | 2009-09-28 | 2012-07-24 | International Business Machines Corporation | Writing to memory using adaptive write techniques |
US8386739B2 (en) * | 2009-09-28 | 2013-02-26 | International Business Machines Corporation | Writing to memory using shared address buses |
US20110078387A1 (en) * | 2009-09-28 | 2011-03-31 | International Business Machines Corporation | Writing to memory using shared address buses |
US8463985B2 (en) | 2010-03-31 | 2013-06-11 | International Business Machines Corporation | Constrained coding to reduce floating gate coupling in non-volatile memories |
US8825967B2 (en) | 2011-12-08 | 2014-09-02 | Conversant Intellectual Property Management Inc. | Independent write and read control in serially-connected devices |
US9442877B2 (en) | 2013-01-10 | 2016-09-13 | Kabushiki Kaisha Toshiba | Storage device |
US20150026394A1 (en) * | 2013-07-18 | 2015-01-22 | Postech Academy-Industry Foundation | Memory system and method of operating the same |
US9389808B2 (en) | 2013-08-22 | 2016-07-12 | Kabushiki Kaisha Toshiba | Storage device and data processing method |
US9141541B2 (en) | 2013-09-20 | 2015-09-22 | Advanced Micro Devices, Inc. | Nested channel address interleaving |
US10528284B2 (en) * | 2016-03-29 | 2020-01-07 | Samsung Electronics Co., Ltd. | Method and apparatus for enabling larger memory capacity than physical memory size |
US10678704B2 (en) | 2016-03-29 | 2020-06-09 | Samsung Electronics Co., Ltd. | Method and apparatus for enabling larger memory capacity than physical memory size |
US20170286010A1 (en) * | 2016-03-29 | 2017-10-05 | Samsung Electronics Co., Ltd. | Method and apparatus for enabling larger memory capacity than physical memory size |
US10496543B2 (en) | 2016-03-31 | 2019-12-03 | Samsung Electronics Co., Ltd. | Virtual bucket multiple hash tables for efficient memory in-line deduplication application |
US10095421B2 (en) | 2016-10-21 | 2018-10-09 | Advanced Micro Devices, Inc. | Hybrid memory module bridge network and buffers |
Also Published As
Publication number | Publication date |
---|---|
CN100444141C (en) | 2008-12-17 |
WO2004102403A3 (en) | 2005-08-25 |
KR20060009345A (en) | 2006-01-31 |
JP4836794B2 (en) | 2011-12-14 |
DE112004000821T5 (en) | 2006-05-11 |
TW200508875A (en) | 2005-03-01 |
US7016213B2 (en) | 2006-03-21 |
GB2416056A (en) | 2006-01-11 |
CN1788260A (en) | 2006-06-14 |
WO2004102403A2 (en) | 2004-11-25 |
GB0521694D0 (en) | 2005-11-30 |
US20040230718A1 (en) | 2004-11-18 |
DE112004000821B4 (en) | 2016-12-01 |
KR101095025B1 (en) | 2011-12-20 |
US20050162882A1 (en) | 2005-07-28 |
US7421525B2 (en) | 2008-09-02 |
JP2006528394A (en) | 2006-12-14 |
GB2416056B (en) | 2006-08-23 |
TWI351613B (en) | 2011-11-01 |
US20050071542A1 (en) | 2005-03-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20050166006A1 (en) | System including a host connected serially in a chain to one or more memory modules that include a cache | |
US8176257B2 (en) | Cache used both as cache and staging buffer | |
US7155572B2 (en) | Method and apparatus for injecting write data into a cache | |
US5892970A (en) | Multiprocessing system configured to perform efficient block copy operations | |
US6681293B1 (en) | Method and cache-coherence system allowing purging of mid-level cache entries without purging lower-level cache entries | |
US5749095A (en) | Multiprocessing system configured to perform efficient write operations | |
US6973543B1 (en) | Partial directory cache for reducing probe traffic in multiprocessor systems | |
US6490661B1 (en) | Maintaining cache coherency during a memory read operation in a multiprocessing computer system | |
US5878268A (en) | Multiprocessing system configured to store coherency state within multiple subnodes of a processing node | |
US6912612B2 (en) | Shared bypass bus structure | |
US6370621B1 (en) | Memory cancel response optionally cancelling memory controller's providing of data in response to a read operation | |
US5848254A (en) | Multiprocessing system using an access to a second memory space to initiate software controlled data prefetch into a first address space | |
KR101497002B1 (en) | Snoop filtering mechanism | |
US7062610B2 (en) | Method and apparatus for reducing overhead in a data processing system with a cache | |
US20020053004A1 (en) | Asynchronous cache coherence architecture in a shared memory multiprocessor with point-to-point links | |
JP2003099383A (en) | Node controller for data storage system | |
US6751705B1 (en) | Cache line converter | |
US7353340B2 (en) | Multiple independent coherence planes for maintaining coherency | |
US20070043912A1 (en) | Multi-socked symmetric multiprocessing (SMP) system for chip multi-threaded (CMT) processors | |
US6393529B1 (en) | Conversation of distributed memory bandwidth in multiprocessor system with cache coherency by transmitting cancel subsequent to victim write | |
US7797495B1 (en) | Distributed directory cache | |
US20090006712A1 (en) | Data ordering in a multi-node system | |
US6487626B2 (en) | Method and apparatus of bus interface for a processor | |
US5898894A (en) | CPU reads data from slow bus if I/O devices connected to fast bus do not acknowledge to a read request after a predetermined time interval | |
US6757793B1 (en) | Reducing probe traffic in multiprocessor systems using a victim record table |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ADVANCED MICRO DEVICES, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TALBOT, GERALD R.;WEBER, FREDERICK D.;PATEL, SHWETAL A.;REEL/FRAME:015314/0499;SIGNING DATES FROM 20040420 TO 20040504 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |