Shared data management scheme using shared data locks for multi-threading
September 13, 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 ReferencesReal time, concurrent garbage collection system and method System and method for controlling a highly parallel multiprocessor using an anarchy based scheduler for parallel execution thread scheduling Dual level scheduling of processes to multiple parallel regions of a multi-threaded program on a tightly coupled multiprocessor computer system Opportunistic task threading in a shared-memory, multi-processor computer system Method and apparatus for sharing a common routine stored in a single virtual machine with other virtual machines operating in a preemptive muli-tasking computer system Data processing system with synchronization coprocessor for multiple threads System for scheduling programming units to a resource based on status variables indicating a lock or lock-wait state thereof Patent #: 5524247 InventorApplicationNo. 305354 filed on 09/13/1994US Classes:711/150, Simultaneous access regulation707/8, Concurrency (e.g., lock management in shared database)710/200, ACCESS LOCKING711/151, Prioritized access regulation711/202, Address mapping (e.g., conversion, translation)718/104Resource allocationExaminersPrimary: Black, Thomas G.Assistant: Homere, Jean R. Attorney, Agent or FirmForeign Patent References
International ClassG06F 012/00Foreign Application Priority Data1993-09-13 JPAbstractA shared data management scheme capable of manipulating the shared data by the multi-threading without requiring the explicit programming of the lock in the program. In this scheme, different shared data identifiers are assigned to different threads, and different locks are set up for different shared data identifiers, so as to enable the detection of an access in violation to the locks among the accesses to the shared data for each thread separately. Preferably, the shared data required in an execution of each thread are mapped to a region exclusively allocated to each thread in a virtual space, in units of pages, a page protection of a memory management unit is set up with respect to each page mapping the shared data, and a lock for the shared data mapped to each page is automatically set up in response to an occurrence of an exception due to the page protection of the memory management unit caused by an access to the shared data mapped to each page from each thread.Other References
| |
