A controller controls an operation of a semiconductor memory device. The controller includes a request analyzer, a storage, and a garbage collection controller. The request analyzer generates invalid data information, based on an erase request received from a host. The storage stores a garbage collection reference table representing memory blocks excluded from selection as a victim block on which a garbage collection operation is to be performed, based on the invalid data information. The garbage collection controller controls the garbage collection operation on the semiconductor memory device, based on exclusion block information generated according to the garbage collection reference table.

Various embodiments discussed herein enable intelligent resource leak detection and associated user interface. In some aspects, if a kernel sends a tracing event (e.g., an ETW event) after a process or application has been requested to be shut down but before the process has actually been shut down, a resource leak can be detected. This is because the application should have requested the reference indicator to be removed in memory before the tracing event, as opposed to the kernel acting alone without an application request to remove the reference indicator. If a reference indicator has not been requested to be removed by the time this tracing event occurs, then it is indicative of the application never having sent a request to remove the reference indicator, which is indicative of a resource leak.

Managing secondary objects efficiently increases garbage collection concurrency and reduces object storage requirements. Aliveness marking of secondary objects is integrated with aliveness marking of referenced objects. Allocation of reference-sized secondary object identifier fields in objects which are not primary objects is avoided; a dedicated bit specifies primary objects, together with an object relationship table. A primary object is one with at least one secondary object which is deemed alive by garbage collection if the primary object is alive, without being a referenced object of the primary object. Any referenced objects of the alive primary object will also still be deemed alive. Code paths for marking referenced objects can be shared to allow more efficient secondary object marking. Primary-secondary object relationships may be represented in dependent handles, and may be specified in a hash table or other data structure.

Methods, systems, and media for supporting snapshots and clones in a scale out storage system are disclosed. The system maintains first metadata that maps logical addresses of logical data blocks to corresponding content IDs, a distributed hash table that maps content IDs to corresponding node IDs, and second metadata that maps content IDs to corresponding physical addresses of physical data blocks. Clones are created by mapping each logical block address of each clone to the content ID associated with its corresponding logical block address of the original and incrementing the reference counts in the second metadata. The task of incrementing reference counts in the second metadata can be distributed across multiple storage nodes. A logical device can be designated as a golden image. Clones of a golden image are created by decrementing its clone credit without incrementing the reference counts in the second metadata.

Described are methods, systems and computer readable media for GUI control elements and associated processing methods.

An operation method of a controller, comprising: selecting a target super block, on which garbage collection (GC) is to be performed, among a plurality of super blocks which are completely programmed, based on a first valid page count of each of the super blocks when a determination to perform GC is made; selecting a first target block among a plurality of memory blocks in the target super block based on a second valid-page decrease amount of each of the memory blocks; and performing a first copy operation on valid pages in the first target block.

Parallel mark processing is disclosed including traversing first objects in a virtual machine heap based on correspondences between memory blocks in the virtual machine heap and N marking threads, pushing a first pointer of a first object into a private stack of a marking thread corresponding to a memory block, the first object being located in the memory block, performing first mark processing of the first object based on a push-in condition of the first pointer, and after traversal of the first objects has been completed, launching the N marking threads to cause the N marking threads to synchronously perform mark processing used in garbage collection based on push-in conditions of first pointers in respective private stacks of the first pointers.

A process for reducing amount of transmission of data to/from an external storage is performed in a computer. The process includes: storing a plurality of data sets by deduplicating a plurality in the external storage, wherein two or more data sets selected in order generated are collected in an object; determining necessity/unnecessity of defragmentation in units of object group in which two or more objects are collected in order generated; when determining to execute defragmentation, executing first defragmentation processing of acquiring all of the objects included in the object group as first objects from the external storage, combining valid data set having a number of references of 1 or more included in the first objects based on the order generated and the number of references to regenerate one or more second object, and storing the second object in place of the first objects in the external storage.

Technical solutions are described to implement a scalable write ahead log using a distributed file system. A general aspect includes a method for providing consistency among metadata replicas and content in an enterprise content management cluster. The method includes recording a transaction log entry in response to receiving a content modification request, the transaction log entry including a version identifier set to a first version value. The method also includes updating the transaction log entry to a second version value in response to successfully modifying content and one of a plurality of metadata replicas containing metadata corresponding to the request. The method also includes updating the transaction log entry to a third version value in response to successfully modifying each of the metadata replicas. The present document further describes examples of other aspects such as methods, computer products.

Described are methods, systems and computer readable media for dynamic updating of query result displays.