Almost fair busy lock

• US 9,697,055 B2
• Filed: 09/22/2015
• Issued: 07/04/2017
• Est. Priority Date: 11/18/2014
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Greco, Marco
• Primary Examiner(s): SWIFT, CHARLES M
• Application Number:
  US14/860,965
• Publication Number:
  US 20160139966A1
• Time in Patent Office: 651 Days
• Field of Search: None
• CPC Class Codes: G06F 9/48 Program initiating; Program switching, e.g. by interrupt
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence
• CPC Class Codes: G06F 9/4881 Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores
• CPC Class Codes: G06F 9/524 Deadlock detection or avoidance
• CPC Class Codes: G06F 9/526 Mutual exclusion algorithms

Abstract

Managing exclusive control of a shareable resource includes publishing a claim non atomically to a lock by a thread that is next to own the lock in an ordered set of threads that have requested to own the lock. The claim includes a structure capable of being read and written only in a single memory access. A determination is made of whether the next owning thread has been pre-empted. Responsive to the determination, the next owning thread of the lock acquires the lock if the next owning thread has not been pre-empted and retries acquisition of the lock if the next owning thread has been pre-empted. Responsive to the next owning thread being pre-empted, a subsequent owning thread acquires the lock unfairly and atomically, consistently modifies the lock such that a next lock owner can determine that the next lock owner has been preempted.

Claims

1. A method for managing exclusive control of a shareable resource, the method comprising:

publishing a current state of a lock and a claim non atomically to the lock by a next owning thread in an ordered set of threads that have requested to own the lock, the claim comprising a structure capable of being read and written only in a single memory access;

determining by the next owning thread whether the next owning thread has been pre-empted;

determining by a subsequent owning thread whether the next owning thread has been preempted by comparing the current state of the lock with the claim,

wherein the subsequent owning thread is scheduled to follow the next owning thread;

responsive to determining whether the next owning thread has been preempted, acquiring by the next owning thread the lock if the next owning thread has not been pre-empted;

responsive to determining whether the next owning thread has been preempted, retrying by the next owning thread acquisition of the lock if the next owning thread has been pre-empted; and

responsive to determining that the next owning thread has been pre-empted, acquiring by the subsequent owning thread the lock unfairly and atomically, consistently modifying the lock such that a next lock owner can determine that the next lock owner has been preempted.

2. The method of claim 1, wherein:

the ordered set of threads comprises tickets, each thread requesting ownership of the lock obtaining a ticket; and

the claim comprises an identifier of the ticket obtained by the next owning thread, and an indication that the next owning thread is claiming the lock.

3. The method of claim 2, further comprising:

comparing the obtained next owning thread ticket with a current ticket; and

responsive to a match between the obtained next owning thread ticket and the current ticket, non-atomically acquiring the lock.

4. The method of claim 1, wherein the claim structure is a union.

5. The method of claim 1, further comprising responsive to a determination that the next owning thread has been pre-empted, cancelling by the next owning thread requesting ownership of the lock.

6. A system for managing exclusive control of a shareable resource between a plurality of concurrently executing threads, comprising:

a lock for controlling access to the shareable resource, the lock maintaining an ordered set of threads requesting ownership of the lock;

a claim structure, capable of being read and written only in a single memory access, non-atomically published by a next owning thread, in the ordered set of threads, making a claim to the lock; and

one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage devices, and program instructions stored on at least one of the one or more computer-readable storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, wherein the system is capable of performing a method comprising

after publishing a current state of the lock and the claim, determining by the next owning thread of the lock whether the next owning thread has been pre-empted,

determining by a subsequent owning thread of the lock whether the next owning thread has been preempted by comparing the current state of the lock with the claim, wherein the subsequent owning thread is scheduled to follow the next owning thread,

responsive to determining whether the next owning thread has been pre-empted, acquiring by the next owning thread the lock if the next owning thread has not been pre-empted,

responsive to determining whether the next owning thread has been pre-empted, retrying acquisition of the lock if the next owning thread has been pre-empted, and

responsive to determining that the next owning thread has been pre-empted, acquiring by the subsequent owning thread the lock unfairly and atomically, consistently modifying the lock such that a next lock owner can determine that the next lock owner has been preempted.

7. The system of claim 6, wherein:

the ordered set of threads comprises tickets, each thread requesting ownership of the lock obtaining a ticket; and

the claim comprises an identifier of the ticket obtained by the next owning thread, and an indication that the next owning thread is claiming the lock.

8. The system of claim 7, wherein the method further comprises:

comparing the obtained next owning thread ticket with a current ticket; and

responsive to a match between the obtained next owning thread ticket and the current ticket, non-atomically acquiring by the next owning thread the lock.

9. The system of claim 6, wherein the method further comprises responsive to the next owning thread being pre-empted, cancelling by the next owning thread requesting ownership of the lock.

10. The system as claimed in claim 6, wherein the claim structure is a union.

11. A computer program product for managing exclusive control of a shareable resource, the computer program product comprising a computer-readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to perform a method comprising:

publishing a current state of a lock and a claim non atomically to the lock by a next owing thread in an ordered set of threads that have requested to own the lock, the claim comprising a structure capable of being read and written only in a single memory access;

determining by the next owning thread whether the next owning thread has been pre-empted;

determining by a subsequent owning thread whether the next owning thread was preempted by comparing the current state of the lock with the claim, wherein the subsequent owning thread is scheduled to follow the next owning thread;

responsive to determining whether the next owning thread has been preempted, acquiring by the next owning thread of the lock the lock if the next owning thread has not been pre-empted;

responsive to determining whether the next owning thread has been preempted, retrying by the next owning thread acquisition of the lock if the next owning thread has been pre-empted; and

responsive to determining that the next owning thread has been pre-empted, acquiring by the subsequent owning thread the lock unfairly and atomically, consistently modifying the lock such that a next lock owner can determine that the next lock owner has been preempted.

12. The computer program product of claim 11, wherein:

the ordered set of threads comprises tickets, each thread requesting ownership of the lock obtaining a ticket; and

the claim comprises an identifier of the ticket obtained by the next owning thread, and an indication that the next owning thread is claiming the lock.

13. The computer program product of claim 12, wherein the method further comprises:

comparing the obtained next owning thread ticket with a current ticket; and

responsive to a match between the obtained next owning thread ticket and the current ticket, non-atomically acquiring the lock.

14. The computer program product of claim 11, wherein the claim structure is a union.

15. The computer program product of claim 11, wherein the method further comprises responsive to a determination that the next owning thread has been pre-empted, cancelling by the next owning thread requesting ownership of the lock.