Patent Grant
8380915
This application claims priority to U.S. patent application Ser. No. 13/015,458 entitled “APPARATUS, SYSTEM, AND METHOD FOR DETERMINING A READ VOLTAGE THRESHOLD” and filed on Jan. 27, 2011 for John Strasser, et al. and U.S. patent application Ser. No. 13/175,637 entitled “APPARATUS, SYSTEM, AND METHOD FOR USING MULTI-LEVEL CELL STORAGE IN A SINGLE-LEVEL CELL MODE” and filed on Jul. 1, 2011 for Robert Wood, et al., both of which are incorporated herein by reference. U.S. patent application Ser. No. 13/015,458 claims priority to U.S. Provisional Patent Application No. 61/298,861 entitled “APPARATUS, SYSTEM, AND METHOD FOR DETERMINING A READ VOLTAGE THRESHOLD FOR SOLID-STATE STORAGE MEDIA” and filed on Jan. 27, 2010 for John Strasser, et al. and to U.S. Provisional Patent Application No. 61/305,205 entitled “APPARATUS, SYSTEM, AND METHOD FOR DETERMINING A READ VOLTAGE THRESHOLD FOR SOLID-STATE STORAGE MEDIA” and filed on Feb. 17, 2010 for John Strasser, et al., both of which are incorporated herein by reference.
1. Field
The subject matter disclosed herein relates to solid-state storage media and more particularly relates to configuration parameters for solid-state storage media.
2. Description of the Related Art
Many solid-state storage devices distinguish between different binary values that a storage cell may store based on a read voltage level of the storage cell, based on a resistivity of the storage cell, or based on another configuration parameter of the storage cell. Solid-state storage devices may use one or more read voltage thresholds, resistivity thresholds, or the like to separate discrete values that may be stored in a storage cell.
Thresholds or other configuration parameters for a storage cell, however, can shift over time. For example, storage cell damage, storage cell leakage, temperature, and other disturbances to storage cells can alter thresholds for storage cells, making different configuration parameters more optimal for the storage cells. The rate of leakage and other disturbances can also increase with age as storage cells are used over time. If the read voltage level or other configuration parameter of a storage cell shifts past a threshold for the storage cell, a data error occurs, as the value of the data read from the storage cell is different than the value of the data written to the storage cell.
From the foregoing discussion, it should be apparent that a need exists for an apparatus, system, and method that improve the utility of solid-state storage media. Beneficially, such an apparatus, system, and method would improve the utility of solid-state storage media by determining one or more configuration parameters for the solid-state storage media to optimize the configuration parameters.
A method of the present invention is presented to manage solid-state storage media. In one embodiment, the method includes referencing one or more storage media characteristics for a set of storage cells of solid-state storage media. The method, in a further embodiment, includes determining a configuration parameter for the set of storage cells based on the one or more storage media characteristics. In another embodiment, the method includes configuring the set of storage cells to use the determined configuration parameter.
An apparatus to manage solid-state storage media is provided with a plurality of modules configured to functionally execute the necessary steps of improving the utility of solid-state storage media. These modules in the described embodiments include a media characteristic module, a configuration parameter module, a storage cell configuration module, a characteristic update module, and a configuration update module.
In one embodiment, the media characteristic module references one or more storage media characteristics for a set of storage cells of solid-state storage media. The configuration parameter module, in one embodiment, determines a configuration parameter for the set of storage cells based on the one or more storage media characteristics. In another embodiment, the storage cell configuration module configures the set of storage cells to use the determined configuration parameter.
A system of the present invention is also presented to manage solid-state storage media. The system may be embodied by a solid-state storage device including solid-state storage media. The system, in certain embodiments, includes a media characteristic module, a configuration parameter module, and a storage cell configuration module.
In one embodiment, the media characteristic module references one or more storage media characteristics for a set of storage cells of the solid-state storage media. The configuration parameter module, in a further embodiment, determines a configuration parameter for the set of storage cells based on the one or more storage media characteristics. In one embodiment, the storage cell configuration module configures the set of storage cells to use the determined configuration parameter.
References throughout this specification to features, advantages, or similar language do not imply that all of the features and advantages may be realized in any single embodiment. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic is included in at least one embodiment. Thus, discussion of the features and advantages, and similar language, throughout this specification may, but do not necessarily, refer to the same embodiment.
Furthermore, the described features, advantages, and characteristics of the embodiments may be combined in any suitable manner. One skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments.
These features and advantages of the embodiments will become more fully apparent from the following description and appended claims, or may be learned by the practice of embodiments as set forth hereinafter.
In order that the advantages of the invention will be readily understood, a more particular description of the invention will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable media.
Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
Reference to a computer readable medium may take any form capable of storing machine-readable instructions on a digital processing apparatus memory device. A computer readable medium may be embodied by a compact disk, digital-video disk, a magnetic tape, a Bernoulli drive, a magnetic disk, a punch card, flash memory, integrated circuits, or other digital processing apparatus memory device.
Furthermore, the described features, structures, or characteristics of the invention may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
The schematic flow chart diagrams included herein are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of one embodiment of the presented method. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the format and symbols employed are provided to explain the logical steps of the method and are understood not to limit the scope of the method. Although various arrow types and line types may be employed in the flow chart diagrams, they are understood not to limit the scope of the corresponding method. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the method. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.
Solid-State Storage System
The system 100 includes at least one solid-state storage device 102. In other embodiments, the system 100 includes two or more solid-state storage devices 102. Each solid-state storage device 102 may include non-volatile, solid-state storage media 110, such as flash memory, nano random access memory (“nano RAM or NRAM”), magneto-resistive RAM (“MRAM”), dynamic RAM (“DRAM”), phase change RAM (“PRAM”), racetrack memory, memristor memory, nanocrystal wire-based memory, silicon-oxide based sub-10 nanometer process memory, graphene memory, silicon-oxide-nitride-oxide-silicon (“SONOS”) memory, resistive random-access memory (“RRAM”), programmable metallization cell (“PMC”), conductive-bridging RAM (“CBRAM”), or the like. The solid-state storage device 102 is described in more detail with respect to
The solid-state storage device 102 is depicted in a computer 112 connected to one or more clients 114 through a computer network 116. In one embodiment, the solid-state storage device 102 is internal to the computer 112 and is connected using a system communications bus, such as a peripheral component interconnect express (“PCI-e”) bus, a Serial Advanced Technology Attachment (“serial ATA”) bus, or the like. In another embodiment, the solid-state storage device 102 is external to the computer 112 and is connected using an external communications bus, such as a universal serial bus (“USB”) connection, an Institute of Electrical and Electronics Engineers (“IEEE”) 1394 bus (“FireWire”), or the like. In other embodiments, the solid-state storage device 102 is connected to the computer 112 using a communications bus such as a peripheral component interconnect (“PCI”) express bus using external electrical or optical bus extension or bus networking solution such as Infiniband or PCI Express Advanced Switching (“PCIe-AS”), or the like.
In various embodiments, the solid-state storage device 102 may be in the form of a dual-inline memory module (“DIMM”), a daughter card, or a micro-module. In another embodiment, the solid-state storage device 102 is an element within a rack-mounted blade. In another embodiment, the solid-state storage device 102 is contained within a package that is integrated directly onto a higher level assembly (e.g. mother board, lap top, graphics processor). In another embodiment, individual components comprising the solid-state storage device 102 are integrated directly onto a higher level assembly without intermediate packaging.
The solid-state storage device 102 includes one or more solid-state storage controllers 104, each may include a write data pipeline 106 and a read data pipeline 108, and each includes solid-state storage media 110, which are described in more detail below with respect to
As used herein, a configuration parameter for a set of storage cells is a parameter that is modifiable by way of an interface. The interface may comprise a publicly known interface or a proprietary interface and may include use of particular command instructions and/or use of particular parameters, register settings, driver settings, controller settings, a particular set of command instruction sequences, or other differences from regular commands (general purpose commands) or settings used to interface with or manage the set of storage cells. Configuration parameters may relate to writing to, or programming, storage cells, reading from storage cells, erasing storage cells, managing storage cells, device driver or storage controller settings for storage cells, or the like. A configuration parameter for a set of storage cells may be associated with a device driver for the solid-state storage device 102, with a solid-state storage controller 104, or the like, and may relate to how the device driver and/or solid-state storage controller 104 use, manage, and interact with the set of storage cells and/or the solid-state storage media 110.
A configuration parameter, in certain embodiments, may include one or more thresholds, such as a read voltage threshold, a resistivity threshold, a programming threshold, an erase threshold, a hardware driver level threshold, a storage controller level threshold, or the like. The configuration parameter may be set once during initialization of the solid-state storage media 110, dynamically with each command issued to the solid-state storage media 110, or during operation of the solid-state storage media 110 in response to triggers such as events or time intervals. The solid-state storage controller 104, in one embodiment, proactively sets one or more configuration parameters for storage cells of the solid-state storage media 110 to improve the utility of the solid-state storage media 110, to reduce errors, and the like.
The system 100 includes one or more computers 112 connected to the solid-state storage device 102. A computer 112 may be a host, a server, a storage controller of a storage area network (“SAN”), a workstation, a personal computer, a laptop computer, a handheld computer, a supercomputer, a computer cluster, a network switch, a router or appliance, a database or storage appliance, a data acquisition or data capture system, a diagnostic system, a test system, a robot, a portable electronic device, a wireless device, or the like. In another embodiment, a computer 112 may be a client and the solid-state storage device 102 operates autonomously to service data requests sent from the computer 112. In this embodiment, the computer 112 and solid-state storage device 102 may be connected using a computer network, system bus, or other communication means suitable for connection between a computer 112 and an autonomous solid-state storage device 102.
In one embodiment, the system 100 includes one or more clients 114 connected to one or more computers 112 through one or more computer networks 116. A client 114 may be a host, a server, a storage controller of a SAN, a workstation, a personal computer, a laptop computer, a handheld computer, a supercomputer, a computer cluster, a network switch, a router or appliance, a database or storage appliance, a data acquisition or data capture system, a diagnostic system, a test system, a robot, a portable electronic device, a wireless device, or the like. The computer network 116 may include the Internet, a wide area network (“WAN”), a metropolitan area network (“MAN”), a local area network (“LAN”), a token ring, a wireless network, a fiber channel network, a SAN, network attached storage (“NAS”), ESCON, or the like, or any combination of networks. The computer network 116 may also include a network from the IEEE 802 family of network technologies, such Ethernet, token ring, WiFi, WiMax, and the like.
The computer network 116 may include servers, switches, routers, cabling, radios, and other equipment used to facilitate networking computers 112 and clients 114. In one embodiment, the system 100 includes multiple computers 112 that communicate as peers over a computer network 116. In another embodiment, the system 100 includes multiple solid-state storage devices 102 that communicate as peers over a computer network 116. One of skill in the art will recognize other computer networks 116 comprising one or more computer networks 116 and related equipment with single or redundant connection between one or more clients 114 or other computer with one or more solid-state storage devices 102 or one or more solid-state storage devices 102 connected to one or more computers 112. In one embodiment, the system 100 includes two or more solid-state storage devices 102 connected through the computer network 116 to a client 114 without a computer 112. The solid-state storage controller 104, in certain embodiments, receives source data for storage in the solid-state storage media 110 from a processor of the computer 112 and/or from a client 114 over one or more communications buses as described above.
Solid-State Storage Device
In one embodiment, at least one solid-state controller 104 includes a field-programmable gate array (“FPGA”) and controller functions are programmed into the FPGA. In a particular embodiment, the FPGA is a Xilinx® FPGA. In another embodiment, the solid-state storage controller 104 comprises components specifically designed as a solid-state storage controller 104, such as an application-specific integrated circuit (“ASIC”) or custom logic solution. Each solid-state storage controller 104 typically includes a write data pipeline 106 and a read data pipeline 108, which are describe further in relation to
Solid-State Storage
The solid-state storage media 110 is an array of non-volatile solid-state storage elements 216, 218, 220, arranged in banks 214, and accessed in parallel through a bi-directional storage input/output (“I/O”) bus 210. The storage I/O bus 210, in one embodiment, is capable of unidirectional communication at any one time. For example, when data is being written to the solid-state storage media 110, data cannot be read from the solid-state storage media 110. In another embodiment, data can flow both directions simultaneously. However bi-directional, as used herein with respect to a data bus, refers to a data pathway that can have data flowing in only one direction at a time, but when data flowing one direction on the bi-directional data bus is stopped, data can flow in the opposite direction on the bi-directional data bus.
A solid-state storage element (e.g. SSS 0.0216a) is typically configured as a chip (a package of one or more dies) or a die on a circuit board. As depicted, a solid-state storage element (e.g. 216a) operates independently or semi-independently of other solid-state storage elements (e.g. 218a) even if these several elements are packaged together in a chip package, a stack of chip packages, or some other package element. As depicted, a row of solid-state storage elements 216a, 216b, 216m is designated as a bank 214. As depicted, there may be “n” banks 214a-n and “m” solid-state storage elements 216a-m, 218a-m, 220a-m per bank in an array of n×m solid-state storage elements 216, 218, 220 in a solid-state storage media 110. Of course different embodiments may include different values for n and m. In one embodiment, the solid-state storage media 110a includes twenty solid-state storage elements 216, 218, 220 per bank 214 with eight banks 214. In one embodiment, the solid-state storage media 110a includes twenty four solid-state storage elements 216, 218, 220 per bank 214 with eight banks 214. In addition to the n×m storage elements 216, 218, 220, one or more additional columns (P) may also be addressed and operated in parallel with other solid-state storage elements 216a, 216b, 216m for one or more rows. The added P columns in one embodiment, store parity data for the portions of an ECC chunk (i.e. an ECC codeword) that span m storage elements for a particular bank. In one embodiment, each solid-state storage element 216, 218, 220 is comprised of single-level cell (“SLC”) devices. In another embodiment, each solid-state storage element 216, 218, 220 is comprised of multi-level cell (“MLC”) devices.
In one embodiment, solid-state storage elements that share a common storage I/O bus 210a (e.g. 216b, 218b, 220b) are packaged together. In one embodiment, a solid-state storage element 216, 218, 220 may have one or more dies per chip with one or more chips stacked vertically and each die may be accessed independently. In another embodiment, a solid-state storage element (e.g. SSS 0.0216a) may have one or more virtual dies per die and one or more dies per chip and one or more chips stacked vertically and each virtual die may be accessed independently. In another embodiment, a solid-state storage element SSS 0.0216a may have one or more virtual dies per die and one or more dies per chip with some or all of the one or more dies stacked vertically and each virtual die may be accessed independently.
In one embodiment, two dies are stacked vertically with four stacks per group to form eight storage elements (e.g. SSS 0.0-SSS 8.0) 216a-220a, each in a separate bank 214a-n. In another embodiment, 24 storage elements (e.g. SSS 0.0-SSS 0.24) 216 form a logical bank 214a so that each of the eight logical banks has 24 storage elements (e.g. SSS 0.0-SSS 8.24) 216, 218, 220. Data is sent to the solid-state storage media 110 over the storage I/O bus 210 to all storage elements of a particular group of storage elements (SSS 0.0-SSS 8.0) 216a, 218a, 220a. The storage control bus 212a is used to select a particular bank (e.g. Bank 0214a) so that the data received over the storage I/O bus 210 connected to all banks 214 is written just to the selected bank 214a.
In certain embodiments, the storage control bus 212 and storage I/O bus 210 are used together by the solid-state controller 104 to communicate addressing information, storage element command information, and data to be stored. Those of skill in the art recognize that this address, data, and command information may be communicated using one or the other of these buses 212, 210, or using separate buses for each type of control information. In one embodiment, addressing information, storage element command information, and storage data travel on the storage I/O bus 210 and the storage control bus 212 carries signals for activating a bank as well as identifying whether the data on the storage I/O bus 210 lines constitute addressing information, storage element command information, or storage data.
For example, a control signal on the storage control bus 212 such as “command enable” may indicate that the data on the storage I/O bus 210 lines is a storage element command such as program, erase, reset, read, and the like. A control signal on the storage control bus 212 such as “address enable” may indicate that the data on the storage I/O bus 210 lines is addressing information such as erase block identifier, page identifier, and optionally offset within the page within a particular storage element. Finally, an absence of a control signal on the storage control bus 212 for both “command enable” and “address enable” may indicate that the data on the storage I/O bus 210 lines is storage data that is to be stored on the storage element at a previously addressed erase block, physical page, and optionally offset within the page of a particular storage element.
In one embodiment, the storage I/O bus 210 is comprised of one or more independent I/O buses (“IIOBa-m” comprising 210a.a-m, 210n.a-m) wherein the solid-state storage elements within each column share one of the independent I/O buses that accesses each solid-state storage element 216, 218, 220 in parallel so that all banks 214 are accessed simultaneously. For example, one channel of the storage I/O bus 210 may access a first solid-state storage element 216a, 218a, 220a of each bank 214a-n simultaneously. A second channel of the storage I/O bus 210 may access a second solid-state storage element 216b, 218b, 220b of each bank 214a-n simultaneously. Each row of solid-state storage element 216a, 216b, 216m is accessed simultaneously. In one embodiment, where solid-state storage elements 216, 218, 220 are multi-level (physically stacked), all physical levels of the solid-state storage elements 216, 218, 220 are accessed simultaneously. As used herein, “simultaneously” also includes near simultaneous access where devices are accessed at slightly different intervals to avoid switching noise. Simultaneously is used in this context to be distinguished from a sequential or serial access wherein commands and/or data are sent individually one after the other.
Typically, banks 214a-n are independently selected using the storage control bus 212. In one embodiment, a bank 214 is selected using a chip enable or chip select. Where both chip select and chip enable are available, the storage control bus 212 may select one level of a multi-level solid-state storage element 216, 218, 220. In other embodiments, other commands are used by the storage control bus 212 to individually select one level of a multi-level solid-state storage element 216, 218, 220. Solid-state storage elements 216, 218, 220 may also be selected through a combination of control and of address information transmitted on storage I/O bus 210 and the storage control bus 212.
In one embodiment, each solid-state storage element 216, 218, 220 is partitioned into erase blocks and each erase block is partitioned into pages. An erase block on a solid-state storage element 216, 218220 may be called a physical erase block or “PEB.” A typical page is 2000 bytes (“2 kB”). In one example, a solid-state storage element (e.g. SSS 0.0) includes two registers and can program two pages so that a two-register solid-state storage element 216, 218, 220 has a capacity of 4 kB. A bank 214 of 20 solid-state storage elements 216a, 216b, 216m would then have an 80 kB capacity of pages accessed with the same address going out the channels of the storage I/O bus 210.
This group of pages in a bank 214 of solid-state storage elements 216a, 216b, 216m of 80 kB may be called a logical page or virtual page. Similarly, an erase block of each storage element 216a-m of a bank 214a may be grouped to form a logical erase block or a virtual erase block. In one embodiment, an erase block of pages within a solid-state storage element 216, 218, 220 is erased when an erase command is received within a solid-state storage element 216, 218, 220. Whereas the size and number of erase blocks, pages, planes, or other logical and physical divisions within a solid-state storage element 216, 218, 220 are expected to change over time with advancements in technology, it is to be expected that many embodiments consistent with new configurations are possible and are consistent with the general description herein.
Typically, when a packet is written to a particular location within a solid-state storage element 216, 218, 220, wherein the packet is intended to be written to a location within a particular page which is specific to a particular physical erase block of a particular storage element of a particular bank, a physical address is sent on the storage I/O bus 210 and followed by the packet. The physical address contains enough information for the solid-state storage element 216, 218, 220 to direct the packet to the designated location within the page. Since all storage elements in a column of storage elements (e.g. SSS 0.0-SSS N.0216a, 218a, 220a) are accessed simultaneously by the appropriate bus within the storage I/O bus 210a.a, to reach the proper page and to avoid writing the data packet to similarly addressed pages in the column of storage elements (SSS 0.0-SSS N.0216a, 218a, 220a), the bank 214a that includes the solid-state storage element SSS 0.0216a with the correct page where the data packet is to be written is simultaneously selected by the storage control bus 212.
Similarly, satisfying a read command on the storage I/O bus 210 requires a simultaneous signal on the storage control bus 212 to select a single bank 214a and the appropriate page within that bank 214a. In one embodiment, a read command reads an entire page, and because there are multiple solid-state storage elements 216a, 216b, 216m in parallel in a bank 214, an entire logical page is read with a read command. However, the read command may be broken into subcommands, as will be explained below with respect to bank interleave. A logical page may also be accessed in a write operation.
An erase block erase command may be sent out to erase an erase block over the storage I/O bus 210 with a particular erase block address to erase a particular erase block. Typically, an erase block erase command may be sent over the parallel paths of the storage I/O bus 210 to erase a logical erase block, each with a particular erase block address to erase a particular erase block. Simultaneously a particular bank (e.g. Bank 0214a) is selected over the storage control bus 212 to prevent erasure of similarly addressed erase blocks in all of the banks (Banks 1-N 214b-n). Alternatively, no particular bank (e.g. Bank 0214a) is selected over the storage control bus 212 to enable erasure of similarly addressed erase blocks in all of the banks (Banks 1-N 214b-n) simultaneously. Other commands may also be sent to a particular location using a combination of the storage I/O bus 210 and the storage control bus 212. One of skill in the art will recognize other ways to select a particular storage location using the bi-directional storage I/O bus 210 and the storage control bus 212.
In one embodiment, packets are written sequentially to the solid-state storage media 110. For example, packets are streamed to the storage write buffers of a bank 214a of storage elements 216 and when the buffers are full, the packets are programmed to a designated logical page. Packets then refill the storage write buffers and, when full, the packets are written to the next logical page. The next logical page may be in the same bank 214a or another bank (e.g. 214b). This process continues, logical page after logical page, typically until a logical erase block (“LEB”) is filled. In another embodiment, the streaming may continue across logical erase block boundaries with the process continuing, logical erase block after logical erase block.
In a read, modify, write operation, data packets associated with requested data are located and read in a read operation. Data segments of the modified requested data that have been modified are not written to the location from which they are read. Instead, the modified data segments are again converted to data packets and then written sequentially to the next available location in the logical page currently being written. The index entries for the respective data packets are modified to point to the packets that contain the modified data segments. The entry or entries in the index for data packets associated with the same requested data that have not been modified will include pointers to original location of the unmodified data packets. Thus, if the original requested data is maintained, for example to maintain a previous version of the requested data, the original requested data will have pointers in the index to all data packets as originally written. The new requested data will have pointers in the index to some of the original data packets and pointers to the modified data packets in the logical page that is currently being written.
In a copy operation, the index includes an entry for the original requested data mapped to a number of packets stored in the solid-state storage media 110. When a copy is made, a new copy of the requested data is created and a new entry is created in the index mapping the new copy of the requested data to the original packets. The new copy of the requested data is also written to the solid-state storage media 110 with its location mapped to the new entry in the index. The new copy of the requested data packets may be used to identify the packets within the original requested data that are referenced in case changes have been made in the original requested data that have not been propagated to the copy of the requested data and the index is lost or corrupted.
Beneficially, sequentially writing packets facilitates a more even use of the solid-state storage media 110 and allows the solid-storage device controller 202 to monitor storage hot spots and level usage of the various logical pages in the solid-state storage media 110. Sequentially writing packets also facilitates a powerful, efficient garbage collection system, which is described in detail below. One of skill in the art will recognize other benefits of sequential storage of data packets.
Solid-State Storage Device Controller
In various embodiments, the solid-state storage device controller 202 also includes a data bus 204, a local bus 206, a buffer controller 208, buffers O-N 222a-n, a master controller 224, a direct memory access (“DMA”) controller 226, a memory controller 228, a dynamic memory array 230, a static random memory array 232, a management controller 234, a management bus 236, a bridge 238 to a system bus 240, and miscellaneous logic 242, which are described below. In other embodiments, the system bus 240 is coupled to one or more network interface cards (“NICs”) 244, some of which may include remote DMA (“RDMA”) controllers 246, one or more central processing unit (“CPU”) 248, one or more external memory controllers 250 and associated external memory arrays 252, one or more storage controllers 254, peer controllers 256, and application specific processors 258, which are described below. The components 244-258 connected to the system bus 240 may be located in the computer 112 or may be other devices.
Typically the solid-state storage controller(s) 104 communicate data to the solid-state storage media 110 over a storage I/O bus 210. In a typical embodiment where the solid-state storage is arranged in banks 214 and each bank 214 includes multiple storage elements 216a, 216b, 216m accessed in parallel, the storage I/O bus 210 is an array of busses, one for each column of storage elements 216, 218, 220 spanning the banks 214. As used herein, the term “storage I/O bus” may refer to one storage I/O bus 210 or an array of data independent busses 204. In one embodiment, each storage I/O bus 210 accessing a column of storage elements (e.g. 216a, 218a, 220a) may include a logical-to-physical mapping for storage divisions (e.g. erase blocks) accessed in a column of storage elements 216a, 218a, 220a. This mapping (or bad block remapping) allows a logical address mapped to a physical address of a storage division to be remapped to a different storage division if the first storage division fails, partially fails, is inaccessible, or has some other problem.
Data may also be communicated to the solid-state storage controller(s) 104 from a requesting device 155 through the system bus 240, bridge 238, local bus 206, buffer(s) 222, and finally over a data bus 204. The data bus 204 typically is connected to one or more buffers 222a-n controlled with a buffer controller 208. The buffer controller 208 typically controls transfer of data from the local bus 206 to the buffers 222 and through the data bus 204 to the pipeline input buffer 306 and output buffer 330. The buffer controller 208 typically controls how data arriving from a requesting device can be temporarily stored in a buffer 222 and then transferred onto a data bus 204, or vice versa, to account for different clock domains, to prevent data collisions, etc. The buffer controller 208 typically works in conjunction with the master controller 224 to coordinate data flow. As data arrives, the data will arrive on the system bus 240, be transferred to the local bus 206 through a bridge 238.
Typically the data is transferred from the local bus 206 to one or more data buffers 222 as directed by the master controller 224 and the buffer controller 208. The data then flows out of the buffer(s) 222 to the data bus 204, through a solid-state controller 104, and on to the solid-state storage media 110 such as NAND flash or other storage media. In one embodiment, data and associated out-of-band metadata (“metadata”) arriving with the data is communicated using one or more data channels comprising one or more solid-state storage controllers 104a-104n−1 and associated solid-state storage media 110a-110n−1 while at least one channel (solid-state storage controller 104n, solid-state storage media 110n) is dedicated to in-band metadata, such as index information and other metadata generated internally to the solid-state storage device 102.
The local bus 206 is typically a bidirectional bus or set of busses that allows for communication of data and commands between devices internal to the solid-state storage device controller 202 and between devices internal to the solid-state storage device 102 and devices 244-258 connected to the system bus 240. The bridge 238 facilitates communication between the local bus 206 and system bus 240. One of skill in the art will recognize other embodiments such as ring structures or switched star configurations and functions of buses 240, 206, 204, 210 and bridges 238.
The system bus 240 is typically a bus of a computer 112 or other device in which the solid-state storage device 102 is installed or connected. In one embodiment, the system bus 240 may be a PCI-e bus, a Serial Advanced Technology Attachment (“serial ATA”) bus, parallel ATA, or the like. In another embodiment, the system bus 240 is an external bus such as small computer system interface (“SCSI”), FireWire, Fiber Channel, USB, PCIe-AS, or the like. The solid-state storage device 102 may be packaged to fit internally to a device or as an externally connected device.
The solid-state storage device controller 202 includes a master controller 224 that controls higher-level functions within the solid-state storage device 102. The master controller 224, in various embodiments, controls data flow by interpreting object requests and other requests, directs creation of indexes to map object identifiers associated with data to physical locations of associated data, coordinating DMA requests, etc. Many of the functions described herein are controlled wholly or in part by the master controller 224.
In one embodiment, the master controller 224 uses embedded controller(s). In another embodiment, the master controller 224 uses local memory such as a dynamic memory array 230 (dynamic random access memory “DRAM”), a static memory array 232 (static random access memory “SRAM”), etc. In one embodiment, the local memory is controlled using the master controller 224. In another embodiment, the master controller 224 accesses the local memory via a memory controller 228. In another embodiment, the master controller 224 runs a Linux server and may support various common server interfaces, such as the World Wide Web, hyper-text markup language (“HTML”), etc. In another embodiment, the master controller 224 uses a nano-processor. The master controller 224 may be constructed using programmable or standard logic, or any combination of controller types listed above. The master controller 224 may be embodied as hardware, as software, or as a combination of hardware and software. One skilled in the art will recognize many embodiments for the master controller 224.
In one embodiment, where the storage device/solid-state storage device controller 202 manages multiple data storage devices/solid-state storage media 110a-n, the master controller 224 divides the work load among internal controllers, such as the solid-state storage controllers 104a-n. For example, the master controller 224 may divide an object to be written to the data storage devices (e.g. solid-state storage media 110a-n) so that a portion of the object is stored on each of the attached data storage devices. This feature is a performance enhancement allowing quicker storage and access to an object. In one embodiment, the master controller 224 is implemented using an FPGA. In another embodiment, the firmware within the master controller 224 may be updated through the management bus 236, the system bus 240 over a network connected to a NIC 244 or other device connected to the system bus 240.
In one embodiment, the master controller 224, which manages objects, emulates block storage such that a computer 112 or other device connected to the storage device/solid-state storage device 102 views the storage device/solid-state storage device 102 as a block storage device and sends data to specific physical addresses in the storage device/solid-state storage device 102. The master controller 224 then divides up the blocks and stores the data blocks as it would objects. The master controller 224 then maps the blocks and physical address sent with the block to the actual locations determined by the master controller 224. The mapping is stored in the object index. Typically, for block emulation, a block device application program interface (“API”) is provided in a driver in the computer 112, client 114, or other device wishing to use the storage device/solid-state storage device 102 as a block storage device.
In another embodiment, the master controller 224 coordinates with NIC controllers 244 and embedded RDMA controllers 246 to deliver just-in-time RDMA transfers of data and command sets. NIC controller 244 may be hidden behind a non-transparent port to enable the use of custom drivers. Also, a driver on a client 114 may have access to the computer network 116 through an I/O memory driver using a standard stack API and operating in conjunction with NICs 244.
In one embodiment, the master controller 224 is also a redundant array of independent drive (“RAID”) controller. Where the data storage device/solid-state storage device 102 is networked with one or more other data storage devices/solid-state storage devices 102, the master controller 224 may be a RAID controller for single tier RAID, multi-tier RAID, progressive RAID, etc. The master controller 224 also allows some objects to be stored in a RAID array and other objects to be stored without RAID. In another embodiment, the master controller 224 may be a distributed RAID controller element. In another embodiment, the master controller 224 may comprise many RAID, distributed RAID, and other functions as described elsewhere. In one embodiment, the master controller 224 controls storage of data in a RAID-like structure where parity information is stored in one or more storage elements 216, 218, 220 of a logical page where the parity information protects data stored in the other storage elements 216, 218, 220 of the same logical page.
In one embodiment, the master controller 224 coordinates with single or redundant network managers (e.g. switches) to establish routing, to balance bandwidth utilization, failover, etc. In another embodiment, the master controller 224 coordinates with integrated application specific logic (via local bus 206) and associated driver software. In another embodiment, the master controller 224 coordinates with attached application specific processors 258 or logic (via the external system bus 240) and associated driver software. In another embodiment, the master controller 224 coordinates with remote application specific logic (via the computer network 116) and associated driver software. In another embodiment, the master controller 224 coordinates with the local bus 206 or external bus attached hard disk drive (“HDD”) storage controller.
In one embodiment, the master controller 224 communicates with one or more storage controllers 254 where the storage device/solid-state storage device 102 may appear as a storage device connected through a SCSI bus, Internet SCSI (“iSCSI”), fiber channel, etc. Meanwhile the storage device/solid-state storage device 102 may autonomously manage objects and may appear as an object file system or distributed object file system. The master controller 224 may also be accessed by peer controllers 256 and/or application specific processors 258.
In another embodiment, the master controller 224 coordinates with an autonomous integrated management controller to periodically validate FPGA code and/or controller software, validate FPGA code while running (reset) and/or validate controller software during power on (reset), support external reset requests, support reset requests due to watchdog timeouts, and support voltage, current, power, temperature, and other environmental measurements and setting of threshold interrupts. In another embodiment, the master controller 224 manages garbage collection to free erase blocks for reuse. In another embodiment, the master controller 224 manages wear leveling. In another embodiment, the master controller 224 allows the data storage device/solid-state storage device 102 to be partitioned into multiple logical devices and allows partition-based media encryption. In yet another embodiment, the master controller 224 supports a solid-state storage controller 104 with advanced, multi-bit ECC correction. One of skill in the art will recognize other features and functions of a master controller 224 in a storage controller 202, or more specifically in a solid-state storage device 102.
In one embodiment, the solid-state storage device controller 202 includes a memory controller 228 which controls a dynamic random memory array 230 and/or a static random memory array 232. As stated above, the memory controller 228 may be independent or integrated with the master controller 224. The memory controller 228 typically controls volatile memory of some type, such as DRAM (dynamic random memory array 230) and SRAM (static random memory array 232). In other examples, the memory controller 228 also controls other memory types such as electrically erasable programmable read only memory (“EEPROM”), etc. In other embodiments, the memory controller 228 controls two or more memory types and the memory controller 228 may include more than one controller. Typically, the memory controller 228 controls as much SRAM 232 as is feasible and by DRAM 230 to supplement the SRAM 232.
In one embodiment, the object index is stored in memory 230, 232 and then periodically off-loaded to a channel of the solid-state storage media 110n or other non-volatile memory. One of skill in the art will recognize other uses and configurations of the memory controller 228, dynamic memory array 230, and static memory array 232.
In one embodiment, the solid-state storage device controller 202 includes a DMA controller 226 that controls DMA operations between the storage device/solid-state storage device 102 and one or more external memory controllers 250 and associated external memory arrays 252 and CPUs 248. Note that the external memory controllers 250 and external memory arrays 252 are called external because they are external to the storage device/solid-state storage device 102. In addition the DMA controller 226 may also control RDMA operations with requesting devices through a NIC 244 and associated RDMA controller 246.
In one embodiment, the solid-state storage device controller 202 includes a management controller 234 connected to a management bus 236. Typically the management controller 234 manages environmental metrics and status of the storage device/solid-state storage device 102. The management controller 234 may monitor device temperature, fan speed, power supply settings, etc. over the management bus 236. The management controller 234 may support the reading and programming of erasable programmable read only memory (“EEPROM”) for storage of FPGA code and controller software. Typically the management bus 236 is connected to the various components within the storage device/solid-state storage device 102. The management controller 234 may communicate alerts, interrupts, etc. over the local bus 206 or may include a separate connection to a system bus 240 or other bus. In one embodiment the management bus 236 is an Inter-Integrated Circuit (“I2C”) bus. One of skill in the art will recognize other related functions and uses of a management controller 234 connected to components of the storage device/solid-state storage device 102 by a management bus 236.
In one embodiment, the solid-state storage device controller 202 includes miscellaneous logic 242 that may be customized for a specific application. Typically where the solid-state device controller 202 or master controller 224 is/are configured using a FPGA or other configurable controller, custom logic may be included based on a particular application, customer requirement, storage requirement, etc.
Data Pipeline
The solid-state storage controller 104 may also include control and status registers 340 and control queues 342, a bank interleave controller 344, a synchronization buffer 346, a storage bus controller 348, and a multiplexer (“MUX”) 350. The solid-state storage controller 104, in the depicted embodiment, includes a configuration module 352 that may be part of the write data pipeline 106 and/or part of the read data pipeline 108, or may be independent from the write data pipeline 106 and the read data pipeline 108. The components of the solid-state controller 104 and associated write data pipeline 106 and read data pipeline 108 are described below. In other embodiments, synchronous solid-state storage media 110 may be used and synchronization buffers 308328 may be eliminated.
Write Data Pipeline
The write data pipeline 106 includes a packetizer 302 that receives a data or metadata segment to be written to the solid-state storage, either directly or indirectly through another write data pipeline 106 stage, and creates one or more packets sized for the solid-state storage media 110. The data or metadata segment is typically part of a data structure such as an object, but may also include an entire data structure. In another embodiment, the data segment is part of a block of data, but may also include an entire block of data. Typically, a set of data such as a data structure is received from a computer 112, client 114, or other computer or device and is transmitted to the solid-state storage device 102 in data segments streamed to the solid-state storage device 102 or computer 112. A data segment may also be known by another name, such as data parcel, but as referenced herein includes all or a portion of a data structure or data block.
Each data structure is stored as one or more packets. Each data structure may have one or more container packets. Each packet contains a header. The header may include a header type field. Type fields may include data, attribute, metadata, data segment delimiters (multi-packet), data structures, data linkages, and the like. The header may also include information regarding the size of the packet, such as the number of bytes of data included in the packet. The length of the packet may be established by the packet type. The header may include information that establishes the relationship of the packet to a data structure. An example might be the use of an offset in a data packet header to identify the location of the data segment within the data structure. One of skill in the art will recognize other information that may be included in a header added to data by a packetizer 302 and other information that may be added to a data packet.
Each packet includes a header and possibly data from the data or metadata segment. The header of each packet includes pertinent information to relate the packet to the data structure to which the packet belongs. For example, the header may include an object identifier or other data structure identifier and offset that indicates the data segment, object, data structure or data block from which the data packet was formed. The header may also include a logical address used by the storage bus controller 348 to store the packet. The header may also include information regarding the size of the packet, such as the number of bytes included in the packet. The header may also include a sequence number that identifies where the data segment belongs with respect to other packets within the data structure when reconstructing the data segment or data structure. The header may include a header type field. Type fields may include data, data structure attributes, metadata, data segment delimiters (multi-packet), data structure types, data structure linkages, and the like. One of skill in the art will recognize other information that may be included in a header added to data or metadata by a packetizer 302 and other information that may be added to a packet.
The write data pipeline 106 includes an ECC encoder 304 that that generates one or more error-correcting codes (“ECC”) for the one or more packets received from the packetizer 302. The ECC encoder 304 typically uses an error correcting algorithm to generate ECC check bits which are stored with the one or more data packets. The ECC codes generated by the ECC encoder 304 together with the one or more data packets associated with the ECC codes comprise an ECC chunk. The ECC data stored with the one or more data packets is used to detect and to correct errors introduced into the data through transmission and storage. In one embodiment, packets are streamed into the ECC encoder 304 as un-encoded blocks of length N. A syndrome of length S is calculated, appended and output as an encoded block of length N+S. The value of N and S are dependent upon the characteristics of the algorithm which is selected to achieve specific performance, efficiency, and robustness metrics. In one embodiment, there is no fixed relationship between the ECC blocks and the packets; the packet may comprise more than one ECC block; the ECC block may comprise more than one packet; and a first packet may end anywhere within the ECC block and a second packet may begin after the end of the first packet within the same ECC block. In one embodiment, ECC algorithms are not dynamically modified. In one embodiment, the ECC data stored with the data packets is robust enough to correct errors in more than two bits.
Beneficially, using a robust ECC algorithm allowing more than single bit correction or even double bit correction allows the life of the solid-state storage media 110 to be extended. For example, if flash memory is used as the storage medium in the solid-state storage media 110, the flash memory may be written approximately 100,000 times without error per erase cycle. This usage limit may be extended using a robust ECC algorithm. Having the ECC encoder 304 and corresponding ECC decoder 322 onboard the solid-state storage device 102, the solid-state storage device 102 can internally correct errors and has a longer useful life than if a less robust ECC algorithm is used, such as single bit correction. However, in other embodiments the ECC encoder 304 may use a less robust algorithm and may correct single-bit or double-bit errors. In another embodiment, the solid-state storage media 110 may comprise less reliable storage such as multi-level cell (“MLC”) flash in order to increase capacity, which storage may not be sufficiently reliable without more robust ECC algorithms.
In one embodiment, the write pipeline 106 includes an input buffer 306 that receives a data segment to be written to the solid-state storage media 110 and stores the incoming data segments until the next stage of the write data pipeline 106, such as the packetizer 302 (or other stage for a more complex write data pipeline 106) is ready to process the next data segment. The input buffer 306 typically allows for discrepancies between the rate data segments are received and processed by the write data pipeline 106 using an appropriately sized data buffer. The input buffer 306 also allows the data bus 204 to transfer data to the write data pipeline 106 at rates greater than can be sustained by the write data pipeline 106 in order to improve efficiency of operation of the data bus 204. Typically when the write data pipeline 106 does not include an input buffer 306, a buffering function is performed elsewhere, such as in the solid-state storage device 102 but outside the write data pipeline 106, in the computer 112, such as within a network interface card (“NIC”), or at another device, for example when using remote direct memory access (“RDMA”).
In another embodiment, the write data pipeline 106 also includes a write synchronization buffer 308 that buffers packets received from the ECC encoder 304 prior to writing the packets to the solid-state storage media 110. The write synchronization buffer 308 is located at a boundary between a local clock domain and a solid-state storage clock domain and provides buffering to account for the clock domain differences. In other embodiments, synchronous solid-state storage media 110 may be used and synchronization buffers 308328 may be eliminated.
In one embodiment, the write data pipeline 106 also includes a bias module 318 that receives the one or more packets from the packetizer 302, either directly or indirectly. The bias module 318 biases the bits of the data packets toward a bias of storage cells of the solid-state storage media 110. As used herein, a “bias” is a preference, probability, tendency, or desirability of values for bits within a set of bits to exhibit a specific data pattern. A bias may be a natural property, a designed attribute, a property of performing an operation on storage media, or a random occurrence. Data itself may have a bias and data storage media may have a bias. A bias may be toward binary ones, toward binary zeroes, toward a balance of binary ones and zeroes, toward a certain binary value for certain bits, or the like.
For example, in one embodiment, end sections of data files may be padded with binary zeroes, causing the data packets that store the end sections to exhibit a bias toward binary zeroes, meaning that the data packets have more binary zeroes than binary ones. Other data packets may have more binary ones than zeroes, or a balance of binary ones and zeroes. While data packets may each have an individual bias based on data within the packets, a bias of the storage cells of the solid-state storage media 110 may be based on some benefit associated with the storage of a particular binary value or pattern, or some property of the storage cells. One example of a storage cell property, NAND flash storage cells presently are biased to all binary one values or almost all binary one values when provided by a manufacturer. In addition, performing an erase operation on the NAND flash storage cells sets the binary values in each storage cell to a binary one, such that programming of the storage cells comprises changing certain storage cells to a binary zero value. This bias to all binary one values or almost all binary one values when provided by a manufacturer or when erased represents one example of an empty state for storage cells of a non-volatile solid-state storage media.
Each of the storage elements 216, 218, 220, in one embodiment, store binary data in a plurality of storage cells that exhibit a bias. Each storage cell stores one or more binary bits, or values. Flash memory storage cells may be single-level cells (“SLC”) that each store a single binary bit, or multi-level cells (“MLC”) that each store two or more binary bits. Examples of storage cells include transistors, capacitors, magnetic elements, mechanical elements, optical elements, and the like. In flash memory, each storage cell is typically a floating-gate transistor. NRAM, MRAM, DRAM, PRAM, and other types of solid-state storage may have other types of storage cells, and may store either a single binary bit or two or more binary bits per storage cell.
In one embodiment, the storage cells in the storage elements 216, 218, 220 in an empty or erased state store initial binary values. The initial binary values represent a bias for the storage cells. For example, the storage cells may have a physical, electrical, mechanical, or other quality that causes them to store a certain value by default. In another embodiment, the bias may be intentionally selected based on design considerations of the solid-state storage media 110, on security considerations, on compatibility issues, or the like, and may not be based on a default property of the storage cells.
For example, in one embodiment, the storage cells of the storage elements 216, 218, 220 may each store a binary value of one upon delivery from a manufacturer, and may each be erased to a value of one prior to being programmed, or written to, as is typical with flash memory. In another embodiment, the storage cells of the storage elements 216, 218, 220 may be biased toward binary zeroes, toward a balance or equal amount of binary ones and zeroes, toward a certain binary value for a plurality of bits, toward a binary pattern, or the like.
In certain embodiments, a bias of one or more storage cells may be influenced by or based on a state of other storage cells physically adjacent to or otherwise in proximity to the one or more storage cells. For example, it may be desirable to bias data stored in storage cells to minimize inter-cell interference between the storage cells and other storage cells, or the like. Inter-cell interference can be caused by voltage differentials between physically adjacent storage cells and, in certain embodiments, biasing data to reduce or minimize the voltage differentials between storage cells based on a physical geometry of the storage cells can reduce inter-cell interference. In one embodiment, storage cells of the solid-state storage media 110 may have a bias toward a binary pattern that satisfies a predefined voltage differential threshold between the storage cells and other physically adjacent storage cells, or the like.
In addition to local types of inter-cell interference, larger multi-cell structures, such as bit strings, word lines, or the like, may experience inter-cell interference. Certain stripes or other patterns in data, such as stripes of binary ones or of binary zeroes, may interfere with the accuracy or effectiveness of sense amplifiers and/or other management circuitry for these larger, multi-cell structures, and it may be advantageous to bias data away from such stripes or other patterns.
For certain types of storage cells, such as SLC flash memory, the voltage level of a storage cell and associated voltage differentials between storage cells may be based on a single bit value for each storage cell and biasing data may include biasing toward a binary pattern with minimal transitions between binary one values and binary zero values within a data packet and/or within a physical region of storage cells. For other types of storage cells, such as MLC flash memory, the voltage level of a storage cell and associated voltage differentials between storage cells may be based on groups of bits forming a sub-pattern or symbol, and biasing data may include biasing toward a binary pattern with minimal transitions between certain sub-patterns or symbols. One example of using sub-patterns or symbols includes binary or Gray-code mapping of multiple binary values to associated charge levels within MLC storage cells. The bits stored by a single MLC storage cell, in certain embodiments, may not have adjacent addresses, but may be stored on different physical pages, logical pages, or the like.
In one embodiment, the bias module 318 biases source data to reduce inter-cell interference as a separate step performed separately from, instead of, or in addition to other biasing techniques. For example, upon flipping, whitening, compressing, relocating, and/or otherwise biasing source data, separate blocks of source data may still exhibit patterns that cause inter-cell interference, and the bias module 318 may bias one or more of the separate blocks of source data toward a pattern that minimizes inter-cell interference, or the like.
The bias module 318 biases a packet by changing a bias of the packet to more closely match a bias of the storage cells of the solid-state storage media 110. The bias module 318 biases the packets in a reversible manner, such that the inverse bias module 332 can convert the packets back to their original source data values with their original source biases. In one embodiment, the packets that the bias module 318 biases are sized for storage in a specific logical or physical storage region or division of the solid-state storage media 110, such as an erase block, a virtual erase block, a page, a virtual page, an ECC chunk, a division within a page, or the like. In one embodiment, the bias module 318 selectively biases certain packets based on a bias of the packets, and may not bias other packets.
Those of skill in the art recognize that the bias module 318 may, alternatively, operate on one or more data segments that form a subset of a data packet. Similarly, the inverse bias module 332 may operate on data segments as well. Alternatively, or in addition, in one embodiment, the data packet (or data packet subsets such as a data segment) may be sized based on a size of a storage region in the solid-state storage media 110, a size of a bus or buffer, a size of a pipeline 106, 108, a number of extra bits available for storage of an indicator, or the like.
By biasing data packets toward the bias of the storage cells, the bias module 318 increases performance and endurance of the solid-state storage media 110 and the solid-state storage device 102. For example, biasing packets to more closely match the bias of the storage cells decreases write times and erase times because fewer actual storage cells must be changed to execute the operation. It also increases the writable life of the storage cells because fewer operations that are executed on a storage cell mean that the storage cell will last longer before wear begins to affect the storage cell performance/reliability. In certain embodiments, biasing data packets may decrease power consumption or have other additional benefits. Because, in one embodiment, the storage cells store initial binary values that satisfy a bias just prior to being programmed or written to, the closer that the data packets match the bias of the storage cells, the fewer the number of storage cells that are changed to store the data packets, and the more storage cells that remain in a biased state.
As depicted, the bias module 318 biases the one or more packets prior to sending the packets to the ECC encoder 304. Depending on the method that the bias module 318 uses to bias the packets, and on other design considerations, in a further embodiment, the bias module 318 may receive data subsequent to the ECC encoder 304 in the write data pipeline 106, or be placed elsewhere in the write data pipeline 106. For example, in certain embodiments, it may be beneficial to keep ECC data separate from data that the bias module 318 biases, while in other embodiments it may be beneficial for the bias module 318 to bias data that includes ECC data from the ECC encoder 304.
In one embodiment, the bias module 318 biases one or more data segments prior to sending the data segments to the ECC encoder 304. The data segment may be a grouping of bits smaller than a data packet in one embodiment. In such an embodiment, the data segment may comprise the width in bits/bytes of the write data pipeline 106. Similarly, the inverse bias module 332 may convert biased data segments back to their original source state after they are read. Biasing and inverse biasing a data segment may facilitate use of the bias module 318 and the inverse bias module 332 in a write data pipeline 106 and a read data pipeline 108 because the data segment may be sized to match the size (bus width) of data streaming through the pipelines 106,108.
In another embodiment, the bias module 318 may be integrated with another element of the write data pipeline 106, such as the compression module 312, the encryption module 314, the ECC encoder 304, or the like. The bias module 318 and corresponding inverse bias module 332 transparently increase the performance of the solid-state storage media 110 as the bias module 318 biases data packets before they are written and the inverse bias module 332 converts the biased data packets back to their original source state after they are read.
In another embodiment, the write data pipeline 106 also includes an encryption module 314 that encrypts a data or metadata segment received from the input buffer 306, either directly or indirectly, prior sending the data segment to the packetizer 302, the data segment encrypted using an encryption key received in conjunction with the data segment. The encryption keys used by the encryption module 314 to encrypt data may not be common to all data stored within the solid-state storage device 102 but may vary on an per data structure basis and received in conjunction with receiving data segments as described below. For example, an encryption key for a data segment to be encrypted by the encryption module 314 may be received with the data segment or may be received as part of a command to write a data structure to which the data segment belongs. The solid-sate storage device 102 may use and store a non-secret cryptographic nonce in each data structure packet that is used in conjunction with the encryption key. A different nonce may be stored with every packet. Data segments may be split between multiple packets with unique nonces for the purpose of improving protection by the encryption algorithm.
The encryption key may be received from a client 114, another computer, key manager, or other device that holds the encryption key to be used to encrypt the data segment. In one embodiment, encryption keys are transferred to the solid-state storage controller 104 from one of a solid-state storage device 102, computer 112, client 114, or other external agent which has the ability to execute industry standard methods to securely transfer and protect private and public keys.
In one embodiment, the encryption module 314 encrypts a first packet with a first encryption key received in conjunction with the packet and encrypts a second packet with a second encryption key received in conjunction with the second packet. In another embodiment, the encryption module 314 encrypts a first packet with a first encryption key received in conjunction with the packet and passes a second data packet on to the next stage without encryption. Beneficially, the encryption module 314 included in the write data pipeline 106 of the solid-state storage device 102 allows data structure-by-data structure or segment-by-segment data encryption without a single file system or other external system to keep track of the different encryption keys used to store corresponding data structures or data segments. Each requesting device 155 or related key manager independently manages encryption keys used to encrypt only the data structures or data segments sent by the requesting device 155.
In one embodiment, the encryption module 314 may encrypt the one or more packets using an encryption key unique to the solid-state storage device 102. The encryption module 314 may perform this media encryption independently, or in addition to the encryption described above. Typically, the entire packet is encrypted, including the headers. In another embodiment, headers are not encrypted. The media encryption by the encryption module 314 provides a level of security for data stored in the solid-state storage media 110. For example, where data is encrypted with media encryption unique to the specific solid-state storage device 102, if the solid-state storage media 110 is connected to a different solid-state storage controller 104, solid-state storage device 102, or computer 112, the contents of the solid-state storage media 110 typically could not be read without use of the same encryption key used during the write of the data to the solid-state storage media 110 without significant effort.
In another embodiment, the write data pipeline 106 includes a compression module 312 that compresses the data for metadata segment prior to sending the data segment to the packetizer 302. The compression module 312 typically compresses a data or metadata segment using a compression routine known to those of skill in the art to reduce the storage size of the segment. For example, if a data segment includes a string of 512 zeros, the compression module 312 may replace the 512 zeros with code or token indicating the 512 zeros where the code is much more compact than the space taken by the 512 zeros.
In one embodiment, the compression module 312 compresses a first segment with a first compression routine and passes along a second segment without compression. In another embodiment, the compression module 312 compresses a first segment with a first compression routine and compresses the second segment with a second compression routine. Having this flexibility within the solid-state storage device 102 is beneficial so that clients 114 or other devices writing data to the solid-state storage device 102 may each specify a compression routine or so that one can specify a compression routine while another specifies no compression. Selection of compression routines may also be selected according to default settings on a per data structure type or data structure class basis. For example, a first data structure of a specific data structure may be able to override default compression routine settings and a second data structure of the same data structure class and data structure type may use the default compression routine and a third data structure of the same data structure class and data structure type may use no compression.
In one embodiment, the write data pipeline 106 includes a garbage collector bypass 316 that receives data segments from the read data pipeline 108 as part of a data bypass in a garbage collection system. A garbage collection system typically marks packets that are no longer valid, typically because the packet is marked for deletion or has been modified and the modified data is stored in a different location. At some point, the garbage collection system determines that a particular section of storage may be recovered. This determination may be due to a lack of available storage capacity, the percentage of data marked as invalid reaching a threshold, a consolidation of valid data, an error detection rate for that section of storage reaching a threshold, or improving performance based on data distribution, etc. Numerous factors may be considered by a garbage collection algorithm to determine when a section of storage is to be recovered.
Once a section of storage has been marked for recovery, valid packets in the section typically must be relocated. The garbage collector bypass 316 allows packets to be read into the read data pipeline 108 and then transferred directly to the write data pipeline 106 without being routed out of the solid-state storage controller 104. In one embodiment, the garbage collector bypass 316 is part of an autonomous garbage collector system that operates within the solid-state storage device 102. This allows the solid-state storage device 102 to manage data so that data is systematically spread throughout the solid-state storage media 110 to improve performance, data reliability and to avoid overuse and underuse of any one location or area of the solid-state storage media 110 and to lengthen the useful life of the solid-state storage media 110.
The garbage collector bypass 316 coordinates insertion of segments into the write data pipeline 106 with other segments being written by clients 114 or other devices. In the depicted embodiment, the garbage collector bypass 316 is before the packetizer 302 in the write data pipeline 106 and after the depacketizer 324 in the read data pipeline 108, but may also be located elsewhere in the read and write data pipelines 106, 108. The garbage collector bypass 316 may be used during a flush of the write pipeline 108 to fill the remainder of the virtual page in order to improve the efficiency of storage within the solid-state storage media 110 and thereby reduce the frequency of garbage collection.
In one embodiment, the write data pipeline 106 includes a write buffer 320 that buffers data for efficient write operations. Typically, the write buffer 320 includes enough capacity for packets to fill at least one virtual page in the solid-state storage media 110. This allows a write operation to send an entire page of data to the solid-state storage media 110 without interruption. By sizing the write buffer 320 of the write data pipeline 106 and buffers within the read data pipeline 108 to be the same capacity or larger than a storage write buffer within the solid-state storage media 110, writing and reading data is more efficient since a single write command may be crafted to send a full virtual page of data to the solid-state storage media 110 instead of multiple commands.
While the write buffer 320 is being filled, the solid-state storage media 110 may be used for other read operations. This is advantageous because other solid-state devices with a smaller write buffer or no write buffer may tie up the solid-state storage when data is written to a storage write buffer and data flowing into the storage write buffer stalls. Read operations will be blocked until the entire storage write buffer is filled and programmed. Another approach for systems without a write buffer or a small write buffer is to flush the storage write buffer that is not full in order to enable reads. Again this is inefficient because multiple write/program cycles are required to fill a page.
For depicted embodiment with a write buffer 320 sized larger than a virtual page, a single write command, which includes numerous subcommands, can then be followed by a single program command to transfer the page of data from the storage write buffer in each solid-state storage element 216, 218, 220 to the designated page within each solid-state storage element 216, 218, 220. This technique has the benefits of eliminating partial page programming, which is known to reduce data reliability and durability and freeing up the destination bank for reads and other commands while the buffer fills.
In one embodiment, the write buffer 320 is a ping-pong buffer where one side of the buffer is filled and then designated for transfer at an appropriate time while the other side of the ping-pong buffer is being filled. In another embodiment, the write buffer 320 includes a first-in first-out (“FIFO”) register with a capacity of more than a virtual page of data segments. One of skill in the art will recognize other write buffer 320 configurations that allow a virtual page of data to be stored prior to writing the data to the solid-state storage media 110.
In another embodiment, the write buffer 320 is sized smaller than a virtual page so that less than a page of information could be written to a storage write buffer in the solid-state storage media 110. In the embodiment, to prevent a stall in the write data pipeline 106 from holding up read operations, data is queued using the garbage collection system that needs to be moved from one location to another as part of the garbage collection process. In case of a data stall in the write data pipeline 106, the data can be fed through the garbage collector bypass 316 to the write buffer 320 and then on to the storage write buffer in the solid-state storage media 110 to fill the pages of a virtual page prior to programming the data. In this way a data stall in the write data pipeline 106 would not stall reading from the solid-state storage device 102.
In another embodiment, the write data pipeline 106 includes a write program module 310 with one or more user-definable functions within the write data pipeline 106. The write program module 310 allows a user to customize the write data pipeline 106. A user may customize the write data pipeline 106 based on a particular data requirement or application. Where the solid-state storage controller 104 is an FPGA, the user may program the write data pipeline 106 with custom commands and functions relatively easily. A user may also use the write program module 310 to include custom functions with an ASIC, however, customizing an ASIC may be more difficult than with an FPGA. The write program module 310 may include buffers and bypass mechanisms to allow a first data segment to execute in the write program module 310 while a second data segment may continue through the write data pipeline 106. In another embodiment, the write program module 310 may include a processor core that can be programmed through software.
Note that the write program module 310 is shown between the input buffer 306 and the compression module 312, however, the write program module 310 could be anywhere in the write data pipeline 106 and may be distributed among the various stages 302-320. In addition, there may be multiple write program modules 310 distributed among the various states 302-320 that are programmed and operate independently. In addition, the order of the stages 302-320 may be altered. One of skill in the art will recognize workable alterations to the order of the stages 302-320 based on particular user requirements.
Read Data Pipeline
The read data pipeline 108 includes an ECC decoder 322 that determines if a data error exists in ECC blocks a requested packet received from the solid-state storage media 110 by using ECC stored with each ECC block of the requested packet. The ECC decoder 322 then corrects any errors in the requested packet if any error exists and the errors are correctable using the ECC. For example, if the ECC can detect an error in six bits but can only correct three bit errors, the ECC decoder 322 corrects ECC blocks of the requested packet with up to three bits in error. The ECC decoder 322 corrects the bits in error by changing the bits in error to the correct one or zero state so that the requested data packet is identical to when it was written to the solid-state storage media 110 and the ECC was generated for the packet.
In certain embodiments, the ECC decoder 322 may provide error information for correctable errors to the configuration module 352, described below, such as locations of the bits in error, values for the bits in error, and/or other error information. For example, the ECC decoder 322 may provide an error bias to the configuration module 352, indicating one or more bits of a data set that are in error, or the like. An error bias, as used herein, is a representation of one or more detected bit errors in a data set. In one embodiment, an error bias includes a location or position of a detected bit error in a data set. In another embodiment, an error bias includes a value for a detected bit error. A value for a detected error may include an error corrected value of a bit in error, an error value of the bit in error, or the like. For example, in one embodiment, the ECC decoder 322 may provide the configuration module 352 with an uncorrected data set and an error bias indicating locations of detected bit errors and the configuration module 352 may determine a known bias by inverting or flipping the bits in those locations. In another embodiment, for example, the ECC decoder 322 may provide the configuration module 352 with an error corrected data set and an error bias indicating locations of detected bit errors and the configuration module 352 may determine a read bias by inverting or flipping the bits in those locations.
If the ECC decoder 322 determines that the requested packets contains more bits in error than the ECC can correct, the ECC decoder 322 cannot correct the errors in the corrupted ECC blocks of the requested packet and sends an interrupt. In one embodiment, the ECC decoder 322 sends an interrupt with a message indicating that the requested packet is in error. The message may include information that the ECC decoder 322 cannot correct the errors or the inability of the ECC decoder 322 to correct the errors may be implied. In another embodiment, the ECC decoder 322 sends the corrupted ECC blocks of the requested packet with the interrupt and/or the message.
In one embodiment, a corrupted ECC block or portion of a corrupted ECC block of the requested packet that cannot be corrected by the ECC decoder 322 is read by the master controller 224, corrected, and returned to the ECC decoder 322 for further processing by the read data pipeline 108. In one embodiment, a corrupted ECC block or portion of a corrupted ECC block of the requested packet is sent to the device requesting the data. The requesting device 155 may correct the ECC block or replace the data using another copy, such as a backup or mirror copy, and then may use the replacement data of the requested data packet or return it to the read data pipeline 108. The requesting device 155 may use header information in the requested packet in error to identify data required to replace the corrupted requested packet or to replace the data structure to which the packet belongs. In another embodiment, the solid-state storage controller 104 stores data using some type of RAID and is able to recover the corrupted data. In another embodiment, the ECC decoder 322 sends an interrupt and/or message and the receiving device fails the read operation associated with the requested data packet. One of skill in the art will recognize other options and actions to be taken as a result of the ECC decoder 322 determining that one or more ECC blocks of the requested packet are corrupted and that the ECC decoder 322 cannot correct the errors.
The read data pipeline 108 includes a depacketizer 324 that receives ECC blocks of the requested packet from the ECC decoder 322, directly or indirectly, and checks and removes one or more packet headers. The depacketizer 324 may validate the packet headers by checking packet identifiers, data length, data location, etc. within the headers. In one embodiment, the header includes a hash code that can be used to validate that the packet delivered to the read data pipeline 108 is the requested packet. The depacketizer 324 also removes the headers from the requested packet added by the packetizer 302. The depacketizer 324 may directed to not operate on certain packets but pass these forward without modification. An example might be a container label that is requested during the course of a rebuild process where the header information is required for index reconstruction. Further examples include the transfer of packets of various types destined for use within the solid-state storage device 102. In another embodiment, the depacketizer 324 operation may be packet type dependent.
The read data pipeline 108 includes an alignment module 326 that receives data from the depacketizer 324 and removes unwanted data. In one embodiment, a read command sent to the solid-state storage media 110 retrieves a packet of data. A device requesting the data may not require all data within the retrieved packet and the alignment module 326 removes the unwanted data. If all data within a retrieved page is requested data, the alignment module 326 does not remove any data.
The alignment module 326 re-formats the data as data segments of a data structure in a form compatible with a device requesting the data segment prior to forwarding the data segment to the next stage. Typically, as data is processed by the read data pipeline 108, the size of data segments or packets changes at various stages. The alignment module 326 uses received data to format the data into data segments suitable to be sent to the requesting device 155 and joined to form a response. For example, data from a portion of a first data packet may be combined with data from a portion of a second data packet. If a data segment is larger than a data requested by the requesting device 155, the alignment module 326 may discard the unwanted data.
In one embodiment, the read data pipeline 108 includes a read synchronization buffer 328 that buffers one or more requested packets read from the solid-state storage media 110 prior to processing by the read data pipeline 108. The read synchronization buffer 328 is at the boundary between the solid-state storage clock domain and the local bus clock domain and provides buffering to account for the clock domain differences.
In another embodiment, the read data pipeline 108 includes an output buffer 330 that receives requested packets from the alignment module 326 and stores the packets prior to transmission to the requesting device 155. The output buffer 330 accounts for differences between when data segments are received from stages of the read data pipeline 108 and when the data segments are transmitted to other parts of the solid-state storage controller 104 or to the requesting device 155. The output buffer 330 also allows the data bus 204 to receive data from the read data pipeline 108 at rates greater than can be sustained by the read data pipeline 108 in order to improve efficiency of operation of the data bus 204.
In one embodiment, the solid-state storage controller 104 includes a configuration module 352 that sets and adjusts configuration parameters for the solid-state storage media 110, such as read voltage thresholds and the like. In a further embodiment, the configuration module 352 may be integrated with the solid-state storage media 110 such that it operates independently from the read data pipeline 108 and/or the write data pipeline 106. In certain embodiments, as described in greater detail below with regard to the proactive configuration module 424 of
In other embodiments, the configuration module 352 may receive a data set from the solid-state storage media 110, either directly or indirectly, to determine configuration parameters for corresponding storage cells in a closed loop manner, with read data sets as feedback from the storage cells. In certain embodiments, the configuration module 352 may receive one or more requested biased packets from the ECC decoder 322. In a further embodiment, the configuration module 352 may receive a data set from the read synchronization buffer 328, directly from the storage I/O bus 210, from the inverse bias module 332, or otherwise. The configuration module 352 is described in greater detail with regard to
In general, the configuration module 352 sets and adjusts one or more configuration parameters for one or more storage cells from the solid-state storage media 110, such as setting and adjusting read voltage thresholds, resistivity thresholds, programming thresholds, erase thresholds, or the like. A read voltage threshold is a voltage level that separates discrete values stored in the storage cells of the solid-state storage media 110. Different solid-state storage technologies may use different thresholds other than voltages to distinguish between discrete states. Phase change RAM or PRAM, for example, stores data in chalcogenide glass that has different electrical resistivity in different states. For PRAM, the configuration module 352 may determine, set, and/or adjust resistivity thresholds that distinguish between discrete storage states. One of skill in the art, in light of this disclosure, will recognize that the configuration module 352 may determine, set, and adjust resistivity thresholds or other configuration parameters in a substantially similar manner to that described herein with regard to read voltage thresholds.
For SLC storage cells that store a single binary value, the read voltage threshold is the boundary between a binary one state and a binary zero state. For example, in one embodiment, a storage cell with a read voltage level above the read voltage threshold stores a binary one while a storage cell with a read voltage level below the read voltage threshold stores a binary zero. Other types of storage cells, such as MLC storage cells, may have multiple read voltage thresholds, to distinguish between more than two discrete states.
For example, in one embodiment, MLC storage cells that store two bits may have three read voltage thresholds, separating binary values of 11, 01, 00, and 10. The three example read voltage thresholds may be x volts, y volts, and z volts, described in greater detail below with regard to the read voltage thresholds 662 of
The voltages for Vmin, Vmax, x, y, z may vary based on the manufacturer of the storage cells. Read voltages, for example, may range between −3.5 and 5.8 volts, or between another predefined range of voltages. Similarly, the order of binary state changes 11, 01, 00, and 10 relative to read voltage thresholds may vary based on the encoding type used, such as a Gray code encoding type, a binary code encoding type, or the like. One example encoding type is described below with regard to
In certain embodiments, instead of referring to a boundary between discrete values, a read voltage threshold comprises a range of voltages (a maximum and a minimum) that indicate a value. A voltage threshold that is a range can be adjusted by changing the boundary at either end, or at both ends, of the range. The read voltage thresholds or other configuration parameters for the solid-state storage media 110, in one embodiment, are initially set at a default level that may be defined by a manufacturer. Often such configuration parameter default levels are set to accommodate a large range of general purpose uses of the solid-state storage media 110. Advantageously, embodiments of the configuration module 352 allow the solid-state storage media 110 to be used most optimally based on more specific use characteristics. The configuration module 352, in certain embodiments, overrides the default level for one or more configuration parameters, setting the one or more configuration parameters to a different level based on storage media characteristics of the solid-state storage media 110. The configuration module 352 may set the configuration parameters to a level that decreases the amount of errors that the solid-state storage media 110 encounters when compared to the default level, to a level that increases the amount of errors that may be detected and corrected when compared to the default level, to a level that increases the number of input/output operations per second (“TOPS”) of the solid-state storage media 110 when compared to the default level, to a level that increases the usable life of the solid-state storage media 110 when compared to the default level, and/or that otherwise improves the utility of the solid-state storage media 110 when compared to the default level.
The read voltage levels of storage cells, and other configuration parameters, can also shift over time, due to leakage and other disturbances of the solid-state storage media 110. The rate of leakage can also increase with the wear and age of the solid-state storage media 110. If the read voltage level of a storage cell shifts past the read voltage threshold, a data error occurs, as the value of the data read from the storage cell is different than the value of the data written to the storage cell. The configuration module 352, in one embodiment, adjusts a read voltage threshold or other configuration parameter for one or more storage cells from the solid-state storage media 110 to compensate for shifts in the read voltage levels of the storage cells. By proactively and/or dynamically adjusting read voltage thresholds, the configuration module 352 can increase the retention rate for and/or the reliability of data stored in the solid-state storage media 110 and extend the useable lifetime of the solid-state storage media 110 itself, improving the utility of the solid-state storage media 110.
The configuration module 352, in one embodiment, uses a known bias of the data set or packet from the solid-state storage media 110 to adjust the read voltage threshold or other configuration parameter. As described above with regard to the bias module 318, a bias is a preference, probability, tendency, or desirability of values for bits within a set of bits to exhibit a specific data pattern. A bias may be a natural property, a designed attribute, a property of performing an operation on storage media, or a random occurrence. A bias may be toward binary ones, toward binary zeroes, toward a balance of binary ones and zeroes, toward a certain binary value for certain bits, toward a specific ratio of binary ones and binary zeroes, toward a binary pattern, or the like.
In one embodiment, the data set or packet that the configuration module 352 receives has a known bias. The data set or packet has a known bias for one of at least three reasons. First, the data set or packet may have a known bias because the bias module 318 biased the data set or packet when the data set or packet was written. In one embodiment, the bias module 318 and/or the inverse bias module 332 cooperate with the configuration module 352, communicating the known bias to the configuration module 352. Second, the data set or packet may have a known bias because the data set or packet is read from a virgin, unwritten region of the solid-state storage media 110. For example, in one embodiment, virgin, unwritten regions of the solid-state storage media 110 may typically have a known bias of exclusively binary ones or exclusively binary zeroes in an unwritten state. Third, the data set or packet may have a known bias because the ECC decoder 322 has corrected the data set or packet and has determined the original, correct values of one or more bits of the data set that were in error. The correct values for the bits in the data set comprise this known bias. A deviation from the known bias caused by errors in the data set is an error bias.
The configuration module 352, in one embodiment, determines that a read bias for the data set or packet deviates from the known bias, and determines a direction of deviation for the data set based on a difference between the read bias and the known bias. In a further embodiment, the configuration module 352 adjusts the read voltage threshold, or another read threshold such as a resistivity threshold, for storage cells corresponding to the data set based on the direction of deviation. For example, in one embodiment, the configuration module 352 may lower the read voltage threshold from the previous read voltage threshold to a new read voltage threshold for the storage cells if the data set has more binary zeroes than expected based on the known bias. For MLC storage cells, in one embodiment, a data set may include data from different addresses, different pages, or the like so that the data set includes all data that the associated storage cells store. The configuration module 352 may base a read voltage threshold adjustment on known characteristics of the storage cells, such as an encoding type used for the storage cells, based on a physical and/or electrical architecture of the storage cells, or the like. In a further embodiment, the configuration module 352 may transform, translate, or combine data from different addresses or pages to facilitate a determination of a known bias, a read bias, and/or a deviation from a known bias for MLC storage cells. In another embodiment, for MLC storage cells, the configuration module 352 may adjust a read voltage threshold for the MLC storage cells based on a subset of the data stored by the MLC storage cells.
The configuration module 352, in one embodiment, may request that the data set be re-read with the new read voltage threshold. The configuration module 352 may determine whether the re-read data set has a read bias that deviates from the known bias, and may iteratively adjust the read voltage threshold to a new read voltage threshold until the read bias of the data set no longer deviates from the known bias more than a threshold amount (which may be zero), until the ECC decoder 322 can correct errors in the data set, or the like. In one embodiment, the configuration module 352 stores the new read voltage threshold such that the new read voltage threshold is persistent for subsequent data reads from the solid-state storage media 110. In a further embodiment, the solid-state storage media 110 stores the new read voltage threshold for subsequent data reads.
The configuration module 352, in one embodiment, may monitor the read bias of each packet read and compare the bias of the packet or other data set to the known bias in response to a read request. In a further embodiment, the configuration module 352 may monitor the read bias of each packet read and may compare the bias of the data set or packet to the known bias in response to a data error, such as, for example, an uncorrectable bit error that the ECC decoder 322 cannot correct, or the like. In a further embodiment, the configuration module 352 may not monitor the read bias of each packet read and may determine and compare the bias of the data set or packet to the known bias exclusively in response to a data error. As described below with regard to the proactive configuration module 424 of
In one embodiment, the solid-state storage controller 104 may read data in a data packet from multiple channels, storage elements, dies, chips, physical erase blocks (“PEBs”), groupings of storage cells, or the like within the solid-state storage media 110, each of which may have independent read voltage thresholds. The manufacturer of the channels, storage elements, dies, chips, and/or grouping of storage cells may make the read voltage thresholds for each channel, storage element, die, chip, and/or grouping of storage cells independently adjustable by the solid-state storage controller 104. Alternatively, or in addition, the manufacturer of the channels, storage elements, dies, chips, and/or grouping of storage cells may make the read voltage thresholds for groups of channels, groups of storage elements, groups of die, groups of chips, and/or groups of groupings of storage cells adjustable by the solid-state storage controller 104 as separate groups.
In one embodiment, the ECC encoder 304 creates independent ECC checkbits for each channel, storage element, die, chip, PEB, or other grouping of storage cells. The ECC checkbits are stored with the data on a particular grouping of storage cells rather than being distributed across multiple groupings. If ECC checkbits are created and stored independently for each grouping of storage cells, the configuration module 352, in response to a data error, may use the ECC checkbits and the known architecture for how an ECC checkbits are written to the groupings of storage cells to determine in which grouping of storage cells the data error occurred, and adjust the read voltage thresholds of those groupings. If ECC checkbits for the data packet are stored across multiple groupings of storage cells, the configuration module 352 may separately check the read biases of data sets from each grouping of storage cells and adjust one or more of the corresponding read voltage thresholds. An array of storage elements with multiple channels is described in greater detail with regard to
In one embodiment, the read data pipeline 108 includes an inverse bias module 332 that receives one or more requested biased packets from the ECC decoder 322, either directly or indirectly, and converts the one or more requested packets back to their original source form by reversing the biasing process of the bias module 318 prior to sending the one or more requested packets to the depacketizer 324. In one embodiment, the inverse bias module 332 may use one or more indicators stored by the bias module 318 to convert the biased packets back to their original source data. In certain embodiments, the inverse bias module 332 may provide a known bias, a read bias, and/or a deviation from a known bias for a packet or other data set to the configuration module 352, as described below with regard to
In a further embodiment, the inverse bias module 332 converts the biased packets back to their original source data without using an indicator. Instead of using an indicator, the inverse bias module 332 may implement an algorithm that is the inverse operation of the bias module 318. This algorithm may inverse the bias for each data packet received and/or a select number of data packets received. In the depicted embodiment, the inverse bias module 332 is located between the ECC decoder 322 and the depacketizer 324. In a further embodiment, the inverse bias module 332 may be located elsewhere in the read data pipeline 108, based on the location of the bias module 318 in the write data pipeline 106.
In another embodiment, the read data pipeline 108 includes a decryption module 334 that decrypts a data segment formatted by the depacketizer 324 prior to sending the data segment to the output buffer 330. The data segment may be decrypted using an encryption key received in conjunction with the read request that initiates retrieval of the requested packet received by the read synchronization buffer 328. The decryption module 334 may decrypt a first packet with an encryption key received in conjunction with the read request for the first packet and then may decrypt a second packet with a different encryption key or may pass the second packet on to the next stage of the read data pipeline 108 without decryption. When the packet was stored with a non-secret cryptographic nonce, the nonce is used in conjunction with an encryption key to decrypt the data packet. The encryption key may be received from a client 114, a computer 112, key manager, or other device that manages the encryption key to be used by the solid-state storage controller 104.
In another embodiment, the read data pipeline 108 includes a decompression module 336 that decompresses a data segment formatted by the depacketizer 324. In one embodiment, the decompression module 336 uses compression information stored in one or both of the packet header and the container label to select a complementary routine to that used to compress the data by the compression module 312. In another embodiment, the decompression routine used by the decompression module 336 is dictated by the device requesting the data segment being decompressed. In another embodiment, the decompression module 336 selects a decompression routine according to default settings on a per data structure type or data structure class basis. A first packet of a first object may be able to override a default decompression routine and a second packet of a second data structure of the same data structure class and data structure type may use the default decompression routine and a third packet of a third data structure of the same data structure class and data structure type may use no decompression.
In another embodiment, the read data pipeline 108 includes a read program module 338 that includes one or more user-definable functions within the read data pipeline 108. The read program module 338 has similar characteristics to the write program module 310 and allows a user to provide custom functions to the read data pipeline 108. The read program module 338 may be located as shown in
The solid-state storage controller 104 includes control and status registers 340 and corresponding control queues 342. The control and status registers 340 and control queues 342 facilitate control and sequencing commands and subcommands associated with data processed in the write and read data pipelines 106, 108. For example, a data segment in the packetizer 302 may have one or more corresponding control commands or instructions in a control queue 342 associated with the ECC encoder 304. As the data segment is packetized, some of the instructions or commands may be executed within the packetizer 302. Other commands or instructions may be passed to the next control queue 342 through the control and status registers 340 as the newly formed data packet created from the data segment is passed to the next stage.
Commands or instructions may be simultaneously loaded into the control queues 342 for a packet being forwarded to the write data pipeline 106 with each pipeline stage pulling the appropriate command or instruction as the respective packet is executed by that stage. Similarly, commands or instructions may be simultaneously loaded into the control queues 342 for a packet being requested from the read data pipeline 108 with each pipeline stage pulling the appropriate command or instruction as the respective packet is executed by that stage. One of skill in the art will recognize other features and functions of control and status registers 340 and control queues 342.
The solid-state storage controller 104 and or solid-state storage device 102 may also include a bank interleave controller 344, a synchronization buffer 346, a storage bus controller 348, and a multiplexer (“MUX”) 350.
Configuring Storage Cells
In the depicted embodiment 301, the configuration module 352 receives inputs from the inverse bias module 332, the ECC decoder 322, and the device factor module 354 and the configuration module 352 determines a configuration parameter adjustment 358 based on the inputs. In other embodiments, the configuration module 352 may receive inputs from just the inverse bias module 332, from just the ECC decoder 322, from just the device factor module 354, or from a different combination of the inverse bias module 332, the ECC decoder 322, and/or the device factor module 354.
The inverse bias module 332, in one embodiment, provides a known bias and/or an actual read bias of a data set to the configuration module 352. The inverse bias module 332 may provide the known bias as an expected bias based on a reversible biasing algorithm that the bias module 318 applies to data written to the solid-state storage media 110. The expected bias, in certain embodiments, may be an exact bias, where the bias module 318 uses a reversible biasing algorithm that biases data to exactly match a bias. For example, the bias module 318 may add padding data to a data set so that the data set has an exact balance of binary ones and binary zeroes, or the like, and the known bias may be exact.
In another embodiment, the inverse bias module 332 may provide the expected bias as a range, a distribution, an average, an estimate, or the like based on the reversible biasing algorithm that the bias module 318 applies to data. For example, the inverse bias module 332 may measure or learn an expected bias over time as the inverse bias module 332 applies an inverse biasing algorithm to data read from the solid-state storage media 110. In one embodiment, the expected bias may be mathematically or otherwise derived from the reversible biasing algorithm of the bias module 318 as a range or distribution of possible or likely biases.
For example, where the bias module 318 biases data toward a balance of one half binary ones and one half binary zeroes, which may also be referred to as a direct current (“DC”) balance, a range of actual biases for biased data may range between about forty-six percent binary ones and fifty-four percent binary ones, or the like. The known bias and the read bias of the data set, in other embodiments, may also be based on multi-bit symbols or patterns of bits instead of being based exclusively on individual binary ones and zeroes, or the like. While the inverse bias module 332, in the depicted embodiment 301, provides input to the configuration module 352, in certain embodiments, the bias module 318 may provide an expected bias to the configuration module 352 as a known bias, the known bias may be hard coded or programmed into the configuration module 352, or the like.
In one embodiment, the inverse bias module 332 provides a read bias of a data set read from the solid-state storage media 110 to the configuration module 352. For example, as the inverse bias module 332 converts biased data packets or other data sets back to their original source form by reversing the biasing process of the bias module 318, the inverse bias module 332 may determine, measure, or detect the read bias of the data packets or other data sets. The inverse bias module 332 may determine a read bias prior to, during, or after reversing the biasing process, depending on the biasing process used. In certain embodiments, if the inverse bias module 332 determines that a read bias of a data set deviates from the known/expected bias of the data set, the inverse bias module 332 may provide the data set to the configuration module 352 to make a configuration parameter adjustment 358 to storage cells of the data set so that the data set may be re-read. In other embodiments, as described above with regard to
The ECC decoder 322, in one embodiment, provides a known bias and/or a read bias for a data set to the configuration module 352. The ECC decoder 322 may provide a known bias for a data set having a correct state of bits for the data set. For example, once the ECC decoder 322 has corrected one or more correctable bit errors in a data set, the ECC decoder 322 may provide the error corrected state of the bits of the data set to the configuration module 352 as a known bias with which the data set was written to the solid-state storage media 110. The ECC decoder 322, in a further embodiment, may provide the read bias for a data set as an error bias that indicates one or more bits of a data set that were in error when the data set was read from the solid-state storage media 110.
Because the ECC decoder 322, for correctable errors, determines the exact, original, correct values of bits (known bias) of a data set and an exact location of bits in error (error bias) of the data set the configuration module 352 can determine an exact deviation of the data set from the known bias. For this reason, in certain embodiments, the configuration module 352 may make more precise configuration parameter adjustments 358 using a known bias and an error bias from the ECC decoder 322, when available, than using an expected bias and a read bias from the inverse bias module 332.
The configuration module 352, in one embodiment, uses a known bias and/or an error bias for a data set from the ECC decoder 322 in response to one or more correctable bit errors in the data set. In a further embodiment, the configuration module 352 uses an expected bias that is based on a reversible biasing algorithm as a known bias. In certain embodiments, the expected bias is used as the known bias in response to one or more uncorrectable bit errors in the data set. An error bias from the ECC decoder 322 may not be available to the configuration module 352 for uncorrectable bit errors because the uncorrectable bit error condition makes the bias undefined. For uncorrectable bit errors in a data set, in certain embodiments, the read bias of the data set may deviate from the known, expected bias for the data set more than for correctable bit errors, because of the greater severity of the errors. Due to the greater magnitude of deviation of the read bias of a data set from the known, expected bias of the data set for uncorrectable bit errors, the bias information from the inverse bias module 332 may provide a better indicator of a direction for a configuration parameter adjustment 358 for uncorrectable bit errors than for correctable bit errors.
The device factor module 354, in one embodiment, provides one or more statistics for the solid-state storage device 102 to the configuration module 352. The configuration module 352, in certain embodiments, may make a configuration parameter adjustment 358 based on the one or more statistics, may supplement information from the inverse bias module 332 and/or the ECC decoder 322 with the one or more statistics, or the like. The one or more statistics for the solid-state storage device 102, in one embodiment, include statistics that may affect read voltages of storage cells of the solid-state storage device 102. For example, in certain embodiments, the one or more statistics may include a temperature for the solid-state storage device 102, an error rate for the solid-state storage device 102 (such as an uncorrectable bit error rate “UBER” or the like), an erase cycle count for the solid-state storage device 102, a storage request latency for the solid-state storage device 102 (such as an average, maximum, or other storage request execution latency), an age of the solid-state storage device 102, and/or other statistics or characteristics.
In the depicted embodiment 301, the device factor module 354 receives input from one or more sensors 356. The one or more sensors 356 each detect a statistic or characteristic for the solid-state storage device 102, such as temperature, moisture, movement, and/or other statistics. For example, in various embodiments, the one or more sensors 356 may include a temperature sensor, a moisture sensor, an accelerometer, and/or another type of sensor for the solid-state storage device 102. In one embodiment, the device factor module 354 and/or the configuration module 352 may receive one or more statistics for the solid-state storage device 102 from one or more other modules or elements. For example, the device factor module 354 and/or the configuration module 352 may receive an error rate for the solid-state storage device 102, such as a UBER or the like, from the ECC decoder 322.
The configuration module 352, in various embodiments, may base a configuration parameter adjustment 358 on a single input or on a combination of inputs from the inverse bias module 332, the ECC decoder 322, and/or the device factor module 354. In certain embodiments, one or more inputs from the inverse bias module 332, the ECC decoder 322, and/or the device factor module 354 may not be available for a data set. For example, the ECC decoder 322 may not provide an error bias and a known bias for a data set with an uncorrectable bit error, the inverse bias module 332 may not provide a known, expected bias or a read bias for a data set during a learning period while the inverse bias module 332 is determining an expected bias, the device factor module 354 may not provide one or more statistics during an initial startup period, or the like.
In one embodiment, the configuration module 352 bases a configuration parameter adjustment 358 on a best available input according to a predefined hierarchy or ranking of inputs. For example, the configuration module 352 may base a configuration parameter adjustment 358 on a known bias and error bias from the ECC decoder 322 if available; on a known, expected bias and a read bias from the inverse bias module 332 if input from the ECC decoder 322 is not available; and on one or more statistics from the device factor module 354 if input from both the ECC decoder 322 and the inverse bias module 332 is unavailable.
In a further embodiment, the configuration module 352 may make a random configuration parameter adjustment 358, in response to a data error or the like, if input from each of the inverse bias module 332, the ECC decoder 322, and the device factor module 354 is unavailable. For example, the configuration module 352 may try a configuration parameter adjustment 358 in one direction, re-read the data set and check for errors, and try a configuration parameter adjustment 358 in the other direction if the error persists.
In another embodiment, the configuration module 352 may base a configuration parameter adjustment 358 on multiple inputs by combining the inputs from the inverse bias module 332, the ECC decoder 322, and/or the device factor module 354. The configuration module 352 may scale the inputs, weight the inputs, convert the inputs to common units, or the like to facilitate combination of the inputs. For example, the configuration module 352, in one embodiment, may convert each of the inputs to individual preliminary threshold adjustments, and then sum the preliminary threshold adjustments to provide a configuration parameter adjustment 358. The configuration module 352, in the example, may weight each preliminary threshold adjustment based on a predefined hierarchy or ranking of the associated inputs. For example, if a known bias and an error bias from the ECC decoder 322 indicates a configuration parameter adjustment 358 in one direction and the known, expected bias and the read bias from the inverse bias module 332 indicates a configuration parameter adjustment 358 in the other direction, the input with greater weight or priority in the predefined hierarchy or ranking will dictate the direction of the configuration parameter adjustment 358.
The configuration module 352, in one embodiment, sets configuration parameters proactively with an open loop model using the proactive configuration module 424. In another embodiment, the configuration module 352 sets configuration parameters reactively with a closed loop model using the data set read module 402, the deviation module 404, the direction module 406, and/or the adjustment module 408. In certain embodiments, the configuration module 352 may make several layers or phases of adjustments to configuration parameters, determining configuration parameters proactively using the proactive configuration module 424 and adjusting the configuration parameters reactively as the data set read module 402 reads data sets from the solid-state storage media 110.
In one embodiment, the data set read module 402 reads a data set from storage cells of the solid-state storage media 110. The data set read module 402 may read the data set either directly or indirectly from the solid-state storage media 110. For example, in one embodiment, the data set read module 402 may receive the data set from another module or element in the read data pipeline 108, the solid-state storage media 110, or the like.
In one embodiment, the data set read module 402 reads the data set in response to a testing operation and the data set may be a sample data set read as part of the testing operation. In a further embodiment, the data set read module 402 reads the data set in response to a read request from a client and the data set may be a data set that the client requested. The data set, in one embodiment, may be a full packet, a portion of a packet, or the like. In another embodiment, a size of the data set may be set by the test operation, by a read request from a client or the like. In a further embodiment, the data set may be raw data from the solid-state storage media 110, independent of packets or other data structures.
The data set, in a further embodiment, was originally stored in the storage cells with a known bias. For example, the data set may be from a packet that the bias module 318 biased, may be from storage cells of the solid-state storage media 110 that are in a virgin state, storing default data or other data programmed to the solid-state storage media 110 with a known bias for example by a manufacturer of the solid-state storage media 110, or the like.
In one embodiment, the data set may be sized relative to a biasing scheme that the bias module 318 employs to bias packets. For example, in one embodiment, the data set may be sized based on the period of a deterministic sequence, such as a pseudorandom binary sequence that the bias module 318 uses to bias packets. The closer the size of the data set is to an integer multiple of the period of the pseudorandom binary sequence, the more likely it is that the bias of the resulting data set will match the known bias. In a further embodiment, the bias module 318 may guarantee that a data set of a predefined size has a bias that does not deviate from the known bias by more than a threshold amount. The threshold amount may range from zero to a given integer value or percentage value.
As described above, a bias is a preference, probability, or tendency of values for bits within a set of bits to exhibit a specific data pattern. In one embodiment, the known bias is a known ratio of binary ones and binary zeroes within a set of bits or groupings of sets of bits. The known ratio, in one embodiment, may be expressed as a proportion or percentage between zero and one, a ratio of zero representing a bias of exclusively one value and a ratio of one representing a bias of exclusively the other value. In one embodiment, the known ratio is greater than zero and less than one, meaning that the known ratio is offset between a ratio of exclusively one binary value and a ratio of exclusively the opposite binary. If the known ratio is greater than zero and less than one, a deviation in the read bias of the data set may occur in either direction from the known ratio and still remain detectable by the configuration module 352.
In the depicted embodiment, the data set read module 402 includes a monitor module 418 and a read error module 420. The data set read module 402, in one embodiment, may read the data set using the monitor module 418 and/or the read error module 420.
In one embodiment, the monitor module 418 monitors data sets that are read from the solid-state storage media 110 in response to read requests from a computer 112 or other client 114. The monitor module 418 may monitor each data set that is read from the solid-state storage media 110 or may select certain data sets that are read from the solid-state storage media 110, at predefined intervals, in response to a command or directive from a storage client, or the like. By using the monitor module 418 to monitor data sets that are read from the solid-state storage media 110, the configuration module 352 may adjust read voltage thresholds for the solid-state storage media 110 dynamically, preventing uncorrectable data errors from occurring.
In one embodiment, the read error module 420 reads the data set in response to a data error identified in the data set. For example, the ECC decoder 322 or another module may determine that a data error has occurred. In one embodiment, the data error is an uncorrectable bit error that the ECC decoder 322 does not have enough information to correct. Specifically, the ECC decoder 322, in one embodiment, is configured to detect and correct up to a certain number of bits (# of Bits in Error-#BER) in error in a data set. When the number of bits in error exceeds the #BER, the ECC decoder 322 may signal an uncorrectable data error, an uncorrectable bit error, or the like.
The data error may occur due to a shift in a voltage level retained in one or more storage cells of the solid-state storage media 110. This retained voltage level of a storage cell is referred to herein as a read voltage level. The read error module 420, in one embodiment, reads the data set as part of a testing operation. The configuration module 352 may conduct the testing operation in response to the data error, in response to a scheduled maintenance operation, in response to an initial calibration operation, or the like. The data set used by the read error module 420 may come from a client-requested packet, or may be sample data read as part of the testing operation.
In certain embodiments, the data set read module 402, when reading a data set of sample data in response to a testing operation, periodically, during monitoring, or the like, may size the sample data set to fit within excess read bandwidth of the solid-state storage media 110. By sizing sample data to fit within excess read bandwidth of the solid-state storage media 110, in one embodiment, reading the sample data may not affect a read bandwidth for servicing read requests to the solid-state storage media 110 or a read throughput of the solid-state storage media 110. In one embodiment, the data set read module 402 may read a data set from the solid-state storage media 110 with a greater amount of data than is requested by a read request to provide a greater sample size of bits for the configuration module 352 to use to determine an adjustment to a read voltage threshold, or the like. A sample size that is greater than an amount of data requested, in certain embodiments, may improve the accuracy of a read voltage threshold adjustment.
For example, if a user application requests 512 bytes of data, and the solid-state storage media 110 can read 800 bytes of data in a read request at substantially the same speed as 512 bytes of data, in one embodiment, the data set read module 402 may read a data set of 800 bytes for adjusting a read voltage threshold, and provide the requested 512 bytes (a subset of the 800 byte data set) to the user application without affecting the read time of the operation. In one embodiment, the data set read module 402 sets a minimum data set request size and retrieves at least the minimum data set request size amount of data for each read request, even if the read request is for less than the minimum data set request size. The minimum data set request size, in certain embodiments, may be selected to fit within a boundary of one or more ECC chunks, one or more pages, one or more erase blocks, within excess bandwidth of the solid-state storage media 110, or the like. In one embodiment, the minimum data set request size may be selected based on an architecture or geometry of the solid-state storage media 110, the read data pipeline 108, or the like.
In one embodiment, the deviation module 404 determines that a read bias for a data set deviates from a known bias with which the data set was originally stored. The read bias of the data set deviates from the known bias when there is a difference between the read bias and the known bias. In one embodiment, where the known bias is exact, such as where the known bias includes error corrected bit values or where the bias module 318 biases to an exact bias, the deviation module 404 may determine that any difference between a read bias and the known bias comprises a deviation from the known bias. In other embodiments, the known bias may include an average bias, an estimated bias, a distribution of biases, a range of biases, or the like. The deviation module 404, in these embodiments, may determine that a read bias outside of a range or distribution of known biases, at least a predefined deviation threshold away from a known bias, or the like deviates from the known bias.
In one embodiment, the difference between the read bias of the data set and the known bias may be a difference in the ratios of binary ones and binary zeroes. In other embodiments, the difference between the bias of the data set and the known bias may be a difference in a binary pattern, a difference in multi-bit binary symbols, or the like. As described above with regard to
The deviation module 404, in one embodiment, determines whether the read bias of the data set deviates from the known bias by comparing the read bias to the known bias. The deviation module 404 may compare the read bias to the known bias by counting the number of binary ones and the number of binary zeroes in the data set to determine the ratio of binary ones and binary zeroes in the data set and comparing that ratio to a ratio of the known bias. In a further embodiment, the deviation module 404 may search for and/or count the occurrences of an expected pattern or other expected attribute of the known bias and compare the results of a similar search and/or count in the data set to the expected attribute. In certain embodiments, the ECC decoder 322 indicates to the deviation module 404 that the read bias of the data set deviates from the known bias by providing an error bias for the data set to the configuration module 352, or the like.
In embodiments where the known bias includes a pattern of bits, multi-bit binary symbols, or the like, the deviation module 404 may perform a transform on bits of the data set, may analyze a subset of bits of the data set, or the like to determine whether the read bias of the data set deviates from the known bias. For example, the deviation module 404 may perform a transform based on an encoding type used for storage cells of the solid-state storage media 110, such as a Gray code encoding type, a binary code encoding type, or the like. The transform, in certain embodiments, may be based on a physical and/or electrical architecture of the storage cells of the storage media 110.
For example, as described below with regard to
Thus, the MSB and LSB in the same multi-level storage cell may have different addresses in the storage device 102. In certain embodiments, the upper page includes the MSBs of a plurality of multi-level storage cells, and the lower page includes the LSBs of the same multi-level storage cells. Writes directed to the upper page may therefore cause changes only in the MSBs of the associated multi-level storage cells, while writes directed to the lower page cause changes only in the LSBs of the associated multi-level storage cells.
As described in greater detail below with regard to
The deviation module 404, in one embodiment, checks the read bias of each data set that the data set read module 402 reads. For example, if the data set read module 402 uses the monitor module 418, the deviation module 404 may monitor the read biases of data sets regularly as they are read from the solid-state storage media 110. The monitor module 418, in one embodiment, may compare read biases of each data set that is requested by a client. In a further embodiment, the monitor module 418 may check read biases of requested data sets for example at regular intervals, and/or in response to a command, or the like. In another embodiment, if the data set read module 402 uses the read error module 420, the deviation module 404 may check the read bias of a data set in response to a data error, as part of a testing operation, or the like.
In one embodiment, the direction module 406 determines a direction of deviation for the data set. The direction of deviation, in one embodiment, is a difference between the read bias of the data set and the known bias. The direction or difference may be represented as a value, a sign (i.e. positive or negative), a relationship (i.e. greater than, less than), a direction (i.e. up, down), or the like. The direction module 406, in certain embodiments, may determine a direction of deviation based on an encoding type used for storage cells of the solid-state storage media 110, based on a physical and/or electrical architecture of the storage cells of the storage media 110, or the like. For example, the direction module 406 may examine the bias deviation in the data set to determine a direction of deviation based on a storage media type (2-bit MLC, 3-bit MLC, n-bit-MLC), which page of a multi-phase programming model was read, an encoding type for the solid-state storage media 110 (such as a Gray code encoding type, a binary code encoding type, or the like), and/or a magnitude of the determined deviation.
The direction module 406, in one embodiment, may determine the direction by subtracting a ratio, proportion, or other representation of the known bias from a representation of the read bias of the data set. For example, in one embodiment, the direction module 406 may subtract the proportion of binary ones, zeroes, multi-bit binary symbols, or the like that are expected based on the known bias from the proportion of binary ones, zeroes, multi-bit binary symbols, or the like that are in the data set. Depending on whether ratios of binary ones are compared or ratios of binary zeroes are compared and whether a high voltage represents a binary one or a binary zero, or other specific architectures of the storage cells, the direction module 406 may invert the difference or perform another transform to determine the direction.
In embodiments where an error bias from the ECC decoder 322 is available, the direction module 406 may determine the direction of deviation based on one or more bits of the data set that are in error, as indicated by the error bias. In other embodiments, as described above with regard to
In one embodiment, a binary zero is represented by a voltage below the read voltage threshold and a binary one is represented by a voltage above the read voltage threshold. In one example, a data set is stored with a known bias of 0.5, representing that the expected bias of the data set should be one half binary ones, or DC balanced. In this example, the data set is read from the storage cells and the data set has a read bias of 0.7, meaning that seventy percent of the data bits are binary ones. To determine the direction, in one embodiment, the direction module 406 subtracts the expected bias, 0.5, from the read bias of the data set, 0.7, for a direction of 0.2. The direction may be the entire result (i.e. “0.2”), the sign of the result (i.e. “positive”), a relationship (i.e. “greater than”), a direction, (i.e. “up”), or another indicator that represents the difference between the expected bias of 0.5 and the read bias of 0.7.
In another example, if the read bias of the data set is 0.3, meaning that thirty percent of the data bits are binary ones, the direction module 406, in one embodiment, would subtract the expected bias, 0.5, from the read bias of the data set, 0.3, for a difference of −0.2. In this example, the direction would be the opposite of the first example, i.e. “−0.2,” “negative,” “less then,” “down,” or the like.
Because the expected bias is known, comparing a read bias relative the known bias indicates that certain bits which should have satisfied the known bias presently do not, which may be due to a data error or due to changes in the voltage level stored in the storage cells after they were written. In addition, determining that the difference is positive or negative indicates whether the read voltage should be increased or decreased such that a re-read of the data set will result in a read bias that is the same as, or comes closer to the known bias. In one embodiment, the configuration module 352 adjusts the read voltage level in the same direction as the direction indicated by the direction module 406.
Advantageously, having an indication as to which direction to adjust the read voltage threshold provides a significant reduction in time and resources needed to identify a new adjusted read voltage level. If the direction in which to make a read voltage threshold was unknown, identifying a new read voltage threshold may require a labor and time intensive process of trial and error as different possible read voltage thresholds are set and then tested and then adjusted as needed. The process may be needed to find a read voltage threshold that results in a re-read of the data packet substantially matching the known bias.
In one embodiment, the adjustment module 408 adjusts a read voltage threshold for the storage cells of the solid-state storage media 110 based on the direction of deviation that the direction module 406 determines. The adjustment module 408, in one embodiment, may adjust the read voltage threshold in the direction of deviation, away from the direction of deviation, or the like. For example, in one embodiment, the adjustment module 408 may raise the read voltage threshold from a previous read voltage threshold in response to the direction module 406 detecting more binary ones than expected in the known bias and lower the read voltage threshold in response to fewer binary ones than expected. While the relative directions may change based on characteristics of the storage cells of the solid-state storage media 110 and the storage scheme employed, the adjustment module 408 adjusts the read voltage threshold to correct or compensate for the difference determined by the direction module 406.
In a further embodiment, the adjustment module 408 determines an amount to adjust the read voltage threshold based on an amplitude of the direction or amplitude of the difference determined by the direction module 406. In another embodiment, the adjustment module 408 may scale or otherwise adjust the amplitude from the direction module 406 and adjust the read voltage threshold the adjusted amount. For example, the adjustment module 408, in one embodiment, may adjust the read voltage threshold by several adjustment levels in a single adjustment, based on the amplitude of the direction. In a further embodiment, the adjustment module 408 may select an amount to adjust the read voltage threshold based on additional factors such as age, amount of wear, usage history, error history, or other aspects of the solid-state storage media 110. As described above with regard to
In another embodiment, the adjustment module 408 uses a search algorithm to determine the read voltage threshold based on the direction of deviation. For example, the range of voltages in the direction of deviation from the current read voltage threshold may be the search space for the search algorithm. The adjustment module 408, in one embodiment, may use a linear search, a binary search, or the like to determine the read voltage threshold. To check each step as part of the search algorithm, the data set read module 402 may re-read the data set in response to each adjustment, and the deviation module 404 may re-determine whether the read bias of the re-read data set deviates from the known bias. The direction module 406 may re-determine a direction of deviation for the re-read data set to further the search. The adjustment module 408 may iteratively readjust the read voltage threshold based on the re-determined direction of deviation until the deviation module 404 determines that the read bias of a re-read data set does not deviate from the known bias, or until each of the read voltage threshold level has been tested, and/or until the data set can be corrected using ECC checkbits, or the like.
In one embodiment, the adjustment module 408 stops readjusting a read voltage threshold once a retry threshold is satisfied. For example, if the ECC decoder 322 cannot correct a data error and/or if the read bias for the data set continues to deviate from the known bias when a retry threshold for the data set is satisfied, the adjustment module 408 may cease making adjustments to the read voltage threshold. The retry threshold may be selected based on a set of possible read voltage threshold levels, or the like. In one embodiment, a retry threshold sets a number of times which the adjustment module 408 may adjust a read voltage threshold. In another embodiment, a retry threshold may set an amount of time in which the adjustment module 408 may make read voltage threshold adjustments. The solid-state storage controller 104, in certain embodiments, may take further remedial action in response to the retry threshold being satisfied, such as retiring the storage cells associated with the data set, logically replacing the storage cells associated with the data set, or the like.
In one embodiment, the adjustment module 408 does not adjust a read voltage threshold, even if the deviation module 404 determines that the read bias of a data set deviates from the known bias, a data error has occurred, a retry threshold has not been met, or the like. The adjustment module 408, in certain embodiments, may selectively adjust a read voltage threshold based on one or more risk factors associated with an adjustment to a grouping of storage cells. For example, risk factors may include an error rate for the grouping of storage cells (such as an UBER or the like), an erase cycle count for the grouping of storage cells, a storage request latency for the grouping of storage cells (such as an average, maximum, or other storage request execution latency), an age of the grouping of storage cells, a number of previous adjustments to a read voltage threshold of the grouping of storage cells, and/or other potential risk factors. In one embodiment, the adjustment module 408 may cancel or delay an adjustment to a read voltage threshold in response to one or more risk factors satisfying a risk threshold. In a further embodiment, the solid-state storage controller 104 may take further remedial action in response to one or more risk factors satisfying a risk threshold.
The adjustment module 408, in one embodiment, adjusts the read voltage threshold using a procedure or command provided by a manufacturer of the solid-state storage media 110. For example, in one embodiment, the adjustment module 408 may adjust the read voltage threshold by writing a value to a settings register of the solid-state storage media 110, sending a read voltage threshold parameter to the solid-state storage media 110, or otherwise communicating an adjustment to a read voltage threshold to the solid-state storage media 110. The adjustment module 408 may communicate the adjustment as an absolute value of a read voltage threshold, an amount to adjust the read voltage threshold, or the like. In a further embodiment, the solid-state storage media 110 provides a plurality of discrete levels (i.e. between 2 and 15 different levels) to which the read voltage threshold may be adjusted. In other embodiments, the magnitude of a read voltage threshold adjustment may be defined or recommended by a manufacturer or vendor of the solid-state storage media 110.
The adjustment module 408, in one embodiment, adjusts the read voltage threshold individually for a die, chip, PEB, or other discrete segment of the solid-state storage media 110. The adjustment module 408, in a further embodiment, adjusts multiple read voltage thresholds for each storage cell. For example, in one embodiment, the storage cells of the solid-state storage media 110 are MLC storage cells, with multiple read voltage thresholds per cell (i.e. a 2 bit MLC storage cell may have three distinct read voltage thresholds). The adjustment module 408 may move each of the multiple read voltage thresholds together or it may move them independently.
In embodiments where the storage cells have multiple read voltage thresholds, each read voltage threshold is separated by a separation distance. In one embodiment, the separation distances are uniform between each read voltage threshold. In a further embodiment, the adjustment module 408 adjusts the multiple read voltage thresholds with a single command or procedure and the separation distances between the multiple read voltage thresholds scale with the adjustment. For example, in one embodiment, the separation distances between read voltage thresholds may increase with larger read voltage thresholds and decrease with lower read voltage thresholds. Scaling the separation distances between read voltage thresholds upon adjustment, in one embodiment, provides a more even distribution of read voltage thresholds, so that the ranges of voltages at the ends of the ranges are not reduced or enlarged while middle ranges remain the same.
In one embodiment, the persistence module 410 stores a state of the read voltage threshold. The persistence module 410, in one embodiment, is part of the solid-state storage controller 104. The persistence module 410, in another embodiment, may send the read voltage threshold to the solid-state storage media 110 with each read operation. In a further embodiment, the persistence module 410 is part of the solid-state storage media 110, causing the solid-state storage media 110 to retain adjustments to the read voltage thresholds that the adjustment module 408 makes. The persistence module 410, in one embodiment, stores multiple read voltage thresholds, each read voltage threshold for a different segment or grouping of storage cells of the solid-state storage media 110.
In one embodiment, a manufacturer of the solid-state storage media 110 provides a command or procedure to adjust a read voltage threshold for a predefined grouping of storage cells, such as a chip, physical erase block, physical page, or a die. In a further embodiment, the persistence module 410 stores read voltage thresholds for sub-groupings of storage cells that are smaller than the predefined groupings of storage cells for which the adjustment module 408 can make adjustments using the manufacturer provided command or procedure. The adjustment module 408 may then, in another embodiment, readjust the read voltage threshold when a data set is read from a sub-grouping based on the read voltage thresholds that the persistence module 410 stores. Examples of sub-groupings may include PEBs, pages, ECC chunks, or other physical or logical divisions of a grouping of storage cells.
For example, in response to a read request for a data set from a first sub-grouping of storage cells, the adjustment module 408 may adjust the read voltage threshold of the entire grouping of storage cells to a level that the persistence module 410 stores for the first sub-grouping. In response to a read request for a data set from a second sub-grouping, in one embodiment, the adjustment module 408 may readjust the read voltage threshold for the entire grouping to a level that the persistence module 410 stores for the second sub-grouping. This allows the configuration module 352 to adjust the read voltage thresholds for the solid-state storage media 110 at a finer scope than may be provided for in commands or procedures available for the solid-state storage media 110. For example, a manufacturer may provide a command, procedure, or methodology for adjusting a read voltage threshold for a die, chip, or other grouping of storage cells and the adjustment module 408 may adjust read voltage thresholds for individual PEBs or other sub-groupings in accordance with that command procedure or methodology.
In one embodiment, the configuration module 352 processes the data set in response to an uncorrectable (meaning herein uncorrectable by the ECC decoder 322, as discussed herein a correction may be possible after an adjustment of the read voltage threshold) data error, as described above, and adjusts the read voltage threshold one or more times until the data error is no longer uncorrectable and can be repaired using ECC checkbits for the data set. In one embodiment, the ECC module 412 cooperates with the ECC decoder 322 to determine whether or not the ECC decoder 322 can correct an error in the data set. Alternatively, the configuration module 352 cooperates with the ECC decoder 322 to determine whether or not the ECC decoder 322 can correct an error in the data set.
The configuration module 352, in one embodiment, repeats the processing steps described above until the ECC module 412 determines that the ECC decoder 322 can correct the error. For example, in a further embodiment, the data set read module 402, the deviation module 404, the direction module 406, and the adjustment module 408 may repeatedly read the data set, determine that the read bias for the data set deviates from the known bias, determine the direction of deviation for the data set, and adjust the read voltage threshold as described above until the ECC module 412 determines that the ECC decoder 322 can correct the error.
As described in greater detail with regard to
In a further embodiment, the ECC module 412 uses ECC checkbits to determine in which die, chip, channel, storage element, PEB, or other grouping of storage cells of the solid-state storage media 110 an uncorrectable error has occurred. The ECC module 412, in one embodiment, verifies data sets of each grouping of storage cells using ECC checkbits to determine which particular grouping from a set of groupings of storage cells have uncorrectable errors. The configuration module 352, in one embodiment, adjusts one or more read voltage thresholds in the particular groupings of storage cells with an uncorrectable error.
In one embodiment, the distribution module 414 determines that the read bias of the data set is within an expected distribution of the known bias, and that no additional adjustments of the read voltage threshold should be made. In a further embodiment, the data set read module 402, the deviation module 404, the direction module 406, and the adjustment module 408 continue to re-read the data set with a new read voltage threshold, re-determine that the read bias for the data set deviates from the known bias, re-determine the direction of deviation for the data set, and readjust the read voltage threshold until the distribution module 414 determines that the read bias of the data set is within the expected distribution.
The distribution module 414, in one embodiment, may cooperate with or be integrated with the deviation module 404. In one embodiment, the configuration module 352 uses either the ECC module 412 or the distribution module 414 to determine when adjustment of the read voltage threshold should be made or is complete. In a further embodiment, the distribution module 414 compares read biases of data sets from several dies, chips, channels, storage elements, PEBs, or other grouping of storage cells of the solid-state storage media 110 to the distribution of the known bias to determine in which grouping of storage cells an error has occurred, and the configuration module 352 adjusts one or more read voltage thresholds in a grouping of storage cells with an error.
In one embodiment, the ECC module 412 and/or the distribution module 414 cooperate with the data set source module 422. The data set source module 422, in one embodiment, determines from which specific grouping of storage cells the data set was read. For example, the data set source module 422 may determine which die, chip, channel, storage element, PEB, or other grouping of storage cells is the source of the data set. In one embodiment, the data set source module 422 determines from which specific grouping of storage cells the data was read in response to the deviation module 404, the ECC module 412, and/or the distribution module 414 determining that the data set has a read bias that deviates from a known bias, has a data error, or the like.
In one embodiment, the data set source module 422 determines from which specific grouping of storage cells the data set was read based on a position of the data set within a sequence of data sets. For example, in one embodiment, the solid-state storage media 110 may comprise a plurality of groupings of storage cells, and each grouping of storage cells may be read in parallel during a read operation. The data set source module 422, in one embodiment, may use known information about how the write data pipeline 106 and/or the read data pipeline 108 processes data, and known information about the plurality of groupings of storage cells, to determine from which grouping of storage cells the data set was read.
For example, in one embodiment the write data pipeline 106 and the read data pipeline 108 may each have a 64 bit (8 byte) data path, the solid-state storage media 110 may comprise a 24 die wide array, and 8 bytes may be read in parallel from each of the 24 dies during a read operation, for a total of 192 bytes per read operation. Based on this information, the data set source module 422, in one embodiment, can determine from which die or other grouping of storage cells, a data set was read based on the position of an 8 byte data set within the 192 bytes.
The data set source module 422, in a further embodiment, may count or otherwise track the number of data sets processed as part of a read operation to determine the position of the data set in the sequence of data sets. For example, 8 bytes may be read in sequence from the 24 die starting with a first die, thus if the ECC module 412 and/or the distribution module 414 detects a read bias deviation or a data error during operations on the fifth 8 byte set of data, the data set source module 422 identifies that this 8 byte set of data came from the fifth die of the 24 die.
By using the position of the data set in a sequence of data sets and other known information, the data set source module 422, in one embodiment, can determine the grouping of storage cells from which the data set was read without using an identifier or other external information. Identifying the die, chip, channel, PEB, or other grouping of storage cells that exhibit the read bias difference permits prompt remedial actions to be taken such as changing the read voltage threshold, logical swapping of the grouping of storage cells with a reserved grouping, and other forms of remedial action.
In one embodiment, the proactive configuration module 424 improves the utility of the solid-state storage media 110 by proactively setting and adjusting configuration parameters for storage cells of the solid-state storage media 110. By determining configuration parameters proactively before an error occurs, the proactive configuration module 424 prevents certain errors from occurring, without the performance penalty of retrying reads or performing other remedial measures for the prevented errors. The proactive configuration module 424, in certain embodiments, optimizes configuration parameters for a use case of the solid-state storage device 102 to optimize storage cells for the use case instead of using default parameters.
As described above, a configuration parameter is a parameter of a set of storage cells that is modifiable by way of an interface, such as a read threshold, a write or program threshold, an erase threshold, or the like. An interface for modifying a configuration parameter may include a programmable data register, a command interface of a control bus for the solid-state storage media 110, an API of a device driver of the solid-state storage device 102, a control parameter for the solid-state storage controller 104, or the like.
The proactive configuration module 424 references one or more storage media characteristics for a set of storage cells to determine a configuration parameter for the set of storage cells. A storage media characteristic is a statistic, heuristic, or other descriptor associated with an attribute of the solid-state storage media 110. A storage media characteristic for a set of storage cells may be substantially static or may be dynamic and change over time. A storage media characteristic, in one embodiment, includes or relates to a make, a model, a manufacturer, a product version, or the like for the solid-state storage device 102 and/or for the solid-state storage media 110. In another embodiment, a storage media characteristic describes an attribute or statistic for a set of particular storage cells, such as a program/erase cycle count for the set of storage cells, a read count for the set of storage cells, a retention time since a previous write for the set of storage cells, an error statistic for the set of storage cells, or the like. A storage media characteristic, in a further embodiment, may include or relate to an environmental condition or a use of the solid-state storage device 102 and/or of the solid-state storage media 110, such as a temperature, a use case (e.g. a cache use case, an archival use case, a server use case, an enterprise use case, a consumer use case, etc.), or the like.
The proactive configuration module 424, in response to determining a configuration parameter for a set of storage cells, configures the set of storage cells to use the determined configuration parameter. The proactive configuration module 424 may periodically update storage media characteristics for a set of storage cells, update a configuration parameter for the set of storage cells, and reconfigure the set of storage cells to use the updated configuration parameter. The proactive configuration module 424 may configure storage cells with configuration parameters during execution of input/output operations, during a startup operation, in response to a background scan of a set of storage cells indicating a changed storage media characteristic, or the like.
In certain embodiments, the proactive configuration module 424 configures storage cells independently of the adjustments described above with regard to the adjustment module 408. For example, the proactive configuration module 424 may be separate from the configuration module 352, the proactive configuration module 424 may be part of a storage controller 104 without a configuration module 352, or the like. In other embodiments, the adjustment module 408 and the proactive configuration module 424 may cooperate. For example, the adjustment module 408 may make closed loop feedback based adjustments to one or more configuration parameters that the proactive configuration module 424 has set using an open loop model, or the like.
In one embodiment, the write voltage module 416 sets a write voltage level for writing data to the storage cells of the solid-state storage media 110. The write voltage level is a programming voltage that specifies the minimum or maximum voltage used to program or change a state of a storage cell, a step magnitude for an incremental step pulse programming operation, a maximum number of iterations for an incremental step pulse programming operation, a program verify threshold for a program operation, an initial bias for an incremental step pulse programming operation, or the like. In one embodiment, the write voltage module 416 may be integrated with the configuration module 352 and/or the proactive configuration module 424.
For example, for NAND flash solid-state storage, the write voltage and/or other program related configuration parameters, changes the state of a storage cell from a binary one to a binary zero. The write voltage module 416, in one embodiment, writes known patterns to the storage cells, then reads the pattern back determining the read voltage threshold, and adjusts the write threshold until the desired read threshold is met. The write voltage module 416, in a further embodiment, adjusts the write voltage level based on a mathematical model that specifies write voltage level values based on endurance and data retention requirements of a storage cell relative to an age of the storage cell. In one embodiment, the age of the storage cell is computed in terms of program and erase cycles. The write voltage module 416, in one embodiment, performs a test write to one or more storage cells, detects the read voltage of at least one of the storage cells, and adjusts the write voltage level until the read voltage meets a threshold value. The write voltage module 416, in a further embodiment, performs the test write by writing a data set with a known bias to the storage cells, and tests the read voltage by determining if a read bias of the read data set deviates from the known bias.
The write voltage module 416, in one embodiment, may begin with a minimum write voltage, and increase the write voltage until the read voltage meets a threshold value. In a further embodiment, the write voltage module 416 may begin with a maximum write voltage, and decrease the write voltage until the read voltage meets a threshold value. The write voltage module 416, in one embodiment, may select a write voltage level that balances the time to program the storage cells with a desired endurance and/or data retention for the storage cells.
Proactive Configuration
In one embodiment, the media characteristic module 502 references one or more storage media characteristics for a set of storage cells of the solid-state storage media 110. The media characteristic module 502 may determine one or more storage media characteristics itself, may receive storage media characteristics from another module, may retrieve storage media characteristics from a storage media characteristic repository, or the like. As described above, a storage media characteristic is a statistic, heuristic, or other descriptor associated with an attribute of the solid-state storage media 110. Storage media characteristics may include and/or relate to a make, a model, a manufacturer, a product version, or the like for the solid-state storage device 102 and/or for the solid-state storage media 110; an attribute or statistic for a set of storage cells; an environmental condition or a use case of the solid-state storage device 102 and/or of the solid-state storage media 110; and/or another statistic, heuristic, or other descriptor for an attribute of the solid-state storage media 110.
A storage media characteristic for a set of storage cells affects or informs the determination of a configuration parameter for the set of storage cells. In one embodiment, the storage media characteristics include a program/erase cycle count for a set of storage cells. In another embodiment, the storage media characteristics include a read count for a set of storage cells. The storage media characteristics, in a further embodiment, include a retention time since a previous write for a set of storage cells. In an additional embodiment, the storage media characteristics include a temperature for a set of storage cells. The storage media characteristics, in certain embodiments, include a use case for a set of storage cells. In another embodiment, the storage media characteristics include an error statistic for a set of storage cells, such as an UBER or the like. In a further embodiment, the storage media characteristic may include previous or historical configuration parameters for a set of storage cells, configuration parameters or storage media characteristics for other sets of storage cells, or the like.
The media characteristic module 502, in certain embodiments, manages the collection of and/or maintenance of storage media characteristics. The media characteristic module 502 may maintain storage media characteristics in and/or retrieve storage media characteristics from a storage media characteristic repository. One example of a storage media characteristic repository is described in greater detail below with regard to
In one embodiment, the media characteristic module 502 may be similar to, may work with, and/or may be integrated with the device factor module 354 described above with regard to
In one embodiment, the configuration parameter module 504 determines a configuration parameter for a set of storage cells based on one or more storage media characteristics from the media characteristic module 502 for the set of storage cells. As described above, a configuration parameter is a parameter of a set of storage cells that is modifiable by way of an interface. Configuration parameters may relate to writing to or programming storage cells, reading from storage cells, erasing storage cells, and/or to another parameter for storage cells. The configuration parameter module 504 may determine a configuration parameter as an absolute data value, as an offset or adjustment to a data value, or as another parameter with which the storage cell configuration module 506 can configure a set of storage cells, as described below.
One embodiment of a configuration parameter for reading from storage cells is a read threshold such as a read voltage threshold, a resistivity threshold, or the like. Various embodiments of configuration parameters for writing/programming storage cells include a step magnitude for an incremental step pulse programming operation, a maximum number of iterations for an incremental step pulse programming operation, a program verify threshold for a program operation, an initial bias for an incremental step pulse programming operation, or the like. A configuration parameter for erasing storage cells, in certain embodiments, may include a step magnitude for an incremental step pulse erase operation, a maximum number of iterations for an incremental step pulse erase operation, an erase verify threshold for an erase operation, an initial bias for an incremental step pulse erase operation, or the like. One of skill in the art, in light of this specification, will recognize other configuration parameters for storage cells that may be modifiable by way of an interface.
The configuration parameter module 504 may base a configuration parameter on one or more storage media characteristics by entering the one or more storage media characteristics into an equation, into a lookup table (“LUT”), into a matrix, or the like; by performing a predefined transform or operation on the one or more storage media characteristics; or by otherwise referencing and/or manipulating the one or more storage media characteristics to determine the configuration parameter. A configuration parameter equation, LUT, matrix, or the like may be based on empirical data, such as test data, historical data, and the like. A design engineer or the like, in one embodiment, may test sets of storage cells with various storage media characteristics, such as solid-state storage media from various manufacturers or the like, and determine optimal configuration parameters for storage cells with the various storage media characteristics. For example, an equation, LUT, matrix, or the like may indicate that solid-state storage media 110 from manufacturer X tends to have Y amount of natural drift in cell values after 1,000 program/erase cycles such that a read threshold can be increased by Z volts to compensate, or the like.
In one embodiment, the storage media characteristics for a set of storage cells include a temperature. A temperature for a set of storage cells may affect the speed of the effects of one or more other storage media characteristics on the set of storage cells. For example at higher temperatures, the rate of change for storage media characteristics relating to error statistic such as Raw Bit Error Rates (RBER) and data retention times may increase and certain adjustments to configuration parameters may mitigate the effect. In certain embodiments, the configuration parameter module 504 may adjust or scale a configuration parameter, a storage media characteristic, or the like by a temperature to compensate for the effects of temperature, normalizing the data for temperature. The temperature for a set of storage cells may be an average temperature, a temperature over a sliding window, a current temperature, a temperature for the solid-state storage device 102, or another temperature measurement associated with one or more sets of storage cells.
The one or more storage media characteristics, in one embodiment, indicate to the configuration parameter module 504 a trend, an optimization, or the like for a configuration parameter and the configuration parameter module 504 determines a configuration parameter to satisfy the trend or optimization. For example, a magnitude of a program/erase cycle count, a read count, a UBER, or another storage media characteristic may indicate an amount that a read voltage has drifted, and the configuration parameter module 504 may proactively determine a read voltage threshold or other configuration parameter based on the storage media characteristic, without direct feedback from the storage cells, such as a read, a read retry, or the like.
In one embodiment, the configuration parameter module 504 maintains configuration parameters for sets of storage cells of different storage regions or storage divisions of the solid-state storage media 110 in a configuration parameter repository. One example of a configuration parameter repository is described in greater detail below with regard to
In certain embodiments, the configuration parameter module 504 may determine a configuration parameter for one set of storage cells based on a target set of storage cells. The target set of storage cells may have known and/or controlled use characteristics (e.g. storage media characteristics or the like) that the configuration parameter module 504 uses to determine a configuration parameter for another set of storage cells. In particular, the configuration parameter module 504 may compare storage media characteristics of the target set of storage cells to storage media characteristics of a set of storage cells presently being configured. Such a comparison can be used to further optimize the determined configuration parameter for the set of storage cells. The target set of storage cells may store known data, such as metadata, system data, a known pattern of data, or the like, and the configuration parameter module 504 may determine a configuration parameter for another set of data based on the known data.
In another embodiment, the configuration parameter module 504 determines a configuration parameter for a set of storage cells based on a determined configuration parameter for a target set of storage cells, based on one or more storage media characteristics for a target set of storage cells, or the like. For example, the configuration parameter module 504 may use a configuration parameter for a target set of storage cells as a configuration parameter for another set of storage cells, may adjust a configuration parameter of a target set of storage cells for use in determining the configuration parameter for another set of storage cells, may use storage media characteristics for a target set of storage cells to determine a configuration parameter for another set of storage cells, or the like. In this manner, the target set of storage cells serves as a control group for use in managing other sets of storage cells. The target set of storage cells may be used in certain embodiments in a manner analogous to how “system tracks” have been used in hard disk drive technologies to make modifications to configuration parameters over the life of the storage device 102. In a further embodiment, the configuration parameter module 504 compares one or more storage media characteristics for a set of storage cells to one or more storage media characteristics for a target set of storage cells and determines a configuration parameter for the set of storage cells based on a difference between the storage media characteristics.
The configuration parameter module 504, in certain embodiments, bases a configuration parameter for a set of storage cells on a target set of storage cells to bootstrap the configuration parameter in response to a lack of known storage media characteristics for the set of storage cells. The configuration parameter module 504 may bootstrap a configuration parameter for a set of storage cells during a startup operation or another operation where storage media characteristics for the set of storage cells may not yet be available, but storage media characteristics or other data may be available for a target set of storage cells. For example, metadata stored in a metadata region of the solid-state storage media 110 may have a known or controlled program/erase count and the configuration parameter module 504 may base a configuration parameter for a region of the solid-state storage media 110 storing user data on the known or controlled program/erase count for the metadata region.
In one embodiment, the storage cell configuration module 506 configures a set of storage cells to use a configuration parameter that the configuration parameter module 504 determines for the set of storage cells. The storage cell configuration module 506 uses an interface of a set of storage cells to configure the set of storage cells. The interface may comprise a publicly known interface or a proprietary interface. The configuration module 506 may configure a set of storage cells by setting a data register, by sending a command over a command interface of a control bus for the solid-state storage media 110, by calling an API of a device driver of the solid-state storage device 102, by setting a control parameter for the solid-state storage controller 104, or otherwise configuring the set of storage cells. The storage cell configuration module 506 may use particular command instructions, a particular sequence of command instructions, and/or use particular parameters, register settings, or other differences from regular commands (general purpose commands) used to interface with the set of storage cells. The storage cell configuration module 506 may receive configuration parameters from the configuration parameter module 504, may retrieve configuration parameters from a configuration parameter repository, or the like.
The storage cell configuration module 506, in one embodiment, configures a set of storage cells to use a determined configuration parameter in response to a trigger. The trigger, in certain embodiments, is selected based on an architecture of the solid-state storage device 102 and/or of the solid-state storage media 110. For example, certain solid-state storage device 102 and/or solid-state storage media 110 may retain a configuration parameter across multiple input/output operations, while another solid-state storage device 102 and/or solid-state storage media 110 may require a configuration parameter to be set with each input/output operation, or the like. The storage cell configuration module 506 may configure a set of storage cells once during initialization of the solid-state storage media 110, dynamically with each command issued to the set of storage cells, during operation of the solid-state storage media 110 in response to events or time intervals, in response to another trigger, or the like.
In one embodiment, a trigger for the storage cell configuration module 506 includes a change in a storage media characteristic for a set of storage cells, a change of a predefined magnitude in a storage media characteristic for the set of storage cells, or the like, and the storage cell configuration module 506 configures the set of storage cells in response to a change in the storage media characteristics. In another embodiment, a trigger for the storage cell configuration module 506 includes an input/output request for a set of storage cells, such as a read request, a write request, an erase request, or the like. For example, in certain embodiments, the storage cell configuration module 506 may configure a set of storage cells to use a read configuration parameter in response to a read request for the storage cells, may configure a set of storage cells to use a write configuration parameter in response to a write request for the storage cells, may configure a set of storage cells to use an erase configuration parameter in response to an erase request, or the like.
In a further embodiment, a startup operation for the solid-state storage device 102, a regular shutdown operation for the solid-state storage device 102, or the like is a trigger for the storage cell configuration module 506 to configure one or more sets of storage cells. In certain embodiments, once the storage cell configuration module 506 configures a set of storage cells with a configuration parameter in response to a startup operation, the set of storage cells retain the configuration parameter until a shutdown operation and a subsequent startup operation, or the like. How a set of storage cells retain configuration parameters may vary depending on the type of configuration parameter, the architecture of the set of storage cells, and the like.
In one embodiment, the characteristic update module 508 updates one or more storage media characteristics for a set of storage cells in response to an update event for the set of storage cells. An update event is a trigger, in response to which, the characteristic update module 508 updates storage media characteristics. Certain storage media characteristics, such as a make, a model, a manufacturer, a product version, or the like of the solid-state storage device 102 and/or the solid-state storage media 110 may be substantially static, and the characteristic update module 508, in certain embodiments, may not update such storage media characteristics, may update such storage media characteristics less frequently, or the like. Other storage media characteristics, such as a program/erase cycle counts, read counts, retention times, temperatures, use cases, error statistics, and the like may be dynamic and change frequently.
In one embodiment, a background scan of the solid-state storage media 110 may be an update event. For example, the characteristic update module 508, may perform a background scan of the solid-state storage media 110 and update records of storage media characteristics for sets of storage cells in response to scanning the sets of storage cells during the background scan. In another embodiment, an input/output request for the set of storage cells or for a neighboring set of storage cells, such as a read request, a write request, an erase request, or the like, is an update event and the characteristic update module 508 updates storage media characteristics for a set of storage cells in response to the input/output request. An update event for the characteristic update module 508, in a further embodiment, may include a startup operation and/or shutdown operation for the solid-state storage device 102. In certain embodiments, a garbage collection operation for a set of storage cells is an update event. For example, the characteristic update module 508 may update storage media characteristics for a set of storage cells as a garbage collection operation recovers storage capacity of the set of storage cells, or the like.
The characteristic update module 508, in one embodiment, updates storage media characteristics in cooperation with the media characteristic module 502, using the media characteristic module 502, or the like. In certain embodiments, the characteristic update module 508 may update storage media characteristics stored in a storage media characteristic repository, as described in greater detail below with regard to
In one embodiment, the configuration update module 510 updates a configuration parameter for a set of storage cells. The configuration update module 510, in certain embodiments, updates a configuration parameter in response to a change in one or more storage media characteristics corresponding to the configuration parameter. The characteristic update module 508 may notify the configuration update module 510 that the characteristic update module 508 has updated a storage media characteristic, the configuration update module 510 may periodically scan storage media characteristics for changes, the configuration update module 510 may check storage media characteristics for changes in response to a configuration trigger for a set of storage cells, or the like.
In certain embodiments, the configuration update module 510 updates a configuration parameter in response to a change in a storage media characteristic that is greater than a predefined change threshold. The configuration update module 510, in one embodiment, updates configuration parameters in cooperation with the configuration parameter module 504, using the configuration parameter module 504, or the like. The configuration update module 510, in another embodiment, may update configuration parameters stored in a configuration parameter repository, as described in greater detail below with regard to
In one embodiment, the adaptive configuration module 512 dynamically adjusts and adapts one or more configuration parameters, thresholds, management techniques, or the like for the solid-state storage device 102 and/or for the solid-state storage media 110. In certain embodiments, the adaptive configuration module 512 may adjust or adapt as the solid-state storage device 102 ages, as a use case for the solid-state storage device 102 changes, or the like. Examples of use cases may include a cache use case, an archival use case, a server use case, an enterprise use case, a consumer use case, or the like.
The adaptive configuration module 512, in one embodiment, bases adjustments or adaptations on a priori knowledge for the solid-state storage device 102, collected run-time statistics for the solid-state storage device 102, storage media characteristics for storage cells of the solid-state storage device 102, or the like. Unlike magnetic storage, media attributes for solid-state storage typically vary over a storage device's useful life. For example, storage regions of the solid-state storage media 110 may be periodically processed for storage capacity recovery or garbage collection to manage the impact of read disturbs and to ensure reliable data retention.
In solid-state storage media 110, an effect called read disturb can occur in unselected storage cells when adjacent storage cells are selected and read, causing charge to collect on the floating gates of the unselected storage cells making the unselected storage cells have an increased voltage that has not been deliberately applied. One approach to combating the effects of read disturb, is to move valid data out of the disturbed cells while the values in those cells are still determinable. The valid data may be re-written to a new physical location and the disturbed cells are erased to remove the effects of the read disturb. This approach is called a refresh and the time between refresh operations is referred to as a data refresh interval. A read disturb threshold is a number of reads of neighboring cells before remedial action is needed to mitigate the effects of read disturb. A data refresh interval at which storage regions are processed for storage capacity recovery and/or data refresh, that is appropriate for a solid-state storage device 102 near an end of life may be too aggressive for a solid-state storage device 102 at the beginning of use.
The adaptive configuration module 512, in various embodiments, may dynamically adjust or adapt a data refresh interval based on an age (in absolute time, in powered-on time, in an amount of user data written, or the like) of the solid-state storage device 102, a read disturb threshold (i.e. a number of read operations before data is refreshed to mitigate effects of read disturb) based on wear of the solid-state storage device 102, an erase block retirement policy based on an age of the solid-state storage device 102, a garbage collection method for the solid-state storage device 102 based on host workload, garbage collection by zone of the solid-state storage device 102 based on levels of extent activity to minimize stir between active and inactive data, scrubbing intervals to increase scrubbing as the solid-state storage device 102 ages, or the like.
The array 600 of storage elements 606, in one embodiment, includes N number of storage elements 606a, 606b, 606c, . . . 606n. Each storage element 606 may comprise a device, a chip, a portion of a chip, a die, or the like. In the depicted embodiment, the storage elements 606a-n form a bank 602a. The array 600, in one embodiment, includes several banks 602a . . . 602m. The banks 602a-m, in the depicted embodiment, include several channels 604a, 604b, 604c, . . . , 604n. In one embodiment, a packet or data set is written across the several channels 604a-n and data is read separately from each channel 604a-n and reassembled into the packet. In another embodiment, an ECC chunk 616, packet, or data set is written across the several channels 604a-n and data is read in parallel from all the channels 604a-n. One read operation on a bank 602a may read a whole ECC chunk 616, packet, or data set or a portion of an ECC chunk 616, packet, or data set that is reassembled into a whole ECC chunk 616, packet, or data set. In the depicted embodiment, each channel includes at least one storage element 606 in each bank 602.
Furthermore, in one embodiment each storage element 606 includes a physical erase block or “PEB” 608. For example, storage element one 606a includes PEB one 608a. A physical erase block is typically an erase block located on one die, chip, or other storage element 606. Each PEB 608 includes m physical pages 610. For example, PEB one 608a includes page 0610a . . . page m 614a. Each physical page 610a stores a portion of data (“D 0, D 1, . . . , D m”) 612 and ECC checkbits distributed with the data 612.
In one embodiment, a group of PEBs (PEB 1608a-PEB m 608m) forms a logical erase block (“LEB”). An LEB spans the array of N storage elements 600. Furthermore, in an embodiment, a logical page (“LP”) spans a plurality of physical pages 610 in a row. In another embodiment a logical page spans N storage elements 606a-n.
In one embodiment, the ECC is a block code that is distributed with the data. Furthermore, the data and the ECC may not align with any particular physical hardware boundary. As a result, error correction with the ECC codes is not dependent on a particular hardware configuration. Therefore, the ECC and corresponding data may form an ECC chunk 616 and the ECC chunk may be divided and stored on one or more of the N storage elements 606a-n. An ECC chunk 616 typically spans at least a portion of a plurality of physical pages 610 of a logical page where the data and ECC generated from the data 612a, 612b, . . . 612m are spread across the N storage elements 606a-n. In one embodiment, a LP includes a plurality of ECC chunks 616. A physical page 610 may contain one or more data bytes of the ECC chunk 616. An ECC chunk 616 may span multiple rows within a physical page 610 and a physical page 610 may include a plurality of ECC chunks 616.
Because, in the depicted embodiment, the ECC checkbits for the ECC chunk 616 are distributed across several storage elements 606a-n and channels 604a-n, when a data error occurs due to a read voltage shift in one or more of the storage elements 606a-n, the ECC module 412 may not be able to determine which storage elements 606 have an error that is correctable by adjusting the read voltage threshold. In one embodiment, the distribution module 414 determines which storage elements 606 or channels 604 have data with a read bias that is outside an expected distribution of the known bias, and the configuration module 352 adjusts the read voltage thresholds of the storage elements 606 determined by the distribution module 414.
In one embodiment, the deviation module 404, the ECC module 412, and/or the distribution module 414 determines that a data set has an error or a read bias that deviates from the known bias, and the data set source module 422 determines from which storage element 606 the data set was read. For example, in one embodiment, the array 600 may have 24 channels 604, and 8 bytes may be read in parallel from 24 storage elements 606 of a single bank 602 during a read operation for a total of 192 bytes per read operation. Based on this information, the data set source module 422, in one embodiment, can determine from which storage element 606 a data set was read based on the position of an 8 byte data set within the 192 bytes. In one embodiment, the 192 bytes comprise the ECC chunk 616.
By comparing read biases of data from each of the channels 604a-n to the known bias, the configuration module 352 can correct data errors that occur due to changes in read voltages for particular channel(s) even without the use of ECC checkbits. Without comparing the read biases of data from the channels 604a-n to the known bias, adjustment of the read voltage thresholds would require a large number of trial-and-error tests adjusting and testing every possible read voltage threshold adjustment for each possible combination of channels 604a-n. By comparing the read biases of data from the channels 604a-n to the known bias, the configuration module 352 can determine exactly which channel 604 to adjust. By determining the direction of deviation for those channels, the configuration module 352 further decreases the search space for the read voltage thresholds for those channels by half.
To illustrate the potential size of the search space for a suitable adjusted read voltage threshold, suppose an ECC chunk 616 (i.e. ECC code word—comprising both data and the corresponding ECC checkbits) is stored on the storage elements 606a-606n. Further suppose that the storage elements 606a-606n in a row of the array 600 that stores the ECC chunk 616 each have an independent adjustable read voltage threshold. For example, in one embodiment, the number of different combinations of read voltage threshold settings for the array 600 with η channels 604a-n, λ number of levels at which the read voltage threshold can be set per channel, and x number of channels that have a read voltage threshold that needs to be adjusted is given by equation 1:
f(x,η,λ)=(xη)·λx (1)
The number of different combinations of read voltage threshold settings for the array 600 with all permutations of up to η channels 604a-n, in one embodiment is given by equation 2:
g(x,η,λ)=Σi=1x(i,η,λ) (2)
Using equation 1, for example, if there are twenty-four channels 606a-n (η=24), eight possible read voltage threshold settings for each channel 606 (λ=8), and only two of the twenty-four channels 606a-n have read voltage thresholds that need to be adjusted (x=2), there are 17,644 total different combinations of read voltage threshold settings. If the number of channels 606 with read voltage thresholds that need adjusting increases to three, the number of different combinations increases to 1,036,288. The configuration module 352 drastically reduces these numbers by detecting which channels 606a-n have read voltage thresholds that need adjusting. In addition, comparing the known bias of the data on the media in a storage grouping to the current bias indicates the direction to adjust the read voltage thresholds. Knowing the direction in which to adjust the read voltage threshold greatly reduces the search space for a suitable voltage in the channels known to have a data error.
Consequently, the number of combinations that may need to be attempted changes from 17,644 where x=2 to 32 and from 1,036,288 where x=3 to 256, because the configuration module 352 uses the known bias to determine which channels have read voltage thresholds that need adjusting and the direction of the adjustment. However, each of these combinations may not need to be tried because as the adjustments are iteratively made, the known bias of the data continues to indicate which direction to make each subsequent adjustment, potentially cutting the search space at least in half with each iteration. Various search algorithms can be used to quickly identify a suitable adjusted read voltage threshold. (i.e. a binary search).
In one embodiment, the LSB corresponds to a lower page of data and the MSB corresponds to an upper page of data. In certain embodiments, the multi-level storage cell may adhere to a two-phase programming model, described below, which requires that the LSB be written to before the MSB can be written or vice versa. In another embodiment, the LSB and MSB may be programmed separately by the solid-state storage controller 104. Such an approach may be taken due to vendor or manufacturer requirements for page pairing (i.e., a LSB bit of MLC cell is paired with an MSB bit of a different MLC cell) and page addressing (i.e., LSB page must be programmed before the MSB page or vice versa). In certain instances, the LSB must be written before the MSB is written, the MSB must be written before the LSB is written, or the like.
In certain embodiments, the solid-state storage media 110 may employ a two-phase programming model. In such a model, a binary value is first written to the LSB by way of a first write command to the lower page. The write command causes the multi-level storage cell to move from its initial state (for example, a 11 state in L0) to an intermediate state (the lower-to-middle LM state—between L1 and L2) configured such that a 00 state is subsequently read. For example, writing a “0” to the lower page causes the multi-level storage cell to change from the L0 state (where both the LSB and the MSB are 1) to the L2 state (where the LSB is changed to a 0). A subsequent write of a “0” to the upper page moves the multi-level storage cell from the intermediate state (typically between the L1 state and the L2 state) to L2 state such that both bits of the MLC are “0”. Thus, in such an embodiment, two writes (one to the lower page and one to the upper page) are needed to move the multi-level cell from L0 to L2, since the cell transitions through the intermediate state and the MLC device requires that the lower page be programmed before the upper page and does not allow partial programming of a page without an intervening erase operation. Writing a “1” to either of the upper page or lower page will cause the MLC to transition to either L1 or L3 depending on the binary value of the lower page at the time. In addition, certain solid-state media vendors may impose a requirement that the lower page must be written to before the upper page, or the like. In other embodiments, the solid-state storage media 110 may employ a two-phase programming model where a binary value is first written to the MSB by way of a first write command to the upper page.
In one embodiment, the configuration module 352 adjusts one or more read voltage thresholds 662 based on a subset of binary data that multi-level storage cells store, such as just an upper page, just a lower page, or the like. In such embodiments, examining the state changes for the LSB bit(s) indicate the direction the voltage in the multi-level storage cell is changing. For both Gray code encoding (as depicted in
For certain types of multi-level storage cells, the middle read voltage threshold 662b and the adjacent L1 and L2 states may be more sensitive to read disturb or other factors that can cause read voltages to drift. Further, as described above, in certain embodiments, the LSB and the MSB of a single multi-level storage cell may represent data stored in different physical pages. Using a single bit from each of a plurality of multi-level storage cell as a data set, in one embodiment, may reduce a number of read operations to retrieve the data set. In other embodiments, use of a single bit from each of a plurality of multi-level storage cells in the lower page simplifies a process of detecting deviation and direction of a read bias from a known bias for multi-level storage cells.
In one embodiment, the direction module 406 determines a direction of deviation for a grouping of multi-level storage cells based on a data set that includes data from one or more lower pages of the multi-level storage cells. Because the lower pages include the LSBs, in certain embodiments, the direction module 406 determines that a read voltage threshold 662 deviates toward a larger read voltage in response to a difference between a read bias for the lower pages and a known bias for the lower pages indicating that storage cell values for the LSBs have transitioned from a binary one to a binary zero. For an LSB to transition from a binary one to a binary zero, a read voltage for a multi-level storage cell using the encoding model of
Similarly, in certain embodiments, the direction module 406 determines that a read voltage threshold 662 deviates toward a smaller read voltage in response to a difference between a read bias for the lower pages and a known bias for the lower pages indicating that storage cell values for the LSBs have transitioned from a binary zero to a binary one. For an LSB to transition from a binary zero to a binary one, a read voltage for a multi-level storage cell using the encoding model of
In another embodiment, the direction module 406 determines a direction of deviation based at least partially on an encoding type used for storage cells of the solid-state storage media 110, a physical and/or electrical architecture of the storage cells of the storage media 110, or the like. For example, based on the encoding model of
Using each bit stored in multi-level storage cells to determine a read voltage threshold adjustment, in certain embodiments, can increase the accuracy of the read voltage threshold adjustment, but may increase the number of read operations or add complexity to the determination. In one embodiment, if the ECC decoder 322 detects a data error in an upper page of a grouping of multi-level storage cells, the data set read module 402 retrieves one or more lower pages for the grouping and the configuration module 352 adjusts a read voltage threshold for the grouping based on the lower pages.
The adjusted configuration parameters 672a-c more closely match the actual distributions of storage cell states of
In one embodiment, the configuration module 352 determines the adjusted configuration parameters 672a-c reactively using the deviation module 404, the direction module 406, the adjustment module 408, or the like, as described above. In another embodiment, the configuration module 352 determines the adjusted configuration parameters 672a-c proactively using the proactive configuration module 424, based on storage media characteristics for a corresponding set of storage cells, as described above.
The media characteristic module 502 may store the storage media characteristic repository in one or more of a metadata area of the solid-state storage media 110, in volatile memory of the solid-state storage device 102 and/or of the computer 112, in a configuration file for the solid-state storage device 102 stored in nonvolatile storage of the computer 112, in dedicated non-volatile storage of the solid-state storage device 102, or the like. The media characteristic module 502 may store the storage media characteristic repository 702 and/or storage media characteristics in a single location, or may divide storage between multiple locations.
For example, in one embodiment, the media characteristic module 502 may access static storage media characteristics such as a make, a model, a manufacturer, a product version, or the like for the solid-state storage device 102 and/or the solid-state storage media 110 from nonvolatile storage of the solid-state storage device 102, such as in a programmable read only memory (“PROM”) or the like that is programmed by a manufacturer or vendor. The media characteristic module 502 may store dynamic storage media characteristics, such as a program/erase cycle counts, read counts, retention times, temperatures, use cases, error statistics, and the like in volatile memory of the solid-state storage device 102 and/or of the computer 112, metadata on the solid-state storage media 110, or the like. If the media characteristic module 502 stores at least a portion of the storage media characteristic repository 702 in volatile memory, in certain embodiments, the media characteristic module 502 may periodically save data of the storage media characteristic repository 702 to the solid-state storage media 110 or to other nonvolatile storage so that the media characteristic module 502 may rebuild a storage media characteristic repository 702 in response to a power failure, an improper shutdown, or the like.
Each entry 708 further includes storage media characteristics 704 for the corresponding storage media region 706. The storage media characteristics 704, in the depicted embodiment, include a program/erase (“P/E”) cycle count 704a, a read count 704b, a retention time 704c, a temperature 704d, and a bit error rate 704e. The characteristic update module 508 may cooperate with the media characteristic module 502 to update the storage media characteristic repository 702 as described above.
In the depicted embodiment, the P/E cycle count 704a varies between 0.7 k and 2.0 k, (i.e., between 700 and 2000, “k” representing 1000). Similarly, the read count 704b varies between 0.5 k and 4.1 k (i.e., between 500 and 4100). The retention time 704c varies from 10 min (minutes) to 100 min, and the temperature 704d varies from 43° C. (degrees Celsius) to 48° C. Lastly, the bit error rate 704(e) varies between 9.7E-5 (9.7 times 10 to the −5th power or 0.000097) and 2.5E-4 (2.5 times 10 to the −4th power or 0.00025). The depicted storage media characteristics 704 are representative examples, and are not limiting; in light of this disclosure it is clear that storage media characteristics 704 outside the depicted ranges are possible, as well as other types of storage media characteristics 704 not depicted in
While the configuration parameters 804 in the depicted embodiment are illustrated as read voltage threshold adjustments, as described above, in other embodiments, configuration parameters 804 may include resistivity thresholds, write or program thresholds, erase thresholds, and/or other modifiable parameters of the solid-state storage media 110. As described above, a configuration parameter 804 may include an absolute data value, an offset or adjustment to a data value, or another parameter. The configuration update module 510 may cooperate with the configuration parameter module 504 to update the configuration parameter repository 802 as described above.
Flow Chart
The configuration update module 510 determines 1006 whether or not there is a change in one or more storage media characteristics for the set of storage cells, from the characteristic update module 508 updating 1004 the one or more storage media characteristics or the like. If the configuration update module 510 determines 1006 that there is a change in the one or more storage media characteristics for the set of storage cells, the media characteristic module 502 references 1008 the one or more storage media characteristics for the set of storage cells and the configuration parameter module 504 and/or the configuration update module 510 determines/updates 1010 a configuration parameter for the set of storage cells. If the configuration update module 510 determines 1006 that there is no change in the one or more storage media characteristics for the set of storage cells, the method 1000 skips the referencing 1008 step and the determining/updating step 1010.
The storage cell configuration module 506 determines 1012 whether or not a configuration trigger has occurred for the set of storage cells. If the storage cell configuration module 506 determines 1012 that a configuration trigger has occurred, the storage cell configuration module 506 configures 1014 the set of storage cells to use the determined/updated 1010 configuration parameter and the method 1000 repeats. If the storage cell configuration module 506 determines 1012 that no configuration trigger has occurred, the method 1000 repeats.
The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5261068 | Gaskins et al. | Nov 1993 | A |
| 5438671 | Miles | Aug 1995 | A |
| 5701434 | Nakagawa | Dec 1997 | A |
| 5812457 | Arase | Sep 1998 | A |
| 5845329 | Onishi et al. | Dec 1998 | A |
| 5960462 | Solomon et al. | Sep 1999 | A |
| 6000019 | Dykstal et al. | Dec 1999 | A |
| 6170039 | Kishida | Jan 2001 | B1 |
| 6170047 | Dye | Jan 2001 | B1 |
| 6173381 | Dye | Jan 2001 | B1 |
| 6185654 | Van Doren | Feb 2001 | B1 |
| 6278633 | Wong et al. | Aug 2001 | B1 |
| 6330688 | Brown | Dec 2001 | B1 |
| 6356986 | Solomon et al. | Mar 2002 | B1 |
| 6370631 | Dye | Apr 2002 | B1 |
| 6385710 | Goldman et al. | May 2002 | B1 |
| 6412080 | Fleming et al. | Jun 2002 | B1 |
| 6418478 | Ignatius et al. | Jul 2002 | B1 |
| 6523102 | Dye et al. | Feb 2003 | B1 |
| 6567889 | DeKoning et al. | May 2003 | B1 |
| 6587915 | Kim | Jul 2003 | B1 |
| 6601211 | Norman | Jul 2003 | B1 |
| 6625685 | Cho et al. | Sep 2003 | B1 |
| 6655758 | Pasotti et al. | Dec 2003 | B2 |
| 6671757 | Multer et al. | Dec 2003 | B1 |
| 6683810 | Sakamoto | Jan 2004 | B2 |
| 6754774 | Gruner et al. | Jun 2004 | B2 |
| 6775185 | Fujisawa et al. | Aug 2004 | B2 |
| 6779088 | Benveniste et al. | Aug 2004 | B1 |
| 6785785 | Piccirillo et al. | Aug 2004 | B2 |
| 6795542 | St. Jean | Sep 2004 | B1 |
| 6807097 | Takano et al. | Oct 2004 | B2 |
| 6877076 | Cho et al. | Apr 2005 | B1 |
| 6880049 | Gruner et al. | Apr 2005 | B2 |
| 6883079 | Priborsky | Apr 2005 | B1 |
| 6938133 | Johnson et al. | Aug 2005 | B2 |
| 6975542 | Roohparvar | Dec 2005 | B2 |
| 6985996 | Nagshain | Jan 2006 | B1 |
| 7010652 | Piccirillo et al. | Mar 2006 | B2 |
| 7020758 | Fisk | Mar 2006 | B2 |
| 7043599 | Ware et al. | May 2006 | B1 |
| 7050337 | Iwase et al. | May 2006 | B2 |
| 7089391 | Geiger et al. | Aug 2006 | B2 |
| 7139894 | Mensching et al. | Nov 2006 | B1 |
| 7181572 | Walmsley | Feb 2007 | B2 |
| 7194577 | Johnson et al. | Mar 2007 | B2 |
| 7219238 | Saito et al. | May 2007 | B2 |
| 7243203 | Scheuerlein | Jul 2007 | B2 |
| 7274600 | Roohparvar | Sep 2007 | B2 |
| 7340558 | Lee et al. | Mar 2008 | B2 |
| 7466575 | Shalvi et al. | Dec 2008 | B2 |
| 7518931 | Shim | Apr 2009 | B2 |
| 7548464 | Kim | Jun 2009 | B2 |
| 7555575 | Kaneda | Jun 2009 | B2 |
| 7593263 | Sokolov et al. | Sep 2009 | B2 |
| 7697326 | Sommer et al. | Apr 2010 | B2 |
| 7706182 | Shalvi et al. | Apr 2010 | B2 |
| 7751240 | Shalvi | Jul 2010 | B2 |
| 7752463 | Hahn et al. | Jul 2010 | B2 |
| 7773413 | Shalvi | Aug 2010 | B2 |
| 7818525 | Frost et al. | Oct 2010 | B1 |
| 7821826 | Shalvi et al. | Oct 2010 | B2 |
| 7856541 | Kaneda et al. | Dec 2010 | B2 |
| 7864573 | Perlmutter et al. | Jan 2011 | B2 |
| 7881107 | Shalvi | Feb 2011 | B2 |
| 7898867 | Hazama et al. | Mar 2011 | B2 |
| 7900102 | Sokolov et al. | Mar 2011 | B2 |
| 7903468 | Litsyn et al. | Mar 2011 | B2 |
| 7924587 | Perlmutter | Apr 2011 | B2 |
| 7925936 | Sommer | Apr 2011 | B1 |
| 7970919 | Duran | Jun 2011 | B1 |
| 7978541 | Sutardja | Jul 2011 | B2 |
| 8135936 | Schaefer et al. | Mar 2012 | B2 |
| 8224782 | Murase | Jul 2012 | B2 |
| 20020069317 | Chow et al. | Jun 2002 | A1 |
| 20020069318 | Chow et al. | Jun 2002 | A1 |
| 20030198084 | Fujisawa et al. | Oct 2003 | A1 |
| 20050002263 | Iwase et al. | Jan 2005 | A1 |
| 20050015539 | Horii et al. | Jan 2005 | A1 |
| 20050027951 | Piccirillo et al. | Feb 2005 | A1 |
| 20050193166 | Johnson et al. | Sep 2005 | A1 |
| 20050246510 | Retnamma et al. | Nov 2005 | A1 |
| 20060004955 | Ware et al. | Jan 2006 | A1 |
| 20060028875 | Avraham | Feb 2006 | A1 |
| 20070104004 | So et al. | May 2007 | A1 |
| 20070132452 | Alsop | Jun 2007 | A1 |
| 20070132453 | Ogino | Jun 2007 | A1 |
| 20070132456 | Salman et al. | Jun 2007 | A1 |
| 20070132457 | Okamoto et al. | Jun 2007 | A1 |
| 20070132458 | Allen, Jr. | Jun 2007 | A1 |
| 20070198770 | Horii et al. | Aug 2007 | A1 |
| 20080026203 | Gates et al. | Jan 2008 | A1 |
| 20080053472 | Hadden | Mar 2008 | A1 |
| 20080053473 | Lee | Mar 2008 | A1 |
| 20080068747 | Sasaki et al. | Mar 2008 | A1 |
| 20080111058 | Feldman et al. | May 2008 | A1 |
| 20080126686 | Sokolov et al. | May 2008 | A1 |
| 20080130341 | Shalvi et al. | Jun 2008 | A1 |
| 20080137415 | Lee | Jun 2008 | A1 |
| 20080139441 | Xiao et al. | Jun 2008 | A1 |
| 20080148115 | Sokolov et al. | Jun 2008 | A1 |
| 20080158958 | Sokolov et al. | Jul 2008 | A1 |
| 20080181001 | Shalvi | Jul 2008 | A1 |
| 20080198650 | Shalvi et al. | Aug 2008 | A1 |
| 20080198652 | Shalvi et al. | Aug 2008 | A1 |
| 20080219050 | Shalvi et al. | Sep 2008 | A1 |
| 20080263262 | Sokolov et al. | Oct 2008 | A1 |
| 20080282106 | Shalvi et al. | Nov 2008 | A1 |
| 20090024905 | Shalvi et al. | Jan 2009 | A1 |
| 20090037691 | Master et al. | Feb 2009 | A1 |
| 20090043951 | Shalvi et al. | Feb 2009 | A1 |
| 20090050703 | Lifson et al. | Feb 2009 | A1 |
| 20090052252 | Kang et al. | Feb 2009 | A1 |
| 20090063450 | Petri | Mar 2009 | A1 |
| 20090091979 | Shalvi | Apr 2009 | A1 |
| 20090103358 | Sommer et al. | Apr 2009 | A1 |
| 20090103365 | Roohparvar | Apr 2009 | A1 |
| 20090106485 | Anholt | Apr 2009 | A1 |
| 20090138652 | Kim et al. | May 2009 | A1 |
| 20090144600 | Perlmutter et al. | Jun 2009 | A1 |
| 20090147581 | Isobe | Jun 2009 | A1 |
| 20090157964 | Kasorla et al. | Jun 2009 | A1 |
| 20090158126 | Perlmutter et al. | Jun 2009 | A1 |
| 20090168524 | Golov et al. | Jul 2009 | A1 |
| 20090187803 | Anholt et al. | Jul 2009 | A1 |
| 20090199074 | Sommer | Aug 2009 | A1 |
| 20090213653 | Perlmutter et al. | Aug 2009 | A1 |
| 20090213654 | Perlmutter et al. | Aug 2009 | A1 |
| 20090228761 | Perlmutter et al. | Sep 2009 | A1 |
| 20090240872 | Perlmutter et al. | Sep 2009 | A1 |
| 20090251969 | Roohparvar et al. | Oct 2009 | A1 |
| 20090296486 | Kim et al. | Dec 2009 | A1 |
| 20100074016 | Higashitani | Mar 2010 | A1 |
| 20100091535 | Sommer et al. | Apr 2010 | A1 |
| 20100110787 | Shalvi et al. | May 2010 | A1 |
| 20100115376 | Shalvi et al. | May 2010 | A1 |
| 20100124088 | Shalvi et al. | May 2010 | A1 |
| 20100124123 | Lee | May 2010 | A1 |
| 20100131826 | Shalvi et al. | May 2010 | A1 |
| 20100131827 | Sokolov et al. | May 2010 | A1 |
| 20100157641 | Shalvi et al. | Jun 2010 | A1 |
| 20100157675 | Shalvi et al. | Jun 2010 | A1 |
| 20100165689 | Rotbard et al. | Jul 2010 | A1 |
| 20100165730 | Sommer et al. | Jul 2010 | A1 |
| 20100195390 | Shalvi | Aug 2010 | A1 |
| 20100199150 | Shalvi et al. | Aug 2010 | A1 |
| 20100220509 | Sokolov et al. | Sep 2010 | A1 |
| 20100220510 | Shalvi | Sep 2010 | A1 |
| 20100250836 | Sokolov et al. | Sep 2010 | A1 |
| 20100332955 | Anholt | Dec 2010 | A1 |
| Number | Date | Country |
|---|---|---|
| 2009011712 | Nov 2009 | KR |
| 2007132452 | Nov 2007 | WO |
| 2007132453 | Nov 2007 | WO |
| 2008026203 | Mar 2008 | WO |
| 2009037691 | Mar 2009 | WO |
| 2009051960 | Apr 2009 | WO |
| 2009053963 | Apr 2009 | WO |
| 2009072102 | Jun 2009 | WO |
| 2009072104 | Jun 2009 | WO |
| Entry |
|---|
| Chung Chiu-Chiao, A multilevel read and verifying scheme for Bi-NAND flash memories, May 2007. |
| CTAN010:SLC vs. MLC NAND, Cactus Technologies, Jun. 3, 2008. |
| International Search Report and Written Opinion, PCT/US2011/022786, Sep. 29, 2011. |
| Application No. PCT/US2011/022786, International Preliminary Report on Patentability, Aug. 9, 2012. |
| U.S. Appl. No. 13/015,458, Office Action, Sep. 7, 2012. |
| U.S. Appl. No. 13/015,458, Notice of Allowance, Sep. 19, 2012. |
| Suh, Kang-Deog, “A 3.3 V 32 Mb NAND Flash Memory with Incremental Step Pulse Programming Scheme”, IEEE Journal of Solid-State Circuits, Nov. 30, 1995, pp. 8, XP 000553051, vol. 30, No. H, New York, US. |
| 2380.2.45EP2, P201002EP2, Application No. 12176826.1, Search Report, Dec. 10, 2012. |
| Number | Date | Country | |
|---|---|---|---|
| 20120203951 A1 | Aug 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61298861 | Jan 2010 | US | |
| 61305205 | Feb 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13015458 | Jan 2011 | US |
| Child | 13189402 | US | |
| Parent | 13175637 | Jul 2011 | US |
| Child | 13015458 | US |
