CA1306312C - Write-shared cache circuit for multiprocessor system - Google Patents
Write-shared cache circuit for multiprocessor systemInfo
- Publication number
- CA1306312C CA1306312C CA000568258A CA568258A CA1306312C CA 1306312 C CA1306312 C CA 1306312C CA 000568258 A CA000568258 A CA 000568258A CA 568258 A CA568258 A CA 568258A CA 1306312 C CA1306312 C CA 1306312C
- Authority
- CA
- Canada
- Prior art keywords
- coupled
- ram
- cache
- cpu
- cache memory
- 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.)
- Expired - Fee Related
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/0806—Multiuser, multiprocessor or multiprocessing cache systems
- G06F12/0815—Cache consistency protocols
- G06F12/0831—Cache consistency protocols using a bus scheme, e.g. with bus monitoring or watching means
- G06F12/0833—Cache consistency protocols using a bus scheme, e.g. with bus monitoring or watching means in combination with broadcast means (e.g. for invalidation or updating)
Abstract
WRITE SHARED CACHE CIRCUIT FOR
MULTIPROCESSOR SYSTEM
Abstract of the Disclosure A "write-shared" cache circuit for multiprocessor systems maintains data consistency throughout the system and eliminates non-essential bus accesses by utilizing additional bus lines between caches of the system and by utilizing additional logic in order to enhance the inter-cache communication. Data is only written through to the system bus when the data is labeled "shared". A write-miss is read only once on the system bus in an "invalidate" cycle, and then it is written only to the requesting cache.
MULTIPROCESSOR SYSTEM
Abstract of the Disclosure A "write-shared" cache circuit for multiprocessor systems maintains data consistency throughout the system and eliminates non-essential bus accesses by utilizing additional bus lines between caches of the system and by utilizing additional logic in order to enhance the inter-cache communication. Data is only written through to the system bus when the data is labeled "shared". A write-miss is read only once on the system bus in an "invalidate" cycle, and then it is written only to the requesting cache.
Description
WRITE-SHARED CA~HE CIRCUIT FOR
Technical Field This invention relates generally to the area of digital data processing, and, in particular, to an improvement in a cache memory aircuit in a multiprocessor system.
Background of the Invention In a typical bus~based multiprocessor system, the bus band-width is exceeded with a small number of processors due to the necessity o~ the processors to access memory frequently for instructions and data. To overcome this problem, cache memories may be associated with each processor to act as a buffer between the processors and the system bus. Ideally, the cache is "hit" for a majority of the random access memory (RAM~ accesses, and the bus is used only a ~mall percentage of the time.
A problem associated with using cache memories in a multiprocessor system is data consistency. If a processor writes to its cache without notifying the other processors' caches, data will become inconsiste~t. For example, assume the following: processor "1" reads data block "A" from global RAM and then caches it; then that processor writes to that block, updating only its cache;
then processor "2" reads that same block "A" out of global RAM and caches it; processor "2" ends up with a di~ferent version of "A!' than processor "1'l. Their caches are inconsiste~t.
, . . :
Technical Field This invention relates generally to the area of digital data processing, and, in particular, to an improvement in a cache memory aircuit in a multiprocessor system.
Background of the Invention In a typical bus~based multiprocessor system, the bus band-width is exceeded with a small number of processors due to the necessity o~ the processors to access memory frequently for instructions and data. To overcome this problem, cache memories may be associated with each processor to act as a buffer between the processors and the system bus. Ideally, the cache is "hit" for a majority of the random access memory (RAM~ accesses, and the bus is used only a ~mall percentage of the time.
A problem associated with using cache memories in a multiprocessor system is data consistency. If a processor writes to its cache without notifying the other processors' caches, data will become inconsiste~t. For example, assume the following: processor "1" reads data block "A" from global RAM and then caches it; then that processor writes to that block, updating only its cache;
then processor "2" reads that same block "A" out of global RAM and caches it; processor "2" ends up with a di~ferent version of "A!' than processor "1'l. Their caches are inconsiste~t.
, . . :
Another way caches could become inconsistent would be if two caches held the same data blocks and only one of the processors updated that bloc}c in its cache. Again, a cache consistency problem would arise.
There exist several prior art solutions to the problem of cache consistency. Each of these attempts to solve the problem by writing all or some of the "writes"
through to global memory. These write-throughs are used to notify the other caches to invalidate like blocks.
However, each of these attempted solutions has one or more problems a~fecting the cache hit ratio and the bus utilization.
The prior art solutions can be grouped into three categories: (1) write-through, (2) global directory, and (3) write-invalidate.
The write-through scheme is the simplest to implement, but it is also the least effective. With this scheme, all "writes" are directed through the cache to global RAM. All other cache controllers monitor the bus ("i. e. snoop") and invalidate their corresponding entry if any "write" hits in their cache. Any data that would become inconsistent with the resulting "write" is invalidated. Hence, the consistency problem is solved.
However, since all "writes" are passed through to global RAM, the bus utilization is substantially increased.
Since about 15% of all accesses are "writes", and since all "writes" write-through on the bus as misses, the maximum hit ratio for a cache with this type of scheme is around 85~. Assuming hit ratios of around 75% to 85%, and bus access times twice the cache access times, the hus utilizations for this type of scheme would be around 30%
to 40% for each processor. Thus, only two to three proce~sors could use this bus before the bandwidth of the .
,, bus would be exceeded. This write-throuyh scheme yields low performance due ~o high bus contention and is not acceptable in a multiprocessor system having four or more processors.
The global directory scheme uses extra bits ~or each block in main memory and a memory controller to maintain information on how many processors have cached each block.
The major problem with this scheme is that, for large global RAM's, it is expensive. Two extra bits are required for each 32-bit block in global RAM, and memory controller hardware is also re~uired. For this extra expense, there is little, if any, performance increase over the "write-through" scheme.
The "write-invalidate" scheme writes-through only to invalidate those blocks which may reside in other caches.
One possible implementation of this scheme would be to perform a write-through on the first "write" to invalidate existing like aopies, but subsequent "writes" are written only to the cache. A new problem arises with this variation. When the "write" is only to the cache, that block becomes "dirty" (it is different in the cache than in global RAM)~ If another processor requests that block, the owning processor must either inhibit the RAM and supply that block itself, or it must halt the requesting processorr write the block back to global R~M, and let the requesting processor request that block again. This snoop requirement is tedious, and it uses multiple bus accesses, but it is necessary to maintain cache consistPncy.
Other "write-invalidate" variations have evolved to reduce the number of times the first write is requir~d.
For example, a routine developed at the University of California at Berkeley introduces the concept of "ownership". The Berkeley scheme includes two type of reads ("read-shared" and "read-for-ownership") and two types of writes ("write-for-invalidation" and "write-~3~
without-invalidation~) to reduce the bus utilization. The problem with the Berkeley routine is that the first "write" will only be eliminated if data is read and cached as private. If the block could possibly be shared, the first write would still be required to invalidate potential like blocks in other caches. Furthermore, a custom compiler which can determine when data will be shared or when it will be private is re~uired.
Summary of the Invention The present invention pertains to a cache circuit for a multiprocessor system which utilizes extra bus lines and corresponding logic for communication between multiple cache controllers. These extra bus lines allow the elimination of all write-throughs where data is not shared at that time betwsen processors. No special compiler is required to determine if the data can be shared, and, even if that data could be shared but is not at that time, the write-shared routine can still mark it as "private" (or "only").
Thus, it is an object of the present invention to provide a new and improved cache circuit for multiprocessor systems which reduces bus accesses while assuring data consistency.
It is a further object of the present invention to provide a new and improved cache circuit for multiprocessor systems which reduces bus accesses without requiring a special compiler.
~ hese and other objects of this invention will become apparent to those skilled in the art upon consideration of the accompanying specifica ion, claims, and drawings.
" ' , ' .
. ,: .
~L3~
Brief Description of the Drawings Referring to the drawings, whe~ein like characters indicate like parts throughout the figures:
FIG. 1 is a system level block diagram embodying the present invention;
FIG. 2 is a block diagram illustrating the central processing unit (CPU) interface logic implemented in conjunction with khe system of FIG. l;
FIG. 3 is block diagram illustrating the RAM
implemented in conjunction with the system o~ FIG. 1.
Description of the Preferred Embodiments Referring specifically to FIG. 1, a block diagram of a multiprocessor system, designated 10, is illustrated.
System 10 has a global RAM 12 connected to a series of CPU'~ 16 by a system bus 14. Each o~ the series of CPU's 16 has a cache memory 22 associated with it. Caches 22 are interconnected by both a SHARED bus line 24 and an INV
(Invalidate) bus line 26. Caches 22 are connected to RAM
12 by INHIBIT bus line 18 and TCOMP bus line 20.
SHARED bus line 24 is an open collector line that is pulled high when no cache controller (element 30 in FIG.
2) drives it low. As with other write-back schemes the cache controllers associated with each processor monitor (snoop) every access on the bus. If the snoop hits (i.e.
some other processor is requestin some data that is valid in this snooping cache), the hit cache controller asserts the SHARED bus line 24. The requesting processor then marks that data block as "shared". If that requesting processor then writes to that block, it must write-through to invalidate all other copies of that block. However, if ~3~
the SHARED bus line 24 was not asserted on the read, the data is marked as "only", and subsequent "wrltes" are not written through.
With the "shared" case, reading and writing data takes as many cycles as with the previously described write-back schemes. However, for the "non-shared" case, system 10 uses one less access of system bus 14. If no other cache 22 contained the requested data block, the requesting processor would mark the new data as "only".
Then, when that processor 16 wrote to that block, it would not write it through. It would write to its cache only and not use another bus cycle.
The above-mentioned prior art systems read data in assuming that it is shared, and they always write it through once. In the present invention, system 10 knows if each data block is shared or not with inter-cache communication supplied by SHARED bus line 24, and it only writes through for the "shared" data. ~'Non-shared" data write-throughs are eliminated by using SHARED bus line 24.
The INV (Invalidate) bus line 26 also eliminates unnecessary bus accesses. Line 26 is also open-collector and is used during a write miss. If the first access to a data block is a write instead of a read, the data block may have to be read from global RAM 12 into cache 22 before it is written. If the size of the write is smaller than the block size (e.g. writing only a byte), the portion of the block that is not a~fected by the write must be read in first so the entire block in the cache will be correct. For example, if CPU 16 is executing a byte write, its cache 22 must first read in the entire blocX and then write the byte to CPU 16. If the block wasn't first read into cache 22, only the written byte, and not the entire block, would be valid in cache 22.
Since a write miss is really a read-write sequence, it could take two cycles of system bus 14. The first , ~ , .' ~ . .'..~ -.
.
.
cycle would be used to read the data in, and the second cycle would be required to invalidate shared blocks. To eliminate this second access of system bus 14, the INV bus lina 26 is used. INV bus line 26 is asserted during the read portion of the read-write sequence to invalidate any and all of the shared blocks. Then the "write" is written only to the reques~ing cache 22, and that block is set as "dirty".
The TCOMP (Transfer COMPlete) bu~ line 20 is utilized to signal that all receiving caches 22 have completed their snoop of the data transfer. For example, for every bus access, global RAM 12, as well as every cache snoop in the system 10, must assert the TCOMP signal to signal a complete transfer.
The SHARED bus line 24 and INV line 26 are used for coordination between the multiple caches 22. The INHIBIT
line 18 i9 used for coordination between individual caches 22 and the global RAM 12. And the TCOMP line 20 is used system-wide to signal that all receiving units have completed the transfer. The cache controllers (e.g. 30, FIG. 2) associated with every processor 16 include logic to drive and receive the SHARED, INV, and TCOMP lines, and they include logic to drive the INHIBIT line. The RAM
card 70 includes logic to receive the INHIBIT line 18 and to drive the TCOMP line 20. The INHIBIT bus line 18 is utilized to inhibit RAM card 70 from responding. The functions of lines 18 and 20 are described below in more detail regarding FIGS. 2 and 3.
Referring specifically to FIG. 2, a block diagram of the logic associated with each CPU to interface to bus lines 18, 20, 24, and 26 is shown. Three major units of this logic are seen in FIG. 2: cache 32, cache controller 30, and snoop controller 34. Other sections of the CPU
logic such as the processor, the standard bus interface, , , ~3~
etc. are commonly known to those skilled in the art and therefore not shown in FIG. 2.
The cache logic units of cache 32 include cache tag RAM 40 which holds the upper half of the cached addresses, the cache state bits logic 42 which holds the 2 bits per block that denote what state the block is in, and the cache data RAM 44 which holds the cached data. For eve~y address that comes into cache 32 on address line 36, the lower portion labeled the "index" addresses the cache lo logi~ units 40, 42, and 4~. compara~or 50 has an input ~upplied from cache tag RAM 40 and another input supplied from the upper portion of address line 36. If these inputs match (i.e. the ADDR TAG matches the CACHE TAG), that access is valid in cache 32.
Cache controller 30 examines the cache state bits from logic circuit 42 for that block and takes appropriate action. For example, if the access is a "write-hit" and the state of the block is "only", cache controller 30 simply writes to cache 32. If the state of ~he block was "shared", cache controller 30 has to write to cache 32 and also write through to system bus 14.
Snoop controller 34 monitors the address strobe line (labeled "AS") on system bus line 14. When "AS" is asserted, that means that another CPU is accessing system bus line 14. Since all caches must snoop on the bus to maintain cache consistency, snoop controller 34 must run the 'IBus Addr" lines throuyh its cache for bus accesses by the other CPU's. To do this, snoop controller 34 disables the "CPU Addr" line and enables the "Bus Addr" line 37 onto the address line 36 by driving "CPU/Snoop" line 38 low. Snoop controller 34 also asserts the "snoop has bus' line 39 to notify cache controller 30 that the next cache access is a snoop.
When the "Bus Addr" 37 line has been enabled onto the "Addr" line 36, cache 32 is checked as described above.
~3~63~
If the snoop "hits" in cache 32, cache controller 30 checks the cache state bits 42 of the hit block and again takes appropriate action. For example, if the hit is a "read shared", the cache controller 30 pulls the "SHARED"
bus line 24 to notify the requesting CPU that it should cache that data item as "shared". If the "hitl' cache block is "dirty", cache controller 30 asserts 'IINHIBIT"
bus line 18 (to keep RAM 12 ~rom responding) and then provides the "dirty~ data itself. Finally, cache lo controller 30 would reset that block as "shared".
For every snoop, cache controller 30 asserts TCOMP
bus line 20 to signal that it has completed the snoop.
~he requesting CPU will not complete its bus cycle until all other cache controllers (as well as global RAM 12) have asserted ~COMP. Bus requester 55 is used to notify cache controller 30 when it is the bus master. When each CPU is the bus master, it does not snoop, and it does not assert TCOMP.
Referring specifically to FIG. 3, the RAM and associated logic 70 are shown in hlock diagram form. RAM
logic 70 differs from ordinary RAM logic in that the "INHIBIT" bus line 18 is included in the "Address Decode"
logic 72. If ''INHIBITIl is asserted, RAM logic 70 must not respond, even if the address on system bus 14 correctly decodes to select RAM logic 70. Also, when the "INHIBIT" signal is asserted, it means that some cache controller is supplying previous}y "dirty" data to another cache. This data that is being asserted on system bus 14 must be written into global RAM 12, so that the shared data in the caches will remain consistent in global RAM
12. To accomplish this "write", global RAM 12 holds off "TCOMP" while it writes the data that is asserted on system bus 14 to the appropriate address. Once the write is done, and that data block is consistent throughout the 31L3~3~
system, the RAM card 70 asserts "TCOMP", and the bus cycle is complete.
Also, for every normal bus cycle, the RAM logic 70 must assert TCOMP (along with the normal DTACK data transfer acknowledge) to notify that the transfer is complete.
In summary, the "write-shared" circuit of the present invention uses hardware to eliminate all non-essential bus accesses in a bus-based multiprocessor system employing private caches. By using extra bus lines for communication between cache controllers, the "write-shared" circuit dynamically determines whether data blocks are shared or private. Data blocks cached as private do not require an extra write-through to invalidate other like blocks in other aaches. Since the bus utilization is lower, higher system performance is achieved, and more processors can be used on a single bus.
The Appendix provides the states and detailed state transitions for cache accesses ànd snoop accesses for the "write-shared" cirauit of the present invention.
Through the descriptions of the figures an improved cache circuit for multiprocessor systems has been disclosed. Further modifications and improvements of the circuit will occur to those skilled in the art. I desire it to be understood, therefore, that this invention is not limited to the particular form shown, and I intend in the appended claims to cover all modifications which do not depart from the spirit and scope of this invention.
~. :
;
P~PPENDIX
STATES:
Invalid - RAM is not in the cache.
Shared RAM has been read to cache and was only, shared, or dirty in another cache.
Only - RAM has been read to cache and it is the only cached copy.
Dirty - Cache has been written and is now different than the RAM
copy .
Internal:
Replacement Invalid, only, or shared - simply write over block dirty - write back to RAM, then write over.
Read Invalid Read whole block from RAM, if SHARED
(or miss) asserted, set shared, if SHARED
unasserted, set only.
25 Write Invalid Read whole block from RAM and assert INV, write to cache, set dirty.
Read Shared Read from cache, leave shared.
Write Sharèd Write to RAM and cache, set only.
Read Only Read from cache, Ieave only.
30 Write Only Write to cache, set dirty.
Read Dirty Read from cache, leave dirty Write dirty Write to cache, leave dirty.
.
, -12~
APPENDIX
Cache Snoop:
Read Invalid Do nothing.
(or mis~) Write Invalid Do nothing.
(or miss) Read Shared Assert SHARED, leave shared.
INV & Read Shared Assert SHARED, set invalid.
Write Shared Set Invalid.
Read Only Assert SH~RED, set to shared.
INV & Read Only Assert SHAR~D, set invalid.
Write Only Not possible.
Read Dirty Inhibit RAM (by ass~rting INHIBIT), provide data and DTACK, assert SHARE~, set shared; data is also written to RAM (so the copy is valid in RAM as well).
INV & Read Dirty Same as above but set invalid.
Write Dirty Not possible . .
~ !
-~
' .
There exist several prior art solutions to the problem of cache consistency. Each of these attempts to solve the problem by writing all or some of the "writes"
through to global memory. These write-throughs are used to notify the other caches to invalidate like blocks.
However, each of these attempted solutions has one or more problems a~fecting the cache hit ratio and the bus utilization.
The prior art solutions can be grouped into three categories: (1) write-through, (2) global directory, and (3) write-invalidate.
The write-through scheme is the simplest to implement, but it is also the least effective. With this scheme, all "writes" are directed through the cache to global RAM. All other cache controllers monitor the bus ("i. e. snoop") and invalidate their corresponding entry if any "write" hits in their cache. Any data that would become inconsistent with the resulting "write" is invalidated. Hence, the consistency problem is solved.
However, since all "writes" are passed through to global RAM, the bus utilization is substantially increased.
Since about 15% of all accesses are "writes", and since all "writes" write-through on the bus as misses, the maximum hit ratio for a cache with this type of scheme is around 85~. Assuming hit ratios of around 75% to 85%, and bus access times twice the cache access times, the hus utilizations for this type of scheme would be around 30%
to 40% for each processor. Thus, only two to three proce~sors could use this bus before the bandwidth of the .
,, bus would be exceeded. This write-throuyh scheme yields low performance due ~o high bus contention and is not acceptable in a multiprocessor system having four or more processors.
The global directory scheme uses extra bits ~or each block in main memory and a memory controller to maintain information on how many processors have cached each block.
The major problem with this scheme is that, for large global RAM's, it is expensive. Two extra bits are required for each 32-bit block in global RAM, and memory controller hardware is also re~uired. For this extra expense, there is little, if any, performance increase over the "write-through" scheme.
The "write-invalidate" scheme writes-through only to invalidate those blocks which may reside in other caches.
One possible implementation of this scheme would be to perform a write-through on the first "write" to invalidate existing like aopies, but subsequent "writes" are written only to the cache. A new problem arises with this variation. When the "write" is only to the cache, that block becomes "dirty" (it is different in the cache than in global RAM)~ If another processor requests that block, the owning processor must either inhibit the RAM and supply that block itself, or it must halt the requesting processorr write the block back to global R~M, and let the requesting processor request that block again. This snoop requirement is tedious, and it uses multiple bus accesses, but it is necessary to maintain cache consistPncy.
Other "write-invalidate" variations have evolved to reduce the number of times the first write is requir~d.
For example, a routine developed at the University of California at Berkeley introduces the concept of "ownership". The Berkeley scheme includes two type of reads ("read-shared" and "read-for-ownership") and two types of writes ("write-for-invalidation" and "write-~3~
without-invalidation~) to reduce the bus utilization. The problem with the Berkeley routine is that the first "write" will only be eliminated if data is read and cached as private. If the block could possibly be shared, the first write would still be required to invalidate potential like blocks in other caches. Furthermore, a custom compiler which can determine when data will be shared or when it will be private is re~uired.
Summary of the Invention The present invention pertains to a cache circuit for a multiprocessor system which utilizes extra bus lines and corresponding logic for communication between multiple cache controllers. These extra bus lines allow the elimination of all write-throughs where data is not shared at that time betwsen processors. No special compiler is required to determine if the data can be shared, and, even if that data could be shared but is not at that time, the write-shared routine can still mark it as "private" (or "only").
Thus, it is an object of the present invention to provide a new and improved cache circuit for multiprocessor systems which reduces bus accesses while assuring data consistency.
It is a further object of the present invention to provide a new and improved cache circuit for multiprocessor systems which reduces bus accesses without requiring a special compiler.
~ hese and other objects of this invention will become apparent to those skilled in the art upon consideration of the accompanying specifica ion, claims, and drawings.
" ' , ' .
. ,: .
~L3~
Brief Description of the Drawings Referring to the drawings, whe~ein like characters indicate like parts throughout the figures:
FIG. 1 is a system level block diagram embodying the present invention;
FIG. 2 is a block diagram illustrating the central processing unit (CPU) interface logic implemented in conjunction with khe system of FIG. l;
FIG. 3 is block diagram illustrating the RAM
implemented in conjunction with the system o~ FIG. 1.
Description of the Preferred Embodiments Referring specifically to FIG. 1, a block diagram of a multiprocessor system, designated 10, is illustrated.
System 10 has a global RAM 12 connected to a series of CPU'~ 16 by a system bus 14. Each o~ the series of CPU's 16 has a cache memory 22 associated with it. Caches 22 are interconnected by both a SHARED bus line 24 and an INV
(Invalidate) bus line 26. Caches 22 are connected to RAM
12 by INHIBIT bus line 18 and TCOMP bus line 20.
SHARED bus line 24 is an open collector line that is pulled high when no cache controller (element 30 in FIG.
2) drives it low. As with other write-back schemes the cache controllers associated with each processor monitor (snoop) every access on the bus. If the snoop hits (i.e.
some other processor is requestin some data that is valid in this snooping cache), the hit cache controller asserts the SHARED bus line 24. The requesting processor then marks that data block as "shared". If that requesting processor then writes to that block, it must write-through to invalidate all other copies of that block. However, if ~3~
the SHARED bus line 24 was not asserted on the read, the data is marked as "only", and subsequent "wrltes" are not written through.
With the "shared" case, reading and writing data takes as many cycles as with the previously described write-back schemes. However, for the "non-shared" case, system 10 uses one less access of system bus 14. If no other cache 22 contained the requested data block, the requesting processor would mark the new data as "only".
Then, when that processor 16 wrote to that block, it would not write it through. It would write to its cache only and not use another bus cycle.
The above-mentioned prior art systems read data in assuming that it is shared, and they always write it through once. In the present invention, system 10 knows if each data block is shared or not with inter-cache communication supplied by SHARED bus line 24, and it only writes through for the "shared" data. ~'Non-shared" data write-throughs are eliminated by using SHARED bus line 24.
The INV (Invalidate) bus line 26 also eliminates unnecessary bus accesses. Line 26 is also open-collector and is used during a write miss. If the first access to a data block is a write instead of a read, the data block may have to be read from global RAM 12 into cache 22 before it is written. If the size of the write is smaller than the block size (e.g. writing only a byte), the portion of the block that is not a~fected by the write must be read in first so the entire block in the cache will be correct. For example, if CPU 16 is executing a byte write, its cache 22 must first read in the entire blocX and then write the byte to CPU 16. If the block wasn't first read into cache 22, only the written byte, and not the entire block, would be valid in cache 22.
Since a write miss is really a read-write sequence, it could take two cycles of system bus 14. The first , ~ , .' ~ . .'..~ -.
.
.
cycle would be used to read the data in, and the second cycle would be required to invalidate shared blocks. To eliminate this second access of system bus 14, the INV bus lina 26 is used. INV bus line 26 is asserted during the read portion of the read-write sequence to invalidate any and all of the shared blocks. Then the "write" is written only to the reques~ing cache 22, and that block is set as "dirty".
The TCOMP (Transfer COMPlete) bu~ line 20 is utilized to signal that all receiving caches 22 have completed their snoop of the data transfer. For example, for every bus access, global RAM 12, as well as every cache snoop in the system 10, must assert the TCOMP signal to signal a complete transfer.
The SHARED bus line 24 and INV line 26 are used for coordination between the multiple caches 22. The INHIBIT
line 18 i9 used for coordination between individual caches 22 and the global RAM 12. And the TCOMP line 20 is used system-wide to signal that all receiving units have completed the transfer. The cache controllers (e.g. 30, FIG. 2) associated with every processor 16 include logic to drive and receive the SHARED, INV, and TCOMP lines, and they include logic to drive the INHIBIT line. The RAM
card 70 includes logic to receive the INHIBIT line 18 and to drive the TCOMP line 20. The INHIBIT bus line 18 is utilized to inhibit RAM card 70 from responding. The functions of lines 18 and 20 are described below in more detail regarding FIGS. 2 and 3.
Referring specifically to FIG. 2, a block diagram of the logic associated with each CPU to interface to bus lines 18, 20, 24, and 26 is shown. Three major units of this logic are seen in FIG. 2: cache 32, cache controller 30, and snoop controller 34. Other sections of the CPU
logic such as the processor, the standard bus interface, , , ~3~
etc. are commonly known to those skilled in the art and therefore not shown in FIG. 2.
The cache logic units of cache 32 include cache tag RAM 40 which holds the upper half of the cached addresses, the cache state bits logic 42 which holds the 2 bits per block that denote what state the block is in, and the cache data RAM 44 which holds the cached data. For eve~y address that comes into cache 32 on address line 36, the lower portion labeled the "index" addresses the cache lo logi~ units 40, 42, and 4~. compara~or 50 has an input ~upplied from cache tag RAM 40 and another input supplied from the upper portion of address line 36. If these inputs match (i.e. the ADDR TAG matches the CACHE TAG), that access is valid in cache 32.
Cache controller 30 examines the cache state bits from logic circuit 42 for that block and takes appropriate action. For example, if the access is a "write-hit" and the state of the block is "only", cache controller 30 simply writes to cache 32. If the state of ~he block was "shared", cache controller 30 has to write to cache 32 and also write through to system bus 14.
Snoop controller 34 monitors the address strobe line (labeled "AS") on system bus line 14. When "AS" is asserted, that means that another CPU is accessing system bus line 14. Since all caches must snoop on the bus to maintain cache consistency, snoop controller 34 must run the 'IBus Addr" lines throuyh its cache for bus accesses by the other CPU's. To do this, snoop controller 34 disables the "CPU Addr" line and enables the "Bus Addr" line 37 onto the address line 36 by driving "CPU/Snoop" line 38 low. Snoop controller 34 also asserts the "snoop has bus' line 39 to notify cache controller 30 that the next cache access is a snoop.
When the "Bus Addr" 37 line has been enabled onto the "Addr" line 36, cache 32 is checked as described above.
~3~63~
If the snoop "hits" in cache 32, cache controller 30 checks the cache state bits 42 of the hit block and again takes appropriate action. For example, if the hit is a "read shared", the cache controller 30 pulls the "SHARED"
bus line 24 to notify the requesting CPU that it should cache that data item as "shared". If the "hitl' cache block is "dirty", cache controller 30 asserts 'IINHIBIT"
bus line 18 (to keep RAM 12 ~rom responding) and then provides the "dirty~ data itself. Finally, cache lo controller 30 would reset that block as "shared".
For every snoop, cache controller 30 asserts TCOMP
bus line 20 to signal that it has completed the snoop.
~he requesting CPU will not complete its bus cycle until all other cache controllers (as well as global RAM 12) have asserted ~COMP. Bus requester 55 is used to notify cache controller 30 when it is the bus master. When each CPU is the bus master, it does not snoop, and it does not assert TCOMP.
Referring specifically to FIG. 3, the RAM and associated logic 70 are shown in hlock diagram form. RAM
logic 70 differs from ordinary RAM logic in that the "INHIBIT" bus line 18 is included in the "Address Decode"
logic 72. If ''INHIBITIl is asserted, RAM logic 70 must not respond, even if the address on system bus 14 correctly decodes to select RAM logic 70. Also, when the "INHIBIT" signal is asserted, it means that some cache controller is supplying previous}y "dirty" data to another cache. This data that is being asserted on system bus 14 must be written into global RAM 12, so that the shared data in the caches will remain consistent in global RAM
12. To accomplish this "write", global RAM 12 holds off "TCOMP" while it writes the data that is asserted on system bus 14 to the appropriate address. Once the write is done, and that data block is consistent throughout the 31L3~3~
system, the RAM card 70 asserts "TCOMP", and the bus cycle is complete.
Also, for every normal bus cycle, the RAM logic 70 must assert TCOMP (along with the normal DTACK data transfer acknowledge) to notify that the transfer is complete.
In summary, the "write-shared" circuit of the present invention uses hardware to eliminate all non-essential bus accesses in a bus-based multiprocessor system employing private caches. By using extra bus lines for communication between cache controllers, the "write-shared" circuit dynamically determines whether data blocks are shared or private. Data blocks cached as private do not require an extra write-through to invalidate other like blocks in other aaches. Since the bus utilization is lower, higher system performance is achieved, and more processors can be used on a single bus.
The Appendix provides the states and detailed state transitions for cache accesses ànd snoop accesses for the "write-shared" cirauit of the present invention.
Through the descriptions of the figures an improved cache circuit for multiprocessor systems has been disclosed. Further modifications and improvements of the circuit will occur to those skilled in the art. I desire it to be understood, therefore, that this invention is not limited to the particular form shown, and I intend in the appended claims to cover all modifications which do not depart from the spirit and scope of this invention.
~. :
;
P~PPENDIX
STATES:
Invalid - RAM is not in the cache.
Shared RAM has been read to cache and was only, shared, or dirty in another cache.
Only - RAM has been read to cache and it is the only cached copy.
Dirty - Cache has been written and is now different than the RAM
copy .
Internal:
Replacement Invalid, only, or shared - simply write over block dirty - write back to RAM, then write over.
Read Invalid Read whole block from RAM, if SHARED
(or miss) asserted, set shared, if SHARED
unasserted, set only.
25 Write Invalid Read whole block from RAM and assert INV, write to cache, set dirty.
Read Shared Read from cache, leave shared.
Write Sharèd Write to RAM and cache, set only.
Read Only Read from cache, Ieave only.
30 Write Only Write to cache, set dirty.
Read Dirty Read from cache, leave dirty Write dirty Write to cache, leave dirty.
.
, -12~
APPENDIX
Cache Snoop:
Read Invalid Do nothing.
(or mis~) Write Invalid Do nothing.
(or miss) Read Shared Assert SHARED, leave shared.
INV & Read Shared Assert SHARED, set invalid.
Write Shared Set Invalid.
Read Only Assert SH~RED, set to shared.
INV & Read Only Assert SHAR~D, set invalid.
Write Only Not possible.
Read Dirty Inhibit RAM (by ass~rting INHIBIT), provide data and DTACK, assert SHARE~, set shared; data is also written to RAM (so the copy is valid in RAM as well).
INV & Read Dirty Same as above but set invalid.
Write Dirty Not possible . .
~ !
-~
' .
Claims (5)
1. A multiprocessor system comprising:
a random access memory (RAM) (12);
a plurality of central processing units (CPU's) (16);
a plurality of cache memories (22), one of said cache memories being coupled to each of said plurality of CPU's;
a plurality of logic means for coordinating data transfer, one of said logic means being coupled to each of said plurality of cache memories;
a system bus (14) to which said RAM, said plurality of CPU's, and said plurality of cache memories are coupled, said system bus enabling address and data information to be exchanged among said RAM, said plurality of CPU's, and said plurality of cache memories;
a first signal line (SHARED) (24) to which each of said plurality of logic means is coupled;
a first one of said plurality of logic means, being coupled to a first cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether a data block being read by a CPU
coupled to a second cache memory of said plurality of cache memories is contained in said first cache memory and, if so, generating a first signal level on said first signal line, and otherwise generating a second signal level on said first signal line; and a second one of said plurality of logic means, being coupled to said second cache memory, comprising means for enabling said CPU coupled to said second cache memory, if it subsequently performs a write operation to a data block in said second cache memory, to write the data in said data block through to said RAM if said first signal level is present on said first signal line, and for inhibiting said CPU from writing said data through to said RAM if said second signal level is present on said first signal line, whereby said CPU coupled to said second cache memory is inhibited from using said system bus when it performs a write operation on said data block in said second cache memory, if said data block is not contained in said first cache memory, thereby reducing traffic on said system bus.
a random access memory (RAM) (12);
a plurality of central processing units (CPU's) (16);
a plurality of cache memories (22), one of said cache memories being coupled to each of said plurality of CPU's;
a plurality of logic means for coordinating data transfer, one of said logic means being coupled to each of said plurality of cache memories;
a system bus (14) to which said RAM, said plurality of CPU's, and said plurality of cache memories are coupled, said system bus enabling address and data information to be exchanged among said RAM, said plurality of CPU's, and said plurality of cache memories;
a first signal line (SHARED) (24) to which each of said plurality of logic means is coupled;
a first one of said plurality of logic means, being coupled to a first cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether a data block being read by a CPU
coupled to a second cache memory of said plurality of cache memories is contained in said first cache memory and, if so, generating a first signal level on said first signal line, and otherwise generating a second signal level on said first signal line; and a second one of said plurality of logic means, being coupled to said second cache memory, comprising means for enabling said CPU coupled to said second cache memory, if it subsequently performs a write operation to a data block in said second cache memory, to write the data in said data block through to said RAM if said first signal level is present on said first signal line, and for inhibiting said CPU from writing said data through to said RAM if said second signal level is present on said first signal line, whereby said CPU coupled to said second cache memory is inhibited from using said system bus when it performs a write operation on said data block in said second cache memory, if said data block is not contained in said first cache memory, thereby reducing traffic on said system bus.
2. A multiprocessor system comprising:
a random access memory (RAM) (12);
a plurality of central processing units (CPU's) (16);
a plurality of cache memories (22), one of said cache memories being coupled to each of said plurality of CPU's;
a plurality of logic means for coordinating data transfer, one of said logic means being coupled to each of said plurality of cache memories;
a system bus (14) to which said RAM, said plurality of CPU's, and said plurality of cache memories are coupled, said system bus enabling address and data information to be exchanged among said RAM, said plurality of CPU's, and said plurality of cache memories;
a signal line (TCOMP) (29) to which each of said plurality of logic means is coupled;
a first one of said plurality of logic means, being coupled to a first cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether a data block being accessed from said RAM by a CPU coupled to a second cache memory of said plurality of cache memories is contained in said first cache memory, said first one of said logic means comprising means for generating a first signal level on said signal line while said first one of said logic means is determining whether said data block is contained in said first cache memory, and otherwise generating a second signal level on said signal line; and logic means coupled to said RAM comprising means for preventing said RAM from completing said access to said data block by said CPU coupled to said second cache memory if said first signal level is present on said signal line, and for enabling said RAM to complete said access to said data block if said second signal level is present on said signal line, whereby said RAM does not complete said access to said data block until said first one of said logic means has determined whether said data block is contained in said first cache memory.
a random access memory (RAM) (12);
a plurality of central processing units (CPU's) (16);
a plurality of cache memories (22), one of said cache memories being coupled to each of said plurality of CPU's;
a plurality of logic means for coordinating data transfer, one of said logic means being coupled to each of said plurality of cache memories;
a system bus (14) to which said RAM, said plurality of CPU's, and said plurality of cache memories are coupled, said system bus enabling address and data information to be exchanged among said RAM, said plurality of CPU's, and said plurality of cache memories;
a signal line (TCOMP) (29) to which each of said plurality of logic means is coupled;
a first one of said plurality of logic means, being coupled to a first cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether a data block being accessed from said RAM by a CPU coupled to a second cache memory of said plurality of cache memories is contained in said first cache memory, said first one of said logic means comprising means for generating a first signal level on said signal line while said first one of said logic means is determining whether said data block is contained in said first cache memory, and otherwise generating a second signal level on said signal line; and logic means coupled to said RAM comprising means for preventing said RAM from completing said access to said data block by said CPU coupled to said second cache memory if said first signal level is present on said signal line, and for enabling said RAM to complete said access to said data block if said second signal level is present on said signal line, whereby said RAM does not complete said access to said data block until said first one of said logic means has determined whether said data block is contained in said first cache memory.
3. A multiprocessor system comprising:
a random access memory (RAM) (12);
a plurality of central processing units (CPU's) (16);
a plurality of cache memories (22), one of said cache memories being coupled to each of said plurality of CPU's;
a plurality of logic means for coordinating data transfer, one of said logic means being coupled to each of said plurality of cache memories;
a system bus (14) to which said RAM, said plurality of CPU's, and said plurality of cache memories are coupled, said system bus enabling address and data information to be exchanged among said RAM, said plurality of CPU's, and said plurality of cache memories;
a signal line (INHIBIT) (18) to which said RAM and each of said plurality of logic means are coupled;
a first one of said plurality of logic means, being coupled to a first cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether a data block being read by a CPU
coupled to a second cache memory of said plurality of cache memories is stored in said first cache memory and differs from the corresponding data block stored in said RAM, and, if so, for generating a first signal level on said signal line and transmitting said data block stored in said first cache memory to said second cache memory, and otherwise generating a second signal level on said signal line; and RAM logic means coupled to said RAM and to said signal line, for inhibiting said RAM from transmitting said data block to said CPU coupled to said second cache memory and for causing said data block which is stored in said first cache memory to be written to said RAM, if said first signal level is present on said signal line, even though said CPU coupled to said second cache memory is asserting that said data block is identical in said RAM and said first and second cache memories.
a random access memory (RAM) (12);
a plurality of central processing units (CPU's) (16);
a plurality of cache memories (22), one of said cache memories being coupled to each of said plurality of CPU's;
a plurality of logic means for coordinating data transfer, one of said logic means being coupled to each of said plurality of cache memories;
a system bus (14) to which said RAM, said plurality of CPU's, and said plurality of cache memories are coupled, said system bus enabling address and data information to be exchanged among said RAM, said plurality of CPU's, and said plurality of cache memories;
a signal line (INHIBIT) (18) to which said RAM and each of said plurality of logic means are coupled;
a first one of said plurality of logic means, being coupled to a first cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether a data block being read by a CPU
coupled to a second cache memory of said plurality of cache memories is stored in said first cache memory and differs from the corresponding data block stored in said RAM, and, if so, for generating a first signal level on said signal line and transmitting said data block stored in said first cache memory to said second cache memory, and otherwise generating a second signal level on said signal line; and RAM logic means coupled to said RAM and to said signal line, for inhibiting said RAM from transmitting said data block to said CPU coupled to said second cache memory and for causing said data block which is stored in said first cache memory to be written to said RAM, if said first signal level is present on said signal line, even though said CPU coupled to said second cache memory is asserting that said data block is identical in said RAM and said first and second cache memories.
4. A multiprocessor system comprising:
a random access memory (RAM) (12);
a plurality of central processing units (CPU's) (16);
a plurality of cache memories (22), one of said cache memories being coupled to each of said plurality of CPU's;
a plurality of logic means for coordinating data transfer, one of said logic means being coupled to each of said plurality of cache memories;
a system bus (14) to which said RAM, said plurality of CPU's, and said plurality of cache memories are coupled, said system bus enabling address and data information to be exchanged among said RAM, said plurality of CPU's, and said plurality of cache memories;
a signal line (INVALID) (26) to which each of said plurality of logic means is coupled;
a first one of said plurality of logic means, being coupled to a first cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether a data block being written to during a WRITE cycle by said CPU coupled to said first cache memory is contained in said first cache memory and, if so, for generating a first signal level on said signal line, and, if not, for generating a second signal level on said signal line and initiating a system bus READ cycle to enable said data block t be read from said RAM into said first cache memory and, after said system bus READ cycle has been completed, for completing said WRITE cycle by enabling said CPU to write to said data block only in said first cache memory; and a second one of said plurality of logic means, being coupled to a second cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether said data block is contained in said second cache memory and, if so, for setting said data block to invalid in said second cache memory, if said second signal level is present on said signal line, whereby a WRITE cycle takes only 1 bus cycle rather than 2 bus cycles for said CPU coupled to said first cache memory to read said dat block into said first cache memory and to indicate that said data block in said second cache memory should be invalidated.
a random access memory (RAM) (12);
a plurality of central processing units (CPU's) (16);
a plurality of cache memories (22), one of said cache memories being coupled to each of said plurality of CPU's;
a plurality of logic means for coordinating data transfer, one of said logic means being coupled to each of said plurality of cache memories;
a system bus (14) to which said RAM, said plurality of CPU's, and said plurality of cache memories are coupled, said system bus enabling address and data information to be exchanged among said RAM, said plurality of CPU's, and said plurality of cache memories;
a signal line (INVALID) (26) to which each of said plurality of logic means is coupled;
a first one of said plurality of logic means, being coupled to a first cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether a data block being written to during a WRITE cycle by said CPU coupled to said first cache memory is contained in said first cache memory and, if so, for generating a first signal level on said signal line, and, if not, for generating a second signal level on said signal line and initiating a system bus READ cycle to enable said data block t be read from said RAM into said first cache memory and, after said system bus READ cycle has been completed, for completing said WRITE cycle by enabling said CPU to write to said data block only in said first cache memory; and a second one of said plurality of logic means, being coupled to a second cache memory of said plurality of cache memories, comprising means for monitoring said system bus to determine whether said data block is contained in said second cache memory and, if so, for setting said data block to invalid in said second cache memory, if said second signal level is present on said signal line, whereby a WRITE cycle takes only 1 bus cycle rather than 2 bus cycles for said CPU coupled to said first cache memory to read said dat block into said first cache memory and to indicate that said data block in said second cache memory should be invalidated.
5. In a data processing system comprising a system bus (14), a signal line (24) for providing a shared signal, a random access memory (RAM) (12) coupled to said system bus for storing information, a plurality of processors (16) coupled to said system bus and requiring read/write access to said information in said RAM over said system bus, a plurality of cache memories (22) each coupled to a one of said plurality of processors, logic means for coordinating information transfer coupled to said system bus, to said signal line, and to said plurality of cache memories, a method of reducing accesses to said RAM over said system bus by said plurality of processors, said method comprising the steps of:
determining, by means of said logic means, whether information stored in one of said plurality of cache memories is valid and requested by one of said plurality of processors not coupled to said one cache memory, and, if so, identifying said information as "shared" via a shared signal on said signal line, but otherwise not identifying said information as "shared"; and enabling said one processor to write said information through to said RAM if said one processor subsequently modifies said information in a second cache memory of said plurality of cache memories, if said information stored in said one cache memory is identified as "shared", otherwise inhibiting said one processor from writing said information through to said RAM.
determining, by means of said logic means, whether information stored in one of said plurality of cache memories is valid and requested by one of said plurality of processors not coupled to said one cache memory, and, if so, identifying said information as "shared" via a shared signal on said signal line, but otherwise not identifying said information as "shared"; and enabling said one processor to write said information through to said RAM if said one processor subsequently modifies said information in a second cache memory of said plurality of cache memories, if said information stored in said one cache memory is identified as "shared", otherwise inhibiting said one processor from writing said information through to said RAM.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US07/078,436 US4959777A (en) | 1987-07-27 | 1987-07-27 | Write-shared cache circuit for multiprocessor system |
| US78,436 | 1987-07-27 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA1306312C true CA1306312C (en) | 1992-08-11 |
Family
ID=22144015
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA000568258A Expired - Fee Related CA1306312C (en) | 1987-07-27 | 1988-05-31 | Write-shared cache circuit for multiprocessor system |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US4959777A (en) |
| EP (1) | EP0301354A3 (en) |
| JP (1) | JPH0247756A (en) |
| CA (1) | CA1306312C (en) |
Families Citing this family (69)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2714952B2 (en) * | 1988-04-20 | 1998-02-16 | 株式会社日立製作所 | Computer system |
| EP0343567A3 (en) * | 1988-05-25 | 1991-01-09 | Hitachi, Ltd. | Multi-processing system and cache apparatus for use in the same |
| US5058006A (en) * | 1988-06-27 | 1991-10-15 | Digital Equipment Corporation | Method and apparatus for filtering invalidate requests |
| IT1227360B (en) * | 1988-11-18 | 1991-04-08 | Honeywell Bull Spa | MULTIPROCESSOR DATA PROCESSING SYSTEM WITH GLOBAL DATA REPLICATION. |
| US5535359A (en) * | 1988-12-02 | 1996-07-09 | Mitsubishi Denki Kabushiki Kaisha | Computer system with cache memory having address mask register |
| JPH0680499B2 (en) * | 1989-01-13 | 1994-10-12 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Cache control system and method for multiprocessor system |
| US5210848A (en) * | 1989-02-22 | 1993-05-11 | International Business Machines Corporation | Multi-processor caches with large granularity exclusivity locking |
| JPH0721781B2 (en) * | 1989-03-13 | 1995-03-08 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Multiprocessor system |
| EP0405318A3 (en) * | 1989-06-20 | 1991-11-27 | Nec Corporation | Microprocessor having cash bypass signal terminal |
| EP0412353A3 (en) * | 1989-08-11 | 1992-05-27 | Hitachi, Ltd. | Multiprocessor cache system having three states for generating invalidating signals upon write accesses |
| US5283886A (en) * | 1989-08-11 | 1994-02-01 | Hitachi, Ltd. | Multiprocessor cache system having three states for generating invalidating signals upon write accesses |
| JP2789479B2 (en) * | 1989-08-14 | 1998-08-20 | 松下電器産業株式会社 | Processing device and multiprocessor system |
| JPH0697449B2 (en) * | 1989-09-20 | 1994-11-30 | 株式会社日立製作所 | Multiplexed shared memory control method, multiplexed shared memory system and shared memory expansion method |
| JPH03188546A (en) * | 1989-12-18 | 1991-08-16 | Fujitsu Ltd | Bus interface control system |
| JPH061463B2 (en) * | 1990-01-16 | 1994-01-05 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Multiprocessor system and its private cache control method |
| US5261067A (en) * | 1990-04-17 | 1993-11-09 | North American Philips Corp. | Method and apparatus for providing synchronized data cache operation for processors in a parallel processing system |
| US5611070A (en) * | 1990-05-10 | 1997-03-11 | Heidelberger; Philip | Methods and apparatus for performing a write/load cache protocol |
| US5452463A (en) * | 1990-05-25 | 1995-09-19 | Dell Usa, L.P. | Processor and cache controller interface lock jumper |
| CA2045756C (en) * | 1990-06-29 | 1996-08-20 | Gregg Bouchard | Combined queue for invalidates and return data in multiprocessor system |
| US5276833A (en) * | 1990-07-02 | 1994-01-04 | Chips And Technologies, Inc. | Data cache management system with test mode using index registers and CAS disable and posted write disable |
| US5276852A (en) * | 1990-10-01 | 1994-01-04 | Digital Equipment Corporation | Method and apparatus for controlling a processor bus used by multiple processor components during writeback cache transactions |
| JPH04353947A (en) * | 1991-02-13 | 1992-12-08 | Hewlett Packard Co <Hp> | Memory-page-characteristic tagging system |
| JPH0776942B2 (en) * | 1991-04-22 | 1995-08-16 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Multiprocessor system and data transmission device thereof |
| US5319768A (en) * | 1991-05-01 | 1994-06-07 | Sgs-Thomson Microelectronics, Inc. | Control circuit for resetting a snoop valid bit in a dual port cache tag memory |
| US5353423A (en) * | 1991-06-21 | 1994-10-04 | Compaq Computer Corporation | Memory controller for use with write-back cache system and multiple bus masters coupled to multiple buses |
| US5426765A (en) * | 1991-08-30 | 1995-06-20 | Compaq Computer Corporation | Multiprocessor cache abitration |
| US5335335A (en) * | 1991-08-30 | 1994-08-02 | Compaq Computer Corporation | Multiprocessor cache snoop access protocol wherein snoop means performs snooping operations after host bus cycle completion and delays subsequent host bus cycles until snooping operations are completed |
| US5386540A (en) * | 1991-09-18 | 1995-01-31 | Ncr Corporation | Method and apparatus for transferring data within a computer using a burst sequence which includes modified bytes and a minimum number of unmodified bytes |
| US5414827A (en) * | 1991-12-19 | 1995-05-09 | Opti, Inc. | Automatic cache flush |
| US5584017A (en) * | 1991-12-19 | 1996-12-10 | Intel Corporation | Cache control which inhibits snoop cycles if processor accessing memory is the only processor allowed to cache the memory location |
| US5469555A (en) * | 1991-12-19 | 1995-11-21 | Opti, Inc. | Adaptive write-back method and apparatus wherein the cache system operates in a combination of write-back and write-through modes for a cache-based microprocessor system |
| US5546560A (en) * | 1993-06-22 | 1996-08-13 | Advance Micro Devices, Inc. | Device and method for reducing bus activity in a computer system having multiple bus-masters |
| US5581734A (en) * | 1993-08-02 | 1996-12-03 | International Business Machines Corporation | Multiprocessor system with shared cache and data input/output circuitry for transferring data amount greater than system bus capacity |
| US5748937A (en) * | 1993-08-26 | 1998-05-05 | Intel Corporation | Computer system that maintains processor ordering consistency by snooping an external bus for conflicts during out of order execution of memory access instructions |
| US5522057A (en) * | 1993-10-25 | 1996-05-28 | Intel Corporation | Hybrid write back/write through cache having a streamlined four state cache coherency protocol for uniprocessor computer systems |
| US5692154A (en) * | 1993-12-20 | 1997-11-25 | Compaq Computer Corporation | Circuit for masking a dirty status indication provided by a cache dirty memory under certain conditions so that a cache memory controller properly controls a cache tag memory |
| US5751995A (en) * | 1994-01-04 | 1998-05-12 | Intel Corporation | Apparatus and method of maintaining processor ordering in a multiprocessor system which includes one or more processors that execute instructions speculatively |
| JP2634141B2 (en) * | 1994-01-19 | 1997-07-23 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Multiprocessor system |
| US5572702A (en) * | 1994-02-28 | 1996-11-05 | Intel Corporation | Method and apparatus for supporting read, write, and invalidation operations to memory which maintain cache consistency |
| US5797026A (en) * | 1994-02-28 | 1998-08-18 | Intel Corporation | Method and apparatus for self-snooping a bus during a boundary transaction |
| KR960009659B1 (en) * | 1994-04-11 | 1996-07-23 | 김광호 | Snoop circuit of multiprocessor system |
| DE69519816T2 (en) * | 1994-05-03 | 2001-09-20 | Hewlett Packard Co | Duplicate cache tag array arrangement |
| JP2748862B2 (en) * | 1994-06-15 | 1998-05-13 | 日本電気株式会社 | Bus interface adapter |
| US5574922A (en) * | 1994-06-17 | 1996-11-12 | Apple Computer, Inc. | Processor with sequences of processor instructions for locked memory updates |
| US5893147A (en) * | 1994-12-22 | 1999-04-06 | Intel Corporation | Method and apparatus for distinguishing system memory data from alternative memory data in a shared cache memory |
| JP3872118B2 (en) * | 1995-03-20 | 2007-01-24 | 富士通株式会社 | Cache coherence device |
| US5592616A (en) * | 1995-06-07 | 1997-01-07 | Dell Usa, Lp | Method for performing efficient memory testing on large memory arrays using test code executed from cache memory |
| FI102788B1 (en) * | 1995-09-14 | 1999-02-15 | Nokia Telecommunications Oy | Control of shared disk data in a duplicate computer unit |
| US5778437A (en) * | 1995-09-25 | 1998-07-07 | International Business Machines Corporation | Invalidation bus optimization for multiprocessors using directory-based cache coherence protocols in which an address of a line to be modified is placed on the invalidation bus simultaneously with sending a modify request to the directory |
| US5822763A (en) * | 1996-04-19 | 1998-10-13 | Ibm Corporation | Cache coherence protocol for reducing the effects of false sharing in non-bus-based shared-memory multiprocessors |
| JP3590203B2 (en) | 1996-07-16 | 2004-11-17 | 株式会社東芝 | Control method of storage means and device therefor |
| US5875469A (en) * | 1996-08-26 | 1999-02-23 | International Business Machines Corporation | Apparatus and method of snooping processors and look-aside caches |
| US5787470A (en) * | 1996-10-18 | 1998-07-28 | At&T Corp | Inter-cache protocol for improved WEB performance |
| US5996049A (en) * | 1997-04-14 | 1999-11-30 | International Business Machines Corporation | Cache-coherency protocol with recently read state for data and instructions |
| US6658536B1 (en) | 1997-04-14 | 2003-12-02 | International Business Machines Corporation | Cache-coherency protocol with recently read state for extending cache horizontally |
| US6216218B1 (en) | 1997-11-03 | 2001-04-10 | Donald L. Sollars | Processor having a datapath and control logic constituted with basis execution blocks |
| US6067601A (en) * | 1997-11-03 | 2000-05-23 | Brecis Communications | Cache memory based instruction execution |
| US6421798B1 (en) | 1999-07-14 | 2002-07-16 | Computer Service Technology, Inc. | Chipset-based memory testing for hot-pluggable memory |
| US7310706B1 (en) | 2001-06-01 | 2007-12-18 | Mips Technologies, Inc. | Random cache line refill |
| US7080210B2 (en) * | 2002-02-12 | 2006-07-18 | Ip-First, Llc | Microprocessor apparatus and method for exclusive prefetch of a cache line from memory |
| US7089368B2 (en) * | 2002-02-12 | 2006-08-08 | Ip-First, Llc | Microprocessor apparatus and method for exclusively prefetching a block of cache lines from memory |
| US7089371B2 (en) * | 2002-02-12 | 2006-08-08 | Ip-First, Llc | Microprocessor apparatus and method for prefetch, allocation, and initialization of a block of cache lines from memory |
| US7080211B2 (en) * | 2002-02-12 | 2006-07-18 | Ip-First, Llc | Microprocessor apparatus and method for prefetch, allocation, and initialization of a cache line from memory |
| US7111125B2 (en) * | 2002-04-02 | 2006-09-19 | Ip-First, Llc | Apparatus and method for renaming a data block within a cache |
| US7188215B2 (en) * | 2003-06-19 | 2007-03-06 | Ip-First, Llc | Apparatus and method for renaming a cache line |
| US20050144397A1 (en) * | 2003-12-29 | 2005-06-30 | Rudd Kevin W. | Method and apparatus for enabling volatile shared data across caches in a coherent memory multiprocessor system to reduce coherency traffic |
| US20060195662A1 (en) * | 2005-02-28 | 2006-08-31 | Honeywell International, Inc. | Method for deterministic cache partitioning |
| JP5520747B2 (en) * | 2010-08-25 | 2014-06-11 | 株式会社日立製作所 | Information device equipped with cache and computer-readable storage medium |
| KR20150090491A (en) * | 2014-01-29 | 2015-08-06 | 삼성전자주식회사 | Electronic device and method for accessing data in the electronic device |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4257095A (en) * | 1978-06-30 | 1981-03-17 | Intel Corporation | System bus arbitration, circuitry and methodology |
| JPS55134459A (en) * | 1979-04-06 | 1980-10-20 | Hitachi Ltd | Data processing system |
| US4399506A (en) * | 1980-10-06 | 1983-08-16 | International Business Machines Corporation | Store-in-cache processor means for clearing main storage |
| US4484267A (en) * | 1981-12-30 | 1984-11-20 | International Business Machines Corporation | Cache sharing control in a multiprocessor |
| US4608688A (en) * | 1983-12-27 | 1986-08-26 | At&T Bell Laboratories | Processing system tolerant of loss of access to secondary storage |
| US4669043A (en) * | 1984-02-17 | 1987-05-26 | Signetics Corporation | Memory access controller |
| US4755930A (en) * | 1985-06-27 | 1988-07-05 | Encore Computer Corporation | Hierarchical cache memory system and method |
-
1987
- 1987-07-27 US US07/078,436 patent/US4959777A/en not_active Expired - Fee Related
-
1988
- 1988-05-31 CA CA000568258A patent/CA1306312C/en not_active Expired - Fee Related
- 1988-07-18 EP EP88111523A patent/EP0301354A3/en not_active Withdrawn
- 1988-07-27 JP JP63189562A patent/JPH0247756A/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| JPH0247756A (en) | 1990-02-16 |
| US4959777A (en) | 1990-09-25 |
| EP0301354A3 (en) | 1990-08-22 |
| EP0301354A2 (en) | 1989-02-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA1306312C (en) | Write-shared cache circuit for multiprocessor system | |
| US5659710A (en) | Cache coherency method and system employing serially encoded snoop responses | |
| US6571322B2 (en) | Multiprocessor computer system with sectored cache line mechanism for cache intervention | |
| US5652859A (en) | Method and apparatus for handling snoops in multiprocessor caches having internal buffer queues | |
| KR100274771B1 (en) | Method of shared intervention for cache lines in the shared state for smp bus | |
| US5623632A (en) | System and method for improving multilevel cache performance in a multiprocessing system | |
| US5325504A (en) | Method and apparatus for incorporating cache line replacement and cache write policy information into tag directories in a cache system | |
| US5561779A (en) | Processor board having a second level writeback cache system and a third level writethrough cache system which stores exclusive state information for use in a multiprocessor computer system | |
| US6629205B2 (en) | System and method for increasing the snoop bandwidth to cache tags in a cache memory subsystem | |
| US5946709A (en) | Shared intervention protocol for SMP bus using caches, snooping, tags and prioritizing | |
| US5963974A (en) | Cache intervention from a cache line exclusively holding an unmodified value | |
| US5940864A (en) | Shared memory-access priorization method for multiprocessors using caches and snoop responses | |
| US6463510B1 (en) | Apparatus for identifying memory requests originating on remote I/O devices as noncacheable | |
| US20030005237A1 (en) | Symmetric multiprocessor coherence mechanism | |
| JPH11506852A (en) | Reduction of cache snooping overhead in a multi-level cache system having a large number of bus masters and a shared level 2 cache | |
| JPH09259036A (en) | Write-back cache and method for maintaining consistency in write-back cache | |
| US20060236039A1 (en) | Method and apparatus for synchronizing shared data between components in a group | |
| US6751705B1 (en) | Cache line converter | |
| US5943685A (en) | Method of shared intervention via a single data provider among shared caches for SMP bus | |
| JPH10320283A (en) | Method and device for providing cache coherent protocol for maintaining cache coherence in multiprocessor/data processing system | |
| US5829027A (en) | Removable processor board having first, second and third level cache system for use in a multiprocessor computer system | |
| US7325102B1 (en) | Mechanism and method for cache snoop filtering | |
| US6484241B2 (en) | Multiprocessor computer system with sectored cache line system bus protocol mechanism | |
| US6021466A (en) | Transferring data between caches in a multiple processor environment | |
| US6553462B2 (en) | Multiprocessor computer system with sectored cache line mechanism for load and store operations |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| MKLA | Lapsed |