Abstract: A storage system configured to mitigate the effect of a long latency tail in solid state drives. The system includes a host and a plurality of solid state drives. The host sets a latency threshold in each solid state drive. Each solid state drive may abort any read command when the execution time exceeds the latency threshold, and the host may then send the same read command to another solid state drive.

Abstract: A storage system configured to mitigate the effect of a long latency tail in solid state drives. The system includes a host and a plurality of solid state drives. The host sets a latency threshold in each solid state drive. Each solid state drive may abort any read command when the execution time exceeds the latency threshold, and the host may then send the same read command to another solid state drive.

Abstract: A storage system configured to mitigate the effect of a long latency tail in solid state drives. The system includes a host and a plurality of solid state drives. The host sets a latency threshold in each solid state drive. Each solid state drive may abort any read command when the execution time exceeds the latency threshold, and the host may then send the same read command to another solid state drive.

Abstract: A data replication system has a chassis including a plurality of eSSDs, a fabrics switch, and a baseboard management controller (BMC). The BMC configures one of the plurality of eSSDs as an active eSSD and one or more of the plurality of eSSDs as one or more passive eSSDs. The fabrics switch of the chassis is programmed to forward packets destined for the active eSSD to both the active eSSD and the one or more passive eSSDs. In response to a host data write command received from the host, the active eSSD stores the host data and sends an address and an instruction corresponding to the host data to the one or more passive eSSDs. Each of the one or more passive eSSDs stores a copy of the host data using the address and the instruction received from the active eSSD and the host data received in the packets forwarded by the fabrics switch.

Abstract: A system and method for managing garbage collection in Solid State Drives (SSDs) in a Redundant Array of Independent Disks (RAID) configuration, using a RAID controller is described. A control logic can control read and write requests for the SSDs in the RAID configuration. A selection logic can select an SSD for garbage collection. Setup logic can instruct the selected SSD to enter a garbage collection setup phase. An execute logic can instruct the selected SSD to enter and exit the garbage collection execute phase.

Abstract: A system and method for distributed erasure coding. A plurality of storage devices is directly connected to one or more host computers, without an intervening central controller distributing data to the storage devices and providing data protection. Parity codes are stored in one or more dedicated storage devices or distributed over a plurality of the storage devices. When a storage device receives a write command, it calculates a partial parity code, and, if the parity code for the data being written is on another storage device, sends the partial parity code to the other storage device, which updates the parity code using the partial parity code.

Abstract: A method includes: preconditioning a reference solid-state drive (SSD) to a steady state by writing to physical media of the reference SSD; transferring metadata of the reference SSD to an application; storing the metadata of the reference SSD in a persistent storage; normalizing the metadata of the reference SSD to a target SSD; and applying the normalized metadata to the target SSD to precondition the target SSD to the steady state.

Abstract: A system and method for distributed erasure coding. A plurality of storage devices is directly connected to one or more host computers, without an intervening central controller distributing data to the storage devices and providing data protection. Parity codes are stored in one or more dedicated storage devices or distributed over a plurality of the storage devices. When a storage device receives a write command, it calculates a partial parity code, and, if the parity code for the data being written is on another storage device, sends the partial parity code to the other storage device, which updates the parity code using the partial parity code.

Abstract: A storage system configured to mitigate the effect of a long latency tail in solid state drives. The system includes a host and a plurality of solid state drives. The host sets a latency threshold in each solid state drive. Each solid state drive may abort any read command when the execution time exceeds the latency threshold, and the host may then send the same read command to another solid state drive.

Abstract: A storage system configured to mitigate the effect of a long latency tail in solid state drives. The system includes a host and a plurality of solid state drives. The host sets a latency threshold in each solid state drive. Each solid state drive may abort any read command when the execution time exceeds the latency threshold, and the host may then send the same read command to another solid state drive.

Abstract: A method for notifying a host to manage background activities in a data storage device is disclosed. The method includes: receiving a query from a host operation system (OS); sending to the host OS, in response to the query, a list of background tasks to be performed in a data storage device; receiving a threshold value for one or more of the background tasks from the host OS; setting a timeout value associated with the threshold value; determining and notifying the timeout value to the host OS; determining that the threshold value is reached for a background task; and notifying the host OS that the SSD may perform the background task in the data storage device after the timeout value expires.

