METHODS AND SYSTEMS FOR AN INTENT LOCK ENGINE

• US 20140040218A1
• Filed: 07/31/2012
• Published: 02/06/2014
• Est. Priority Date: 07/31/2012
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hideaki Kimura
• Inventors: Kuno, Harumi, KIMURA, Hideaki, Graefe, Geotz
• Application Number:
  US13/563,609
• Publication Number:
  US 20140040218A1
• Time in Patent Office: Days
• US Class Current: 707/704
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity

Abstract

In at least some examples, a system may include a processor core and a non-transitory computer-readable memory in communication with the processor core. The non-transitory computer-readable memory may store an intent lock engine to manage intent locks based on a private lock table for each process associated with said processor core and a global lock table for a plurality of processes associated with at least one of a plurality of processor cores including said processor core.

Claims

1. A system, comprising:

a processor core; and

a non-transitory computer-readable memory in communication with the processor core and storing an intent lock engine to manage intent locks based on a private lock table for each process associated with said processor core and a global lock table for a plurality of processes associated with at least one of a plurality of processor cores including said processor core.

2. The system of claim 1, wherein upon receipt of an intent lock request, the intent lock engine causes a process associated with said processor core to check its private lock table for an intent lock compliant with the intent lock request before submitting the intent lock request to the global lock table.

3. The system of claim 2, wherein the intent lock engine, when the intent lock request is submitted to the global lock table, increments a counter separate from the global lock table for an intent lock type associated with the intent lock request.

4. The system of claim 1, wherein the private lock table and the global lock table track share mode locks, share mode intent locks, exclusive mode locks, and exclusive mode intent locks.

5. The system of claim 1, wherein the intent lock engine causes a process associated with the processor core to apply a mutex lock when the intent lock request corresponds to an absolute lock.

6. The system of claim 1, wherein the intent lock engine, when an intent lock corresponding to the intent lock request is released, decrements a counter separate from the global lock table for an intent lock type associated with the intent lock request.

7. The system of claim 6, wherein the intent lock engine causes a process associated with the processor core to broadcast a message to awaiting threads when the intent lock corresponding to the intent lock request is released.

8. The system of claim 1, wherein the intent lock engine causes a thread associated with at least one of the plurality of processor cores to wake up according to a predetermined multi-thread schedule upon release of an intent lock.

9. A non-transitory computer-readable medium storing an intent lock management program that, when executed, causes a processor running a process to:

maintain a private lock table for the process with status information for intent locks granted to the process;

in response to initiation of an intent lock request, check the status information for any intent locks in the maintained private lock table; and

in response to detecting that no intent locks in the maintained private lock table correspond to the intent lock request, submit the intent lock request to a global lock table for a plurality of processes associated with at least one of a plurality of processor cores including said processor core.

10. The non-transitory computer-readable medium of claim 9, wherein the intent lock management program, when executed, further causes the processor running the process to increase a counter separate from the global lock table for an intent lock type associated with the intent lock request.

11. The non-transitory computer-readable medium of claim 9, wherein the intent lock management program, when executed, further causes the processor running the process to maintain share mode locks, share mode intent locks, exclusive mode locks, and exclusive mode intent locks for the private lock table and the global lock table.

12. The non-transitory computer-readable medium of claim 9, wherein the intent lock management program, when executed, further causes the processor running the process to apply a mutex lock when the intent lock request corresponds to an absolute lock.

13. The non-transitory computer-readable medium of claim 9, wherein the intent lock management program, when executed, further causes the processor running the process to decrement a counter separate from the global lock table for an intent lock type associated with the intent lock request when the intent lock request is released.

14. The non-transitory computer-readable medium of claim 9, wherein the intent lock management program, when executed, further causes the processor running the process to broadcast a message to awaiting threads when the intent lock corresponding to the intent lock request is released.

15. The non-transitory computer-readable medium of claim 9, wherein the intent lock management program, when executed, further causes the processor running the process to wake up a thread according to a predetermined multi-thread schedule upon release of an intent lock.

16. A method, comprising:

maintaining, by a processor running a process, a private lock table for the process with status information for current intent locks granted to the process;

determining, by the processor running the process, whether a new intent lock request can be handled by any current intent locks granted to the process based on the status information in the private lock table; and

submitting, by the processor running the process, the new intent lock request to a global lock table for a plurality of processes in response to determining that a new intent lock request cannot be handled by any current intent lock granted to the process.

17. The method of claim 16 further comprising increasing a counter separate from the global lock table for an intent lock type associated with the new intent lock request in response to said submitting.

18. The method of claim 16, further comprising decrementing a counter separate from the global lock table for an intent lock type associated with the intent lock request when an intent lock corresponding to the intent lock request is released.

19. The method of claim 16, further comprising broadcasting a message to awaiting threads when the intent lock corresponding to the intent lock request is released.

20. The method of claim 16, further comprising waking up a thread according to a predetermined multi-thread schedule upon release of an intent lock.