Kioxia Corporation

F5 Networks, Inc.

Nutanix, Inc.

Juniper Networks, Inc.

Cisco Technology, Inc.

Toshiba Memory Corporation

Intuit, Inc.

Amit Jain

Gyan Prakash

Ashwini Puttaswamy

Karan Gupta

Navindra Yadav

Steven E Wells

Sameer Merchant

Pirabhu Raman

Senthil Thangaraj

Girish Desai

Narasimhulu Dharani Kotte

Mark Carlson

Dennis Zhou

Barada Mishra

Satyam B Vaghani

Saxon Carl Amdahl

Parthasarathy Ramachandran

Ravi Natarajan

Ranjan Parthasarathy

David Holmes

Rajagopalan Sivaramakrishnan

John Robert Hughes

Jie Li

Pavan Kumar Konka

Siva Madasamy

Yong Luo

Akhilesh Joshi

Jeff James Costlow

Bryan Jeffrey Crowe

Suresh Sivaprakasam

Vinod Pisharody

Harry Hai Yang

Kilol Surjan

Paul Michael Digioia

Charles Cano

Satoshi Asami

Timothy E Hobson

Elizabeth C Douglas

Timothy Sujay Isaacs

Sanika Nitin Mokashi

Krishna Ganti

Konstantin Martynenko

Paul Jiang

Hinal Gala

Abhiman Yashpala Karkera

James S Goodwin, Iii

Nigel Tremar Menendez

Young Luo

Aashish Akhouri

Avinash Manjaya Shetty

Yang Xiao

Sanika Mokashi

A platform-as-a-service (PaaS) manager abstracts deployment of PaaS software stacks to different computing platforms such that the PaaS software stacks provide a common platform to host an application despite differences in the underlying architectures of the computing platforms. Each PaaS software stack is hosted on a service domain installed on a respective one of the computing platforms, and includes an operating system and provides access to a set of services for execution of applications. The some examples, the different computing platforms include multiple different cloud architectures.

Platform-as-a-service deployment including service domains

Various implementations described herein relate to systems and methods for enabling a data lane for communicating messages for each of a plurality of regions of a non-volatile memory. Each of the plurality of regions includes a plurality of dies. The messages for each of the plurality of regions are communicated via the data lane.

Independent set data lanes for IOD SSD

In one embodiment, a solid state drive (SSD) comprises a plurality of non-volatile memory dies communicatively arranged in one or more communication channels, each of the plurality of non-volatile memory dies comprising a plurality of physical blocks, one or more channel controllers communicatively coupled to the one or more communication channels, respectively, and a memory controller communicatively coupled to the plurality of non-volatile memory dies via the one or more channel controllers, wherein the memory controller is configured to assign (i) the plurality of physical blocks of a first die of the plurality of non-volatile memory dies to only a first region and (ii) the plurality of physical blocks of a second die of the plurality of non-volatile memory dies to only a second region, perform only read operations on the first region in a first operation mode, and perform write operations or maintenance operations on the second region in a second operation mode concurrently with read operations on the first region in the first operation mode.

SSD architecture supporting low latency operation

A method of operating a Solid State Drive (SSD), comprising identifying critical metadata corresponding to data previously written to the SSD. In response to a power loss event the method also includes storing the critical metadata in a non-volatile memory. Further, the method also involves writing a first table of contents corresponding to the stored critical metadata to the non-volatile memory and storing a pointer to the first table of contents. A Solid State Drive (SSD) including a memory controller, a non-volatile memory, and a power loss protection capacitor. The memory controller is configured to identify critical metadata corresponding to data previously written to the SSD. The memory controller is also configured to, in response to a power loss event, store the critical metadata in a non-volatile memory write a first table of contents corresponding to the stored critical metadata to the non-volatile memory, and store a pointer to the first table of contents.

SSD supporting read-only mode after PLP backup failure

A method performed by a controller of a solid state drive (SSD) comprising receiving from a host a write request to store write data in a nonvolatile semiconductor storage device of the SSD. The method also comprises identifying a first codeword and a second codeword stored in the nonvolatile storage device, the first codeword and the second codeword configured to store write data corresponding to the write request. Responsive to the write request, the method comprises writing a first portion of the write data to the first codeword and writing a second portion of the write data to the second codeword, and sending a message to the host once the write data has been written to the nonvolatile semiconductor storage device. The first and second codewords are adjacently stored, and the write data has a length that is greater than the length of the first and second codewords.

Payload distribution in solid state drives

A solid state drive (SSD) is presented herein that includes a plurality of memory dies communicatively arranged in a plurality of communication channels such that each respective memory die is associated with a respective one communication channel of the plurality of communication channels, each respective memory die comprises one or more die regions, and each of the one or more die regions comprises a plurality of physical blocks configured to store data. The SSD further includes a memory controller communicatively coupled to the plurality of memory dies. The memory controller is configured to, upon a first power up of the SSD, determine a parameter of the SSD and for each of the one or more die regions, associate, based on the parameter, a number of physical blocks of the plurality of physical blocks with a block region of a plurality of block regions.

Systems and methods for implementing a four-dimensional superblock

An improved solid state drive (SSD). The SSD comprising a plurality of non-volatile memory dies, each configured to store at least one block of data associated with one of a plurality of superblocks each containing a plurality of blocks; a volatile memory; and a memory controller. The memory controller configured to store a bit map associated with a first superblock of the plurality of superblocks in the volatile memory, wherein the bit map is configured to indicate whether each of the plurality of blocks is a replacement block, store a block address list in the volatile memory, the block address list is configured to store an address of one or more replacement blocks, and store a replacement block index in the volatile memory associated with the first superblock of the plurality of superblocks, the replacement block index corresponding to the location of an address of a first replacement block of the first superblock in the block address list.

SSD with compressed superblock mapping table

A method performed by a controller of a solid state drive comprising receiving from a host a read request for read data stored in nonvolatile semiconductor storage devices of the solid state drive. The method also comprises identifying a first codeword and a second codeword, the first codeword and the second codeword comprising the read data corresponding to the read request. Responsive to the read request, the method comprises reading a first portion of the read data contained in the first codeword and reading a second portion of the read data contained in the second codeword, assembling the first portion and the second portion as assembled read data, and transferring the assembled read data to the host responsive to the read request. The first and second codewords are adjacently stored, and the assembled read data has a length that is greater than the length of the first and second codewords.

Payload spill boundary table assisted read in solid state drives

Various implementations described herein relate to systems and methods for defining an optimal transfer and processing unit (OTPU) size for communicating messages for a plurality of non-volatile memory (NVM) sets of a non-volatile memory of the SSD. Each of the plurality of NVM sets corresponds to one of a plurality of regions of the non-volatile memory. Each of the plurality of regions includes a plurality of dies.

Transfer and processing unit for IOD SSD

A data storage site receives data from different data producer sites. Each of the data producer sites has a particular relationship to the data storage site, and each particular relationship carries corresponding data storage policies, constraints and commitments. When a data storage site receives a data storage request from a data producer, and that particular data is already present from a prior storage operation at the data storage site, the characteristics of the policies, constraints and commitments that were applied when that data was saved by the prior storage operation are reconciled with the policies, constraints and commitments of the requesting data producer. Deduplication logic reconciles different sets of policies, constraints and commitments such that the data can be effectively deduplicated by saving data-producer-specific metadata. Alternatively, the data can be effectively deduplicated by promoting the storage of the data so it covers a broader set of policies, constraints and commitments.

Policy-based data deduplication

Growing community of inventors

San Jose, CA, United States of America

Amit Jain