Class / Patent application number | Description | Number of patent applications / Date published |
707818000 | Copying | 11 |
20100049776 | FAT DIRECTORY STRUCTURE FOR USE IN TRANSACTION SAFE FILE - Directories in a file system are defined with a dummy cluster in a file allocation table as the initial entry. Subsequent clusters in a directory's definition may define any data for the directory that can be changed in a transaction-safe mode. A directory may be modified in a transaction-safe mode by modifying any of the subsequent clusters while tracking changes in a second file allocation table. When the changes have been made to the directory, a pointer to the second file allocation table may be switched to indicate that the second file allocation table is now last known good. The first file allocation table may then be synchronized with the second. | 02-25-2010 |
20100106753 | CYCLIC COMMIT TRANSACTION PROTOCOL - A cyclic commit protocol is used to store relationships between transactions and is used by the technology to determine whether a transaction is committed or not. The protocol allows creation of a cycle of transactions which can be used to recover the state of a storage device after a host failure by identifying the last committed version of intention records as committed or uncommitted based on the data stored in the physical pages. | 04-29-2010 |
20100115000 | Journaling Database Changes Using a Bit Map for Zones Defined in Each Page - The disclosure and claims herein are directed to efficient journaling for recovery of a database index by journaling zones of a page. A journal mechanism maintains a page zone bit map that includes a bit for a plurality of zones in each page to indicate which zones have had their unchanged image journaled before being changed since a last sync point update. The page zone bit map has a bit for each zone in each page so that the status of each zone can be tracked separately. Tracking the smaller zones of the pages makes the process more efficient both at run time and during recovery by reducing the period of time for memory deposits and reducing the amount of total redundant/recovery data sent to disk for larger pages. | 05-06-2010 |
20100179971 | Concurrent, Lock-Free Object Copying - Described is a technology by which a real-time data relocating mechanism is provided for multiprocessing environments, including supporting lock-free programs that run in parallel. The relocating mechanism moves an object by using a status field related to the data field, possibly in an interim (wide) object space, which is then copied to a to-space object. The status information for each data field of the original object contains information indicating where a current version of the data for each field is present, that is, in the original, wide or to-space object. In one example, a handshake mechanism of a garbage collector establishes preparation and copy phases between the mechanism and other threads that determine where memory accesses occur. Also described is support for program thread compare-and-swap (CAS) operations and/or multi-word atomic operations. | 07-15-2010 |
20110137962 | Applying Limited-Size Hardware Transactional Memory To Arbitrarily Large Data Structure - A technique for applying hardware transaction memory to an arbitrarily large data structure is disclosed. A data updater traverses the data structure to locate an update point using a lockless synchronization technique that synchronizes the data updater with other updaters that may be concurrently updating the data structure. At the update point, the updater performs an update on the data structure using a hardware transactional memory transaction that operates at the update point. | 06-09-2011 |
20110252075 | Monitoring writes using thread-local write barrier buffers and soft synchronization - During garbage collection, writes to objects being copied (relocated) are monitored (tracked) using a write barrier that uses a thread-local write barrier buffer. In the preferred embodiment, soft synchronization is used for reading the thread-local write barrier buffers. In response to detecting a write to an object, the object may be re-copied, the copying may be made to fail, the write may be propagated to another copy of the object, or, e.g., another node in a distributed system may be notified of the write. | 10-13-2011 |
20110264712 | Copy planning in a concurrent garbage collector - A garbage collector is disclosed that permits extensive separation of mutators and the garbage collector from a synchronization perspective. This relative decoupling of mutator and collector operation allows the garbage collector to perform relatively time-intensive operations during garbage collection without substantially slowing down mutators. The present invention makes use of this flexibility by first conservatively determining which objects in a set of regions of interest are live, then planning where to copy the objects (preferably including clustering), and finally performing the actual copying. | 10-27-2011 |
20110264713 | Garbage collector with concurrent flipping without read barrier and without verifying copying - In an object-relocating garbage collector, objects are copied and new copies taken into use concurrently with mutator execution without needing to use a read barrier, and importantly, without requiring verification (read-back) of each copied word and without requiring atomic instructions for the copying. Write barriers, thread-local write barrier buffers and processing them by the garbage collector, and write propagation are used for achieving this. | 10-27-2011 |
20110289125 | METHOD FOR INCREMENTAL ANTI-TEAR GARBAGE COLLECTION - Persistent memory in an integrated circuit cars (ICC) must be managed in such a way that removal of power from the device at any moment does not leave the data stored in this memory in a faulty or inconsistent state. The mechanisms of this disclosure accomplish this end using the tag-length-value data structures found extensively in ICC software and standards. | 11-24-2011 |
20120254266 | NUMA-AWARE GARBAGE COLLECTION - Methods and systems for garbage collection are described. In some embodiments, Garbage collector threads may maximize local accesses and minimize remote access by copying Young objects and Old objects differently. When copying a Young object, a garbage collector thread may determine the lgroup of the pool that contains the object and copy the object to a pool of the same lgroup. The garbage collector thread may spread Old objects among lgroups by copying Old objects to pools of the same lgroup as the respective garbage collector thread. Additional methods and systems are disclosed. | 10-04-2012 |
20120254267 | NUMA-AWARE GARBAGE COLLECTION - System and Methods for non-uniform memory (NUMA) garbage collection are provided. Multiple memories and processors are categorized into local groups. A heap space is divided into multiple pools and stored in each of the memories. Garbage collection threads are assigned to each of the local groups. Garbage collection is performed using the garbage collection threads for objects contained in the pools using the garbage collector threads, memory, and processor assigned to each local group, minimizing remote memory accesses. | 10-04-2012 |