Apparatus and method for achieving reduced overhead mutual-exclusion and maintaining coherency in a multiprocessor system utilizing execution history and thread monitoring

• US 5,727,209 A
• Filed: 11/01/1996
• Issued: 03/10/1998
• Est. Priority Date: 07/19/1993
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: Sequent Computer Systems, Inc. (International Business Machines Corporation)
• Inventors: McKenney, Paul E., Slingwine, John D.
• Primary Examiner(s): Kim, Matthew M.
• Application Number:
  US08/742,613
• Time in Patent Office: 494 Days
• Field of Search: 395/474, 395/477, 395/672, 395/676, 395/451, 395/486, 395/485, 395/468, 395/476, 395/447, 395/448, 395/469, 395/470, 395/471-473
• US Class Current: 718/102
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores
• CPC Class Codes: G06F 9/526 Mutual exclusion algorithms

Abstract

A substantially zero overhead mutual-exclusion apparatus and method (90, 120) is provided that allows concurrent reading and updating data while maintaining data coherency. That is, a data reading process executes the same sequence of instructions that would be executed if the data were never updated. Rather than depending exclusively on overhead-imposing locks, this mutual-exclusion mechanism tracks an execution history (138) of a thread (16, 112) to determine safe times for processing a current generation (108, 130, 131) of data updates while a next generation (110, 132, 133) of data updates is concurrently being saved. A thread is any locus of control, such as a processor. A summary of thread activity (106, 122) tracks which threads have passed through a quiescent state after the current generation of updates was started. When the last thread related to the current generation passes through a quiescent state, the summary of thread activity signals a callback processor (104, 124) that it is safe to end the current generation of updates. The callback processor then processes and erases all updates in the current generation. The next generation of updates then becomes the current generation of updates. The callback processor restarts the summary of thread activity and initiates a new next generation of updates. All data-updating threads pass through a quiescent state between the time they attempt to update data and the time the data are actually updated.

Claims

1. A method of using an updater thread to update an original element of a shared data structure in a computer system while maintaining access to the data structure for reader threads, the method comprising the following steps:

with an updater thread, updating the original element by creating a new element;

with the updater thread, modifying links used by reader threads for referencing the original element to now reference the new element; and

using a summary of thread activity to determine when the original element may be erased.

2. The method of claim 1 wherein the shared data structure is adapted to map a handle to the handle'"'"'s associated data element.

3. The method of claim 1 including registering a callback to initiate erasing of the original element.

4. The method of claim 1 wherein the updater thread uses mutual exclusion to allow multiple threads to act as updater threads.

5. The method of claim 1 including erasing the original element with the updater thread.

6. The method of claim 1 wherein the updating step comprises:

creating a new element;

copying data from the original element into the new element; and

changing the data in the new element to complete the update.

7. A computer-readable medium for storing a computer program comprising instructions for executing the method of claim 1.

8. A computer system in accordance with the method of claim 1.

9. Apparatus for using an updater thread to update an original element of a shared data structure in a computer system while maintaining access to the data structure for reader threads, comprising:

means for updating with an updater thread the original element by creating a new element;

means for modifying with the updater thread links used by reader threads for referencing the original element to now reference the new element; and

means for using a summary of thread activity to determine when the original element may be erased.

10. The apparatus of claim 9 including means for registering a callback to initiate erasing of the original element.

11. The apparatus of claim 9 including means for erasing the original element with the updater thread.