Abstract: A data replication system has a chassis including a plurality of eSSDs, a fabrics switch, and a baseboard management controller (BMC). The BMC configures one of the plurality of eSSDs as an active eSSD and one or more of the plurality of eSSDs as one or more passive eSSDs. The fabrics switch of the chassis is programmed to forward packets destined for the active eSSD to both the active eSSD and the one or more passive eSSDs. In response to a host data write command received from the host, the active eSSD stores the host data and sends an address and an instruction corresponding to the host data to the one or more passive eSSDs. Each of the one or more passive eSSDs stores a copy of the host data using the address and the instruction received from the active eSSD and the host data received in the packets forwarded by the fabrics switch.

Abstract: A storage system configured to mitigate the effect of a long latency tail in solid state drives. The system includes a host and a plurality of solid state drives. The host sets a latency threshold in each solid state drive. Each solid state drive may abort any read command when the execution time exceeds the latency threshold, and the host may then send the same read command to another solid state drive.

Abstract: A method includes: preconditioning a reference solid-state drive (SSD) to a steady state by writing to physical media of the reference SSD; transferring metadata of the reference SSD to an application; storing the metadata of the reference SSD in a persistent storage; normalizing the metadata of the reference SSD to a target SSD; and applying the normalized metadata to the target SSD to precondition the target SSD to the steady state.

Abstract: A system and method for managing garbage collection in Solid State Drives (SSDs) in a Redundant Array of Independent Disks (RAID) configuration, using a RAID controller is described. A control logic can control read and write requests for the SSDs in the RAID configuration. A selection logic can select an SSD for garbage collection. Setup logic can instruct the selected SSD to enter a garbage collection setup phase. An execute logic can instruct the selected SSD to enter and exit the garbage collection execute phase.

Abstract: A system and method for managing garbage collection in Solid State Drives (SSDs) (120-1, 120-2, 120-3, 120-4, 120-5) in a Redundant Array of Independent Disks (RAID) configuration, using a RAID controller (115) is described. A control logic (505) can control read and write requests (805, 810) for the SSDs (120-1, 120-2, 120-3, 120-4, 120-5) in the RAID configuration. A selection logic (515) can select an SSD for garbage collection. Setup logic (520) can instruct the selected SSD to enter a garbage collection setup phase (920). An execute logic (525) can instruct the selected SSD to enter and exit the garbage collection execute phase (925).

Abstract: A method for notifying a host to manage background activities in a data storage device is disclosed. The method includes: receiving a query from a host operation system (OS); sending to the host OS, in response to the query, a list of background tasks to be performed in a data storage device; receiving a threshold value for one or more of the background tasks from the host OS; setting a timeout value associated with the threshold value; determining and notifying the timeout value to the host OS; determining that the threshold value is reached for a background task; and notifying the host OS that the SSD may perform the background task in the data storage device after the timeout value expires.

Abstract: A system and method for managing garbage collection in Solid State Drives (SSDs) (120-1, 120-2, 120-3, 120-4, 120-5) in a Redundant Array of Independent Disks (RAID) configuration, using a RAID controller (115) is described. A control logic (505) can control read and write requests (805, 810) for the SSDs (120-1, 120-2, 120-3, 120-4, 120-5) in the RAID configuration. A selection logic (515) can select an SSD for garbage collection. Setup logic (520) can instruct the selected SSD to enter a garbage collection setup phase (920). An execute logic (525) can instruct the selected SSD to enter and exit the garbage collection execute phase (925).

Abstract: In some embodiments, a non-volatile cache memory may include a segmented non-volatile cache memory configured to be located between a system memory and a mass storage device of an electronic system and a controller coupled to the segmented non-volatile cache memory, wherein the controller is configured to control utilization of the segmented non-volatile cache memory. The segmented non-volatile cache memory may include a file cache segment, the file cache segment to store complete files in accordance with a file cache policy, and a block cache segment, the block cache segment to store one or more blocks of one or more files in accordance with a block cache policy, wherein the block cache policy is different from the file cache policy.

Abstract: In some embodiments, an electronic system may include a cache located between a mass storage and a system memory, and code stored on the electronic system to prevent storage of stream data in the cache and to send the stream data directly between the system memory and the mass storage based on a comparison of first metadata of a first request for first information and pre-boot stream information stored in a previous boot context. Other embodiments are disclosed and claimed.