Optimization of Data Locks for Improved Write Lock Performance and CPU Cache usage in Mulit Core Architectures

• US 20160098361A1
• Filed: 10/07/2014
• Published: 04/07/2016
• Est. Priority Date: 10/07/2014
• Status: Active Grant

• Current Assignee: Check Point Software Technologies Limited
• Original Assignee: Check Point Software Technologies Limited
• Inventors: CHANDEL, Ajay
• Granted Patent: US 9,569,265 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 2209/523 Mode
• CPC Class Codes: G06F 2212/1008 Correctness of operation, e.g. memory ordering
• CPC Class Codes: G06F 2212/1032 Reliability improvement, data loss prevention, degraded operation etc
• CPC Class Codes: G06F 2212/62 Details of cache specific to multiprocessor cache arrangements
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]
• CPC Class Codes: G06F 9/526 Mutual exclusion algorithms

Abstract

Data access optimization features the innovative use of a writer-present flag when acquiring read-locks and write-locks. Setting a writer-present flag indicates that a writer desires to modify a particular data. This serves as an indicator to readers and writers waiting to acquire read-locks or write-locks not to acquire a lock, but rather to continue waiting (i.e., spinning) until the write-present flag is cleared. As opposed to conventional techniques in which readers and writers are not locked out until the writer acquires the write-lock, the writer-present flag locks out other readers and writers once a writer begins waiting for a write-lock (that is, sets a writer-present flag). This feature allows a write-lock method to acquire a write-lock without having to contend with waiting readers and writers trying to obtain read-locks and write-locks, such as when using conventional spinlock implementations.

Claims

1. A method for data access by a CPU, the method comprising the steps of:

(a) checking if a writer-present flag is set or cleared; and

(b) acquiring a read-lock when said writer-present flag is cleared.

2. The method of claim 1 wherein said step of checking includes performing a first writer-present flag status check, and if said first writer-present flag status check determines that said writer-present flag is:

(i) set, repeating said step of checking;

or

(ii) cleared, initially acquiring said read-lock,

(c) subsequent to said initially acquiring said read-lock, performing a second writer-present flag status check, and

(d) if said second writer-present flag status check determines that said writer-present flag is;

(i) set, releasing said read-lock and repeating said first writer-present flag status check;

or

(ii) cleared, maintaining said read-lock.

3. The method of claim 2 wherein said repeating said step of checking includes implementing a spinlock.

4. The method of claim 1 wherein said read-lock is:

(a) associated with a CPU group that includes a plurality of CPUs; and

(b) for data accessed via said CPU group.

5. The method of claim 1 further comprising the step of:

(c) releasing said read-lock.

6. The method of claim 5 wherein releasing said read-lock includes clearing said read-lock flag.

7. A method for data access by a CPU, the method comprising the steps of:

(a) checking if a writer-present flag is set or cleared; and

(b) acquiring a write-lock when said writer-present flag is cleared.

8. The method of claim 7 wherein said step of checking includes performing a first writer-present flag status check, and if said first writer-present flag status check determines that said writer-present flag is:

(i) set, repeating said step of checking;

or

(ii) cleared, setting said writer-present flag, and

(c) subsequent to setting said writer-present flag, performing a second writer-present flag status check, and

(d) if said second writer-present flag status check determines that said setting said writer-present flag is;

(i) unsuccessful, repeating said first writer-present flag status check;

or

(ii) successful, performing a read-lock check, if said read-lock check determines that said read-lock is;

(A) set, repeating said performing a read-lock check;

or

(B) cleared, acquiring said write-lock.

9. The method of claim 8 wherein said repeating said step of checking includes implementing a spinlock.

10. The method of claim 8 wherein said repeating said step of performing a second writer-present flag status check includes implementing a spinlock.

11. The method of claim 7 wherein said write-lock is:

(a) associated with a CPU group that includes a plurality of CPUs; and

(b) for data accessed via said CPU group.

12. The method of claim 7 further comprising the step of:

(c) releasing said write-lock.

13. The method of claim 12 wherein releasing said write-lock includes clearing said writer-present flag.

14. A system comprising:

(a) a processing system containing one or more processors, said processing system being configured to;

(i) check if a writer-present flag is set or cleared; and

(ii) acquire a read-lock when said writer-present flag is cleared.

15. The system of claim 14 wherein said processing system is further configured to perform said checking via a first writer-present flag status check, and if said first writer-present flag status check determines that said writer-present flag is:

(A) set, repeating said checking;

or

(B) cleared, initially acquiring said read-lock,

(iii) subsequent to said initially acquiring said read-lock, performing a second writer-present flag status check, and

(iv) if said second writer-present flag status check determines that said writer-present flag is;

(A) set, releasing said read-lock and repeating said first writer-present flag status check;

or

(B) cleared, maintaining said read-lock.

16. A system comprising:

(a) a processing system containing one or more processors, said processing system being configured to;

(i) check if a writer-present flag is set or cleared; and

(ii) acquire a write-lock when said writer-present flag is cleared.

17. The system of claim 16 wherein said processing system is further configured to perform said checking via a first writer-present flag status check, and if said first writer-present flag status check determines that said writer-present flag is:

(A) set, repeating said step of checking;

or

(B) cleared, setting said writer-present flag, and

(iii) subsequent to setting said writer-present flag, performing a second writer-present flag status check, and

(iv) if said second writer-present flag status check determines that said setting said writer-present flag is;

(A) unsuccessful, repeating said first writer-present flag status check;

or

(B) successful, performing a read-lock check, and if said read-lock check determines that said read-lock is;

(I) set, repeating said performing a read-lock check;

or

(II) cleared, acquiring said write-lock.

18. A computer-readable storage medium having embedded thereon computer-readable code for data access by a CPU, the computer-readable code comprising program code for:

(a) checking if a writer-present flag is set or cleared; and

(b) acquiring a read-lock when said writer-present flag is cleared.

19. A computer-readable storage medium having embedded thereon computer-readable code for data access by a CPU, the computer-readable code comprising program code for:

(a) checking if a writer-present flag is set or cleared; and

(b) acquiring a write-lock when said writer-present flag is cleared.

20. The computer-readable storage medium of claim 19 wherein said program code further performs said checking via a first writer-present flag status check, and if said first writer-present flag status check determines that said writer-present flag is:

(i) set, repeating said step of checking;

or

(ii) cleared, setting said writer-present flag, and

(c) subsequent to setting said writer-present flag, performing a second writer-present flag status check, and

(d) if said second writer-present flag status check determines that said setting said writer-present flag is;

(i) unsuccessful, repeating said first writer-present flag status check;

or

(ii) successful, performing a read-lock check, if said read-lock check determines that said read-lock is;

(A) set, repeating said performing a read-lock check;

or

(B) cleared, acquiring said write-lock.