Seagate Technology Incorporated

Other

Seagate Technologies, Inc.

Ryan James Goss

Mark A Gaertner

Antoine Khoueir

David Scott Seekins

Ara Patapoutian

Kevin Arthur Gomez

David Scott Ebsen

Daniel John Benjamin

Ryan Charles Weidemann

Jon David Trantham

Dana Lynn Simonson

David W Claude

Graham David Ferris

Jonathan M Henze

Nicholas Odin Lien

Michael Joseph Steiner

Bruce Douglas Buch

Stacey Secatch

Thomas V Spencer

Navneeth Kankani

Sumanth Jannyavula Venkata

Kristofer Carlson Conklin

James David Sawin

Jeffrey L Whaley

Timothy Richard Feldman

Jonathan Williams Haines

Luke William Friendshuh

Jay Allen Sheldon

Frank R Dropps

Robert Wayne Moss

Wayne Howard Vinson

Rodney Virgil Bowman

Arvind Sridharan

Matthew B Lovell

Jeffrey John Pream

Jeremy Blair Goolsby

Tong Shirh Stone

Indrajit Zagade

Christopher A Smith

Bruce Dunlop

Charles McJilton

Kris Conklin

Jack Vincent Anderson

Erich Franz Haratsch

Timothy Lawrence Canepa

Steven Scott Williams

Jackson L Ellis

Stephen D Hanna

Zheng Wang

Peng Li

Jeffrey Munsil

Shuhei Tanakamaru

Stephen H Perlmutter

Benjamin J Scott

Siddhartha Kumar Panda

Mehmet Emin Aklik

Yunaldi Yulizar

Reid Alan Welch

A data storage system may store a first data block having a first data configuration generated by a host in a non-volatile memory that is connected to a data module. A data strategy may be generated with the data module in response to the storage of data with the data strategy consisting of at least one trigger associated with identifying the first data block as hot. The first data block can be replicated to a different memory location with a second data configuration as directed by the data strategy with the first data configuration being different than the second data configuration.

Hot data management in a data storage system

Method and apparatus for managing data in a storage device, such as a solid-state drive (SSD). An apparatus includes a main non-volatile memory (NVM) such as a NAND flash memory. A host command queue lists pending data transfer commands to transfer data between the NVM and a host. For each write command received by the NVM to store write data to an associated target location, a controller examines the host command queue. Based on this review, the controller may direct the NVM to read data adjacent the associated target location to which data are to be written by the write command and to transfer the read data to a read cache. The read data may use some or all of the same resources used to store the write data to the NVM. The read data may be subsequently transferred from the read cache to the host.

Pre-suspend before program in a non-volatile memory (NVM)

A data storage system may connect a non-volatile memory to a quarantine module that generates a quarantine strategy in response to a pending data access request to the non-volatile memory. The quarantine strategy can proactively prescribing a plurality of status levels for physical data addresses of the non-volatile memory. A comparison of a volume of errors for the non-volatile memory to a first threshold of the quarantine strategy with the quarantine module may prompt the alteration of a first status level of the plurality of status levels for a first physical data address of the non-volatile memory, as directed by the quarantine strategy.

Data storage system with intelligent error management

A system can log data access activity to a memory array with a metadata module while the memory array is logically divided into multiple namespaces. A workload can be determined for each namespace by the metadata module and a metadata strategy can be created with the metadata module in view of the respective namespace workloads. A first metadata and second metadata may be generated for respective first and second user-generated data for storage into a first namespace of the multiple namespaces. The first metadata can be compressed with a compression level prescribed by the metadata strategy in response to a detected or predicted workload to the first namespace before the first metadata, second metadata, first user-generated data, and second user-generated data are each stored in the first namespace.

Lossless namespace metadata management system

A solid-state memory may have many non-individually erasable memory cells arranged into dies with each die having a first plane and a second plane. Receipt of a single read command from a host connected to the solid-state memory can prompt generation of a first reference voltage and a second reference voltage by the controller to produce asynchronous data retrieval. The reference voltages can be different and selected by the controller to induce a predetermined delay between retrieval of data from the first plane and retrieval of data from the second plane from the single read command. Passage of each reference voltage concurrently to a common single data address of the first plane and the second plane may produce asynchronous retrieval of data from the respective first plane and second plane.

Asynchronous access multi-plane solid-state memory

A solid-state memory may have many non-individually erasable memory cells arranged into calibration groups with each memory cell in each respective calibration group using a common set of read voltages to sense programmed states. An evaluation circuit of the solid-state memory may be configured to measure at least one read parameter for each calibration group responsive to read operations carried out upon the memory cells in the associated calibration group. An adjustment circuit of the solid-state memory may redistribute the memory cells of an existing calibration group into at least one new calibration group in response to the at least one measured read parameter.

Solid-state memory with intelligent cell calibration

