Transaction activation processor for controlling memory transaction processing in a packet switched cache coherent multiprocessor system

• US 5,905,998 A
• Filed: 05/19/1997
• Issued: 05/18/1999
• Est. Priority Date: 03/31/1995
• Status: Expired due to Term

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Normoyle, Kevin, Nishtala, Satyanarayana, Coffin, Louis F. III, Loewenstein, Paul, Van Loo, William C., Ebrahim, Zahir
• Primary Examiner(s): Chan, Eddie P.
• Assistant Examiner(s): KIM, HONG CHONG
• Application Number:
  US08/858,792
• Time in Patent Office: 729 Days
• Field of Search: 711/144, 711/121, 711/146, 711/143, 711/150, 711/145, 711/120, 711/141
• US Class Current: 711/144
• CPC Class Codes: G06F 12/0822 Copy directories local copy tags for implementing a bus snooping protocol G06F12/0831
• CPC Class Codes: G06F 12/0828 with concurrent directory accessing, i.e. handling multiple concurrent coherency transactions

Abstract

A multiprocessor computer system has a multiplicity of sub-systems and a main memory coupled to a system controller. Some of the sub-systems are data processors, each having a respective cache memory that stores multiple blocks of data and a respective set of master cache tags (Etags), including one Etag for each data block stored by the cache memory. Each data processor includes an interface for sending memory transaction requests to the system controller and for receiving cache transaction requests from the system controller corresponding to memory transaction requests by other ones of the data processors. The system controller includes transaction activation logic for activating each said memory transaction request when it meets predefined activation criteria, and for blocking each said memory transaction request until the predefined activation criteria are met. An active transaction status table stores status data representing memory transaction requests that have been activated, including an address value for each activated transaction. The transaction activation logic includes comparator logic for comparing each memory transaction request with the active transaction status data for all activated memory transaction requests so as to detect whether activation of a particular memory transaction request would violate the predefined activation criteria. With certain exceptions concerning writeback transactions, an incoming transaction for accessing a data block that maps to the same cache line a pending, previously activated transaction, will be blocked until the pending transaction that maps to the same cache line is completed.

Claims

1. A computer system, comprising:

a system controller;

a multiplicity of sub-systems coupled to the system controller;

a main memory coupled to the system controller; and

a plurality of the sub-systems comprising data processors, a plurality of the data processors each having a respective cache memory that stores multiple blocks of data and a respective set of cache tags, including one cache tag for each data block stored by the cache memory;

each of the plurality of data processors including an interface, coupled to the system controller, for sending memory transaction requests to the system controller;

the interface for each of the data processors that has a cache memory including circuitry for receiving cache transaction requests from the system controller corresponding to memory transaction requests by other ones of the data processors;

each memory transaction request having an associated address value;

the system controller including;

transaction activation logic for activating each memory transaction request when it meets predefined activation criteria, and for blocking each memory transaction request until the predefined activation criteria are met;

wherein the predefined activation criteria include an address conflict criterion that is a function of the address value associated with the memory transaction request and the address value of activated memory transaction requests;

an active transaction status table that stores active transaction status data representing memory transaction requests which have been activated by the transaction activation logic, the active transaction status data including data for each activated transaction representing an address value associated with the transaction;

the active transaction status data including data representing memory transaction requests received from the plurality of data processors; and

memory transaction request logic for processing the memory transaction request after it has been activated by the transaction activation logic;

the transaction activation logic including parallel comparison logic for simultaneously comparing one not-yet-activated memory transaction request with the stored active transaction status data for all activated memory transaction requests so as to detect whether activation of the each memory transaction request would violate the predefined activation criteria with respect to any of the activated memory transaction requests;

wherein the transaction activation logic blocks all transaction requests by any of the data processors that violate the predefined activation criteria with respect to any memory transaction that has already been activated.

2. The computer system of claim 1,

the comparison logic blocking the transaction activation logic from activating the one memory transaction request when (A) a cache index portion of the address value associated with the memory transaction request matches a corresponding portion of the address value associated with any of the activated memory transaction requests represented in the active transaction status table, without regard to which data processors sent the activated memory transaction requests to the system controller, unless (B) the memory transaction request and the activated memory transaction request with the matching cache index comprise a read transaction request and a writeback transaction request.

3. The computer system of claim 1,

the interface for the data processor including at least two parallel outbound request queues for storing memory transaction requests to be sent to the system controller;

the memory transaction requests including read requests and write requests;

each memory transaction request specifying an address for an associated data block to be read or written;

wherein the system controller processes the memory transaction requests stored in the outbound request queues in accordance with resource availability such that a first of the memory transaction requests stored in one of the outbound request queues may be processed later by the system controller than a second of the memory transaction requests stored in a second of the outbound request queues even when the second memory transaction request is stored in the second outbound request queue later than when the first memory transaction request is stored in the first outbound request queue.

4. The computer system of claim 3,

the data processors each storing read requests in a first of the outbound request queues and storing writeback requests in a second of the outbound request queues such that the system controller can process in parallel a read request and a writeback request from a same one of the data processors and that both reference address values having matching cache index values.

5. A method of operating a cache coherent multiprocessor system having a system controller coupled to a main memory and to a plurality of data processors each of which has a cache memory, comprising the steps of:

sending memory transaction requests from each of the plurality of data processors to the system controller, each memory transaction request having an associated address value;

activating the memory transaction request when it meets predefined activation criteria, and blocking the memory transaction request until the predefined activation criteria are met;

wherein the predefined activation criteria include an address conflict criterion that is a function of the address value associated with the memory transaction request and the address value associated with activated memory transaction requests;

storing active transaction status data representing memory transaction requests which have been activated, the active transaction status data including data for each activated transaction representing an address value associated with the transaction;

the active transaction status data including data representing memory transaction requests received from the plurality of data processors; and

processing the memory transaction request after it has been activated by the transaction activation logic;

the activating step including simultaneously comparing one not-yet-activated memory transaction request with the stored active transaction status data for all activated memory transaction requests so as to detect whether activation of the one memory transaction request would violate the predefined activation criteria with respect to any of the activated memory transaction requests;

wherein the activating step includes blocking all transaction requests by any of the data processors that violate the predefined activation criteria with respect to memory transaction that has already been activated.

6. The method of claim 5,

the comparing step blocking the activating step from activating the memory transaction request when (A) a cache index portion of the address value associated with the memory transaction request matches a corresponding portion of the address value associated with any of the activated memory transaction requests represented in the active transaction status table, without regard to which data processors sent the activated memory transaction requests to the system controller, unless (B) the memory transaction request and the activated memory transaction request with the matching cache index comprise a read transaction request and a writeback transaction request.

7. The method of claim 5,

at each data processor, storing the memory transaction requests to be sent to the system controller in at least two parallel outbound request queues associated with that data processor;

the memory transaction requests including read requests and write requests;

each memory transaction request specifying an address for an associated data block to be read or written;

at each data processor, storing a respective set of cache tags, including one cache tag for each data block stored in the data processor'"'"'s cache memory;

the processing step includes processing the memory transaction requests stored in the outbound request queues in accordance with resource availability such that a first of the memory transaction requests stored in one of the outbound request queues may be processed later by the system controller than a second of the memory transaction requests stored in a second of the outbound request queues even when the second memory transaction request is stored in the second outbound request queue later than when the first memory transaction request is stored in the first outbound request queue.

8. The method of claim 7,

at each data processor, storing read requests in a first of the outbound request queues and storing writeback requests in a second of the outbound request queues such that the system controller can process in parallel a read request and a writeback request from a same one of the data processors and that both reference address values having matching cache index values.