EP1204925A1 - Ampic dram system - Google Patents
Ampic dram systemInfo
- Publication number
- EP1204925A1 EP1204925A1 EP99907810A EP99907810A EP1204925A1 EP 1204925 A1 EP1204925 A1 EP 1204925A1 EP 99907810 A EP99907810 A EP 99907810A EP 99907810 A EP99907810 A EP 99907810A EP 1204925 A1 EP1204925 A1 EP 1204925A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- ampic
- resource
- stale
- read
- 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.)
- Withdrawn
Links
Classifications
-
- 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/0893—Caches characterised by their organisation or structure
-
- 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/0806—Multiuser, multiprocessor or multiprocessing cache systems
- G06F12/0815—Cache consistency protocols
Definitions
- the present invention relates to the validation of data to be read at a DRAM bank prior to such being read, to insure that it is current and up-to-date data; being more particularly, though not exclusively, directed to such validation of data read out of a multi-port internally cached DRAM memory system of the type described in co-pending US patent application Serial No.581,467 , filed December 29, 1995, for High Performance Universal Multi Port Internally Cached Dynamic Random Access Memory System, Architecture and Method, by Mu esh Chatter, and of common assignee herewith, and t ⁇ the ability to optimize the performance of such a device with a minimal amount of complexity.
- AMPIC devices multi-ported internally cached dynamically accessed memory systems
- - - independent serial interface cache data is written into the AMPIC device before writing it into shared internal DRAM banks, ovter which contention arises.
- the caching of the data received on the serial interfaces reduces the chances that internal contention to a particular DRAM bank will affect the overall external performance of the serial interfaces by increasing the number of requests that may be outstanding to a particular internal AMPIC DRAM bank before it becomes necessary to stop the writing of information on one of the external serial interfaces in order to avoid overrunning the limited write cache space for the particular serial interface.
- the time it takes the AMPIC device to write data into one of the internal DRAM banks can significantly vary up to some finite maximum amount of time. If data is written to a particular address in one of the internal DRAM banks within the AMPIC and that same address is requested before the written data moves from the write cache into the actual DRAM bank location specified by the address, the old data (or stale data) currently stored at that address will be returned instead of the newly written data in the event that the read access to the DRAM bank should be granted before the write access.
- data validation mechanisms are used for microprocessor caching and for networking data transmission validation, but these mechanisms differ greatly in purpose and in implementation from the invention described in the present application for use with the AMPIC technology.
- Designers of microprocessors have used memory caching techniques for some time, for example, to ease the bottleneck in processor performance between a processor and its memory. Basically, the processor keeps duplicate copies of smaller sections of what is in the main memory in a faster caching memory to improve performance. There is, however, the problem of keeping the duplicate copies of data up-to-date, or having the same value.
- data is placed in AMPIC devices, informing the destination of the existence of this data, and enabling the destination then actively to fetch the data
- AMPIC devices informing the destination of the existence of this data, and enabling the destination then actively to fetch the data
- specialized logic is provided in the AMPIC devices themselves to ensure that only valid data or appropriately marked invalid data is transmitted back to the destination source.
- the primary object of the present invention accordingly, is to provide a novel method of and apparatus for guaranteeing that only valid data is read out of a multi-port internally cached DRAM device (AMPIC), thereby eliminating any race condition in which stale data could potentially get read out of an AMPIC device before the desired data has actually been written into the appropriate internal AMPIC DRAM banks.
- AMPIC multi-port internally cached DRAM device
- a further object is to provide such an apparatus that can avoid dead-lock situations that may arise when the AMPIC device can not identify and return valid data within some finite amount of time.
- An additional object is to enable the scaling of the apparatus such that it is equally efficient with an array of AMPIC devices to validate data.
- the invention provides methods of guaranteeing that only valid data is read from a single multi-port internally cached DRAM device (AMPIC) or an array of such devices, where a plurality of system I/O resources read and write data into and out of an AMPIC device or devices through independent serial interfaces that contain caching to optimize the utilization of the shared internal DRAM banks,
- AMPIC internally cached DRAM device
- independent serial interfaces that contain caching to optimize the utilization of the shared internal DRAM banks
- the invention embraces in a multi-port internally cached array of AMPIC DRAM devices in which a plurality of system I/O resources write and read data into and out of DRAM banks through independent serial interfaces and along shared internal dala busses connected to corresponding DRAM banks in each unit of the array, a method, that comprises, checking the data stored at a particular address in a DRAM bank before reading out therefrom to a requesting system I/O resource, to guarantee against that data being stale, as from bus contention delays that have potentially prevented updated valid dala from having been written into the bank before it is requested to read out; and upon such checking that the data is up-to-date, transferring such valid data to the requesting system I/O resource.
- a method that comprises, checking the data stored at a particular address in a DRAM bank before reading out therefrom to a requesting system I/O resource, to guarantee against that data being stale, as from bus contention delays that have potentially prevented updated valid dala from having been written into the bank before it is requested to read out; and
- Fig. 1 is an illustrative block diagram of the internal architecture of the AMPIC DRAM of said co-pending application, the operation of which is enhanced by the present invention
- Fig. 2 is a block diagram of an illustrative system architecture based on the AMPIC DRAM of Fig. I :
- Fig, 3 illustrates a system in which a totally self contained AMPIC data validation scheme will not work
- Fig. 4 shows one type of system with a separate control and data path that requires some system level data validation scheme
- Fig. 5 illustrates how the stale bits are stored within all of the multi-port internally cached DRAM memory when the apparatus shown in Fig. 6 is used;
- Fig. 6 illustrates the preferred apparatus for and method of providing a novel mechanism and technique for guaranteeing only valid data is read out of a multi-port internally cached DRAM memory device (AMPIC device), in accordance with the present invention;
- AMPIC device multi-port internally cached DRAM memory device
- Fig. 7 illustrates a modification that, though not completely operating to guarantee only valid data read-out as in the system of Fig. 6, is still useful at least to identify the existence of stale or bad data;
- Fig. 8 illustrates where the stale bit is stored within the data in the AMPIC memory banks when using such modification that just identifies bad data read from AMPIC memories.
- Fig. 1 the basic structure provided by the AMPIC DRAM device of said co-pending application is illustrated in Fig. 1, providing a very high bandwidth connection between system I/O resources #0 through #Y- 1, applied at data ports or pins n to corresponding serial interfaces O through Y-l to DRAM memory array banks O through X-1 located within the AMPIC DRAM device.
- the architecture illustrated in Fig. I is all - encompassing of the different AMPIC memory devices that can be created by varying the number X of DRAM banks, varying the number Y of serial interfaces, and varying the number 'n' of data pins per serial interface.
- a system I/O resource for the purpose of the present invention refers to a block of logic that requires the ability to read and write data into an AMPIC device or a group of AMPIC devices.
- the AMPIC device shown in Fig. 1 provides a mechanism for transferring large amounts of data from one system I/O resource to another, granted that a source system I/O resource can inform a destination system I/O resource that is has placed data at a specific address inside of the AMPIC device for that destination system I/O resource.
- the AMPIC device contains internal DRAM banks each of which has 'k' number of memory locations in it, resulting in a total of l x*k' memory locations to which variable sized data blocks can be read and written.
- the maximum allowable data size is fixed by the particular implementation of the AMPIC device,
- Each of the AMPIC memory addresses identifies a particular memory location in a particular internal DRAM bank, to which data can be written and read through all of the serial data interfaces shown in Fig. 1 All system I/O resources can read and write all of the AMPIC memory locations through the serial interface to which they are connected.
- write control and write data busses connect with the right-hand inputs of the serial dala interface and to the write cache of the interface; for example, from system I/O resource #0 to serial data interface O.
- the read control bus is similarly applied to the interface O and to its read cache, which also connects to the read data bus of system I/O resource O All the serial interfaces share a common bus to access Dram bank O.
- This shared bus is independent of the shared bus that all of the interfaces use to access DRAM bank 1, allowing different serial interfaces to be accessing the different DRAM banks at the same time.
- the CPU port may have its own busses into each of the DRAM banks, as shown in Fig. 1, or it may also share the same busses that the serial interfaces must share to access the DRAM banks,
- each system I/O resource has a write control bus and a write data bus connected to one of the AMPIC device serial interfaces to write data into the AMPIC device.
- a system I/O resource sends an AMPIC address on its write control bus and the variable sized bloc c of data on its write data bus.
- the serial data interface on the AMPIC receives the address and data, it places such into the before-mentioned write cache of that serial data interface. After completing the current write operation into the serial data interface to which a particular system I/O resource is connected, it can immediately start writing another variable sized data burst to another AMPIC device address.
- each serial interface has the means to stall (or temporarily stop) the current data write transfer until enough space has been freed up in the write cache to finish completing the current write transfer.
- the serial data interface signals the system I/O resource to stop sending data through the system I/O resource write control bus.
- the serial data interfaces request access to internal DRAM banks in the AMPIC device.
- the schematically represented DRAM bank arbiters (there being one arbiter for each DRAM bank) grant the different serial data interfaces access to the DRAM banks of the AMPIC device, allowing the serial data interfaces to move the data from the write cache into the proper memory location in the internal DRAM banks
- the write caching is used in the serial data interfaces to help smooth over periods of contention when multiple serial data interfaces are attempting to write data into the same DRAM bank
- some of the serial interfaces are forced to stall the current write operations, as before-mentioned, in order to prevent their write caches from being overflowed.
- each system I/O resource has a read control bus and a read dala bus connected to one of the AMPIC device serial interfaces to read data from the AMPIC device.
- a system I/O resource wants to read the variable sized data block located at a particular AMPIC address, it writes the address into the AMPIC serial data interface to which it connects on its read control bus.
- the serial data interface on the AMPIC places the address in the read cache until it can gain control of the internal DRAM bank in which the data is stored and read it out. After retrieving the data, the serial data interface transmits the variable sized data block back to the system I/O resource.
- the AMPIC device is designed such that data from several addresses can be requested and stored in the read cache before the first variable sized data block is fetched and returned. This allows multiple blocks of data to be requested and retrieved out of the DRAM banks at the same lime.
- the flexibility of the AMPIC device is further enhanced by its ability to 'stack' multiple AMPIC devices into an array of AMPIC devices to create a much larger virtual AMPIC device, as illustrated in Fig, 2, showing AMPlCs 0, 1... M-l , each of the type shown in Fig. 1.
- This makes it possible to scale the data busses from the array of AMPIC devices or virtual AMPIC device to m*n bits that attach to N' system I/O resources, where there arc 'rn' AMPIC devices used, each of which has 'n' bits of data on the serial interfaces to read and write information into the AMPIC devices.
- This non-deterministic timing of the AMPIC device or virtual AMPIC device can potentially create a race condition where it becomes possible for the destination system I/O resource actually to request data before it has had time to be read out of a write cache data written into its destination internal AMPIC device DRAM bank.
- the logic required to check all the write caches for a particular address becomes a monstrous task when considering doing this for all requested addresses and for all serial ports, and in fast, orderly fashion.
- there are any pipelined ingress write transfer blocks of logic so-labeled in Fig.
- any data validation scheme entirely contained within a single AMPIC device or virtual AMPIC device will be inadequate because the AMPIC device will not be cognizant of the existence of the write operations in the ingress write transfer logic.
- An example of a system in which such ingress write transfer logic might be required is a system in which a set of backplane transceiver chips are required to send the write addresses and data across some type of high-speed serial interface before transferring the write information i ⁇ to'the AMPIC device itself Any data validation scheme that is going to be successful for such a system, therefore, must start at the same place at which the address is chosen for where to place the data in the AMPIC.
- FIG 4 illustrates one such type of system that has a separate control and data paLh in which an array of AMPIC devices or a virtual ⁇ MP1C device is used, and for which a system data validation scheme will be required to ensure that valid data is read out of the AMPIC devices. It is possible, indeed, for addresses to circulate around the separate control path and get inserted into the AMPIC DRAM devices before the data for the addresses have been written into the internal DRAM AMPIC banks.
- the novel apparatus and method of the invention can readily be implemented for guaranteeing that only valid data'is read out of the multi-port internally cached DRAM memory (AMPIC device), and also providing for avoiding dead-lock situations that may arise when the AMPIC device or virtual AMPIC device can not identify and return valid data within some finite amount of time.
- Systems like the one shown in Fig. 4 can therefore be readily modified to provide that the system I/O resources are guaranteed to obtain correct data, or appropriately marked invalid data, when the system I/O resources read the data out of a single AMPIC device or a virtual AMPIC device in the system.
- the invention works at the system level such that any amount of pipelined ingress write logic and any amount of pipelined egress read logic can be used without affecting the data validation scheme of the invention.
- the data validation scheme of the invention associates an extra bit, termed a "stale bit" herein, with each address location within an AMPIC device or virtual AMPIC device, and incorporates a new stale bit checking scheme into the architecture of the AMPIC device.
- Fig. 5 only shows exemplary system I/O resource O write control, system I/O resource O write data, system I/O resource Y-l read control, and system I/ resource Y-I read data busses, instead of showing all the system I/O resource busses as in Figs. 1 and 3,
- the data validation technique of the invention requires that the system I/O resource know the state of the stale bit for an address which corresponds to a location in one of the internal DRAM banks before the system I/O resource writes data to that AMPIC address. While the details of how the system I/O resource maintains this information is later discussed, for present purposes of explanation, it is first assumed that all of the stale bit locations at all of the addresses in the AMPIC devices in the array are set to zero.
- the system I/O resource must insert an address and a stale bit through its write control bus into the same serial interface on each of the AMPIC devices in the array of AMPIC devices, while the different bits of the data are distributed and written into different AMPIC devices in the array through the same system I/O resource write data bus.
- the same stale bit and different data are received on the same serial interface on different AMPIC devices in the array, the address, stale bit and data are written into each AMPIC device serial interface write cache.
- the data is then moved into the appropriate internal DRAM bank after that serial interface has been granted control over that particular DRAM bank. It should be noted that this happens on the same serial interface on all the AMPIC devices contained in the virtual AMPIC device at the same time because all AMPIC devices in a virtual AMPIC device are always synchronized, as previously explained.
- a different system I O resource may attempt to read the newly written data out of the virtual AMPIC device.
- the system I/O resource that wants to read the data, inserts the address and stale bit through its read control bus into all the AMPIC devices in the virtual AMPIC device.
- Each serial interface on the different AMPIC devices in the array all performing the same action at the same time, write the address and stale bit into their read cache.
- the serial interfaces of the virtual AMPIC device obtains access to the same internal DRAM bank in the virtual AMPIC device, the data is read out of the DRAM bank together with the writte ⁇ -in stale bit.
- the serial interface on the virtual AMPIC device connected to the requesting I/O resource will set an error bit in the data being transferred back so that the system I/O resource that requested the data will know that the data is not valid.
- Fig. 5 shows the address 0x5 and a stale bit of one being written through the system I/O resource O write control but into the serial interface O on all of the AMPIC devices in the virtual AMPIC device, while different bits of data AAA, BBB and * CCC are written to the different AMPIC devices through the system I/O O write data bus.
- Serial interface O on all the AMPIC devices in the virtual AMPIC device then temporarily stores this data into its write cache until the serial interface obtains permission to write the data into the appropriate location in the appropriate DRAM bank.
- the system I/O resource Y-I reads address 0x5 by inserting that address and a stale bit of one into the serial interface Y- l on all of the AMPIC devices in the, array O, I ...M-I ,
- the serial interface Y- l on all of the AMPIC devices in the virtual AMPIC device then fetches its section of data from the internal DRAM bank specified by the address.
- the serial interface Y-l on each AMPIC device in the virtual AMPIC device uses the stale checking logic to compare the stale bit inserted for the read access with the one that was read out of the internal DRAM bank location.
- the data is sent out on the Y-l serial interface on all the AMPIC devices in the virtual AMPIC device to system I/O resource Y-l that readit. If the stale bits do not match, the data has not been placed in the AMPIC DRAM bank yet, and all of the of Y-l serial interfaces on the AMPIC devices will fetch the data from that address location again and compare the stale bits again. This process continues until a data value is fetched that has a stale bit that matches the stale bit that was inserted on the read control serial interface, and the data from the address is sent to the system I/O resource that requested it.
- each AMPIC read access is only allowed to be outstanding for a finite maximum predetermined amount of time. If that amount of time expires before the stale bits match, an error bil is set in the data that is passed back to the system I/O resource. This prevents the AMPIC devices from entering a dead-lock stale when an error in the system occurs, and yet still provides the system I/O resource information so that it will not use invalid information.
- Fig. 6 includes flow chart information "A"-"F” showing what must be done in the system for this data validation scheme to work properly.
- the stale bit located in the data at every address must be programmed to zero in all of the AMPIC devices in the array through the CPU control interface ("A"). This ensures that all of the system I/O resources know the state of all the stale bits for the addresses that they will use Because the stale bit is inserted on the CPU control interface, it goes to all AMPIC devices in the system, not just one AMPIC device.
- the AMPIC devices will continue to fetch the data out of the particular memory location in one of the internal DRAM banks either until the stale bit inserted on the read control bus matches the stale bit stored with the data or until some finite amount of time has passed with no success If the stale bits match, the data is sent back to the system I/O resource that requested the data. If, however, the stale bits never match, an error bit is set within the data that is returned to system I/O resource that requested it, allowing the system I/O resource to discard that data instead of using invalid dala.
- the destination system I/O resource After the destination system I/O resource receives either the valid data, or the marked invalid data, it sends a message across the control path to the source system I/O resource saying that it is done with the address ("F"). The source system I/O resource then flips the stale bit associated with the returned address so that the next time it uses the address, it will know to use the opposite value for the stale bit ("G"). By flipping the value of the stale bit for a particular address each time a source I/O resource uses it, the AMPIC device internal stale checking logic can validate that data being sent to the system I/O resources is valid or invalid.
- FIG. 7 A modification that, while not achieving all the verification and control features of the preferred system of Fig. 6, is useful at least to identify the existence of stale or old data, is presented in Fig. 7, it employs a stale bit with each address in the AMPIC memory device, and works at the system level to provide an easy means for determining if the data retrieved from a requested address is valid or not. To achieve this result, one bit must be set aside in the same place of the data at every address in the virtual AMPIC device. When the AMPIC memory first powers-up, the stale bit stored in the data at every address must be written to a zero through the AMPIC CPU interfaces ("A").
- the source system I/O resource After transferring the data that contains the stale bit to the AMPIC devices in the virtual AMPIC device, the source system I/O resource then must send the destination I/O resource a message through the control path, stating that there is data available for it in a particular address with a stale bit of 1 ("D").
- the destination system I/O resource can then retrieve the data by inserting the address into the AMPIC device or array of AMPIC devices O'E").
- the destination system I/O resource can compare the stale bit contained in the data with the one that was sent to it by the source system I/O resource. If the two stale bits match, the data is the correct data that was sent.
- the stale bits do not match, it means that the ingress data had not been written into the appropriate internal AMPIC DRAM bank in the virtual AMPIC device by the time the address contents were requested by the destination I/O resource. If the destination I/O resource wants to try to get the correct data again, it can simply reinsert the address a second time in hopes that in the period of time since it received the incorrect data, the correct data was written into the internal DRAM bank in the AMPIC devices.
- This process of comparing the stale bits after data is returned for the address can be iterated until the correct data is finally retrieved.
- the destination I/O resource After the destination I/O resource has either retrieved the correct dala from the AMPIC devices or decided to give up re- requesting the data after a number of tries, the destination I/O resource sends the source I/O resource a message through the control path telling it that it can use the address again ("F").
- F the source I/O resource a message through the control path telling it that it can use the address again
- the stale bit in the data written to the address will be set to O since the stale value in the AMPIC memory devices will now be one ("G") .
- the stale bit By constantly flipping the stale bit each time of use of a particular AMPIC address, the stale bit always provides enough information to determine whether the data is the most current data, or the last data left over from the. previous data transfer.
- Fig, 8 makes clear that in this data validation method of Fig. 7, the stale bit actually resides in the data written to the AMPIC address and therefore only gets stored into one of the AMPIC devices in the virtual AMPIC device.
- This modified method of performing data validation can be used with a virtual AMPIC device that provides no internal stale checking scheme to create a system where all data read from AMPIC devices is validated before being used, providing a reliable method of ensuring that all data read out of the AMPIC devices is correct.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Dram (AREA)
- Memory System Of A Hierarchy Structure (AREA)
Abstract
Description
Claims
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IB1999/000529 WO2000058840A1 (en) | 1999-03-26 | 1999-03-26 | Ampic dram system |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1204925A1 true EP1204925A1 (en) | 2002-05-15 |
Family
ID=11004838
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP99907810A Withdrawn EP1204925A1 (en) | 1999-03-26 | 1999-03-26 | Ampic dram system |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1204925A1 (en) |
AU (1) | AU2742999A (en) |
CA (1) | CA2367878A1 (en) |
WO (1) | WO2000058840A1 (en) |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5655103A (en) * | 1995-02-13 | 1997-08-05 | International Business Machines Corporation | System and method for handling stale data in a multiprocessor system |
US5799209A (en) * | 1995-12-29 | 1998-08-25 | Chatter; Mukesh | Multi-port internally cached DRAM system utilizing independent serial interfaces and buffers arbitratively connected under a dynamic configuration |
-
1999
- 1999-03-26 CA CA002367878A patent/CA2367878A1/en not_active Abandoned
- 1999-03-26 AU AU27429/99A patent/AU2742999A/en not_active Abandoned
- 1999-03-26 EP EP99907810A patent/EP1204925A1/en not_active Withdrawn
- 1999-03-26 WO PCT/IB1999/000529 patent/WO2000058840A1/en not_active Application Discontinuation
Non-Patent Citations (1)
Title |
---|
See references of WO0058840A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2000058840A1 (en) | 2000-10-05 |
CA2367878A1 (en) | 2000-10-05 |
AU2742999A (en) | 2000-10-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6085290A (en) | Method of and apparatus for validating data read out of a multi port internally cached dynamic random access memory (AMPIC DRAM) | |
US7953936B2 (en) | Hiding conflict, coherence completion and transaction ID elements of a coherence protocol | |
US6799252B1 (en) | High-performance modular memory system with crossbar connections | |
US5263142A (en) | Input/output cache with mapped pages allocated for caching direct (virtual) memory access input/output data based on type of I/O devices | |
US6654858B1 (en) | Method for reducing directory writes and latency in a high performance, directory-based, coherency protocol | |
US6636949B2 (en) | System for handling coherence protocol races in a scalable shared memory system based on chip multiprocessing | |
US6636906B1 (en) | Apparatus and method for ensuring forward progress in coherent I/O systems | |
JP3557617B2 (en) | Microprocessor architecture capable of supporting multiple heterogeneous processors | |
US5664151A (en) | System and method of implementing read resources to maintain cache coherency in a multiprocessor environment permitting split transactions | |
EP0351955B1 (en) | Multiprocessor systems with cross-interrogated store-in-caches | |
US7668997B2 (en) | High speed bus system that incorporates uni-directional point-to-point buses | |
US7281092B2 (en) | System and method of managing cache hierarchies with adaptive mechanisms | |
US7418555B2 (en) | Multiprocessor system and method to maintain cache coherence | |
US7376793B2 (en) | Cache coherence protocol with speculative writestream | |
US6823431B2 (en) | Method for increasing efficiency in a multi-processor system and multi-processor system with increased efficiency | |
CA2183223A1 (en) | Symmetric multiprocessing computer with non-uniform memory access architecture | |
US20060265554A1 (en) | Apparatus and method of controlling data sharing on a shared memory computer system | |
US7469322B2 (en) | Data processing system and method for handling castout collisions | |
US6928519B2 (en) | Mechanism for maintaining cache consistency in computer systems | |
US7797495B1 (en) | Distributed directory cache | |
JP4112050B2 (en) | Method and system for maintaining strong ordering in a coherent memory system | |
WO2000058840A1 (en) | Ampic dram system | |
US5696938A (en) | Computer system permitting mulitple write buffer read-arounds and method therefor | |
US6847990B2 (en) | Data transfer unit with support for multiple coherency granules | |
EP1096384B1 (en) | Bridge unit between a system bus and a local bus |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20020117 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE Kind code of ref document: A1 Designated state(s): DE FR GB IT SE |
|
RBV | Designated contracting states (corrected) |
Designated state(s): DE FR GB IT SE |
|
17Q | First examination report despatched |
Effective date: 20030122 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20030603 |