Method and apparatus for enhancing performance of a storage device, such as a solid-state drive (SSD). In some embodiments, the storage device monitors a rate at which client I/O access commands are received from a client to transfer data with a non-volatile memory (NVM) of the storage device. A ratio of background access commands to the client I/O access commands is adjusted to maintain completion rates of the client I/O access commands at a predetermined level. The background access commands transfer data internally with the NVM to prepare the storage device to service the client I/O access commands, and can include internal reads and writes to carry out garbage collection and metadata map updates. The ratio may be adjusted by identifying a workload type subjected to the storage device by the client.

Client input/output (I/O) access rate variation compensation

Apparatus and method for managing metadata in a data storage device such as a solid-state drive (SSD). The metadata are stored in combined (combo) pages in a non-volatile memory (NVM) each having first and second level map entries. The second level map entries provide a logical-to-physical address translation layer for user data blocks stored to the NVM, and the first level map entries describe the second level map entries in the combo page. A global map structure is accessed to identify a selected combo page in the NVM associated with a pending access command. The first and second level map entries are retrieved from the combo page, and the second level map entries are used to identify a target location for the transfer of user data blocks to or from the NVM.

Combined page footer for parallel metadata storage

Method and apparatus for managing data in a storage device, such as a solid-state drive (SSD). In some embodiments, a main memory has memory cells arranged on dies arranged as die sets accessible using parallel channels. A controller is configured to arbitrate resources required by access commands to transfer data to or from the main memory using the parallel channels, to monitor an occurrence rate of collisions between commands requiring an overlapping set of the resources, and to adjust a ratio among different types of commands executed by the controller responsive to the occurrence rate of the collisions. In further embodiments, the controller may divide a full command into multiple partial commands, each of which are executed as the associated system resources become available. In some cases, the ratio is established between read commands and write commands issued to the main memory.

Collision reduction through just-in-time resource allocation

Method and apparatus for managing data in a cloud computing environment. In accordance with some embodiments, data updates are received to a multi-tier memory structure across a cloud network and stored as working data in an upper rewritable non-volatile memory tier of the memory structure. The working data are periodically logged to a lower non-volatile memory tier in the memory structure while a current version of the working data remain in the upper memory tier. The upper and lower memory tiers each are formed of rewritable memory cells having different constructions and storage attributes.

Data update management in a cloud computing environment

Method and apparatus for intelligent caching, protection and transfers of data between a cache and a main memory in a data storage environment, such as but not limited to a solid-state drive (SSD). A main memory (MM) has non-volatile memory (NVM) cells configured for persistent storage of user data. A fast response cache (FRC) has NVM cells configured to provide storage of first data prior to transfer to the MM. A write cache (WC) has NVM cells configured to provide storage of second data prior to transfer to the MM. A controller directs input data to either the FRC or the WC. A first type of error correction encoding (ECC1) is applied to the first data and a different, second type of error correction encoding (ECC2) is applied to the second data. Data may be sent from the FRC to the MM either directly or through the WC.

Fast cache with intelligent copyback

Apparatus and method for object storage, such as a solid-state drive (SSD) or array thereof. In some embodiments, data arranged as an object are presented for storage to a non-volatile memory (NVM) of a data storage device. Prior to storage, a configuration of the NVM is adaptively adjusted, such as by adjusting a garbage collection unit (GCU) layout, an error correction code (ECC) scheme, and/or a map metadata format used by the NVM. The object is thereafter stored to the NVM using the adaptively adjusted configuration. A controller of the data storage device generates a predicted remaining storage capacity of the NVM in terms of additional objects that can be stored by the NVM responsive to the adaptively adjusted configuration of the NVM. A non-linear sliding scale may be used such that a greater number of smaller objects or a smaller number of larger objects may be accommodated.

Data storage device with adaptive object storage capabilities

Improving performance in solid state devices (SSDs) by controlling or throttling the depth of the request queue. In one implementation, a method includes monitoring a request queue in a solid state device (an SSD), the request queue comprising a first request and a second request having an actual time interval therebetween, determining a queue depth for the request queue, determining a target interval based on the queue depth and a target queue depth, and responsive to the actual time interval being less than the target interval, delaying acting on the second request until after the target interval.

Controlling SSD performance by queue depth

A data storage system can transfer user-generated data from a data storage device to a host responsive to a host workload that consists of data read requests from the host received at a requested rate. A completion rate of a data read request can be delayed in accordance to a data access uniformity strategy to nominally match the requested rate.

Data storage system with access completion uniformity

Method and apparatus for enhancing performance of a storage device, such as a solid-state drive (SSD). A non-volatile memory (NVM) stores user data from a client device. Map metadata in a local memory describes locations of the user data in the NVM. The map metadata is arranged as a snapshot and accumulated journal updates. A metadata manager circuit combines a first portion of the journal updates with the existing snapshot to generate a new snapshot, and places a second portion of the journal updates into a read-only journal table in accordance with a selected metadata journaling strategy. A controller uses the updated snapshot and the table to service subsequently received client commands. Only dirty entries are processed and are written at the slowest acceptable rate, thereby improving client I/O performance during normal operation and time to ready (TTR) performance of the device during initialization.

Processing map metadata updates to reduce client I/O variability and device time to ready (TTR)

Growing community of inventors

Prior Lake, MN, United States of America

Ryan James Goss