Resource locking and thread synchronization in a multiprocessor environment

• US 6,782,440 B2
• Filed: 07/25/2001
• Issued: 08/24/2004
• Est. Priority Date: 07/26/2000
• Status: Active Grant

• Current Assignee: Times N Systems, Monterey Research, LLC (Vector Capital Corporation)
• Original Assignee: TNS Holdings, Inc. (Trident Private Holdings I LLC)
• Inventors: Miller, Chris D.
• Primary Examiner(s): Ray, Gopal C.
• Application Number:
  US09/912,870
• Publication Number:
  US 20020016879A1
• Time in Patent Office: 1,126 Days
• Field of Search: 710/200, 710/36, 710/108, 710/52, 710/240, 709/100, 709/104, 707/8, 711/147, 711/148, 711/152, 711/163
• US Class Current: 710/200
• CPC Class Codes: G06F 12/0284 Multiple user address space allocation, e.g. using different base addresses interprocessor communication G06F15/163
• CPC Class Codes: G06F 12/0817 using directory methods
• CPC Class Codes: G06F 12/0837 with software control, e.g. non-cacheable data
• CPC Class Codes: G06F 12/0862 with prefetch
• CPC Class Codes: G06F 13/28 using burst mode transfer, e.g. direct memory access DMA, cycle steal G06F13/32 takes precedence
• CPC Class Codes: G06F 2212/507 using speculative control
• CPC Class Codes: G06F 8/457 Communication intertask communication G06F9/54
• CPC Class Codes: G06F 9/5016 the resource being the memory
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database

Abstract

Systems and methods are described for resource locking and thread synchronization in a multiprocessor environment. One method includes restricting access to a protected shared resource by use of a lock; issuing the lock to a requesting software to permit access to the protected shared resource; indicating the issuance of the lock to the requesting software by writing a first value to a lock register; freeing the lock, thereby making the lock available for use by another requesting software, after the requesting software completes accessing the protected shared resource; and indicating that the lock is free by writing a second value to the lock register.

Claims

1. A method, comprising:

receiving a request from a requesting software to access a protected shared resource,

the protected shared resource currently being accessed by another requesting software;

designating a proxy value to represent the requesting software;

adding the proxy value to a queue of proxy values contained in a lock register;

suspending execution of the requesting software;

determining when the protected shared resource is no longer being accessed by another requesting software;

if the proxy value representing the requesting software is first in the queue of proxy values, resuming execution of the requesting software using the proxy value;

if the proxy value representing the requesting software is first in the queue of proxy values, allowing the requesting software to access the protected shared resource using the proxy value;

if the proxy value representing the requesting software is first in the queue of proxy values, upon completion of access to the protected shared resource by the requesting software, removing the proxy value representing the requesting software from the queue of proxy values; and

if there is no next proxy value in the queue of proxy values, writing a release value to the lock register.

2. The method of claim 1, wherein the protected shared resource can only be accessed by one requesting software at a time.

3. The method of claim 1, wherein the queue of proxy values in the lock register is maintained in a chronological order.

4. The method of claim 1, wherein access to the protected shared resource is allowed by the acquisition of a spinlock.

5. The method of claim 1, wherein the requesting software is executed on a requesting central processing unit.

6. The method of claim 5, wherein the requesting central processing unit is free to execute other software while the requesting software is suspended.

7. The method of claim 1, wherein writing a release value to the lock register enables other requesting software to access the protected shared resource without the use of the proxy value.