Abstract: A memory controller may control a memory device for storing logical to physical (L2P) mapping information, the memory controller comprising: a map data storage configured to store a plurality of L2P address segments included in the L2P mapping information; and a map data manager configured to: provide at least one L2P address segment of the plurality of L2P address segments to the host in response to a map data request of the host; and remove a L2P address segment from the map data storage, wherein the L2P address segment is selected, among the plurality of L2P address segments, based on a least recently used (LRU) frequency and whether the L2P address segment is provided to the host.

Abstract: An upper system of an NVM device transmits, to the NVM device, a write command that designates a logical address, the write command being associated with an expiration date corresponding to a data expiration date correlated with write target data. The NVM device correlates an expiration date correlated with the write command with a logical address specified from the write command. The NVM device writes pieces of data of which the remaining time which is the time to an expiration date belongs to the same remaining time range to the same physical storage area among the plurality of physical storage areas. The NVM device erases data from a physical storage area when the expiration dates of all pieces of data in the physical storage area have expired.

Abstract: Disclosed in an embodiment of the present invention are a hardware-based flash FTL function realization method and data storage device thereof, wherein the method comprises: when the data storage device is powered on, a state machine identifies the flash chip to acquire the chip information of the flash chip; the state machine establishes a target table according to the chip information; and the state machine realizes the FTL function of the flash controller according to the target table, wherein the FTL function comprises an address mapping function, a bad block management function and a garbage collection function.

Abstract: Example storage systems, storage controllers, and methods provide data redundancy reconfiguration using logical subunits. Storage devices are configured in a storage group with a first data redundancy configuration. A second data redundancy configuration is selected and the space available in the storage group is determined. For each logical data unit, logical data subunits are selected, written to the space available in the second data redundancy configuration, and deleted from the logical data unit. Storage operations using the storage group may be maintained during the migration process.

Abstract: Devices and techniques for host accelerated operations in managed NAND devices are described herein. A controller can receive an operation. Here the operation includes address data with a logical address portion and a physical address portion. The controller can then extract an index value and a location value from the physical address portion. The controller can retrieve a key using the index value and invoke a reversible function—using the index value and the location value—to produce a physical address. The controller can then perform the operation using the physical address.

Abstract: A technique for garbage collection in a storage system includes generating regrouping metadata for one or more pages of at least two logical erase blocks (LEB). The regrouping metadata indicates an associated stream for each of the pages. Multiple of the LEBs that include valid pages associated with a first stream are selected, based on the regrouping metadata, for regrouping. The valid pages associated with the first stream from the selected LEBs are regrouped into a new LEB.

Abstract: The method for preloading data of a file containing the following steps of defining a plurality of bins of predetermined sizes in a file, for each input and/or output operation executed on the file, determining the bin involved in the operation, counting the number of input and/or output operations executed in each bin of the file by taking into account only a predetermined number of last operations on the whole file, and when the sum of the operations counted in a bin is greater than a predetermined threshold, loading, in a memory medium, at least one area of the file determined on the basis of this bin.

Abstract: A non-disruptive cross-protocol live data migration process, such as from a legacy SAN storage network to a modern NVMe-oF storage network, includes maintaining a bitmap to track the transferred blocks at migration time, and utilizing the bitmap for intelligent I/O routing decisions that take into account characteristics of SSD-type NVM storage, such as endurance characteristics associated with solid state type memory. Furthermore, protocol command translations and multipath layer capabilities such as I/O queuing are advantaged at migration time to hide the underlying complexities related to a cross-protocol mass data migration, to enable a non-disruptive data migration process intended to avoid application downtime.

Abstract: A memory system may include a memory device comprising a plurality of memory banks, and a memory controller suitable for allocating data of successive logical addresses to the respective memory banks, and controlling read/write operations of the data, wherein the memory controller groups pages of the respective memory banks, and performs a wear-leveling operation based on the read/write operations of the data on each group of the pages.

