Distributed lock manager using a passive, state-full control-server
January 26, 2014. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.Patent ReferencesMethod for managing lock escalation in a multiprocessing, multiprogramming environment Method for lock management, page coherency, and asynchronous writing of changed pages to shared external store in a distributed computing system Information control system for counting lock application against composite information infrastructure Information control system for reserve locking infrastructure nodes for subsequent exclusive and share locking by the system Multilevel locking system and method Synchronizing and processing of memory access operations in multiprocessor systems using a directory of lock bits System for file and record locking between nodes in a distributed data processing environment maintaining one copy of each file lock Multi-processor caches with large granularity exclusivity locking Multiprocessor system includes operating system for notifying only those cache managers who are holders of shared locks on a designated page by global lock manager File lock management in a distributed data processing system InventorsApplicationNo. 187432 filed on 01/26/1994US Classes:718/104, Resource allocation710/200ACCESS LOCKINGExaminersPrimary: Heckler, Thomas M.Attorney, Agent or FirmInternational ClassG06F 015/167AbstractA locking apparatus for a multicomputer system. The lock apparatus is a two level system wherein local lock managers grant locks on a resource only after they have acquired an appropriate token from a rock control server which is the owner of the resource. The lock control server is passive and has all the control information for a resource it owns. When a local lock manager needs a token in a specified mode for a particular resource, it acquires the token from the lock control server. If there are no conflicting tokens, then the rock control server grants the token. However, if there are conflicting tokens, then the lock control server responds with a list of the local lock managers with conflicting tokens. The requesting lock manager then requests each of the local lock managers with conflicting tokens to give it up and to acknowledge when it has done so. When the acknowledgements have been received, the local lock manager requests the lock control server to update its table and grant the requested token.Other References
| |
