Computer-implemented system and method for lock handling
First Claim
1. A memory for storing a computer-implemented shared locking data store for handling multiple executable entities'"'"' access to at least one resource, said shared locking data store being stored in a computer memory, said shared locking data store comprising:
- write requested data that is indicative of when a write request for the resource has been made;
writer active data that is indicative of whether a writer process is actively undergoing a write operation with respect to the resource;
wait event posted data, wherein the wait event posted data is indicative of whether a read request to the resource has completed, wherein the wait event posted data may be used to indicate when a write request can access the resource;
reader data that is indicative of whether a reader process is active and attempting to read from the resource;
wherein the shared locking data store allows writer and reader locking state information to be determined so that access to the resource may be handled;
wherein the write requested data has a set status when a write request has been made, wherein the set status indicates whether a mutex lock is to be used for processing access to the resource, wherein the set status is set to indicate that the mutex lock is not to be used if no write request is pending.
0 Assignments
0 Petitions
Accused Products
Abstract
Computer-implemented systems and methods for handling access to one or more resources. Executable entities that are running substantially concurrently provide access requests to an operating system (OS). One or more traps of the OS are avoided to improve resource accessing performance through use of information stored in a shared locking mechanism. The shared locking mechanism indicates the overall state of the locking process, such as the number of processes waiting to retrieve data from a resource and/or whether a writer process is waiting to access the resource.
33 Citations
19 Claims
-
1. A memory for storing a computer-implemented shared locking data store for handling multiple executable entities'"'"' access to at least one resource, said shared locking data store being stored in a computer memory, said shared locking data store comprising:
-
write requested data that is indicative of when a write request for the resource has been made; writer active data that is indicative of whether a writer process is actively undergoing a write operation with respect to the resource; wait event posted data, wherein the wait event posted data is indicative of whether a read request to the resource has completed, wherein the wait event posted data may be used to indicate when a write request can access the resource; reader data that is indicative of whether a reader process is active and attempting to read from the resource; wherein the shared locking data store allows writer and reader locking state information to be determined so that access to the resource may be handled; wherein the write requested data has a set status when a write request has been made, wherein the set status indicates whether a mutex lock is to be used for processing access to the resource, wherein the set status is set to indicate that the mutex lock is not to be used if no write request is pending. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A computer-implemented method for handling multiple executable entities'"'"' access to at least one resource, comprising:
-
executing instructions on a computer system for receiving a request from an executable entity to access a resource within the computer system; and executing instructions on the computer system for determining how to process the resource request based upon lock state data that is stored in a computer-readable storage medium; wherein the lock state data comprises write requested data and reader data; wherein the write requested data is indicative of when a write request for the resource has been made with respect to the resource; wherein the reader data is indicative of whether a reader executable entity is active and attempting to read from the resource; wherein the write requested data has a set status when a write request has been made, wherein the set status indicates whether a mutex lock is to be used for processing access to the resource, wherein the set status is set to indicate that the mutex lock is not to be used if no write request is pending; executing instructions on the computer system for accessing the resource based upon said determining of how to process the resource request based upon lock state data.
-
Specification