Abstract: An example system may comprise a network-attached storage device including a base station having a hardware interface including a drive port and a connectivity port; a modular storage drive attachable to and detachable from the drive port; and a modular wireless adapter attachable to and detachable from the connectivity port. The portable storage device is formable by detaching the modular storage drive and the modular wireless adapter from the hardware interface of the network-attached storage device, and coupling the modular storage drive and the modular wireless adapter to one another via a portable hardware interface. Further, a rechargeable modular power unit is removable from the base station and attachable to and detachable from a power port of the network-attached storage device.

Abstract: A technique manages data in a flash memory drive which includes single-level cell (SLC) flash memory and multi-level cell (MLC) flash memory. The technique involves performing, within the flash memory drive, data placement operations on data which has been written to the flash memory drive. The technique further involves, based on the data placement operations, storing hot data in the SLC flash memory. The technique further involves, based on the data placement operations, storing cold data in the MLC flash memory, the hot data being accessed more frequently than the cold data. Such hot data and cold data can be distinguished based on access frequency.

Abstract: There are provided a memory controller and a memory system having the same. A memory controller includes: a command queue for queuing commands and outputting command information including Information of a previous command and a subsequent command; a command detector for outputting a detection signal according to the command information; and a command generator for generating the command and outputting a management command for managing a last command immediately following the previous command in response to the detection signal.

Abstract: A non-volatile memory (NVM) express (NVMe) system includes at least one user application, an NVMe controller and a hypervisor. Each user application runs in a respective virtual machine environment and including a user input/output (I/O) queue. The NVMe controller is coupled to at least one NVM storage device, and the NVMe controller includes a driver that includes at least one device queue. The hypervisor is coupled to the user I/O queue of each user application and to the NVMe controller, and selectively forces each user I/O queue to empty to a corresponding device queue in the driver of the NVMe controller or enables a private I/O channel between the user I/O queue and a corresponding device queue in the driver of the NVMe controller.

Abstract: Techniques are disclosed for determining ownership of a data segment. The techniques include providing a data segment in a data storage appliance that facilitates multiple references of the data segment by one or more storage entities. The techniques also include maintaining a plurality of counts in connection with the data segment, the plurality of counts comprising (i) a first count representing a sum of first values that identify the respective storage entities associated with each reference of the data segment, (ii) a second count representing a sum of second values that derive from key values of the respective storage entities associated with each reference of the data segment, and (iii) a third count representing a number of references of the data segment by the respective storage entities. The techniques also include determining whether the said storage entity exclusively owns the data segment based on the plurality of counts and a key value of one of the respective storage entities.

Abstract: A memory system includes first, second, third, and fourth nonvolatile memory, a memory controller configured to modulate write data for the first and second memory into a first time slot of a data signal according to an allocation scheme, and modulate write data for the third and fourth memory into a second time slot of the data signal according to the allocation scheme, a first bridge circuit configured according to the allocation scheme to extract first write data from the first time slot, a second bridge circuit configured according to the allocation scheme to extract second write data from the first time slot, a third bridge circuit configured according to the allocation scheme to extract third write data from the second time slot, and a fourth bridge circuit configured according to the allocation scheme to extract fourth write data from the second time slot.

Abstract: An application programming interface (API) is used to migrate, from a specified source LUN to a specified target LUN, at least one specified sub-LUN data chunk, the API functioning as an interface between a storage controller and an owning application.

Abstract: A source code-based specification is implemented for use as an interface between a storage controller and an owning application to migrate a specified size of data from physical storage behind the LUN to a new physical location.

Abstract: An application programming interface (API) is used to migrate, from a specified source LUN to a specified target LUN, at least one specified sub-LUN data chunk, the API functioning as an interface between a storage controller and an owning application.

Abstract: An application programming interface (API), functioning as an interface between a storage controller and an owning application, is used to migrate, from a specified source LUN to a specified target LUN, at least one specified sub-LUN data chunk, the at least one specified sub-LUN data chunk having a predefined chunk size fixed by the storage controller. A specified total migration size is incrementally reduced by each completed migration of the at least one specified sub-LUN data chunk until the total migration size is zero and the migration is completed.

Abstract: A source code-based specification is implemented for use as an interface between a storage controller and an owning application to migrate a specified size of data from physical storage behind the LUN to a new physical location.