Abstract:
This disclosure describes a snooping coherency protocol for a multiprocessor network wherein every processor has its own private cache and bus interface means and the network is connected via a common system bus. Each processor has its own cache directory and image directory that duplicate each other non-atomically. The snooping protocol utilizes the duality of directories coupled with the non-atomicity of directory updates to maximize processor-cache availability and minimize processor-cache access times thus supporting high performance architectures.

Description:
FIELD OF THE INVENTION 
     This disclosure refers to multiprocessor systems having individual cache memories including means to keep the cache memories coherent. 
     BACKGROUND OF THE INVENTION 
     Due to the continually increasing demands for computing power and speed, the use of multiprocessor networks has been continually brought to the fore for handling computational problems. However, when it comes to the design and programming of efficient multiprocessor systems, a number of problems are presented among which are the problems of synchronizing various of the processes used and maintaining data coherence plus the proper ordering of events. These are all factors which must be addressed by the designer. 
     In a multiprocessor system, there is generally an instruction set which contains basic instructions used for the handling of synchronization and communication between various processing activities. 
     In these situations, the concept of &#34;communication&#34; refers to the exchange of data between different processing activities while the concept of &#34;synchronization&#34; is a special type of communication in which the data transferred is involved with control data information. Synchronization is used for the dual purpose of regulating the proper sequencing of processes and for insuring mutually exclusive access to certain shared data. The multiprocessor systems which use shared-memory will provide for the handling of communication and synchronization by the use of the controlled sharing of data in memory. 
     A major problem involved in these systems is that of memory coherence which involves the system&#39;s ability to execute memory operations correctly. Multiprocessor systems also have a requirement for sequential consistency which means that there must be a certain order in the allowable sequence of executive instructions during the same process activity which may be shared by different processors. For example, it may be noted that when two concurrent processors are operating, they can effect each others execution through the sharing of writable data and the sending of interrupt signals, but it is the order of these events that is of significant importance. Accesses to shared writable (alterable) data should be executed in a mutually exclusive manner. 
     The problem of &#34;coherency&#34; is an ever-present problem in that contradictory information or inconsistencies can occur between various ones of the memories involved. As an example, in a computer having a processor and main memory together with a cache, it may be found that the cache and main memory may contain inconsistent copies (contradictory) of data. Thus multiple cache memories could possess different copies of the same memory block due to the fact that one or more of the processors has modified its own private copy. This type of inconsistency could possibly affect correct execution of a program. 
     Thus the problem of inconsistency or &#34;cache incoherence&#34; can occur due to the following: (a) sharing of writable data; (b) process migration; (c) I/O activity. 
     In some systems the process activity is allowed to migrate, that is to be scheduled in different processors in order to balance the workload. When this occurs in a multiprocessor system whereby each processor has its own private cache, then data inconsistencies can result. 
     Previous methods of handling the coherency of memory or handling of data inconsistency have included the following techniques: (i) to use only shared cache memories which are associated with the main memory module and not permit any &#34;private&#34; cache memory for each individual processor; (ii) attaching a private cache memory to each processing unit, but operating such that any &#34;shared writable data&#34; is not permitted in the cache memory. This type of data is called &#34;non-cachable&#34;. The instructions and other data, which can be copied into cache memory, would be referred to as &#34;cachable&#34;. However, in this situation, the data must be tagged as to whether it is cachable or noncachable; (iii) tagging of shared writable data as noncachable and in this case, the performance of the system is considerably diminished; (iv) a system which allow shared writable data to exist in multiple cache memories but which requires a centralized global table which stores the status of memory blocks so that coherence enforcement signals can be generated on the basis of the status of the memory block; (v) the use of a &#34;snooping&#34; cache controller which can be used in bus-oriented multiple processors having a table that records the status of each memory block and which can be efficiently distributed among the processors involved. Consistency between the cache memories here is maintained by a bus-watching mechanism called the &#34;snooping cache controller&#34; which implements the cache coherency protocol on the bus. 
     For example, in a multiprocessor network, where each processor has its own private cache memory, the snooping controllers are used to watch the system bus for the &#34;Store&#34; command. If a store operation is made to a location in a cache memory, then the &#34;copies&#34; of this block of memory in the cache are updated. 
     A detailed discussion of the various problems involved in such type of multiprocessor systems is discussed in a Feb. 1988 article entitled &#34;Synchronization, Coherence, and Event Ordering in Multiprocessors&#34; (pages 9 through 21 in Computer, published by IEEE, by the authors Dubois, Scheurich, and Briggs). 
     The present disclosure provides improved methods for handling the coherency problems in multiprocessor systems by the provision of a snooping cache coherency protocol for shared bus multiprocessors. The improved system provides for the update of the cache memory and an image directory unit on a serial basis often designated as &#34;non-atomic&#34; which is to indicate that the updates are done at different times and not concurrently. The non-atomicity of the directory updates thus allows for the processor-to-cache memory cycle time to be minimized and provide for a higher performance throughput. 
     SUMMARY OF THE INVENTION 
     The present disclosure involves improvements to multiprocessor networks wherein each processor has a private cache memory and the network is connected through a common system bus. The network is provided with a snooping cache coherency protocol having distributed directories such that the updates of each cache memory and its associated image directory are accomplished at different time periods (non-atomic) thus permitting the processor-to-cache cycle time to be minimized. 
     The non-atomicity of directory updates will cause directory inconsistencies (in various memory blocks) to occur during the period between updates. The system bus protocol is arranged to allow for correct operation to maintain data coherency, despite the temporary period of inconsistency. 
     The protocol supports a memory subsystem which queues memory requests such that the processor, or cache memory requesting data, relinquishes the shared bus after making its request. 
     While previous implementations used atomic (concurrent) directory updates using two basic schemes, these schemes caused an increase in processor-cache memory cycle time. These schemes involved a split cycle with duplicated directories or the use of dual ports to the same directory. In the present situation, time-independent directory updates allow the processor-to-cache access time to be minimized thus allowing for a high performance multiprocessor architecture. 
    
    
     BRIEF DESCRIPTION OF DRAWINGS 
     FIG. 1 is a block diagram of a multiprocessor network architecture; 
     FIG. 2 is a block diagram of the architecture for the cache memory and bus interface unit for each processor; 
     FIGS. 3A, 3B and 3C are schematic drawings illustrating the organization of the cache memory showing the cache data array, tag array, and PV array; 
     FIGS. 5A, 5B are timing charts illustrating the Command Transmit-Receive Sequence; 
     FIG. 6 is a list of the cache-to-bus interface unit commands; 
     FIG. 7 is a list of the bus interface unit-cache commands; 
     FIGS. 8A and 8B are flow charts illustrating the sequence of activities on the bus response lines; 
     FIG. 9 is a table indicating how commands are accepted depending on the collective bus response; 
     FIGS. 10 and 11 are schematic drawings showing the state changes in the cache PV array and the image PV array; 
     FIGS. 12A and 12B are examples used to illustrate data transfers (copy) and the non-atomicity of directory updates. 
     FIGS. 13A and 13B are examples used to illustrate data transfers (master) and the non-atomicity of directory updates; 
     FIGS. 14A and 14B are examples used to illustrate cache-cache data transfer (Master) and the directory updates; 
     FIGS. 15A and 15B are examples used to illustrate cache-cache data transfer (copy) and the directory updates; 
    
    
     DESCRIPTION OF PREFERRED EMBODIMENT 
     Multiprocessor Architecture (FIG. 1) 
     FIG. 1 shows a multiprocessor network having a series of processor element modules (PE modules) 6a, 6b, 6c, 6d which are connected to a system bus 24. Also connected to the system bus 24 is a group of memory modules (MM&#39;s) 20a, 20b, and 20c. 
     Each PE module, 6a, 6b, 6c, 6d, has processing element (PE) shown as 10a, 10b, 10c, 10d, a private cache memory unit shown as 12a, 12b, 12c, 12d, and a bus interface unit (BIU) shown as 14a, 14b, 14c, and 14d. Each PE is linked to its cache memory unit (also called a private cache) which, in turn, is connected to a BIU which links the module to the system bus 24. 
     Each memory module (20a, 20b, 20c) consists of an input queue shown as 20aiq, 20biq, 20ciq, an output queue shown as 20aoq, 20boq, 20coq, and a main memory unit designated 20am, 20bm, 20cm. The input queue queues up accesses (request commands) to the main memory unit. The main memory unit responds to each access by placing a return command in the corresponding output queue. The return command is a system bus command used to transfer information back to the requesting module in response to a request command. The input queue receives commands from the system bus and output queue transmits commands onto the system bus. 
     Thus the system consists of processing elements with private caches, queueing memory modules and a system bus which interconnects all processor and memory modules. The system bus is a backplane bus operated in a synchronous manner. The signals which use the system bus are described hereinafter under the heading &#34;System Bus Signals&#34;. 
     Cache and BIU Architecture (FIG. 2) 
     FIG. 2 shows in detail the components of the cache and bus interface unit (BIU) and how they are interconnected. 
     The processor 10, typical of each of the processors 10a, 10b, 10c, and 10d, etc., connects to a cache controller circuit 8 by means of a command bus 7b. The command bus 7b is used by the processor 10 in order to transmit commands to the cache controller 8. These commands are typically Read, Write, etc. 
     The address bus designated 7c is driven by the processor 10, or by the the cache controller 8, or by the BIU 28. The address bus 7c carries the address of a particular data word or specific status information. Arbitration as to who shall have access to the address bus 7c is controlled by the cache controller 8. 
     The data bus 7d is used to connect the processor 10 and the cache data array unit 12da. The cache data array unit 12da is also connected to the BIU Data device 34 by means of data bus 7d. Data is transferred from the cache 12da to the BIU Data device 34 via the data bus 7d, and from the BIU Data device 34 to main memory 20, or to BIU&#39;s on other modules, over the system bus 24. 
     The cache memory data array 12da is a memory which is used to store data from the memory module 20 for subsequent use by the processor 10. The detailed architecture of the cache memory data array 12da is shown in FIG. 3A. 
     Connected to the cache controller 8 and to the address bus 7c is the cache memory tag array 12ta FIG. 3B. Since a portion of the address of a data block is designated as the &#34;tag&#34;, this portion designated as the tag is stored in the cache memory tag array 12ta. Thus for every data block stored in the cache memory data array 12da, the cache memory tag array 12ta will store its own associative tag. The cache memory tag array 12ta, is part of the cache directory 32cd which also includes the cache memory PV array 12pv. The cache memory tag array 12ta as part of the cache directory, is used to find out whether a particular data block resides in the cache memory data array 12da. 
     The cache memory PV array 12pv is also part of the cache directory 32cd. The cache PV array 12pv stores the &#34;status&#34; of each cache data block that resides in the cache data array 12da. Each data block in the cache data array 12da will be found to be in one of four states; invalid, copy, master, pending. These states are illustrated in FIG. 10. 
     As seen in FIG. 2, the cache directory 32cd is made up of the cache tag array 12ta together with the cache PV array 12pv. 
     The data bus between the cache data array 12da and the BIU 34 is shown as bus 7d. The bus designated 15b is the command bus for transmitting commands between the cache controller 8 and the BIU 28. The commands transferred on this command bus 15b are listed in the tables in FIGS. 6 and 7. 
     The BIU (bus interface unit) consists of two chips, the BIU-Data Chip 34 and the BIU address and control chip 28 (BIU-AC). The BIU-AC 28 controls the BIU-Data 34, by means of the control bus 32a. The main functions of the BIU are to &#34;snoop&#34; on the system bus 24 to maintain coherent data and also buffer data, such data going from the cache memory 12da to the system bus 24, and reversely from the system bus 24 to the cache memory data array 12da. 
     The BIU-AC 28 (FIG. 2) receives commands from the cache controller 8 and transmits them on the system bus 24. Likewise, any commands arriving from the system bus 24, which are relevant to the particular module, are received by the BIU-AC and then passed on to the cache controller 8. 
     The BIU-AC 28 implements the bus protocol which guarantees coherent data in the cache. To maintain data coherency the BIU-AC 28 needs to know the state of all data held in the cache. It does so by means of the image directory 32ti. The image directory is an exact copy of the cache directory 32cd, and consists of the image tag array 32ta and the image PV array 32p. FIGS 4A and 4B show the organization of the image directory in detail. 
     Cache Organization (FIGS. 3, 3A, 3B, 3C) 
     The signals which connect the cache directory 32cd to the cache controller 8 are as follows: The TAG address bits [31:12] are stored in the tag array 12ta, FIG. 3B. The PV status bits are stored in the PV array 12pv, FIG. 3C. Data is stored in the cache data array 12da, FIG. 3A. All three arrays are addressed by the ten address bits ADDR[11:2] obtained from address bus 7c. The ten address bits define 1k sets, where each set consists of four blocks. The BLOCK SELECT lines select one block in any set for writing. The READ/WRITE line selects a read or write operation on the arrays. 
     Given an address, the TAGMATCH lines (FIGS. 3B, 4B) indicate whether, and in which block, the address exists, while the PV status lines indicate the status of the desired block in the set. 
     Image Organization (FIGS. 4, 4A, 4B) 
     The signals which connect the image directory 32ti to the BIU-AC 28 are as follows. The TAG (address bits [31:12]) are stored in the tag array 32ta, FIG. 4A. The PV status bits are stored in the PV array 32p. Both arrays are addressed by the ten address bits ADDR[11:2] obtained from the system bus. The ten address bits define 1k sets, where each set consists of four blocks. The BLOCK SELECT lines select one block in any set for writing. The READ/WRITE line selects a read or write operation on the arrays. Given an address, the TAGMATCH lines indicate whether, and in which block, the address exists, while the PV status lines indicate the status of the desired block in the set. Thus the image directory provides a means of maintaining data coherency without accessing the cache directory 32cd. 
     Further, updates to the image directory are done separately and non-atomically from the cache directory. This feature allows the PE (10) to access the cache as fast and as frequently as desired since the snooping activity is now done by the BIU using the image directory. 
     Command Transmit Receive Sequence (FIGS. 5A, 5B) 
     These figures show how commands are transmitted on the system bus 24 on a clock by clock basis. 
     Commands between BIU and Cache Controller (FIGS. 6 and 7) 
     These tables show the command encodings for all commands from cache controller 8 to BIU-28 and from BIU-28 to cache controller 8. The commands are described hereinafter under the heading of System Bus Commands. 
     Individual Bus Response Determination (FIGS. 8A, 8B) 
     This flow chart defines how the bus response lines are asserted based on the system bus command and image status. 
     Collective Bus Response and Command Acceptance (FIG. 9) 
     This table shows how commands are accepted based on the collective bus response. 
     State Changes in Image and Cache PV Arrays (FIGS. 10 and 11) 
     These State diagrams specify how the status of a data block changes in response to bus commands. 
     The four examples, discussed hereinafter in connection with FIGS. 12, 13, 14 and 15, illustrate the non-atomicity of directory updates and how the protocol maintains coherency. 
     The following discussion details the information transfer scheme and the coherency protocol which use the cache and image directories to maintain coherency of data in the multiprocessor system shown in FIG. 1. 
     Information is transferred from one module to another by means of the system bus. The information relevant here is memory data. Other information, time-of-day, SPES (Signal Processor Element Set), are necessary for overall system operation but have no coherency implications. 
     A. Information Transfer Scheme 
     The following subsections detail the information transfer scheme, beginning with the system bus signals in Paragraph A-1, and followed by the system bus commands in Paragraph A-3. In Paragraph A-5 a description of how commands are transmitted and received is provided. 
     (A-1) System Bus Signals 
     Each field, or group of signals is defined below: 
     Address ADDR[31:0]: Thirty-two signal lines are used to convey the address of a data word. 
     Data DAT[51:0]: Fifty-two data lines are used to transfer one data word per clock. 
     Command COM[5:0]: The command lines define the type of bus transaction and are defined in Paragraph A-3. 
     Source ID/Destination ID SDID[4:0]: These lines specify the identification number of either the transmitting module (source) or some specific receiving module called the destination. Whether the ID is a source or destination is implicit in the type of command. Unique ID numbers are assigned to each module at system initialization time. 
     Bus Request REQ[19:0]: Each module uses a unique Request line by which it signals to all other modules its intention of using the system bus (i.e. bus request). In this particular implementation the system can have up to twenty modules. 
     (A-2) Bus Response Lines: 
     PE-ACK: This signal is used by any PE module to acknowledge receiving a bus transmission correctly. If the transmission received was a request command (i.e. a command which is a request for data), then a PE which finds (by reading its image directory) that it has the data will assert PE-ACK. Thus PE-ACK tells the transmitter that its request for data will be honored. It also tells the memory modules that they must ignore the command. 
     If the transmission received was data, then the receiving module asserts PE-ACK, to inform the transmitter that the data was received correctly. 
     PE-BUSY: PE-BUSY is used by a receiving PE module to signal the transmitter module that it cannot handle the transmission due to a full input queue. The transmitter will then retransmit later. PE-BUSY also informs the memory modules to ignore the command. PE-BUSY may be asserted by many PE modules at once. 
     MM-ACK: Memory modules acknowledge a transmission received without error by asserting MM-ACK. Only one memory module may assert MM-ACK at a given time. 
     MM-BUSY: If a command is received by a memory module which finds its input queue full then it asserts MM-BUSY. The transmitter will retransmit that command later. 
     BUS-ERROR: Any module which finds an error in a transmission on the system bus, signals the fact by asserting BUS-ERROR. The transmitter will retransmit later. 
     PARITY SIGNALS: Address, data, command and source/destination ID signals are protected by parity signals. Parity is checked by all modules on every transmission. 
     (A-3) System Bus Commands 
     The system bus specified in Paragraph A-1 is used to transfer different types of information. The type of information is defined by the command on the bus command lines. This section specifies all the commands which transfer memory data from MM to PE, PE to PE, and PE to MM. Other commands, which have nothing to do with coherency operations, are also defined because they are essential for system operation. Coherency operations caused by these commands are described in Paragraph B. 
     No Operation (NOP): When no module is transmitting, the command lines have a logic value of 111111 (binary) due to the open-collector nature of the system bus. Modules read the system bus (i.e., all the lines specified in Paragraph A-1) on every clock. When a module reads the command lines and finds a NOP it knows that there is no transmission. 
     Shared Read (SR): SR is identified by the logic value 000001 on the command lines. The command originates when a PE reads the data word at some address, say C0C00001 (Hexadecimal) for example, and the cache controller reads its directory (see FIGS. 2 and 3) and finds that none of the tags in set 1 matches the tag of the processor address C0C000. Then the cache controller issues a SR command with the specific address C0C00001 to the BIU which transmits the command on the system bus. The BIU transmits the command (000001), the address (C0C00001) and the specific ID of the module for one clock period. 
     The memory module which has the address C0C00001 will then send a &#34;copy&#34; of the data block back to the requestor (i.e. the module that issued the SR). 
     Private Read (PR): PR is identified by the logic value 000010 (binary) on the command lines. The command originates when a PE writes at a specific address, say C0C00001 for example, and the cache controller finds that it does not have that address in its directory. Therefore, the cache controller issues a PR command to the BIU with the address specified as C0C00001. Then the BIU transmits the command (000010), the address (C0C00001), and the ID of the module on the system bus. 
     The memory, or PE module which finds the data as a &#34;master&#34;, will return the data to the requestor designated as a master. A block of data is classified as &#34;master&#34; when it can be modified by the processor element (PE) which has that master block of data in its cache. 
     Transmit Block Shared (TBS): TBS is identified by the logic value 010001 on the command lines. When a memory module receives a SR command, with address C0C00001 for example, it will send back to the requestor a copy of the data block using a TBS command. The data block consists of the four words at addresses C0C00000, C0C00001, C0C00002 and C0C00003. Since there are four data words the transmission takes four clock cycles. In the first clock the command (010001), the address (C0C001) and the corresponding data word, and the requestors ID are transmitted. On the second, third and fourth clocks, only the data words corresponding to addresses C0C00001, C0C00002 and C0C00003 are transmitted. 
     Transmit Block Private (TBP): TBP is identified by the logic value 010010 on the command lines. When a memory module or PE module receives a PR command it returns the data using a TBP command. The command implies that the data transferred is designated as a master (private). The transfer takes four clocks and occurs exactly like a TBS. 
     Purge: A Purge command is used by a PE module when it returns a block of data, designated as a master, back to memory. The command originates at the cache controller, when the PE does a read or write and none of the four blocks in the particular set match the address required by the processor. As described before, the cache controller issues a SR or PR command to get the block of data. The cache controller also determines where in the particular set the requested data is to be placed. If that location already has a valid master, it must be returned back to memory using a Purge command. Note that a master cannot be overwritten like a copy can be. A Purge command takes four clocks on the system bus. In the first clock the address, the command (000110), the ID of the transmitting module and the word corresponding to the address are transmitted. In the second, third and fourth clocks the other data words are transmitted just as in a TBP or TBS command. A Purge command is received by the memory module which contains the specified address. 
     New Data Write (ND): ND is identified by the logic value 000111 on the command lines. This command provides the capability for PE modules doing I/O functions to overwrite a block in memory, for example when a file is being read from a peripheral device. The command causes the existing master to be overwritten by the new data. If the ND is received by a PE, then the cache controller executes the overwrite, else it is done by the memory module when the master is in memory. The ND command consists of four words and is transmitted like a TBP. 
     (A-4) The following commands perform functions not related to data coherency. A brief description follows. 
     Time-of-Day-Read (TODR): A Processor Element (PE) reads the time of day from the memory module which contains the time-of-day clock by issuing a TODR. 
     Time-of-Day-Write (TODW): A PE may change the time-of-day clock in the memory module by issuing TODW. 
     Time-of-Day (TOD): A memory module returns the time of day, in response to a TODR by transmitting a TOD command. 
     Signal PE Set (SPES): A PE may send a message to another PE or set of PE&#39;s using the SPES command. 
     SPES Acknowledge (SPESACK): A PE which receives a SPES may respond by sending back a SPESACK command. 
     Result: A Result command may be sent as a response to any command to report status or errors. 
     B. Command Transmit-Receive Sequence on the System Bus 
     This section describes how the system bus commands are transmitted and received, the role of the bus response lines, and how the &#34;snooping function&#34; uses the image directory. Events are described on a clock-by-clock basis using FIG. 5 which illustrates the entire sequence. 
     The sequence of actions taken by the transmitter, and by all other receivers are the same for all one-clock commands. The sequence begins in clock A (FIG. 5A) when the transmitter module drives a command on the system bus 24. In clock A+1 all modules 6a, 6b, 6c, 20a, 20b, 20c evaluate the command. Evaluation consists of decoding the command lines to find out what the command means, checking parity (on address, data, source/destination ID and command) and executing the snooping function. 
     &#34;Snooping&#34; is the process of using the address specified in the bus command to access the image directory to find whether a matching address exists in the image and, if so, what the status of the data (master, copy, invalid, pending) is. The results of the snoop is relevant only if the command is a SR, PR, ND, Purge, TBS or TBP, as defined in Paragraph A-2 above. 
     The purpose of snooping is to make the appropriate response on the PE-ACK, PE-BUSY or BUS-ERROR lines. The response depends on the type of command received (in Clock A for example) and on the image status for that address. The criteria for driving each response line are outlined next. 
     Asserting BUS-ERROR in Clock A+2: If a command received has a parity error then the module (may be more than one) which finds the parity error asserts BUS-ERROR. 
     Asserting PE-ACK in Clock A+2: If command received is SR, PR or ND, and the image state is Master, then PE-ACK is asserted by a PE module (FIG. 5) provided its input queue is not full. If a TBS, TBP (or Result, TOD or SPESACK) is received and the destination ID of the transmission matches the ID of the PE and, the state in the image is &#34;pending&#34; then PE-ACK is asserted. PE-ACK is asserted by only one PE module. 
     Asserting PE-BUSY in Clock A+2: If the command received is SR, PR or ND, and the image state is Master, then PE-BUSY is asserted when the input queue is full. PE-BUSY is also asserted when an ND command is received, the image state is &#34;copy&#34;, and the input queue is full. 
     Asserting MM-ACK or MM-BUSY in Clock A+2: A memory module which contains the address specified in a SR, PR, ND or Purge command will assert MM-ACK if its input queue is not full. If the input queue is full then MM-BUSY will be asserted. 
     Four-Clock Commands (ND, TBS, TBP, Purge): Towards the end of clock A+1, each receiver determines for itself whether the command has to be processed. All commands except SPES are meant to be processed by one receiver only. Therefore, for four-clock commands only one receiver is actively receiving the data words in clocks A+1, A+2, A+3. The active receiver uses PE-ACK or MM-ACK (depending on whether the module is a PE or MM) to signal the transmitter whether the data parity was correct. If incorrect parity is found then BUS-ERROR is asserted. The active receiver drives its bus response (FIGS. 5A, 5B) for each data word in clocks A+2 (for data word A), A+3 (for data word B), A+4 (for data word C) and A+5 (for data word D). 
     The Collective Response: The purpose of driving the individual response (in clock A+2) after a command is received (in clock A+1) is to determine the collective bus response. The collective bus response is determined based on the individual bus response driven by each module. A command is accepted by the receiver, and considered to be successfully transmitted by the transmitter, only when the collective response is an acknowledge. FIG. 9 specifies for each command how the bus response lines are interpreted. The collective response (FIG. 9) guarantees that a command is acknowledged only when all modules agree (by transmitting their individual bus responses on the bus response lines) that a command is error-free. 
     C. Coherency Functions 
     This section describes what the coherency rules are, and what actions are taken by the bus protocol to guarantee data coherency. Examples are used to illustrate the various coherency related actions for each command. 
     (C.1) Coherency Rules: 
     The bus protocol implements the following rules to guarantee data coherency, i.e., a PE reading any specific address will always find the current value which is the value of the master block. Thus any copies made must have the same value and only one master can exist for each address. 
     a. At system power-up, master blocks reside in main memory. 
     b. Any number of PE&#39;s may have copies (in their caches) of a given master block located in main memory 20. 
     c. When a PE obtains the master from memory, other PE&#39;s must invalidate their copies of that master. 
     d. When a PE has a copy, a ND command causes that copy to be invalidated. 
     e. From the time a PE module issues a PR command till it receives the master block, that PE should assert PE-BUSY in response to all PR, SR and ND commands issued subsequently by other PE&#39;s for that same block of data. 
     f. When a PE has the master block for a given address it must respond with PE-ACK (unless it has an error) for SR, PR and ND commands which are transmitted on the system bus. It must also take appropriate action depending on the type of command to be described hereinafter. 
     g. When data is requested, received, or returned, the cache and image directories must be updated to reflect the status of that block. 
     (C.2) Coherency Actions 
     This section details the actions taken to maintain coherency, by the cache controller 8 using the cache directory 32cd, and by the BIU (34 and 28) using the image directory 32ti. FIGS. 10 and 11 represent the four states of any data block (at a given address) which may reside in the cache data array 12da. Coherency actions taken by the cache controller 8 or BIU (34, 28) change the status of a data block. 
     Cache Controller Coherency Operations 
     The &#34;status&#34; of a data block in cache (12da, FIGS. 2, 3A) may change due to PE accesses or BIU commands. Coherency actions caused by each command are detailed next hereunder. 
     a. SR issued by cache controller due to PE read: When a PE reads a data word and the state in cache is &#34;invalid&#34; (FIGS. 10, 14B) the cache controller 8 issues a Shared Read Command SR (also called a local SR because it was issued by the local PE) to the BIU 28. The &#34;status&#34; in cache directory 32cd , corresponding to the address requested by the PE, is marked &#34;Pending&#34;. The marking process consists of writing the tag (for example, if address is FFF00005, then tag is FFF00) into the cache tag array 12ta and writing the PV array 12pv with binary &#34;10&#34; which represents the Pending state. This coherency action is represented in FIG. 10 by the arrow from Invalid to Pending, a status change caused by a local SR (labelled beside the arrow). 
     b. (Private Read) issued by Cache Controller due to PE write: The PR will not be issued if the data exists as a Valid Master or is Pending. However, if the data exists as &#34;a copy&#34; or does not exist (Invalid) then a PR is issued to the BIU 28. The cache controller 8 marks its cache directory 32cd as Pending, exactly as it does for the SR (depicted by the arrow from Invalid and the arrow from Valid Copy to Pending, labelled &#34;local PR&#34;). 
     Purge Command issued by cache controller due to local SR or PR: If the cache controller 8 finds that it needs to remove a master block in cache 12da, to create space for a block that needs to be marked as Pending, it issues a Purge command. A Purge returns a master block from cache to memory 20. FIG. 10 represents such an action by the arrow from Valid Master (binary 11) to Invalid (binary 00). The Invalid location in the directory 32cd is now used to accommodate the incoming TBS or TBP and is marked Pending. 
     d. Purge Command issued by cache controller due to external SR: An external SR is an SR (Shared Read) command that comes to the cache controller 8 from the BIU 28 which received the SR from the system bus 24. Such a command, which comes into the cache controller from the system bus via the BIU, is called an external (or remote) command, because it originated in some other PE 10 (as 10a, 10b, 10c, or 10d) An external SR causes the cache controller 8 to return the master block to memory 20, and mark its directory 32cd as Invalid (see arrow in FIG. 10 labelled &#34;Purge due to external SR&#34;). 
     TBP (Transmit Block Private Command) by cache controller due to external PR: An external PR received by the cache controller 8 will cause it to transfer the master block 32cd by issuing a TBP command and marking the cache directory as Invalid (see arrow in FIG. 10 labelled &#34;TBP due to external PR&#34;). 
     f. The INVCOPY Command: The BIU 28 will direct the cache controller 8 to invalidate a specific copy if it determines that a valid copy exists in the cache 12da while another module 6 (6a, 6b, 6c, 6d), 20 (20a, 20b, 20c), is receiving the corresponding master block. Such an invalidation is facilitated by the INVCOPY command issued by the BIU to the cache controller. An INVCOPY command is also generated when a New Data ND command is detected and a valid copy exists in cache. 
     TBP (Transmit Block Private Command) and TBS (Transmit Block Share Command) from the BIU: The cache controller 8 expects to receive TBS or TBP from the BIU 28 in response to a prior issue of SR or PR to the BIU. When data is transferred to the cache controller 8 from the BIU 28 via a TBP or TBS command, the status of the block in cache 12da is updated from Pending to Valid Copy (for TBS), or from Pending to Valid Master (for TBP) as seen in FIG. 10. 
     The commands detailed above comprise all the state changes that can occur for any given data block in the cache. Next, a description of coherency operations done by the BIU follows. 
     (C.4) BIU Coherency Operations 
     The coherency actions taken by the BIU 28 are based on its snooping function. The BIU performs the following functions when a command is received from the bus 24. 
     a. Drive the individual bus response on the system bus response lines. 
     b. Update the image directory 32ti if required. 
     c. Pass the system bus command, or an INVCOPY command, to the cache controller 8 if required. Since the above actions are triggered only by the commands on the system bus, each command will be detailed separately. The status changes that are done by the BIU, for any given address in the image directory, are shown in FIG. 11. 
     Local SR or PR: Any BIU can identify &#34;local&#34; commands from &#34;external&#34; ones (issued by other modules) by simply comparing the source ID field of the system bus to its own ID value. When a local SR or PR is identified, the BIU marks its directory as Pending. Note that the transition arrows correspond in FIGS. 10 and 11, and each arrow is denoted with a (1) or (2). A (1) denotes that this particular state change occurs before its counterpart in the other diagram. A (2) denotes that this state change occurs after its counterpart in the other diagram. For example, a state change associated with a local SR or PR occurs first in the cache directory 32cd and afterwards in the image directory 32ti. In fact, the (1) or (2) denotes the natural flow of the command and therefore the sequence of updates as well. This illustrates how the two directories are updated at different times (i.e. non-atomically) in the same PE module 6. 
     Local Purge and TBP due to external PR: The BIU marks its image directory 32ti &#34;invalid&#34; when a master leaves the module by way of a TBP command or Purge command issued by the local cache controller 8. The arrow from Valid Master to Invalid in FIGS. 10 and 11 depicts the sequence--first the cache controller 8 marks its cache directory 32cd and later, when the command, is on the system bus, the image directory 32ti marked by the BIU 28. 
     INVCOPY command due to external TBP or ND: If the BIU detects a TBP or ND on the system bus, and also finds a valid copy status in the image directory for the same address, it updates the image directory to change the &#34;valid copy&#34; status to &#34;invalid&#34; and also issues an INVCOPY command to the cache controller 8 which does the same to cache directory 32cd. This ensures coherency rule #3. The sequence numbers show that the image directory 32ti in FIG. 11 does this update before the cache directory 32cd in FIG. 10. 
     Incoming TBS or TB Commands: Data required by the local cache controller 8 of a given PE module will be transmitted on the system bus 24 as a TBS (Transmit Block Shared) or TBP (Transmit Block Private) command. The BIU 28 of the requesting module will update its image directory as shown in FIG. 11 and then forward the command to the cache controller 8 which marks its own cache directory 32cd. Thus, in FIG. 11 the incoming TBS goes from Pending to Valid Copy Status while incoming TBP goes from Pending to Valid Master. 
     External SR, PR, ND commands: If the BIU detects a SR, PR, ND on the system bus and also finds the corresponding &#34;Valid Master&#34; status in its image directory it asserts PE-ACK, as outlined in Paragraph B. Then the BIU passes the command to the cache controller 8 which takes appropriate action depending on the command. 
     For a SR command, the cache controller executes a Purge. Such a Purge performs two functions; it returns the master data block to memory, and also allows the module which issued the SR to make a copy while the Purge is on the system bus 24. 
     For a PR command, the cache controller executes a TBP, and for an ND the cache controller updates the existing master with the new value and sends back a Result command to the module which issued the ND. 
     Four examples are shown in FIGS. 12A and B, 13A and B, 14A and B, and 15A and B to illustrate a complete sequence of directory updates. The examples show how coherency is maintained by using duplicated directories (image and cache) which are updated at different times (i.e. non-atomically). Thus, despite the temporary inconsistencies between the directories, the PE&#39;s 10 are provided with coherent data. Since the cache directory is &#34;decoupled&#34; from the image directory, the PE-cache speed can be maximized. 
     In FIGS. 12A, 13A, 14A, and 15A two PE modules P1 and P2, and a memory module MM 20 are shown connected to the system bus 24 which may have other modules as well. Events are defined as actions occurring in a clock period. Clock periods (FIGS. 12B, 13B, 14B, 15B) are identified by t0, t1, t2, etc., where t1 is one or more clocks after t0, t2 is one or more clocks after t1 and so on. 
     FIGS. 12A, 12B show a system where a master data block, at address FFF00005 for example, is in a MM and no copies exist. At clock t0, PE1 reads the value at FFF00005 and the cache controller finds that the location is invalid. In clock t1 the cache controller writes a Pending status in the cache directory. FIG. 12B illustrates the important events that occur in t2, t3, t4, t5, t6 and t7. Finally in t8 the cache controller receives the data block and passes the requested data word to PE1 and also updates its directory to show Copy status. Note that the updates are done in t6 and t8, i.e. non-atomically. The state of the cache directory is shown in FIGS. 3A and 3B. 
     FIGS. 13A, 13B show a subsequent event in the same system where P1 has a copy of the data in cache, at address FFF00005 for example. At t0, PE2 writes at address FFF00005 and the cache controller of P2 finds that it has a status of Invalid for FFF00005. In t1, the cache controller of P2 updates its directory to Pending and in t2 issues a PR to the BIU of P2. In t5 the MM returns the master block, and in t6 all BIUs check their image directories. Both images are updated simultaneously, i.e. atomically. The BIU of P1 finds a copy of the same block in its directory which it invalidates. In t7 the BIU forwards an INVCOPY command to P1 cache controller. Meanwhile the BIU of P2 (in t6) finds the status &#34;Pending&#34; for the block that the MM sent, and so it receives the data block. In t8, P1 &#34;invalidates&#34; the status of the copy in its cache and in t10, P2 writes the &#34;master&#34; status into its cache directory. This example illustrates how coherency is maintained even though the directory updates of P1 are non-atomic; cache of P1 is updated in t8 and cache of P2 in t10. 
     FIGS. 14A, 14B show the transfer of a master block, for example, at address FFF00005, from P2 to P1. MM does not get involved because, in t4, P1 checks its image directory, finds the corresponding master and asserts PE-ACK. Thus MM knows that it must ignore this PR command. FIGS. 15A, 15B show the case where a master block in P1 is returned to memory via a Purge command, caused by a SR command issued by P2. 
     GLOSSARY 
     Atomic: Events are termed atomic when they occur simultaneously, or one after the other &#34;without interruption&#34;. 
     Bus Protocol: A set of rules and command functions that determine data transfer and data coherency across the multiprocessor system. 
     Block: A data block is defined as a set of four words whose addresses differ only in the least two address bits (A0,A1). 
     Copy: A block of data classified as a copy allows the PE containing that copy to read any word in the block. No writes are permitted. Copies are made from the master primarily by MM&#39;s. 
     Copy-back Cache: A copy-back cache allows PE writes to be copied back to memory sometime after the write is done, rather than immediately. 
     Directory: A look-up table which shows the existence and status of a data block, i.e. cache directory, image directory. 
     Image Array: Also called image directory, is an exact copy of the cache directory, but subject to time lag. 
     Invalid: Designates that the data does not exist in cache memory. 
     Master: A block of data when classified as a master gives the PE containing that master in its cache the right to modify it. 
     MM: Main memory module. 
     Non-Atomic: Two events are non-atomic if other events can occur between them. See Atomic. 
     PE: Processor Element. 
     Pending: Designates that a location in cache memory is reserved for a requested block of data. 
     Request Command: A system bus command which is used to obtain (request) information such as memory data. 
     Return Command: A system bus command which is used to transfer information, such as memory data, back to the requesting module in response to a request command. 
     Snooping: The process of using the address specified in the bus command to read the image directory to find out whether a matching address exists in the image, and if so, what the status of the block is. 
     There has been described herein a multiprocessor network where each processor has its own private cache means and bus interface means which connect to a common system bus to permit intercommunication between the processors and a main memory means. Each processor has its own cache directory and image directory which duplicate each other non-atomically so that the image directory can provide information as to the availability and status of requested data blocks while leaving the cache directory uninhibited for immediate access by a requesting processor, thus providing rapid data access from cache to the requesting processor without unnecessary delays. 
     Although the disclosure indicates the preferred implementation, other embodiments of this invention may be possible, but which are encompassed by the following claims.