# Patent

## Title
Apparatus, system, and method for managing a cache

## Abstract

An apparatus, system, and method are disclosed for managing a cache. A cache interface module provides access to a plurality of virtual storage units of a solid-state storage device over a cache interface. At least one of the virtual storage units comprises a cache unit. A cache command module exchanges cache management information for the at least one cache unit with one or more cache clients over the cache interface. A cache management module manages the at least one cache unit based on the cache management information exchanged with the one or more cache clients.

## Background
CROSS-REFERENCES TO RELATED APPLICATIONS
This application claims priority to U.S. Provisional Patent Application No. 61/590,272 entitled “APPARATUS, SYSTEM, AND METHOD FOR MANAGING A CACHE” filed on Jan. 24, 2012 for Jim Peterson, et al., which is incorporated herein by reference, and further incorporates by reference U.S. patent application Ser. No. 13/193,559 entitled “APPARATUS, SYSTEM, AND METHOD FOR ATOMIC STORAGE OPERATIONS” filed on Jul. 28, 2011 for David Flynn et al.


FIELD OF THE INVENTION
This invention relates to caching data and more particularly relates to managing cache units using a cache interface.
BACKGROUND
Description of the Related Art
Data storage caches typically use a small amount of high performance, more expensive storage media to cache data for less expensive bulk storage. Caches traditionally handle data uniformly, caching data from a single source or treating data similarly regardless of the source.
However, different cache clients may have different characteristics. A database cache client uses a cache differently than a storage system cache client. Uniform treatment of cache clients that have different characteristics can result in cache inefficiencies. A cache client typically cannot remedy such inefficiencies, because the associated caches are not customizable.
SUMMARY
From the foregoing discussion, it should be apparent that a need exists for an apparatus, system, and method for efficiently caching data. Beneficially, such an apparatus, system, and method would manage one or more cache units based on information from cache clients to customize operation of the cache units.
The present invention has been developed in response to the present state of the art, and in particular, in response to the problems and needs in the art that have not yet been fully solved by currently available data storage caches. Accordingly, the present invention has been developed to provide an apparatus, system, and method for managing a cache that overcome many or all of the above-discussed shortcomings in the art.
A method of the present invention is presented for managing a cache. The method in the disclosed embodiments substantially includes the steps necessary to carry out the functions presented below with respect to the operation of the described apparatus and system. In one embodiment, the method includes providing access to a plurality of virtual storage units of a solid-state storage device over a cache interface. At least one of the virtual storage units, in certain embodiments, comprises a cache unit. The method, in a further embodiment, includes exchanging cache management information for the at least one cache unit with one or more cache clients over the cache interface. In an additional embodiment, the method includes managing the at least one cache unit based on the cache management information exchanged with the one or more cache clients.
In one embodiment, managing the at least one cache unit comprises selecting data for eviction from the at least one cache unit based on the cache management information. Exchanging cache management information, in certain embodiments, includes sending a garbage collection request to the one or more cache clients and receiving a garbage collection response from the one or more cache clients. The garbage collection request, in one embodiment, identifies logical block addresses of an erase block targeted for garbage collection. In a further embodiment, the garbage collection response indicates which data of the erase block to evict from the at least one cache unit.
In various embodiments, the cache management information may comprise a command received from the one or more cache clients over the cache interface, such as a cache admission command, a cache eviction command, a cache prefetch command, a cache destage command, a quality-of-service command, a physical capacity allotment command, a TRIM command, and/or a data priority command. In another embodiment, the cache management information comprises a message sent to the one or more cache clients over the cache interface, such as an eviction request and/or an available storage capacity report. The cache management information, in a further embodiment, comprises a virtual storage unit command such as a create command, a delete command, an enumerate command, a TRIM command, and/or a resize command.
In one embodiment, the at least one cache unit comprises a plurality of cache units operating simultaneously on the solid-state storage device. At least a portion of the plurality of cache units, in certain embodiments, each present a distinct sparse logical address space to the one or more cache clients. In a further embodiment, the distinct sparse logical address spaces are mapped to a single sparse logical address space of the solid-state storage device. Data from each of the plurality of cache units, in certain embodiments, is intermingled in a sequential log-based writing structure of the solid-state storage device.
The cache management information, in one embodiment, comprises a selection from the one or more cache clients of a logical address space type for the at least one cache unit. The logical address space type may include a sparse logical address space, a contiguous block address space, or the like.
The method, in another embodiment, includes allocating physical storage capacity of the solid-state storage device according to a prioritization of the plurality of virtual storage units. In one embodiment, the method includes reducing storage capacity of the solid-state storage device over time in response to data errors. The method, in a further embodiment, includes notifying the one or more cache clients, over the cache interface, of the reduced storage capacity of the solid-state storage device.
In one embodiment, a single mapping structure maps logical block addresses for the plurality of virtual storage units to physical storage addresses on solid-state storage media of the solid-state storage device. The plurality of virtual storage units, in certain embodiments, include a plurality of cache units. The single mapping structure, in a further embodiment, directly maps the logical block addresses for the plurality of cache units to logical block addresses of one or more backing store devices, so that the single mapping structure comprises a fully associative relationship between logical block addresses of the one or more backing store devices and the physical storage addresses on the solid-state storage media of the solid-state storage device.
Another method is presented for managing a solid-state storage device. In one embodiment, the method includes providing access to a plurality of virtual storage units of a solid-state storage device over an interface. The method, in a further embodiment, includes mapping, using a single mapping structure, logical block addresses for the plurality of virtual storage units to physical storage addresses on solid-state storage media of the solid-state storage device. In another embodiment, the method includes satisfying input/output (“I/O”) requests for the plurality of virtual storage units using the single mapping structure.
The method, in one embodiment, includes exchanging management information for the plurality of virtual storage units with one or more clients over the interface. In a further embodiment, the method includes managing the plurality of virtual storage units based on the management information exchanged with the one or more clients. The plurality of virtual storage units, in certain embodiments, include a plurality of cache units. The single mapping structure, in one embodiment, directly maps the logical block addresses for the plurality of cache units to logical block addresses of one or more backing store devices, so that the single mapping structure comprises a fully associative relationship between logical block addresses of the one or more backing store devices and the physical storage addresses on the solid-state storage media of the solid-state storage device.
An apparatus to manage a cache is provided with a plurality of modules configured to functionally execute the necessary steps of the method described above. These modules in the described embodiments include a cache interface module, a cache command module, and a cache management module.
In one embodiment, the cache interface module provides access to a plurality of virtual storage units of a solid-state storage device over a cache interface. At least one of the virtual storage units, in another embodiment, comprises a cache unit.
The cache command module, in one embodiment, exchanges cache management information for the at least one cache unit with one or more cache clients over the cache interface. In a further embodiment, the cache management information comprises a command received from the one or more cache clients over the cache interface, such as a cache admission command, a cache eviction command, a cache prefetch command, a cache destage command, a quality-of-service command, a physical capacity allotment command, a TRIM command, and/or a data priority command.
In one embodiment, the cache command module sends a garbage collection request to the one or more cache clients. The garbage collection request, in certain embodiments, identifies logical block addresses of an erase block targeted for garbage collection. In another embodiment, the cache command module receives a garbage collection response from the one or more cache clients. The garbage collection response, in one embodiment, indicates which data of the erase block to evict from the at least one cache unit.
In a further embodiment, the cache management module manages the at least one cache unit based on the cache management information exchanged with the one or more cache clients. The cache management module, in one embodiment, selects data for eviction from the at least one cache unit based on the cache management information.
A system of the present invention is also presented for managing a cache. The system may be embodied by a solid-state storage device and a cache controller for the solid-state storage device. In particular, the system, in one embodiment, includes a host computer system.
The solid-state storage device, in one embodiment, comprises a plurality of virtual storage units. At least one of the virtual storage units, in a further embodiment, comprises a cache unit.
In one embodiment, the cache controller includes a cache interface module, a cache command module, and a cache management module. The cache interface module, in one embodiment, provides access to the plurality of virtual storage units over a cache interface. The cache command module, in a further embodiment, exchanges cache management information for the at least one cache unit with one or more cache clients over the cache interface. In another embodiment, the cache management module manages the at least one cache unit based on the cache management information exchanged with the one or more cache clients. The cache management module, in certain embodiments, selects data for eviction from the at least one cache unit based on the cache management information.
The one or more cache clients, in one embodiment, comprise software clients executing on the host computer system. The cache controller, in a further embodiment, comprises a device driver executing on the host computer system.
Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present invention should be or are in any single embodiment of the invention. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present invention. 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 invention may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the invention 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 of the invention.
These features and advantages of the present invention will become more fully apparent from the following description and appended claims, or may be learned by the practice of the invention as set forth hereinafter.



BRIEF DESCRIPTION OF THE DRAWINGS
In order that the advantages of the invention will be readily understood, a more particular description of the invention briefly described above 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:
FIG. 1A is a schematic block diagram illustrating one embodiment of a system for managing a cache in accordance with the present invention;
FIG. 1B is a schematic block diagram illustrating another embodiment of a system for managing a cache in accordance with the present invention;
FIG. 2 is a schematic block diagram illustrating one embodiment of a solid-state storage device controller in a cache device in accordance with the present invention;
FIG. 3 is a schematic block diagram illustrating one embodiment of a solid-state storage controller with a write data pipeline and a read data pipeline in a solid-state storage device in accordance with the present invention;
FIG. 4 is a schematic block diagram illustrating one embodiment of a bank interleave controller in the solid-state storage controller in accordance with the present invention;
FIG. 5 is a schematic block diagram illustrating one embodiment of a host device in accordance with the present invention;
FIG. 6 is a schematic block diagram illustrating one embodiment of a direct cache module in accordance with the present invention;
FIG. 7 is a schematic block diagram illustrating another embodiment of a direct cache module in accordance with the present invention;
FIG. 8 is a schematic block diagram illustrating one embodiment of a storage controller in accordance with the present invention;
FIG. 9 is a schematic block diagram illustrating another embodiment of a storage controller in accordance with the present invention;
FIG. 10 is a schematic block diagram illustrating one embodiment of a forward map and a reverse map in accordance with the present invention;
FIG. 11 is a schematic block diagram illustrating one embodiment of a mapping structure, a logical address space of a cache, a sequential, log-based, append-only writing structure, and an address space of a storage device in accordance with the present invention;
FIG. 12 is a schematic flow chart diagram illustrating one embodiment of a method for caching data in accordance with the present invention;
FIG. 13 is a schematic flow chart diagram illustrating another embodiment of a method for caching data in accordance with the present invention;
FIG. 14 is a schematic flow chart diagram illustrating one embodiment of a method for managing a cache in accordance with the present invention; and
FIG. 15 is a schematic flow chart diagram illustrating another embodiment of a method for managing a cache in accordance with the present invention.



DETAILED DESCRIPTION OF THE INVENTION
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
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 computer readable program 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 computer readable program 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 computer readable program code may be stored and/or propagated on or in one or more computer readable medium(s).
The computer readable medium may be a tangible computer readable storage medium storing the computer readable program code. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
More specific examples of the computer readable medium may include but are not limited to a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, a holographic storage medium, a micromechanical storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, and/or store computer readable program code for use by and/or in connection with an instruction execution system, apparatus, or device.
The computer readable medium may also be a computer readable signal medium. A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electrical, electro-magnetic, magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport computer readable program code for use by or in connection with an instruction execution system, apparatus, or device. Computer readable program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, Radio Frequency (RF), or the like, or any suitable combination of the foregoing. In one embodiment, the computer readable medium may comprise a combination of one or more computer readable storage mediums and one or more computer readable signal mediums. For example, computer readable program code may be both propagated as an electro-magnetic signal through a fiber optic cable for execution by a processor and stored on RAM storage device for execution by the processor.
Computer readable program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
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. 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, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.
Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. 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. One skilled in the relevant art will recognize, however, that embodiments 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 an embodiment.
Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of the invention. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by computer readable program code. These computer readable program code may be provided to a processor of a general purpose computer, special purpose computer, sequencer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
The computer readable program code may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
The computer readable program code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the program code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the program code for implementing the specified logical function(s).
It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer readable program code.
Caching System
FIG. 1A depicts one embodiment of a system 100 for managing a cache in accordance with the present invention. The system 100, in the depicted embodiment, includes a solid-state storage device 102, a host device 114, a direct cache module 116, and a backing store 118. The solid-state storage device 102, in the depicted embodiment, includes a solid-state storage controller 104, a write data pipeline 106, a read data pipeline 108, and a solid-state storage media 110. In general, the system 100 caches data for the backing store 118 in the solid-state storage device 102 and the host device 114 communicates with the direct cache module 116 over a cache interface 112.
In the depicted embodiment, the system 100 includes a single solid-state storage device 102, which is used at least partially as a cache. In other embodiments, the system 100 may include two or more caches. For example, the solid-state storage device 102 may host multiple virtual cache units (described in greater detail below with regard to the virtual storage units 122 of FIG. 1B), the system 100 may mirror cached data between several caches, may virtually stripe cached data across multiple caches, or may otherwise cache data in more than one cache. In general, the solid-state storage device 102 includes one or more read and/or a write cache units for the backing store 118 and the backing store 118 provides backing storage for the solid-state storage device 102. In other embodiments, the system 100 may include multiple backing stores 118, with separate backing stores 118 for different cache units of the solid-state storage device 102 or the like.
In the depicted embodiment, the solid-state storage device 102 is a non-volatile, solid-state storage device, with a solid-state storage controller 104 and non-volatile, solid-state storage media 110. The non-volatile, solid-state storage media 110 may include 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. In certain embodiments, the solid-state storage device 102 is a sequential log-based data storage device that stores data in one or more append-only log-based writing structures of the solid-state storage media 110.
The solid-state storage device 102 may be a general-purpose storage device, and may serve other functions in addition to caching data. For example, as described below with regard to FIG. 1B, the solid-state storage device 102 may store several virtual storage units 122 (“VSUs”) for clients 120, which may serve as cache units, object stores, general-purpose storage units, swap/memory extension units, sparse address space units, or the like. The direct cache module 116 provides a cache interface 112 over which the direct cache module 116 exchanges cache management information for cache unit VSUs of the solid-state storage device 102.
Embodiments of the solid-state storage device 102 that include a solid-state storage controller 104 and solid-state storage media 110 are described in more detail with respect to FIGS. 2 and 3. The solid-state storage controller 104, in certain embodiments, may mask differences in latency for storage operations performed on the solid-state storage media 110 by grouping erase blocks by access time, wear level, and/or health, by queuing storage operations based on expected completion times, by splitting storage operations, by coordinating storage operation execution in parallel among multiple buses, or the like.
In general, the solid-state storage device 102 caches data for the backing store 118 in one or more cache unit VSUs. The backing store 118, in one embodiment, is a storage device associated with the solid-state storage device 102, with a cache unit VSU of the solid-state storage device 102, and/or with the direct cache module 116. The backing store 118 may include a hard disk drive, an optical drive with optical media, a magnetic tape drive, or another type of storage device. In one embodiment, the backing store 118 may have a greater data storage capacity than the solid-state storage device 102. In another embodiment, the backing store 118 may have a higher latency, a lower throughput, or the like, than the solid-state storage device 102.
The backing store 118 may have a higher latency, a lower throughput, or the like due to properties of the backing store 118 itself, or due to properties of a connection to the backing store 118. For example, in one embodiment, the solid-state storage device 102 and the backing store 118 may each include non-volatile, solid-state storage media 110 with similar properties, but the backing store 118 may be in communication with the host device 114 over a data network, while the solid-state storage device 102 may be directly connected to the host device 114, causing the backing store 118 to have a higher latency relative to the host 114 than the solid-state storage device 102.
In the depicted embodiment, the solid-state storage device 102 and the backing store 118 are in communication with the host device 114 through the direct cache module 116. The solid-state storage device 102 and/or the backing store 118, in one embodiment, may be direct attached storage (“DAS”) of the host device 114. DAS, as used herein, is data storage that is connected to a device, either internally or externally, without a storage network in between.
In one embodiment, the solid-state storage device 102 and/or the backing store 118 are internal to the host device 114 and are connected using a system bus, such as a peripheral component interconnect express (“PCI-e”) bus, a Serial Advanced Technology Attachment (“SATA”) bus, or the like. In another embodiment, the solid-state storage device 102 and/or the backing store 118 may be external to the host device 114 and may be connected using a universal serial bus (“USB”) connection, an Institute of Electrical and Electronics Engineers (“IEEE”) 1394 bus (“FireWire”), an external SATA (“eSATA”) connection, or the like. In other embodiments, the solid-state storage device 102 and/or the backing store 118 may be connected to the host device 114 using 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 and/or the backing store 118 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 and/or the backing store 118 may be elements within a rack-mounted blade. In another embodiment, the solid-state storage device 102 and/or the backing store 118 may be contained within packages that are integrated directly onto a higher level assembly (e.g. mother board, laptop, graphics processor). In another embodiment, individual components comprising the solid-state storage device 102 and/or the backing store 118 are integrated directly onto a higher level assembly without intermediate packaging. In the depicted embodiment, the solid-state storage device 102 includes one or more solid-state storage controllers 104 with a write data pipeline 106 and a read data pipeline 108, and a solid-state storage media 110, which are described in more detail below with respect to FIGS. 2 and 3.
In a further embodiment, instead of being connected directly to the host device 114 as DAS, the solid-state storage device 102 and/or the backing store 118 may be connected to the host device 114 over a data network. For example, the solid-state storage device 102 and/or the backing store 118 may include a storage area network (“SAN”) storage device, a network attached storage (“NAS”) device, a network share, or the like. In one embodiment, the system 100 may include a data network, such as 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, a NAS, ESCON, or the like, or any combination of networks. A data network may also include a network from the IEEE 802 family of network technologies, such Ethernet, token ring, Wi-Fi, Wi-Max, and the like. A data network may include servers, switches, routers, cabling, radios, and other equipment used to facilitate networking between the host device 114 and the solid-state storage device 102 and/or the backing store 118.
In one embodiment, at least the solid-state storage device 102 is connected directly to the host device 114 as a DAS device. In a further embodiment, the solid-state storage device 102 is directly connected to the host device 114 as a DAS device and the backing store 118 is directly connected to the solid-state storage device 102. For example, the solid-state storage device 102 may be connected directly to the host device 114, and the backing store 118 may be connected directly to the solid-state storage device 102 using a direct, wire-line connection, such as a PCI express bus, an SATA bus, a USB connection, an IEEE 1394 connection, an eSATA connection, a proprietary direct connection, an external electrical or optical bus extension or bus networking solution such as Infiniband or PCIe-AS, or the like. One of skill in the art, in light of this disclosure, will recognize other arrangements and configurations of the host device 114, the solid-state storage device 102, and the backing store 118 suitable for use in the system 100.
The system 100 includes the host device 114 in communication with the solid-state storage device 102 and the backing store 118 through the direct cache module 116. A host device 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, 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 the depicted embodiment, the host device 114 is in communication with the direct cache module 116. The direct cache module 116, in general, receives or otherwise detects read and write requests from the host device 114 for the backing store 118 and manages the caching of data in the solid-state storage device 102. In one embodiment, the direct cache module 116 comprises a software application, file system filter driver, or the like.
The direct cache module 116, in various embodiments, may include one or more software drivers on the host device 114, one or more storage controllers, such as the solid-state storage controllers 104 of the solid-state storage device 102, a combination of one or more software drivers and storage controllers, or the like. In certain embodiments, hardware and/or software of the direct cache module 116 comprises a cache controller that is in communication with the solid-state storage controller 104 to manage operation of one or more cache unit VSUs of the solid-state storage device 102.
In one embodiment, the host device 114 loads one or more device drivers for the solid-state storage device 102 and/or the backing store 118 and the direct cache module 116 communicates with the one or more device drivers on the host device 114. In another embodiment, the direct cache module 116 may communicate directly with a hardware interface of the solid-state storage device 102 and/or of the backing store 118. In a further embodiment, the direct cache module 116 may be fully or partially integrated with the solid-state storage device 102, the backing store 118, and/or their associated controllers 104, 120. For example, in one embodiment, the direct cache module 116 is integrated with the solid-state storage controller 104, together forming a virtual storage layer (“VSL”) installed as a device driver on the host device 114, or the like, such that the solid-state storage controller 104 (the VSL), performs each of the functions and actions described herein with regard to the direct cache module 116.
In one embodiment, the solid-state storage device 102 and/or the backing store 118 have block device interfaces that support block device commands. For example, the solid-state storage device 102 and/or the backing store 118 may support the standard block device interface, the ATA interface standard, the ATA Packet Interface (“ATAPI”) standard, the small computer system interface (“SCSI”) standard, and/or the Fibre Channel standard which are maintained by the InterNational Committee for Information Technology Standards (“INCITS”). The direct cache module 116 may interact with the solid-state storage device 102 and/or the backing store 118 using block device commands to read, write, and clear (or trim) data.
In one embodiment, the direct cache module 116 serves as a proxy for the backing store 118, receiving read and write requests for the backing store 118 directly from the host device 114. The direct cache module 116 may represent itself to the host device 114 as a storage device having a capacity similar to and/or matching the capacity of the backing store 118. In certain embodiments, the direct cache module 116 and/or the solid-state storage controller 104 dynamically reduce a cache size for the solid-state storage device 102 in response to an age characteristic for the solid-state storage media 110 of the solid-state storage device 102. For example, as storage elements of the solid-state storage device 102 age, the direct cache module 116 and/or the solid-state storage controller 104 may remove the storage elements from operation, thereby reducing the cache size for the solid-state storage device 102. Examples of age characteristics, in various embodiments, may include a program/erase count, a bit error rate, an uncorrectable bit error rate, or the like that satisfies a predefined age threshold.
The direct cache module 116, upon receiving a read request or write request from a client on the host device 114, in one embodiment, fulfills the request by caching write data in a cache unit VSU of the solid-state storage device 102 or by retrieving read data from a cache unit VSU of the solid-state storage device 102 or from the backing store 118 and returning the read data to the client.
Data caches are typically organized into cache lines which divide up the physical capacity of the cache, these cache lines may be divided into several sets. A cache line is typically larger than a block or sector of a backing store associated with a data cache, to provide for prefetching of additional blocks or sectors and to reduce cache misses and increase the cache hit rate. Data caches also typically evict an entire, fixed size, cache line at a time to make room for newly requested data in satisfying a cache miss. Data caches may be direct mapped, fully associative, N-way set associative, or the like.
In a direct mapped cache, each block or sector of a backing store has a one-to-one mapping to a cache line in the direct mapped cache. For example, if a direct mapped cache has T number of cache lines, the backing store associated with the direct mapped cache may be divided into T sections, and the direct mapped cache caches data from a section exclusively in the cache line corresponding to the section. Because a direct mapped cache always caches a block or sector in the same location or cache line, the mapping between a block or sector address and a cache line can be a simple manipulation of an address of the block or sector.
In a fully associative cache, any cache line can store data from any block or sector of a backing store. A fully associative cache typically has lower cache miss rates than a direct mapped cache, but has longer hit times (i.e. it takes longer to locate data in the cache) than a direct mapped cache. To locate data in a fully associative cache, either cache tags of the entire cache can be searched, a separate cache index can be used, or the like.
In an N-way set associative cache, each sector or block of a backing store may be cached in any of a set of N different cache lines. For example, in a 2-way set associative cache, either of two different cache lines may cache data for a sector or block. In an N-way set associative cache, both the cache and the backing store are typically divided into sections or sets, with one or more sets of sectors or blocks of the backing store assigned to a set of N cache lines. To locate data in an N-way set associative cache, a block or sector address is typically mapped to a set of cache lines, and cache tags of the set of cache lines are searched, a separate cache index is searched, or the like to determine which cache line in the set is storing data for the block or sector. An N-way set associative cache typically has miss rates and hit rates between those of a direct mapped cache and those of a fully associative cache.
Cache unit VSUs of the solid-state storage device 102, in one embodiment, may have characteristics of both a directly mapped cache and a fully associative cache. A logical address space of the solid-state storage device 102 and/or of a cache unit VSU, in one embodiment, may be directly mapped to an address space of the backing store 118 while the physical storage media 110 of the solid-state storage device 102 may be fully associative with regard to the backing store 118. In other words, each block or sector of the backing store 118, in one embodiment, is directly mapped to a single logical address of the solid-state storage device 102 or of a cache unit VSU, while any portion of the physical storage media 110 of the solid-state storage device 102 may store data for any block or sector of the backing store 118. In one embodiment, a logical address is an identifier of a block of data that is distinct from a physical address of the block of data, but that may be mapped to the physical address of the block of data. Examples of logical addresses, in various embodiments, include logical block addresses (“LBAs”), logical identifiers, object identifiers, pointers, references, and the like.
Instead of traditional cache lines, in one embodiment, the solid-state storage device 102 has logical or physical data blocks associated with each logical address that are equal in size to a block or sector of the backing store 118. In a further embodiment, the solid-state storage device 102 caches ranges and/or sets of ranges of blocks or sectors for the backing store 118 at a time, providing dynamic or variable length cache line functionality. A range or set of ranges of blocks or sectors, in a further embodiment, may include a mixture of contiguous and/or noncontiguous blocks. For example, the solid-state storage device 102, in one embodiment, supports block device requests that include a mixture of contiguous and/or noncontiguous blocks and that may include “holes” or intervening blocks that the solid-state storage device 102 does not cache or otherwise store.
In one embodiment, one or more groups of addresses of the backing store 118 are directly mapped to corresponding logical addresses of the solid-state storage device 102. The addresses of the backing store 118 may comprise physical addresses or logical addresses. Directly mapping logical addresses of the backing store 118 to logical addresses of the solid-state storage device 102, in one embodiment, provides a one-to-one relationship between the logical addresses of the backing store 118 and the logical addresses of the solid-state storage device 102. Directly mapping logical or physical address space of the backing store 118 to logical addresses of the solid-state storage device 102 (or of a cache unit VSU), in one embodiment, precludes the use of an extra translation layer in the direct cache module 116, such as the use of cache tags, a cache index, the maintenance of a translation data structure, or the like. In one embodiment, while the logical address space of the solid-state storage device 102 may be larger than a logical address space of the backing store 118, both logical address spaces include at least logical addresses 0-N. In a further embodiment, at least a portion of the logical address space of the solid-state storage device 102 represents or appears as the logical address space of the backing store 118 to a client, such as the host device 114.
Alternatively, in certain embodiments where physical blocks or sectors of the backing store 118 are directly accessible using physical addresses, at least a portion of logical addresses in a logical address space of the solid-state storage device 102 may be mapped to physical addresses of the backing store 118. At least a portion of the logical address space of the solid-state storage device 102, in one embodiment, may correspond to the physical address space of the backing store 118. At least a subset of the logical addresses of the solid-state storage device 102, in this embodiment, are directly mapped to corresponding physical addresses of the backing store 118.
In one embodiment, the logical address space of the solid-state storage device 102 (or of an individual cache unit VSU) is a sparse address space that is either as large as or is larger than the physical storage capacity of the solid-state storage device 102. This allows the backing store 118 to have a larger storage capacity than the solid-state storage device 102, while maintaining a direct mapping between the logical addresses of the solid-state storage device 102 and logical or physical addresses of the backing store 118. The sparse logical address space may be thinly provisioned, in one embodiment. In a further embodiment, as the direct cache module 116 writes data to the solid-state storage device 102 using logical addresses, the solid-state storage device 102 directly maps the logical addresses to distinct physical addresses or locations on the solid-state storage media 110 of the solid-state storage device 102, such that the physical addresses or locations of data on the solid-state storage media 110 are fully associative with the backing store 118. In one embodiment, the direct cache module 116 and/or the solid-state storage device 102 use the same single mapping structure to map addresses (either logical or physical) of the backing store 118 to logical addresses of the solid-state storage device 102 and to map logical addresses of the solid-state storage device 102 to locations/physical addresses of a block or sector (or range of blocks or sectors) on the physical solid state storage media 110. In one embodiment, using a single mapping structure for both functions eliminates the need for a separate cache map, cache index, cache tags, or the like, decreasing access times of the solid-state storage device 102.
As the direct cache module 116 and/or the solid-state storage controller 104 clear, trim, replace, expire, and/or evict, data from the solid-state storage device 102, the physical addresses and associated physical storage media, the solid state storage media 110 in the depicted embodiment, are freed to store data for other logical addresses. In one embodiment, the solid state storage controller 104 stores the data at the physical addresses using a log-based, append only writing structure such that data evicted or otherwise cleared from the solid-state storage device 102 or overwritten by a subsequent write request invalidates other data in the log. Consequently, a garbage collection process recovers the physical capacity of the invalid data in the log. One embodiment of the log-based, append only writing structure is a logically ring-like, cyclic data structure, as new data is appended to the log-based writing structure, previously used physical capacity is reused in a circular, theoretically infinite manner.
The direct cache module 116, in the depicted embodiment, provides a cache interface 112 to clients, such as the clients 120 described below with regard to FIG. 1B, over which the direct cache module 116 may exchange cache management information with the clients. The cache interface 112 may comprise an application program interface (“API”) or another interface between the direct cache module 116 and clients. In certain embodiments, the cache interface 112 is a two-way interface, over which clients may issue cache commands to the direct cache module 116 and the direct cache module 116 may issue callbacks, notifications, or the like to clients. One embodiment of clients communicating with the direct cache module 116 over a cache interface 112 is described below with regard to FIG. 1B.
FIG. 1B depicts a further embodiment of a system 101 for managing a cache. The system 101, in certain embodiments, may be substantially similar to the system 100 described above with regard to FIG. 1A. The system 101 includes a plurality of clients 120 and a plurality of VSUs 122. Several of the clients 120, in the depicted embodiment, comprise software clients executing on the host device 114 and communicating with the direct cache module 116 over the cache interface 112 internally within the host device 114. The system 101 also includes a client 120 that is external to the host device 114 and communicating with the direct cache module 116 over the cache interface 112 externally to the host device 114, over a data network or the like.
The clients 120, in one embodiment, each comprise software and/or hardware that use cached data. For example, a client 120 may include a database program such as a database management system (“DBMS”), a server, an operating system, a file system manager, or other software that uses cached data. In certain embodiments, the clients 120 may have differing characteristics or different caching requirements. The direct cache module 116 exchanges cache management information with the clients 120 over the cache interface 112, allowing the clients 120 to customize setup and management of individual VSUs 122 of the solid-state storage device 102, including cache unit VSUs 122.
The direct cache module 116 cooperates with the solid-state storage controller 104 to create and manage the VSUs 122 for the clients 120. Each VSU is a data structure maintained by the solid-state storage controller 104 to logically divide the solid-state storage device 102 into independent storage units or containers, so that the solid-state storage device 102 may be shared between multiple clients 120. Each VSU 122 may have different properties and attributes, such as different use cases, different quality-of-service (“QoS”) levels, different priority levels, different logical address space types (e.g. sparse logical address space, contiguous logical address space), different replication attributes, different logical and/or physical storage capacities, or the like. VSUs 122, in certain embodiments, may be independently created, deleted, and managed. The solid-state storage controller 104 may store metadata defining attributes of the VSUs 122 in volatile and/or nonvolatile storage of the host device 114, the solid-state storage device 102, the backing store 118, or the like.
Attributes and metadata of a VSU 122 may be used to ensure high availability, to provide failover, or the like. For example, if a first VSU 122 encounters a fault, error, or otherwise fails, the solid-state storage controller 104 may use the attributes and metadata of the failed first VSU 122 to migrate one or more clients 120 to a second VSU 122. The attributes of a failed VSU 122 may allow the solid-state storage controller 104 to manage storage capacity allocation for a newly allocated VSU 122, to select a suitable VSU 122 as a failover candidate, and the like.
While the VSUs 122 depicted in FIG. 1B are logically associated with a single solid-state storage controller 104, with physical storage media 110 provided by a single solid-state storage device 102, in another embodiment, the system 101 may include a plurality of solid-state storage devices 102, a plurality of solid-state storage controllers 104, or the like, each with associated VSUs 122. The solid-state storage controller 104, in certain embodiments, may use a plurality of VSUs 122 in cooperation. For example, the solid-state storage controller 104 may stack, layer, aggregate, export, and/or replicate one or more VSUs 122 to extend across multiple software layers, across data networks, across solid-state storage devices 102, or the like. In other embodiments, the solid-state storage controller 104 may stripe or mirror data to multiple VSUs 122, provide snapshots of one or more VSUs 122, or the like.
While each VSU 122 may be logically independent, in one embodiment, data stored in different VSUs 122 is intermingled in the solid-state storage media 110. For example, the solid-state storage media 110 may store data using a sequential, append-only, log-based writing structure, and the solid-state storage controller 104 may write data of several VSUs 122 sequentially to an append point of the log-based writing structure as the direct cache module 116 receives data from clients 120. Because data from each VSU 122, in certain embodiments, is written to the same append point, the data from different VSUs 122 may be dispersed throughout the log-based writing structure on the solid-state storage media 110.
By logically separating the data from different VSUs 122 but intermingling the data physically, data from each VSU 122 receives the same data protection characteristics. For example, as described in greater detail below with regard to FIG. 3, the solid-state storage controller 104, the write data pipeline 106, and the read data pipeline 108 provide certain data protection characteristics for data, such as error correction, garbage collection or storage capacity recovery, power cut or power loss protection, or the like to protect the integrity of data on the solid-state storage media 110. The solid-state storage controller 104 applies these data protection characteristics to data regardless of which VSU 122 logically corresponds to the data.
Another benefit of storing data for VSUs 122 in a sequential, append-only, log-based writing structure as the solid-state storage controller 104 receives data from clients 120, is that one or more of the VSUs 122 may be thinly provisioned, having a larger logical address space than the physical storage capacity of the solid-state storage media 110 and/or of the backing store 118. In a thinly provisioned embodiment, the solid-state storage controller 104 may allocate physical storage capacity of the solid-state storage media 110 to a VSU 122 as the physical storage capacity is used, instead of allocating the entire storage capacity of the VSU 122 initially when the VSU 122 is created. Additionally, the solid-state storage controller 104 may export a logical address space for a VSU 122 to a client 120 (e.g. a sparse address space) that is much larger than the physical storage capacity of the solid-state storage media 110 and/or of the backing store 118. The solid-state storage controller 104 may provision the logical address space when creating a VSU 122, and allocate physical storage capacity to the VSU 122 dynamically in response to a write request from a client 120.
As described above with regard to the system 100 of FIG. 1A, the direct cache module 116 may be independent from the solid-state storage controller 104, as depicted, or may be integrated with the solid-state storage controller 104, in a virtual storage layer, or the like. In the depicted embodiment, the system 101 includes the cache interface 112 between clients 120 and the direct cache module 116 and also includes a storage controller interface 124 between clients 120 and the solid-state storage controller 104. Clients 120 that use VSUs 122 as cache units send and receive cache management information over the cache interface 112 while other clients 120 may send and receive general storage commands over the storage controller interface 124. Certain clients 120 may communicate with both the direct cache module 116 over the cache interface 112 and the solid-state storage controller 104 over the storage controller interface 124. In other embodiments, where the direct cache module 116 and the solid-state storage controller 104 are integrated, the cache interface 112 and the storage controller interface 124 may comprise a single interface, as parts of a single API or the like.
In the depicted embodiment, the direct cache module 116 sends and receives cache management information, and communicates with the solid-state storage controller 104, which manages and controls the solid-state storage device 102 and cooperates with the backing store controller 120 for operations on the backing store 118. In other embodiments, the direct cache module 116 may communicate directly with the backing store controller 120 for operations related to the backing store 118.
In response to a request or command from a client 120, the direct cache module 116 and/or the solid-state storage controller 104 may create a VSU 122, configure the VSU 122 as a cache unit, and further manage the cache unit VSU 122. Examples of how the cache management module 116 may manage cache unit VSUs 122 based on exchanging cache management information with clients 120 are described in greater detail below with regard to FIGS. 6 and 7, such as managing address spaces for VSUs 122, managing storage capacity for VSUs 122, prioritizing data within VSUs 122 and/or between VSUs 122, evicting data from cache unit VSUs 122, trimming data from VSUs 122, setting retention requirements for data of VSUs 122, adjusting capacity over time as the solid-state storage device 102 ages, and the like. Providing a cache interface 112 over which clients 120 may customize and manage their own cache unit VSUs 122 allows the direct cache module 116 to provide caching capabilities that closely match the use patterns and caching requirements of the clients 120, even for clients 120 of different types with different characteristics.
Solid-State Storage Device
FIG. 2 is a schematic block diagram illustrating one embodiment 201 of a solid-state storage device controller 202 that includes a write data pipeline 106 and a read data pipeline 108 in a solid-state storage device 102 in accordance with the present invention. The solid-state storage device controller 202 may be embodied as hardware, as software, or as a combination of hardware and software.
The solid-state storage device controller 202 may include a number of solid-state storage controllers 0-N 104a-n, each controlling solid-state storage media 110. In the depicted embodiment, two solid-state controllers are shown: solid-state controller 0 104a and solid-state storage controller N 104n, and each controls solid-state storage media 110a-n. In the depicted embodiment, solid-state storage controller 0 104a controls a data channel so that the attached solid-state storage media 110a stores data. Solid-state storage controller N 104n controls an index metadata channel associated with the stored data and the associated solid-state storage media 110n stores index metadata. In an alternate embodiment, the solid-state storage device controller 202 includes a single solid-state controller 104a with a single solid-state storage media 110a. In another embodiment, there are a plurality of solid-state storage controllers 104a-n and associated solid-state storage media 110a-n. In one embodiment, one or more solid-state controllers 104a-104n−1, coupled to their associated solid-state storage media 110a-110n−1, control data while at least one solid-state storage controller 104n, coupled to its associated solid-state storage media 110n, controls index metadata.
In one embodiment, at least one solid-state controller 104 is 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 FIG. 3. In another embodiment, at least one solid-state storage controller 104 is made up of a combination FPGA, ASIC, and custom logic components.
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.0 216a) 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 column of solid-state storage elements 216, 218, 220 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. In one embodiment, a solid-state storage media 110a includes twenty solid-state storage elements per bank (e.g. 216a-m in bank 214a, 218 a-m in bank 214b, 220a-m in bank 214n, where m=22) with eight banks (e.g. 214a-n where n=8) and a solid-state storage media 110n includes two solid-state storage elements (e.g. 216a-m where m=2) per bank 214 with one bank 214a. There is no requirement that two solid-state storage media 110a, 110n have the same number of solid-state storage elements and/or same number of banks 214. In one embodiment, each solid-state storage element 216, 218, 220 is comprised of a 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 for multiple banks that share a common storage I/O bus 210a row (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.0 216a) 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.0 216a 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 0.8) 216a-220a, each in a separate bank 214a-n. In another embodiment, 20 storage elements (e.g. SSS 0.0-SSS 20.0) 216 form a virtual bank 214a so that each of the eight virtual banks has 20 storage elements (e.g. SSS0.0-SSS 20.8). 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 0.8) 216a, 218a, 220a. The storage control bus 212a is used to select a particular bank (e.g. Bank-0 214a) 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 row share one of the independent I/O buses across each solid-state storage element 216, 218, 220 in parallel so that all banks 214 are accessed simultaneously. For example, one HOB 210a.a 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 HOB 210a.b 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 elements 216, 218, 220 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 using either of the chip select signal and the chip enable signal. 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. A typical page is 2000 bytes (“2 kB”). In one example, a solid-state storage element (e.g. SSS0.0) includes two registers and can program two pages so that a two-register solid-state storage element has a page size of 4 kB. A single bank 214a of 20 solid-state storage elements 216a-m would then have an 80 kB capacity of pages accessed with the same address going out of the storage I/O bus 210.
This group of pages in a bank 214 of solid-state storage elements 216, 218, 220 of 80 kB may be called a logical 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. In one embodiment, erasing a logical erase block causes a physical erase block of each storage element 216a-m of a bank 214a to be erased. 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. In another embodiment, a single physical erase block on each storage element (e.g. SSS M.N) collectively forms a logical erase block for the solid-state storage media 110a. In such an embodiment, erasing a logical erase block comprises erasing an erase block at the same address within each storage element (e.g. SSS M.N) in the solid-state storage media 110a. 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 may 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.
In one embodiment, data is written in packets to the storage elements. The solid-state controller 104 uses the storage I/O bus 210 and storage control bus 212 to address a particular bank 214, storage element 216, 218, 220, physical erase block, physical page, and optionally offset within a physical page for writing the data packet. In one embodiment, the solid-state controller 104 sends the address information for the data packet by way of the storage I/O bus 210 and signals that the data on the storage I/O bus 210 is address data by way of particular signals set on the storage control bus 212. The solid-state controller 104 follows the transmission of the address information with transmission of the data packet of data that is to be stored. The physical address contains enough information for the solid-state storage element 216, 218, 220 to direct the data packet to the designated location within the page.
In one embodiment, the storage I/O bus 210a.a connects to each storage element in a row of storage elements (e.g. SSS 0.0-SSS 0.N 216a, 218a, 220a). In such an embodiment, the solid-state controller 104a activates a desired bank 214a using the storage control bus 212a, such that data on storage I/O bus 210a.a reaches the proper page of a single storage element (e.g. SSS 0.0 216a).
In addition, in certain embodiments, the solid-state controller 104a simultaneously activates the same bank 214a using the storage control bus 212a, such that different data (a different data packet) on storage I/O bus 210a.b reaches the proper page of a single storage element on another row (e.g. SSS 1.0 216b). In this manner, multiple physical pages of multiple storage elements 216, 218, 220 may be written to simultaneously within a single bank 214 to store a logical page.
Similarly, a read command may require a command 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 physical page from each storage element, and because there are multiple solid-state storage elements 216, 218, 220 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.
In one embodiment, a solid-state controller 104 may send an erase block erase command over all the lines of the storage I/O bus 210 to erase a physical erase block having a particular erase block address. In addition, the solid-state controller 104 may simultaneously activate a single bank 214 using the storage control bus 212 such that each physical erase block in the single activated bank 214 is erased as part of a logical erase block.
In another embodiment, the solid-state controller 104 may send an erase block erase command over all the lines of the storage I/O bus 210 to erase a physical erase block having a particular erase block address on each storage element 216, 218, 220 (SSS 0.0-SSS M.N). These particular physical erase blocks together may form a logical erase block. Once the address of the physical erase blocks is provided to the storage elements 216, 218, 220, the solid-state controller 104 may initiate the erase command on a bank 214a by bank 214b by bank 214n basis (either in order or based on some other sequence). 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, the storage controller 104 sequentially writes data on the solid-state storage media 110 in a log structured format and within one or more physical structures of the storage elements, the data is sequentially stored on the solid-state storage media 110. Sequentially writing data involves the storage controller 104 streaming data packets into storage write buffers for storage elements, such as a chip (a package of one or more dies) or a die on a circuit board. When the storage write buffers are full, the data packets are programmed to a designated virtual or logical page (“LP”). Data packets then refill the storage write buffers and, when full, the data packets are written to the next LP. The next virtual page may be in the same bank 214a or another bank (e.g. 214b). This process continues, LP after LP, typically until a virtual or logical erase block (“LEB”) is filled. LPs and LEBs are described in more detail below.
In another embodiment, the streaming may continue across LEB boundaries with the process continuing, LEB after LEB. Typically, the storage controller 104 sequentially stores data packets in an LEB by order of processing. In one embodiment, where a write data pipeline 106 is used, the storage controller 104 stores packets in the order that they come out of the write data pipeline 106. This order may be a result of data segments arriving from a requesting device mixed with packets of valid data that are being read from another storage location as valid data is being recovered from another LEB during a recovery operation.
The sequentially stored data, in one embodiment, can serve as a log to reconstruct data indexes and other metadata using information from data packet headers. For example, in one embodiment, the storage controller 104 may reconstruct a storage index by reading headers to determine the data structure to which each packet belongs and sequence information to determine where in the data structure the data or metadata belongs. The storage controller 104, in one embodiment, uses physical address information for each packet and timestamp or sequence information to create a mapping between the physical locations of the packets and the data structure identifier and data segment sequence. Timestamp or sequence information is used by the storage controller 104 to replay the sequence of changes made to the index and thereby reestablish the most recent state.
In one embodiment, erase blocks are time stamped or given a sequence number as packets are written and the timestamp or sequence information of an erase block is used along with information gathered from container headers and packet headers to reconstruct the storage index. In another embodiment, timestamp or sequence information is written to an erase block when the erase block is recovered.
In a read, modify, write operation, data packets associated with the logical structure are located and read in a read operation. Data segments of the modified structure 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 to the next available location in the virtual page currently being written. 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 logical structure that have not been modified will include pointers to original location of the unmodified data packets. Thus, if the original logical structure is maintained, for example to maintain a previous version of the logical structure, the original logical structure will have pointers in the index to all data packets as originally written. The new logical structure will have pointers in the index to some of the original data packets and pointers to the modified data packets in the virtual page that is currently being written.
In a copy operation, the index includes an entry for the original logical structure mapped to a number of packets stored on the solid-state storage media 110. When a copy is made, a new logical structure is created and a new entry is created in the index mapping the new logical structure to the original packets. The new logical structure is also written to the solid-state storage media 110 with its location mapped to the new entry in the index. The new logical structure packets may be used to identify the packets within the original logical structure that are referenced in case changes have been made in the original logical structure that have not been propagated to the copy and the index is lost or corrupted. In another embodiment, the index includes a logical entry for a logical block.
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 virtual 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.
The system 100 may comprise a log-structured storage system or log-structured array similar to a log-structured file system and the order that data is stored may be used to recreate an index. Typically an index that includes a logical-to-physical mapping is stored in volatile memory. If the index is corrupted or lost, the index may be reconstructed by addressing the solid-state storage media 110 in the order that the data was written. Within a logical erase block (“LEB”), data is typically stored sequentially by filling a first logical page, then a second logical page, etc. until the LEB is filled. The solid-state storage controller 104 then chooses another LEB and the process repeats. By maintaining an order that the LEBs were written to and by knowing that each LEB is written sequentially, the index can be rebuilt by traversing the solid-state storage media 110 in order from beginning to end. In other embodiments, if part of the index is stored in non-volatile memory, such as on the solid-state storage media 110, the solid-state storage controller 104 may only need to replay a portion of the solid-state storage media 110 to rebuild a portion of the index that was not stored in non-volatile memory. 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 0-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 host device 114 or may be other devices.
In one embodiment, 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 certain embodiment where the solid-state storage is arranged in banks 214 and each bank 214 includes multiple storage elements 216, 218, 220 accessible in parallel, the storage I/O bus 210 comprises an array of busses, one for each row 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 row 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 row of storage elements 216a, 218a, 220a. This mapping 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. Remapping is explained further in relation to the remapping module 430 of FIG. 4.
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 155 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 and bridges 238.
The system bus 240 is typically a bus of a host device 114 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 requests, directs creation of indexes to map 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 controller 152/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 a data structure to be written to the data storage devices (e.g. solid-state storage media 110a-n) so that a portion of the data structure is stored on each of the attached data storage devices. This feature is a performance enhancement allowing quicker storage and access to a data structure. 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 emulates block storage such that a host device 114 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 or logical addresses in the storage device/solid-state storage device 102. The master controller 224 then divides up the blocks and stores the data blocks. The master controller 224 then maps the blocks and physical or logical address sent with the block to the actual locations determined by the master controller 224. The mapping is stored in the index. Typically, for block emulation, an API is provided in a driver in the host device 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 host device 114 may have access to a computer network 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, the master controller 224 may be a RAID controller for single tier RAID, multi-tier RAID, progressive RAID, etc. The master controller 224 may also allows some objects and other data structures to be stored in a RAID array and other data structures 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 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 a computer network) 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 or other data structures 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 virtual 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 152, 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 logical-to-physical 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
FIG. 3 is a schematic block diagram illustrating one embodiment 300 of a solid-state storage controller 104 with a write data pipeline 106 and a read data pipeline 108 in a solid-state storage device 102 in accordance with the present invention. The embodiment 300 includes a data bus 204, a local bus 206, and buffer control 208, which are substantially similar to those described in relation to the solid-state storage device controller 202 of FIG. 2. The write data pipeline 106 includes a packetizer 302 and an error-correcting code (“ECC”) generator 304. In other embodiments, the write data pipeline 106 includes an input buffer 306, a write synchronization buffer 308, a write program module 310, a compression module 312, an encryption module 314, a garbage collector bypass 316 (with a portion within the read data pipeline 108), a media encryption module 318, and a write buffer 320. The read data pipeline 108 includes a read synchronization buffer 328, an ECC correction module 322, a depacketizer 324, an alignment module 326, and an output buffer 330. In other embodiments, the read data pipeline 108 may include a media decryption module 332, a portion of the garbage collector bypass 316, a decryption module 334, a decompression module 336, and a read program module 338. 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 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 308 328 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 such as the host device 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 and/or the host device 114. 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 indicate 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 generator 304 that that generates one or more error-correcting codes (“ECC”) for the one or more packets received from the packetizer 302. The ECC generator 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 generator 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 generator 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 generator 304 and corresponding ECC correction module 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 generator 304 may use a less robust algorithm and may correct single-bit or double-bit errors. In another embodiment, the solid-state storage device 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 host device 114, 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 generator 304 prior to writing the packets to the solid-state storage media 110. The write synch 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 308 328 may be eliminated.
In one embodiment, the write data pipeline 106 also includes a media encryption module 318 that receives the one or more packets from the packetizer 302, either directly or indirectly, and encrypts the one or more packets using an encryption key unique to the solid-state storage device 102 prior to sending the packets to the ECC generator 304. Typically, the entire packet is encrypted, including the headers. In another embodiment, headers are not encrypted. In this document, encryption key is understood to mean a secret encryption key that is managed externally from a solid-state storage controller 104.
The media encryption module 318 and corresponding media decryption module 332 provide a level of security for data stored in the solid-state storage media 110. For example, where data is encrypted with the media encryption module 318, if the solid-state storage media 110 is connected to a different solid-state storage controller 104, solid-state storage device 102, or server, 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 a typical embodiment, the solid-state storage device 102 does not store the encryption key in non-volatile storage and allows no external access to the encryption key. The encryption key is provided to the solid-state storage controller 104 during initialization. The solid-state storage device 102 may use and store a non-secret cryptographic nonce that is used in conjunction with an 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 host device 114, a server, key manager, or other device that manages the encryption key to be used by the solid-state storage controller 104. In another embodiment, the solid-state storage media 110 may have two or more partitions and the solid-state storage controller 104 behaves as though it was two or more solid-state storage controllers 104, each operating on a single partition within the solid-state storage media 110. In this embodiment, a unique media encryption key may be used with each partition.
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-state 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 host device 114, a 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, a computer, a host device 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 host device 114, 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 the host device 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 a host device 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 correction module 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 correction module 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 correction module 322 corrects ECC blocks of the requested packet with up to three bits in error. The ECC correction module 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.
If the ECC correction module 322 determines that the requested packets contains more bits in error than the ECC can correct, the ECC correction module 322 cannot correct the errors in the corrupted ECC blocks of the requested packet and sends an interrupt. In one embodiment, the ECC correction module 322 sends an interrupt with a message indicating that the requested packet is in error. The message may include information that the ECC correction module 322 cannot correct the errors or the inability of the ECC correction module 322 to correct the errors may be implied. In another embodiment, the ECC correction module 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 correction module 322 is read by the master controller 224, corrected, and returned to the ECC correction module 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 correction module 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 correction module 322 determining that one or more ECC blocks of the requested packet are corrupted and that the ECC correction module 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 correction module 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 read data pipeline 108 includes a media decryption module 332 that receives one or more encrypted requested packets from the ECC correction module 322 and decrypts the one or more requested packets using the encryption key unique to the solid-state storage device 102 prior to sending the one or more requested packets to the depacketizer 324. Typically the encryption key used to decrypt data by the media decryption module 332 is identical to the encryption key used by the media encryption module 318. In another embodiment, the solid-state storage media 110 may have two or more partitions and the solid-state storage controller 104 behaves as though it was two or more solid-state storage controllers 104 each operating on a single partition within the solid-state storage media 110. In this embodiment, a unique media encryption key may be used with each partition.
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 host device 114, a computer, 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 FIG. 3, may be located in another position within the read data pipeline 108, or may include multiple parts in multiple locations within the read data pipeline 108. Additionally, there may be multiple read program modules 338 within multiple locations within the read data pipeline 108 that operate independently. One of skill in the art will recognize other forms of a read program module 338 within a read data pipeline 108. As with the write data pipeline 106, the stages of the read data pipeline 108 may be rearranged and one of skill in the art will recognize other orders of stages within the read data pipeline 108.
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 generator 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 the 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, which are described in relation to FIG. 4.
Bank Interleave
FIG. 4 is a schematic block diagram illustrating one embodiment 400 of a bank interleave controller 344 in the solid-state storage controller 104 in accordance with the present invention. The bank interleave controller 344 is connected to the control and status registers 340 and to the storage I/O bus 210 and storage control bus 212 through the MUX 350, storage bus controller 348, and synchronization buffer 346, which are described below. The bank interleave controller 344 includes a read agent 402, a write agent 404, an erase agent 406, a management agent 408, read queues 410a-n, write queues 412a-n, erase queues 414a-n, and management queues 416a-n for the banks 214 in the solid-state storage media 110, bank controllers 418a-n, a bus arbiter 420, and a status MUX 422, which are described below. The storage bus controller 348 includes a mapping module 424 with a remapping module 430, a status capture module 426, and a NAND bus controller 428, which are described below.
The bank interleave controller 344 directs one or more commands to two or more queues in the bank interleave controller 104 and coordinates among the banks 214 of the solid-state storage media 110 execution of the commands stored in the queues, such that a command of a first type executes on one bank 214a while a command of a second type executes on a second bank 214b. The one or more commands are separated by command type into the queues. Each bank 214 of the solid-state storage media 110 has a corresponding set of queues within the bank interleave controller 344 and each set of queues includes a queue for each command type.
The bank interleave controller 344 coordinates among the banks 214 of the solid-state storage media 110 execution of the commands stored in the queues. For example, a command of a first type executes on one bank 214a while a command of a second type executes on a second bank 214b. Typically the command types and queue types include read and write commands and queues 410, 412, but may also include other commands and queues that are storage media specific. For example, in the embodiment depicted in FIG. 4, erase and management queues 414, 416 are included and would be appropriate for flash memory, NRAM, MRAM, DRAM, PRAM, etc.
For other types of solid-state storage media 110, other types of commands and corresponding queues may be included without straying from the scope of the invention. The flexible nature of an FPGA solid-state storage controller 104 allows flexibility in storage media. If flash memory were changed to another solid-state storage type, the bank interleave controller 344, storage bus controller 348, and MUX 350 could be altered to accommodate the media type without significantly affecting the data pipelines 106, 108 and other solid-state storage controller 104 functions.
In the embodiment depicted in FIG. 4, the bank interleave controller 344 includes, for each bank 214, a read queue 410 for reading data from the solid-state storage media 110, a write queue 412 for write commands to the solid-state storage media 110, an erase queue 414 for erasing an erase block in the solid-state storage, an a management queue 416 for management commands. The bank interleave controller 344 also includes corresponding read, write, erase, and management agents 402, 404, 406, 408. In another embodiment, the control and status registers 340 and control queues 342 or similar components queue commands for data sent to the banks 214 of the solid-state storage media 110 without a bank interleave controller 344.
The agents 402, 404, 406, 408, in one embodiment, direct commands of the appropriate type destined for a particular bank 214a to the correct queue for the bank 214a. For example, the read agent 402 may receive a read command for bank-1 214b and directs the read command to the bank-1 read queue 410b. The write agent 404 may receive a write command to write data to a location in bank-0 214a of the solid-state storage media 110 and will then send the write command to the bank-0 write queue 412a. Similarly, the erase agent 406 may receive an erase command to erase an erase block in bank-1 214b and will then pass the erase command to the bank-1 erase queue 414b. The management agent 408 typically receives management commands, status requests, and the like, such as a reset command or a request to read a configuration register of a bank 214, such as bank-0 214a. The management agent 408 sends the management command to the bank-0 management queue 416a. 
The agents 402, 404, 406, 408 typically also monitor status of the queues 410, 412, 414, 416 and send status, interrupt, or other messages when the queues 410, 412, 414, 416 are full, nearly full, non-functional, etc. In one embodiment, the agents 402, 404, 406, 408 receive commands and generate corresponding sub-commands. In one embodiment, the agents 402, 404, 406, 408 receive commands through the control & status registers 340 and generate corresponding sub-commands which are forwarded to the queues 410, 412, 414, 416. One of skill in the art will recognize other functions of the agents 402, 404, 406, 408.
The queues 410, 412, 414, 416 typically receive commands and store the commands until required to be sent to the solid-state storage banks 214. In a typical embodiment, the queues 410, 412, 414, 416 are first-in, first-out (“FIFO”) registers or a similar component that operates as a FIFO. In another embodiment, the queues 410, 412, 414, 416 store commands in an order that matches data, order of importance, or other criteria.
The bank controllers 418 typically receive commands from the queues 410, 412, 414, 416 and generate appropriate subcommands. For example, the bank-0 write queue 412a may receive a command to write a page of data packets to bank-0 214a. The bank-0 controller 418a may receive the write command at an appropriate time and may generate one or more write subcommands for each data packet stored in the write buffer 320 to be written to the page in bank-0 214a. For example, bank-0 controller 418a may generate commands to validate the status of bank 0 214a and the solid-state storage array 216, select the appropriate location for writing one or more data packets, clear the input buffers within the solid-state storage memory array 216, transfer the one or more data packets to the input buffers, program the input buffers into the selected location, verify that the data was correctly programmed, and if program failures occur do one or more of interrupting the master controller 224, retrying the write to the same physical location, and retrying the write to a different physical location. Additionally, in conjunction with example write command, the storage bus controller 348 will cause the one or more commands to multiplied to each of the each of the storage I/O buses 210a-n with the logical address of the command mapped to a first physical addresses for storage I/O bus 210a, and mapped to a second physical address for storage I/O bus 210b, and so forth as further described below.
Typically, bus arbiter 420 selects from among the bank controllers 418 and pulls subcommands from output queues within the bank controllers 418 and forwards these to the Storage Bus Controller 348 in a sequence that optimizes the performance of the banks 214. In another embodiment, the bus arbiter 420 may respond to a high level interrupt and modify the normal selection criteria. In another embodiment, the master controller 224 can control the bus arbiter 420 through the control and status registers 340. One of skill in the art will recognize other means by which the bus arbiter 420 may control and interleave the sequence of commands from the bank controllers 418 to the solid-state storage media 110.
The bus arbiter 420 typically coordinates selection of appropriate commands, and corresponding data when required for the command type, from the bank controllers 418 and sends the commands and data to the storage bus controller 348. The bus arbiter 420 typically also sends commands to the storage control bus 212 to select the appropriate bank 214. For the case of flash memory or other solid-state storage media 110 with an asynchronous, bi-directional serial storage I/O bus 210, only one command (control information) or set of data can be transmitted at a time. For example, when write commands or data are being transmitted to the solid-state storage media 110 on the storage I/O bus 210, read commands, data being read, erase commands, management commands, or other status commands cannot be transmitted on the storage I/O bus 210. For example, when data is being read from the storage I/O bus 210, data cannot be written to the solid-state storage media 110.
For example, during a write operation on bank-0 the bus arbiter 420 selects the bank-0 controller 418a which may have a write command or a series of write sub-commands on the top of its queue which cause the storage bus controller 348 to execute the following sequence. The bus arbiter 420 forwards the write command to the storage bus controller 348, which sets up a write command by selecting bank-0 214a through the storage control bus 212, sending a command to clear the input buffers of the solid-state storage elements 110 associated with the bank-0 214a, and sending a command to validate the status of the solid-state storage elements 216, 218, 220 associated with the bank-0 214a. The storage bus controller 348 then transmits a write subcommand on the storage I/O bus 210, which contains the physical addresses including the address of the logical erase block for each individual physical erase solid-stage storage element 216a-m as mapped from the logical erase block address. The storage bus controller 348 then muxes the write buffer 320 through the write sync buffer 308 to the storage I/O bus 210 through the MUX 350 and streams write data to the appropriate page. When the page is full, then storage bus controller 348 causes the solid-state storage elements 216a-m associated with the bank-0 214a to program the input buffer to the memory cells within the solid-state storage elements 216a-m. Finally, the storage bus controller 348 validates the status to ensure that page was correctly programmed.
A read operation is similar to the write example above. During a read operation, typically the bus arbiter 420, or other component of the bank interleave controller 344, receives data and corresponding status information and sends the data to the read data pipeline 108 while sending the status information on to the control and status registers 340. Typically, a read data command forwarded from bus arbiter 420 to the storage bus controller 348 will cause the MUX 350 to gate the read data on storage I/O bus 210 to the read data pipeline 108 and send status information to the appropriate control and status registers 340 through the status MUX 422.
The bus arbiter 420 coordinates the various command types and data access modes so that only an appropriate command type or corresponding data is on the bus at any given time. If the bus arbiter 420 has selected a write command, and write subcommands and corresponding data are being written to the solid-state storage media 110, the bus arbiter 420 will not allow other command types on the storage I/O bus 210. Beneficially, the bus arbiter 420 uses timing information, such as predicted command execution times, along with status information received concerning bank 214 status to coordinate execution of the various commands on the bus with the goal of minimizing or eliminating idle time of the busses.
The master controller 224 through the bus arbiter 420 typically uses expected completion times of the commands stored in the queues 410, 412, 414, 416, along with status information, so that when the subcommands associated with a command are executing on one bank 214a, other subcommands of other commands are executing on other banks 214b-n. When one command is fully executed on a bank 214a, the bus arbiter 420 directs another command to the bank 214a. The bus arbiter 420 may also coordinate commands stored in the queues 410, 412, 414, 416 with other commands that are not stored in the queues 410, 412, 414, 416.
For example, an erase command may be sent out to erase a group of erase blocks within the solid-state storage media 110. An erase command may take 10 to 1000 times more time to execute than a write or a read command or 10 to 100 times more time to execute than a program command. For N banks 214, the bank interleave controller 344 may split the erase command into N commands, each to erase a virtual erase block of a bank 214a. While bank-0 214a is executing an erase command, the bus arbiter 420 may select other commands for execution on the other banks 214b-n. The bus arbiter 420 may also work with other components, such as the storage bus controller 348, the master controller 224, etc., to coordinate command execution among the buses. Coordinating execution of commands using the bus arbiter 420, bank controllers 418, queues 410, 412, 414, 416, and agents 402, 404, 406, 408 of the bank interleave controller 344 can dramatically increase performance over other solid-state storage systems without a bank interleave function.
In one embodiment, the solid-state controller 104 includes one bank interleave controller 344 that serves all of the storage elements 216, 218, 220 of the solid-state storage media 110. In another embodiment, the solid-state controller 104 includes a bank interleave controller 344 for each column of storage elements 216a-m, 218a-m, 220a-m. For example, one bank interleave controller 344 serves one column of storage elements SSS 0.0-SSS M.0 216a, 216b, . . . 216m, a second bank interleave controller 344 serves a second column of storage elements SSS 0.1-SSS M.1 218a, 218b, . . . 218m etc.
Storage-Specific Components
The solid-state storage controller 104 includes a synchronization buffer 346 that buffers commands and status messages sent and received from the solid-state storage media 110. The synchronization buffer 346 is located 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. The synchronization buffer 346, write synchronization buffer 308, and read synchronization buffer 328 may be independent or may act together to buffer data, commands, status messages, etc. In one embodiment, the synchronization buffer 346 is located where there are the fewest number of signals crossing the clock domains. One skilled in the art will recognize that synchronization between clock domains may be arbitrarily moved to other locations within the solid-state storage device 102 in order to optimize some aspect of design implementation.
The solid-state storage controller 104 includes a storage bus controller 348 that interprets and translates commands for data sent to and read from the solid-state storage media 110 and status messages received from the solid-state storage media 110 based on the type of solid-state storage media 110. For example, the storage bus controller 348 may have different timing requirements for different types of storage, storage with different performance characteristics, storage from different manufacturers, etc. The storage bus controller 348 also sends control commands to the storage control bus 212.
In one embodiment, the solid-state storage controller 104 includes a MUX 350 that comprises an array of multiplexers 350a-n where each multiplexer is dedicated to a row in the solid-state storage array 110. For example, multiplexer 350a is associated with solid-state storage elements 216a, 218a, 220a. MUX 350 routes the data from the write data pipeline 106 and commands from the storage bus controller 348 to the solid-state storage media 110 via the storage I/O bus 210 and routes data and status messages from the solid-state storage media 110 via the storage I/O bus 210 to the read data pipeline 108 and the control and status registers 340 through the storage bus controller 348, synchronization buffer 346, and bank interleave controller 344.
In one embodiment, the solid-state storage controller 104 includes a MUX 350 for each row of solid-state storage elements (e.g. SSS 0.1 216a, SSS 0.2 218a, SSS 0.N 220a). A MUX 350 combines data from the write data pipeline 106 and commands sent to the solid-state storage media 110 via the storage I/O bus 210 and separates data to be processed by the read data pipeline 108 from commands. Packets stored in the write buffer 320 are directed on busses out of the write buffer 320 through a write synchronization buffer 308 for each row of solid-state storage elements (SSS x.0 to SSS x.N 216, 218, 220) to the MUX 350 for each row of solid-state storage elements (SSS x.0 to SSS x.N 216, 218, 220). The commands and read data are received by the MUXes 350 from the storage I/O bus 210. The MUXes 350 also direct status messages to the storage bus controller 348.
The storage bus controller 348 includes a mapping module 424. The mapping module 424 maps a logical address of an erase block to one or more physical addresses of an erase block. For example, a solid-state storage media 110 with an array of twenty storage elements (e.g. SSS 0.0 to SSS M.0 216) per block 214a may have a logical address for a particular erase block mapped to twenty physical addresses of the erase block, one physical address per storage element. Because the storage elements are accessed in parallel, erase blocks at the same position in each storage element in a row of storage elements 216a, 218a, 220a will share a physical address. To select one erase block (e.g. in storage element SSS 0.0 216a) instead of all erase blocks in the row (e.g. in storage elements SSS 0.0, 0.1, . . . 0.N 216a, 218a, 220a), one bank (in this case bank-0 214a) is selected.
This logical-to-physical mapping for erase blocks is beneficial because if one erase block becomes damaged or inaccessible, the mapping can be changed to map to another erase block. This mitigates the loss of losing an entire virtual erase block when one element's erase block is faulty. The remapping module 430 changes a mapping of a logical address of an erase block to one or more physical addresses of a virtual erase block (spread over the array of storage elements). For example, virtual erase block 1 may be mapped to erase block 1 of storage element SSS 0.0 216a, to erase block 1 of storage element SSS 1.0 216b, . . . , and to storage element M.0 216m, virtual erase block 2 may be mapped to erase block 2 of storage element SSS 0.1 218a, to erase block 2 of storage element SSS 1.1 218b, . . . , and to storage element M.1 218m, etc. Alternatively, virtual erase block 1 may be mapped to one erase block from each storage element in an array such that virtual erase block 1 includes erase block 1 of storage element SSS 0.0 216a to erase block 1 of storage element SSS 1.0 216b to storage element M.0 216m, and erase block 1 of storage element SSS 0.1 218a to erase block 1 of storage element SSS 1.1 218b, . . . , and to storage element M.1 218m, for each storage element in the array up to erase block 1 of storage element M.N 220m. 
If erase block 1 of a storage element SSS0.0 216a is damaged, experiencing errors due to wear, etc., or cannot be used for some reason, the remapping module 430 could change the logical-to-physical mapping for the logical address that pointed to erase block 1 of virtual erase block 1. If a spare erase block (call it erase block 221) of storage element SSS 0.0 216a is available and currently not mapped, the remapping module 430 could change the mapping of virtual erase block 1 to point to erase block 221 of storage element SSS 0.0 216a, while continuing to point to erase block 1 of storage element SSS 1.0 216b, erase block 1 of storage element SSS 2.0 (not shown) . . . , and to storage element M.0 216m. The mapping module 424 or remapping module 430 could map erase blocks in a prescribed order (virtual erase block 1 to erase block 1 of the storage elements, virtual erase block 2 to erase block 2 of the storage elements, etc.) or may map erase blocks of the storage elements 216, 218, 220 in another order based on some other criteria.
In one embodiment, the erase blocks could be grouped by access time. Grouping by access time, meaning time to execute a command, such as programming (writing) data into pages of specific erase blocks, can level command completion so that a command executed across the erase blocks of a virtual erase block is not limited by the slowest erase block. In other embodiments, the erase blocks may be grouped by wear level, health, etc. One of skill in the art will recognize other factors to consider when mapping or remapping erase blocks.
In one embodiment, the storage bus controller 348 includes a status capture module 426 that receives status messages from the solid-state storage media 110 and sends the status messages to the status MUX 422. In another embodiment, when the solid-state storage media 110 is flash memory, the storage bus controller 348 includes a NAND bus controller 428. The NAND bus controller 428 directs commands from the read and write data pipelines 106, 108 to the correct location in the solid-state storage media 110, coordinates timing of command execution based on characteristics of the flash memory, etc. If the solid-state storage media 110 is another solid-state storage type, the NAND bus controller 428 would be replaced by a bus controller specific to the storage type. One of skill in the art will recognize other functions of a NAND bus controller 428.
Data Caching
FIG. 5 depicts one embodiment of a host device 114. The host device 114 may be similar, in certain embodiments, to the host device 114 depicted in FIGS. 1A and 1B. The depicted embodiment includes a user application 502 in communication with a storage client 504. The storage client 504 is in communication with a direct cache module 116, which, in one embodiment, is substantially similar to the direct cache module 116 of FIGS. 1A and 1B, described above. The direct cache module 116, in the depicted embodiment, is in communication with the solid-state storage device 102 through the solid-state storage controller 104. The direct cache module 116 and/or the solid-state storage controller 104 may be in communication with the backing store 118 through a backing store controller 120 or the like.
In one embodiment, the user application 502 is a software application operating on or in conjunction with the storage client 504. The storage client 504 manages file systems, files, data, and the like and utilizes the functions and features of the direct cache module 116, the solid-state storage device 102, and the backing store 118. Representative examples of storage clients include, but are not limited to, a server, a file system, an operating system, a DBMS, a volume manager, and the like. Both user applications 502 and storage clients 504 may be clients 120 of the direct cache module 116 as described above with regard to FIG. 1B, and may use and manage VSUs 122 as cache unit VSUs 122.
In the depicted embodiment, the storage client 504 is in communication with the direct cache module 116, over a cache interface 112 or the like. In a further embodiment, the storage client 504 may also be in communication with the solid-state storage device 102 and/or the backing store 118 directly, for non-cache related functions or the like. The storage client 504, in one embodiment, reads data from and writes data to the backing store 118 through the direct cache module 116, which uses the solid-state storage device 102 to cache read data and write data for the backing store 118 in one or more VSUs 122 configured as cache unit VSUs 122.
In one embodiment, the direct cache module 116 (through the solid-state storage controller 104 or the like) has exclusive access to, and/or control over the solid-state storage device 102 and the backing store 118. The direct cache module 116 may represent itself to the storage client 504 as a storage device. For example, the direct cache module 116 may represent itself as a conventional block storage device. In a particular embodiment, the direct cache module 116 may represent itself to the storage client 504 as a storage device having the same number of logical blocks (0 to N) as the backing store 118, as a storage device having the same number of logical blocks of the backing store that are associated with a specific VSU 122, or the like. In another embodiment, the direct cache module 116 may represent itself to the storage client 504 as a storage device that has more logical blocks (0 to N+X) than the backing store 118, where X=the number of logical blocks addressable for a VSU 122 by the direct cache module 116 beyond N. In certain embodiments, X=2^64−N.
As described above with regard to the direct cache module 116 depicted in the embodiment of FIG. 1A, in various embodiments, the direct cache module 116 may be embodied by one or more of a storage controller 104 of the solid-state storage device 102 and/or a storage controller 120 of the backing store 118; a separate hardware controller device that interfaces with the solid-state storage device 102 and the backing store 118; a device driver/software controller loaded on the host device 114; or the like.
In one embodiment, the host device 114 loads a device driver for the direct cache module 116. In a further embodiment, the host device 114 loads device drivers for the solid-state storage device 102 and/or the backing store 118. The direct cache module 116 may communicate with the solid-state storage device 102 and/or the backing store 118 through device drivers loaded on the host device 114, through a storage controller 104 of the solid-state storage device 102 and/or through a storage controller 120 of the backing store 118, or the like. Hardware and/or software elements of the direct cache module 116 may form a cache controller for the solid-state storage device 102 and may be in communication with the solid-state storage controller 104, sending commands to the solid-state storage controller 104 to manage operation of the solid-state storage device 102.
In one embodiment, the storage client 504 communicates with the direct cache module 116 through an input/output (“I/O”) interface represented by a block I/O emulation layer 506. The block I/O emulation layer 506 may be part of the cache interface 112, the cache interface 112 may be a separate control channel, or the like.
In a further embodiment, the solid-state storage device 102 and/or the backing store 118 either include a distinct block I/O emulation layer 506 or are conventional block storage devices. Certain conventional block storage devices divide the storage media into volumes or partitions. Each volume or partition may include a plurality of sectors. One or more sectors are organized into a logical block. In certain storage systems, such as those interfacing with the Windows® operating systems, the logical blocks are referred to as clusters. In other storage systems, such as those interfacing with UNIX, Linux, or similar operating systems, the logical blocks are referred to simply as blocks. A logical block or cluster represents a smallest physical amount of storage space on the storage media that is addressable by the storage client 504. A block storage device may associate n logical blocks available for user data storage across the storage media with a logical block address, numbered from 0 to n. In certain block storage devices, the logical block addresses may range from 0 to n per volume or partition. In conventional block storage devices, a logical block address maps directly to a particular logical block. In conventional block storage devices, each logical block maps to a particular set of physical sectors on the storage media.
However, the direct cache module 116, the solid-state storage device 102 and/or the backing store 118 may not directly or necessarily associate logical block addresses with particular physical blocks. The direct cache module 116, the solid-state storage device 102, and/or the backing store 118 may emulate a conventional block storage interface to maintain compatibility with block storage clients 504 and with conventional block storage commands and protocols.
When the storage client 504 communicates through the block I/O emulation layer 506, the direct cache module 116 (or a cache unit VSU 122 of the direct cache module 116) appears to the storage client 504 as a conventional block storage device. In one embodiment, the direct cache module 116 provides the block I/O emulation layer 506 which serves as a block device interface, or API, over the cache interface 112 or in addition to the cache interface 112. In this embodiment, the storage client 504 communicates with the direct cache module 116 through this block device interface. In one embodiment, the block I/O emulation layer 506 receives commands and logical block addresses from the storage client 504 in accordance with this block device interface. As a result, the block I/O emulation layer 506 provides the direct cache module 116 compatibility with block storage clients 504. In certain embodiment, the direct cache module 116 may communicate with the solid-state storage device 102 and/or the backing store 118 using corresponding block device interfaces. In embodiments where the block I/O emulation layer 506 is separate from the cache interface 112, the direct cache module 116 may receive storage commands over the block I/O emulation layer 506 and receive cache management commands over the cache interface 112.
In one embodiment, a storage client 504 communicates with the direct cache module 116 through a direct interface layer 508. The cache interface 112 described above with regard to FIGS. 1A and 1B is one example of a direct interface layer 508. In this embodiment, the direct cache module 116 directly exchanges information specific to the solid-state storage device 102 and/or the backing store 118 with the storage client 504. Similarly, the direct cache module 116, in one embodiment, may communicate with the solid-state storage device 102 and/or the backing store 118 through direct interface layers 508.
A direct cache module 116 using the direct interface 508 may store data on the solid-state storage device 102 and/or the backing store 118 as blocks, sectors, pages, logical blocks, logical pages, erase blocks, logical erase blocks, ECC chunks or in any other format or structure advantageous to the technical characteristics of the solid-state storage device 102 and/or the backing store 118. For example, in one embodiment, the backing store 118 comprises a hard disk drive and the direct cache module 116 stores data on the backing store 118 as contiguous sectors of 512 bytes, or the like, using physical cylinder-head-sector addresses for each sector, logical block addresses for each sector, or the like. The direct cache module 116 may receive a logical address and a command from the storage client 504 and perform the corresponding operation in relation to the solid-state storage device 102, and/or the backing store 118. The direct cache module 116, the solid-state storage device 102, and/or the backing store 118 may support a block I/O emulation layer 506, a direct interface 508, or both a block I/O emulation layer 506 and a direct interface 508 as part of a cache interface 112 or the like.
As described above, certain storage devices, while appearing to a storage client 504 to be a block storage device, do not directly associate particular logical block addresses with particular physical blocks, also referred to in the art as sectors. Such storage devices may use a logical-to-physical translation layer 510. In the depicted embodiment, the solid-state storage controller 104 includes a logical-to-physical translation layer 510. In a further embodiment, the backing store 118 may also include a logical-to-physical translation layer 510. In another embodiment, the solid-state storage controller 104 maintains a single logical-to-physical translation layer 510 for the solid-state storage device 102 and the backing store 118. In another embodiment, the solid-state storage controller 104 maintains a distinct logical-to-physical translation layer 510 for each of the solid-state storage device 102 and the backing store 118.
The logical-to-physical translation layer 510 provides a level of abstraction between the logical block addresses used by the storage client 504 and the physical block addresses at which the solid-state storage device 102 and/or the backing store 118 store the data. In the depicted embodiment, the logical-to-physical translation layer 510 maps logical block addresses to physical block addresses of data stored on the media 110 of the solid-state storage device 102. This mapping allows data to be referenced in a logical address space using logical identifiers, such as a logical block address. A logical identifier does not indicate the physical location of data in the solid-state storage device 102, but is an abstract reference to the data. The mapping module 424 and the remapping module 430 of FIG. 4, discussed above, are one example of a logical-to-physical translation layer 510. Further examples of a logical-to-physical translation layer 510, in various embodiments, include the direct mapping module 808, the forward mapping module 802, and the reverse mapping module 804 of FIG. 8, each of which are discussed below.
In the depicted embodiment, the solid-state storage device 102 and the backing store 118 separately manage the physical block addresses in the distinct, separate physical address spaces of the solid-state storage device 102 and the backing store 118. In one example, contiguous logical block addresses may in fact be stored in non-contiguous physical block addresses as the logical-to-physical translation layer 510 determines the location on the physical media 110 of the solid-state storage device 102 at which to perform data operations.
Furthermore, in one embodiment, the logical address space of the solid-state storage device 102 is substantially larger than the physical address space or storage capacity of the solid-state storage device 102. This “thinly provisioned” or “sparse address space” embodiment, allows the number of logical addresses for data references to greatly exceed the number of possible physical addresses. A thinly provisioned and/or sparse address space also allows the solid-state storage device 102 to cache data for a backing store 118 with a larger address space (i.e. a larger storage capacity) than the physical address space of the solid-state storage device 102.
In one embodiment, the logical-to-physical translation layer 510 includes a map or index that maps logical block addresses to physical block addresses. The map or index may be in the form of a B-tree, a content addressable memory (“CAM”), a binary tree, and/or a hash table, and the like. In certain embodiments, the logical-to-physical translation layer 510 is a tree with nodes that represent logical block addresses and include references to corresponding physical block addresses. Example embodiments of B-tree mapping structure are described below with regard to FIGS. 10 and 11.
As stated above, in conventional block storage devices, a logical block address maps directly to a particular physical block. When a storage client 504 communicating with the conventional block storage device deletes data for a particular logical block address, the storage client 504 may note that the particular logical block address is deleted and can re-use the physical block associated with that deleted logical block address without the need to perform any other action.
Conversely, when a storage client 504, communicating with a storage controller 104 or device driver with a logical-to-physical translation layer 510 (a storage controller 104 or device driver that does not map a logical block address directly to a particular physical block), deletes data of a logical block address, the corresponding physical block address may remain allocated because the storage client 504 may not communicate the change in used blocks to the storage controller 104 or device driver. The storage client 504 may not be configured to communicate changes in used blocks (also referred to herein as “data block usage information”). Because the storage client 504, in one embodiment, uses the block I/O emulation 506 layer, the storage client 504 may erroneously believe that the direct cache module 116, the solid-state storage device 102, and/or the backing store 118 is a conventional block storage device that would not utilize the data block usage information. Or, in certain embodiments, other software layers between the storage client 504 and the direct cache module 116, the solid-state storage device 102, and/or the backing store 118 may fail to pass on data block usage information.
Consequently, the storage controller 104 or device driver may preserve the relationship between the logical block address and a physical address and the data on the solid-state storage device 102 and/or the backing store 118 corresponding to the physical block. As the number of allocated blocks increases, the performance of the solid-state storage device 102 and/or the backing store 118 may suffer depending on the configuration of the solid-state storage device 102 and/or the backing store 118.
Specifically, in certain embodiments, the solid-state storage device 102, and/or the backing store 118 are configured to store data sequentially, using an append-only writing process, and use a storage space recovery process that re-uses non-volatile storage media storing deallocated/unused logical blocks. Specifically, as described above, the solid-state storage device 102, and/or the backing store 118 may sequentially write data on the solid-state storage media 110 in a log structured format and within one or more physical structures of the storage elements, the data is sequentially stored on the solid-state storage media 110. Those of skill in the art will recognize that other embodiments that include several solid-state storage devices 102 can use the same append-only writing process and storage space recovery process.
As a result of storing data sequentially and using an append-only writing process, the solid-state storage device 102 and/or the backing store 118 achieve a high write throughput and a high number of I/O operations per second (“IOPS”). The solid-state storage device 102 and/or the backing store 118 may include a storage space recovery, or garbage collection process that re-uses data storage cells to provide sufficient storage capacity. The storage space recovery process reuses storage cells for logical blocks marked as deallocated, invalid, unused, or otherwise designated as available for storage space recovery in the logical-physical translation layer 510. In one embodiment, the direct cache module 116 marks logical blocks as deallocated or invalid based on a cache eviction policy, to recover storage capacity for caching additional data for the backing store 118. The storage space recovery process is described in greater detail below with regard to the storage space recovery module 806 of FIG. 8.
As described above, the storage space recovery process determines that a particular section of storage may be recovered. Once a section of storage has been marked for recovery, the solid-state storage device 102 and/or the backing store 118 may relocate valid blocks in the section. The storage space recovery process, when relocating valid blocks, copies the packets and writes them to another location so that the particular section of storage may be reused as available storage space, typically after an erase operation on the particular section. The solid-state storage device 102 and/or the backing store 118 may then use the available storage space to continue sequentially writing data in an append-only fashion. Consequently, the storage controller 104 expends resources and overhead in preserving data in valid blocks. Therefore, physical blocks corresponding to deleted logical blocks may be unnecessarily preserved by the storage controller 104, which expends unnecessary resources in relocating the physical blocks during storage space recovery.
Some storage devices are configured to receive messages or commands notifying the storage device of these unused logical blocks so that the storage device may deallocate the corresponding physical blocks. As used herein, to deallocate a physical block includes marking the physical block as invalid, unused, or otherwise designating the physical block as available for storage space recovery, its contents on storage media no longer needing to be preserved by the storage device. Data block usage information may also refer to information maintained by a storage device regarding which physical blocks are allocated and/or deallocated/unallocated and changes in the allocation of physical blocks and/or logical-to-physical block mapping information. Data block usage information may also refer to information maintained by a storage device regarding which blocks are in use and which blocks are not in use by a storage client 504. Use of a block may include storing of data in the block on behalf of the storage client 504, reserving the block for use by the storage client 504, and the like.
While physical blocks may be deallocated, in certain embodiments, the solid-state storage device 102 and/or the backing store 118 may not immediately erase the data on the storage media. An erase operation may be performed later in time. In certain embodiments, the data in a deallocated physical block may be marked as unavailable by the solid-state storage device 102 and/or the backing store 118 such that subsequent requests for data in the physical block return a null result or an empty set of data.
One example of a command or message for such deallocation is the “TRIM” function of the “Data Set Management” command under the T13 technical committee command set specification maintained by INCITS. A storage device, upon receiving a TRIM command, may deallocate physical blocks for logical blocks whose data is no longer needed by the storage client 504. A storage device that deallocates physical blocks may achieve better performance and increased storage space, especially storage devices that write data using certain processes and/or use a similar data storage recovery process as that described above.
Consequently, the performance of the storage device is enhanced as physical blocks are deallocated when they are no longer needed such as through the TRIM command or other similar deallocation commands issued to the solid-state storage device 102 and/or the backing store 118. In one embodiment, the direct cache module 116 clears, trims, and/or evicts cached data from the solid-state storage device 102 based on a cache eviction policy, or the like. As used herein, clearing, trimming, or evicting data includes deallocating physical media associated with the data, marking the data as invalid or unused (using either a logical or physical address of the data), erasing physical media associated with the data, overwriting the data with different data, issuing a TRIM command or other deallocation command relative to the data, or otherwise recovering storage capacity of physical storage media corresponding to the data. Clearing cached data from the solid-state storage device 102 based on a cache eviction policy frees storage capacity in the solid-state storage device 102 to cache more data for the backing store 118.
The direct cache module 116, in various embodiments, may represent itself, the solid-state storage device 102, and the backing store 118 to the storage client 504 in different configurations. In one embodiment, the direct cache module 116 may represent itself to the direct cache module 116 as a cache device (e.g. as a cache device with certain cache functions or APIs available over the cache interface 112, or the like). The backing store 118 may be separately visible and/or available to the storage client 504 (with parts of the physical capacity of the backing store 118 reserved for each VSU 122 of the solid-state storage device 102 or the like). In a further embodiment, the direct cache module 116 may represent itself to the storage client 504 as a hybrid cache/storage device including both the solid-state storage device 102 and the backing store 118.
Depending on the configuration, the direct cache module 116 may pass certain commands down to the solid-state storage device 102 and/or to the backing store 118 and may not pass down other commands. In a further embodiment, the direct cache module 116 may support certain custom or new block I/O commands. In one embodiment, the direct cache module 116 supports a deallocation or trim command that clears corresponding data from both the solid-state storage device 102 and the backing store 118, i.e. the direct cache module 116 passes the command to both the solid-state storage device 102 and the backing store 118. In a further embodiment, the direct cache module 116 supports a flush type trim or deallocation command that ensures that corresponding data is stored in the backing store 118 (i.e. that the corresponding data in the solid-state storage device 102 is clean) and clears the corresponding data from the solid-state storage device 102, without clearing the corresponding data from the backing store 118. In another embodiment, the direct cache module 116 supports an evict type trim or deallocation command that evicts corresponding data from the solid-state storage device 102, marks corresponding data for eviction in the solid-state storage device 102, or the like, without clearing the corresponding data from the backing store 118.
In a further embodiment, the direct cache module 116 may receive, detect, and/or intercept one or more predefined commands that a storage client 504 or another storage manager sent to the backing store 118, that a storage manager sends to a storage client 504, or the like. For example, in various embodiments, the direct cache module 116 or a portion of the direct cache module 116 may be part of a filter driver that receives or detects the predefined commands, the direct cache module 116 may register with an event server to receive a notification of the predefined commands, or the like. In another embodiment, the direct cache module 116 may present a cache interface 112 or another API through which the direct cache module 116 receives predefined commands. The direct cache module 116, in one embodiment, performs one or more actions on the solid-state storage device 102 in response to detecting or receiving one or more predefined commands for the backing store 118, such as writing or flushing data related to a command from the solid-state storage device 102 to the backing store 118, evicting data related to a command from the solid-state storage device 102, switching from a write back policy to a write through policy for data related to a command, or the like.
One example of predefined commands that the direct cache module 116 may intercept or respond to, in one embodiment, includes a “freeze/thaw” commands. “Freeze/thaw” commands are used in SANs, storage arrays, and the like, to suspend storage access, such as access to the backing store 118 or the like, to take an snapshot or backup of the storage without interrupting operation of the applications using the storage. “Freeze/thaw” commands alert a storage client 504 that a snapshot is about to take place, the storage client 504 flushes pending operations, for example in-flight transactions, or data cached in volatile memory, the snapshot takes place while the storage client 504 use of the storage is in a “frozen” or ready state, and once the snapshot is complete the storage client 504 continues normal use of the storage in response to a thaw command.
The direct cache module 116, in one embodiment, flushes or cleans dirty data from the solid-state storage device 102 to the backing store 118 in response to detecting a “freeze/thaw” command. In a further embodiment, the direct cache module 116 suspends access to the backing store 118 during a snapshot or other backup of a detected “freeze/thaw” command and resumes access in response to a completion of the snapshot or other backup. In another embodiment, the direct cache module 116 may cache data for the backing store 118 during a snapshot or other backup without interrupting the snapshot or other backup procedure. In other words, rather than the backup/snapshot software signaling the application to quiesce I/O operations, the direct cache module 116 receives and responds to the freeze/thaw commands. Other embodiments of predefined commands may include one or more of a read command, a write command, a TRIM command, an erase command, a flush command, a pin command, an unpin command, and the like.
FIG. 6 depicts one embodiment of the direct cache module 116. The direct cache module 116, in various embodiments, may be substantially similar to the direct cache module 116 described above with regard to FIG. 1A, FIG. 1B, and/or FIG. 5. In the depicted embodiment, the direct cache module 116 includes a cache interface module 602, a cache command module 604, and a cache management module 606.
In one embodiment, the cache interface module 602 provides clients 120 with access to a plurality of VSUs 122 over a cache interface 112. At least one of the VSUs 122 is configured as a cache unit VSU 122. A cache unit VSU 122 is a VSU 122 that the direct cache module 116 configures to cache data for a client 120. The cache interface module 602 may provide the cache interface 112 as an API, as a hardware command channel, or as another communications interface. The cache interface module 602, in certain embodiments, provides the cache interface 112 as a two way interface, over which clients 120 may communicate with the direct cache module 116 and over which the direct cache module 116 may communicate with clients 120.
The cache command module 604, in one embodiment, exchanges cache management information for at least one cache unit VSU 122 with one or more cache clients 120 over a cache interface 112. Cache management information includes commands, notifications, and/or other communications associated with the creation, maintenance, and execution of cache unit VSUs 122 or other VSUs 122. The cache command module 604 may support a predefined set of cache commands and/or other cache communications for managing cache unit VSUs 122. In one embodiment, the cache command module 604 receives cache management information from clients 120. In a further embodiment, the cache command module 604 sends cache management information to clients 120.
Clients 120, in one embodiment, may issue virtual storage unit commands to the cache command module 604 over the cache interface 112. The cache command module 604 and/or the cache management module 606 may cooperate with or be integrated with the solid-state storage controller 104 to process and fulfill virtual storage unit commands. Virtual storage unit commands and management of VSUs 122 are described in greater detail below with regard to the virtual storage unit module 812 of FIG. 8. Examples of virtual storage unit commands which the cache command module 604 may receive include create commands, delete commands, enumerate commands, TRIM commands, resize commands, or the like. Using these virtual storage unit commands, a client 120 may create a new VSU 122, configure the VSU 122 as a cache unit, and the like.
In another embodiment, a client 120 may select a logical address space type for a cache unit VSU 122 over the cache interface 112. The direct cache module 116 may support multiple types of logical address spaces, such as a sparse logical address space type, a contiguous block address space type, or the like. In one embodiment, different VSUs 122 of the same solid-state storage device 102 may have different logical address space types at the same time. Certain clients 120 may request that a VSU 122 use or export a sparse address space to reduce metadata overhead, as sparse address spaces track only LBAs that are allocated and in use. Other clients 120 may request that a VSU 122 use or export a contiguous block-address space, where each LBA is tracked with associated metadata, regardless of whether the LBA is allocated and in use.
In response to a client 120 creating a VSU 122 and configuring the VSU 122 as a cache unit VSU 122, the client 120 may send additional cache management commands to the cache command module 604. Examples of cache management commands that the cache command module 604 may receive from a cache client 120 over the cache interface 112 may include cache admission commands, cache eviction commands, cache prefetch commands, cache destage commands, quality-of-service commands, physical capacity allotment commands, TRIM commands, data priority commands, or the like. Those of skill in the art, in light of this disclosure, will recognize other cache management commands which the cache command module 604 may support.
A cache admission command, in one embodiment, defines what data an associated cache unit VSU 122 should cache for a client 120. For example, a client 120 may select one or more ranges of LBAs for which the client 120 would like a cache unit VSU 122 to cache data, i.e. admit to the cache unit VSU 122, or the like. A cache eviction command, in certain embodiments, instructs the direct cache module 116 to evict specified data from a cache unit VSU 122, according to an LBA of the data or the like. A cache prefetch command instructs the direct cache module 116 to retrieve or prefetch specified data from the backing store 118 and to store the specified data in a cache unit VSU 122, without a read or write miss for the specified data.
A cache destage command instructs the direct cache module 116 to destage specified data from a cache unit VSU 122 to the backing store 118. For example, a cache destage command may specify that an entire cache unit VSU 122 is to be destaged (a flush operation), that data of a range of LBAs is to be destaged, or the like. A quality-of-service command sets a service level for a cache unit VSU 122, relative to other cache unit VSUs 122 or the like. A physical capacity allotment command sets an amount of the storage capacity of the solid-state storage media 110 that is available for a cache unit VSU 122. A TRIM command requests that the direct cache module 116 persistently clear associated blocks from a cache unit VSU 122. For example, if a client 120 is using a cache unit VSU 122 in a write around mode, the client 120 may use TRIM commands to clear invalid data from the cache unit VSU 122, or the like. A data priority command prioritizes data either within a single cache unit VSU 122 or between multiple cache unit VSUs 122. For example, certain data may have higher retention or replication requirements than other data, and may be assigned a higher priority, or the like. In embodiments where the data priority command determines a prioritization between VSUs 122, the cache management module 606 may allocate physical storage capacity of the solid-state storage device 102 between the different VSUs 122 according to the prioritization identified by the data priority command.
In another embodiment, the cache management information includes one or more messages that the cache command module 604 sends to clients 120 over the cache interface 112. One embodiment of a message that the cache command module 604 may send to a client 120 is an eviction request. An eviction request may be a request for permission to evict specified data from a cache unit VSU 122, a request for a client 120 to identify data to evict, or the like, typically identified by an LBA of the data.
One type of eviction request is a garbage collection request that the cache command module 604 sends to one or more cache clients 120. In one embodiment, a garbage collection request is a notification that a garbage collection or storage capacity recovery operation is going to begin. In a further embodiment, a garbage collection request identifies LBAs of an erase block that the solid-state storage controller 104 has selected for garbage collection, so that a cache client 120 may indicate which data of the selected erase block may be evicted from the associated cache unit VSU 122. For example, a cache client 120 may send a garbage collection response to the cache command module 604 identifying LBAs of data in an erase block that may be evicted. Evicting data during a garbage collection operation can reduce the overhead of copying the data forward to a new location, also referred to as write amplification, thereby increasing the efficiency of the solid-state storage device 102.
Another embodiment of a message that the cache command module 604 may send to one or more clients 120 is an available storage capacity report. The available storage capacity report may identify a remaining amount of available storage capacity for the solid-state storage device 102 and/or for one or more VSUs 122. In one embodiment, where the cache management module 606 reduces storage capacity of the solid-state storage device 102 over time in response to data errors as described below, the cache command module 604 may send an available storage capacity report notifying one or more cache clients 120, over the cache interface 112, of the reduced storage capacity of the solid-state storage device 102. One of skill in the art, in light of this disclosure, will recognize other messages and notifications that the cache command module 604 may send to cache clients 120 over the cache interface 112.
In one embodiment, the cache management module 606 manages each cache unit VSU 122 based on cache management information that the cache command module 604 exchanges with the one or more cache clients 120 over the cache interface 112. The cache management module 606, in certain embodiments, may cooperate with or be integrated with the solid-state storage controller 104 to manage VSUs 122, such as those configured as cache unit VSUs 122 or the like. A virtual storage unit module 812, as described below with regard to FIG. 8, may manage VSUs 122 generally (for non-cache-specific management or the like) based on management information exchanged with the one or more clients 120 over the storage controller interface 124.
In response to a virtual storage unit command, in one embodiment, the cache management module 606 cooperates with the solid-state storage controller 104 to manage a VSU 122. For example, the cache management module 606 may create a VSU 122, configure a VSU 122 as a cache unit VSU 122, delete a VSU 122, enumerate or list existing VSUs 122 to a client 122, trim or clear data from a VSU 122, resize a VSU 122, or the like, depending on the specific command. In one embodiment, the cache management module 606 sets a logical address space type for a VSU 122, such as a cache unit VSU 122, in response to a client 120 sending the cache command module 604 a command selecting a logical address space type for the VSU 122, such as a sparse logical address space type, a contiguous block address space type, or the like. The cache management module 606 may set how the direct cache module 116 presents the logical address space to clients 120 (i.e. sparsely or contiguously), may set whether the underlying mapping is sparse or contiguous, or both. Management of VSUs 122 is described in greater detail below with regard to the virtual storage unit module 812 of FIG. 8.
In response to a cache admission command, the cache management module 606 may admit data identified by the cache admission command into a cache unit VSU 122. In response to a cache eviction command, the cache management module 606 may evict or clear identified data from a cache unit VSU 122. The cache management module 608, in response to receiving a cache prefetch command, may populate a cache unit VSU 122 with data identified in the cache prefetch command. In response to a cache destage command, the cache management module 608 may destage dirty data from a cache unit VSU 122 to the backing store 118. The cache management module 608 may cooperate with the destage module 704 described below with regard to FIG. 7 to destage data to the backing store 118.
In response to a quality-of-service command from a client 120, the cache management module 608 may enforce a specified level of quality-of-service with regard to one or more VSUs 122, such as cache unit VSUs 122 or the like. The cache management module 608, in response to a TRIM command, may persistently remove, delete, invalidate, evict, or otherwise clear blocks of data from a VSU 122. In response to a data priority command, the cache management module 608 may enforce an identified priority (either within a VSU 122 or between multiple VSUs 122). For example, the cache management module 608 may follow a predefined retention policy, replication policy, or the like based on an identified priority. In another embodiment, the cache management module 606 allocates physical storage capacity of the solid-state storage device 102 between the VSUs 122 according to a prioritization of VSUs 122 from a data priority command, allocating more storage capacity to VSUs 122 with a higher priority, or the like. In certain embodiments, the cache management module 606 may thinly provision one or more VSUs 122, and may not allocate physical storage capacity of the solid-state storage media 110 to a VSU 122 until a client 120 sends a write request for a logical block address associated with the VSU 122.
The cache management module 606, in one embodiment, selects data for eviction from one or more cache unit VSUs 122 based on cache management information from the one or more clients 120. The cache management module 606 may cooperate with the eviction module 706 described below with regard to FIG. 7 to evict data. The cache management module 606, in certain embodiments, may evict data based on a prioritization of VSUs 122 (such as cache unit VSUs 122), evicting data from lower priority cache unit VSUs 122 before evicting data from higher priority cache unit VSUs 122, evicting more data from lower priority cache unit VSUs 122, or the like. In another embodiment, the cache management module 606 evicts data that a client 120 has selected or authorized for eviction. For example, as described above, the cache command module 604 may send a garbage collection request to one or more clients 120 and a client 120 may send back a garbage collection response identifying data that may be evicted, or a client 120 may send an eviction request, and the cache management module 606 may evict the identified data.
In one embodiment, the cache management module 606 reduces a usable storage capacity of the solid-state storage device 102 over time in response to data errors. As described above, the cache command module 604 may notify one or more clients 120 of the reduced storage capacity. To reduce the storage capacity, the cache management module 606, in certain embodiments, may dynamically remove a storage element from operation in response to data errors for the storage element satisfying a threshold as the solid-state storage device 102 ages, such as a bit error rate, an uncorrectable bit error rate, or the like that satisfies a predefined error threshold.
In certain embodiments, selecting data for eviction based on information from clients 120 and otherwise managing cache unit VSUs 122 and/or other VSUs 122 based on information and commands from clients 120 allows the clients 120 to determine their own policies and to customize aspects of their associated VSUs 122 to fit the specific usage patterns of the clients 120. As clients 120 share cache management information or other management information with the direct cache module 116, such as which data may be evicted, in one embodiment, cache unit VSUs 122 cache data more optimally for the clients 120 and the solid-state storage controller 104 operates more efficiently because data may be evicted instead of copied forward and retained.
FIG. 7 depicts another embodiment of the direct cache module 116. In certain embodiments, the direct cache module 116 of FIG. 7 may be substantially similar to the direct cache module 116 described above with regard to FIGS. 1A, 1B, 5, and 6. In the depicted embodiment, the direct cache module 116 includes the cache interface module 602, the cache command module 604, and the cache management module 606. The direct cache module 116, in the depicted embodiment, further includes a cache fulfillment module 702, a destage module 704, and an eviction module 706. The cache fulfillment module 702, in the depicted embodiment, includes a write request module 718 and a read request module 720.
In one embodiment, the cache fulfillment module 702 detects input/output (“I/O”) requests from the one or more clients 120, such as read requests, write requests, erase requests, TRIM requests, and/or other I/O requests for the backing store 118 or the like. The cache fulfillment module 702 may detect an I/O request by receiving the I/O request directly, detecting an I/O request sent to a different module or entity (such as detecting an I/O request sent directly to the backing store 118), or the like. In one embodiment, the host device 114 sends the I/O request. The direct cache module 116, in one embodiment, represents itself to the host device 114 as a storage device, and the host device 114 sends I/O requests directly to the cache fulfillment module 702.
An I/O request, in one embodiment, may include or may request data that is not stored in a cache unit VSU 122 of the solid-state storage device 102. Data that is not stored on the solid-state storage device 102, in various embodiments, may include new data not yet stored on the backing store 118, modifications to data that is stored on the backing store 118, data that is stored on the backing store 118 but not currently stored in a cache unit VSU 122 of the solid-state storage device 102, or the like. An I/O request, in various embodiments, may directly include data, may include a reference, a pointer, or an address for data, or the like. For example, in one embodiment, an I/O request (such as a write request or the like) may include a range of addresses indicating data to be stored on the backing store 118 by way of a Direct Memory Access (“DMA”) or Remote DMA (“RDMA”) operation.
In a further embodiment, a single I/O request may include several different contiguous and/or noncontiguous ranges of addresses or blocks. In a further embodiment, an I/O request may include one or more destination addresses for data, such as logical and/or physical addresses for the data on the solid-state storage device 102 and/or on the backing store 118. The cache fulfillment module 702 and/or another cooperating module, in various embodiments, may retrieve the data of an I/O request directly from an I/O request itself, from a storage location referenced by an I/O request (i.e. from a location in system memory or other data storage referenced in a DMA or RDMA request), or the like.
The cache fulfillment module 702 also satisfies the I/O requests that it detects. In certain embodiments, if the storage controller 104 determines that the solid-state storage device 102 stores data of an I/O request, such as storing at least one data block of the I/O request or the like, the cache fulfillment module 702 satisfies the I/O request at least partially using the solid-state storage device 102. The cache fulfillment module 702 satisfies an I/O request based on the type of I/O request. For example, the cache fulfillment module 702 may satisfy a write I/O request by storing data of the I/O request to the solid-state storage device 102, may satisfy a read I/O request by reading data of the I/O request from the solid-state storage device 102, and the like.
In one embodiment, if the storage controller 104 (using the direct mapping module 808 described below or the like) determines that the solid-state storage device 102 does not store data of an I/O request, i.e. there is a cache miss, the cache fulfillment module 702 stores data of the I/O request to an associated cache unit VSU 122 of the solid-state storage device 102. The cache fulfillment module 702, in response to a write I/O request, a cache miss, or the like, in certain embodiments, stores data of an I/O request to the solid-state storage media 110 of the solid-state storage device 102 sequentially to preserve an ordered sequence of I/O operations performed on the solid-state storage media 110. For example, the cache fulfillment module 702 may store the data of I/O requests to the solid-state storage device 102 sequentially by appending the data to an append point of a sequential, log-based, cyclic writing structure of the solid-state storage media 110, in the order that the cache fulfillment module 702 receives the I/O requests. Because, in certain embodiments, the cache fulfillment module 702 stores cached data sequentially, regardless of which cache unit VSU 122 the data is associated with, data from a plurality of VSUs 122 may be intermingled in the sequential, log-based, cyclic writing structure of the solid-state storage device 102. One embodiment of a sequential, log-based, cyclic writing structure is described below with regard to FIG. 11.
The cache fulfillment module 702, in one embodiment, stores data in a manner that associates the data with a sequence indicator for the data. The cache fulfillment module 702 may store a numerical sequence indicator as metadata with data of an I/O request, may use the sequential order of a log-based writing structure as a sequence indicator, or the like. In a further embodiment, the cache fulfillment module 702 stores data in a manner that associates the data with respective logical addresses of the data, storing one or more logical block addresses of the data with the data in a sequential, log-based writing structure or the like. By storing sequence indicators and logical addresses of data with the data on the solid-state storage media 110 of the solid-state storage device 102, the cache fulfillment module 702 enables the storage controller 104 to reconstruct, rebuild, and/or recover entries in the mapping structure using the stored sequence indicators and logical addresses, as described below.
The cache fulfillment module 702, in the depicted embodiment, includes a write request module 718 and a read request module 720. In one embodiment, the write request module 718 services and satisfies write I/O requests that the cache fulfillment module 702 detects, as described above. A write request, in one embodiment, includes data that is not stored on the backing store 118, such as new data not yet stored on the backing store 118, modifications to data that is stored on the backing store 118, and the like. A write request, in various embodiments, may directly include the data, may include a reference, a pointer, or an address for the data, or the like. For example, in one embodiment, a write request includes a range of addresses indicating data to be stored on the backing store 118 by way of a Direct Memory Access (“DMA”) or Remote DMA (“RDMA”) operation.
In a further embodiment, a single write request may include several different contiguous and/or noncontiguous ranges of addresses or blocks. In a further embodiment, a write request includes one or more destination addresses for the associated data, such as logical and/or physical addresses for the data on the backing store 118. The write request module 718 and/or another cooperating module, in various embodiments, may retrieve the data of a write request directly from the write request itself, from a storage location referenced by a write request (i.e. from a location in system memory or other data storage referenced in a DMA or RDMA request), or the like to service the write request.
The write request module 718, in one embodiment, writes data of a write request to the solid-state storage device 102 at one or more logical addresses of the solid-state storage device 102 corresponding to the addresses of the write request as mapped by the direct mapping module 808, described below. The VSUs 122, including cache unit VSUs 122, may share a single logical address space of the solid-state storage device 102 (each having an offset within the single logical address space), may each have separate logical address spaces (which may be mapped to a single logical address space of the solid-state storage device 102), or the like. In embodiments where the VSUs 122 have separate, overlapping logical address spaces, clients 120 may address each VSU 122 as a separate, independent storage device, and the cache fulfillment module 702 may service the VSUs 122 as such.
In one embodiment, the write request module 718 writes the data of the write request to the solid-state storage device 102 by appending the data to a sequential, log-based, cyclic writing structure of the physical solid-state storage media 110 of the solid-state storage device 102 at an append point, with data from different VSUs 122 intermingled in the log-based writing structure. The write request module 718, in one embodiment, returns one or more physical addresses or locations corresponding to the append point and the direct mapping module 808 (described below) maps the one or more logical addresses of the solid-state storage device 102 to the one or more physical addresses corresponding to the append point.
In one embodiment, the read request module 720 services and satisfies read I/O requests that the cache fulfillment module 702 detects for data stored in the solid-state storage device 102 and/or the backing store 118. A read request is a read command with an indicator, such as a logical address or range of logical addresses, of the data being requested. In one embodiment, the read request module 720 supports read requests with several contiguous and/or noncontiguous ranges of logical addresses, as discussed above with regard to the cache fulfillment module 702.
In the depicted embodiment, the read request module 720 includes a read miss module 722 and a read retrieve module 724. The read miss module 722, in one embodiment, determines whether or not requested data is stored in a corresponding VSU 122 of the solid-state storage device 102, in cooperation with the direct mapping module 808 (described below) or the like. The read miss module 722 may query the solid-state storage device 102 directly, query the direct mapping module 808, query the mapping structure of the direct mapping module 808, or the like to determine whether or not requested data is stored in a VSU 122 of the solid-state storage device 102.
The read retrieve module 724, in one embodiment, returns requested data to the requesting entity, such as a client 120. If the read miss module 722 determines that a VSU 122 of the solid-state storage device 102 stores the requested data, in one embodiment, the read retrieve module 724 reads the requested data from the solid-state storage device 102 and returns the data to the requesting entity. The direct mapping module 808, in one embodiment, provides the read retrieve module 724 with one or more physical addresses of the requested data in the solid-state storage device 102 by mapping one or more logical addresses of the requested data to the one or more physical addresses of the requested data.
If the read miss module 722 determines that a VSU 122 of the solid-state storage device 102 does not store the requested data, in one embodiment, the read retrieve module 724 reads the requested data from the backing store 118, stores the requested data to the corresponding VSU 122 of the solid-state storage device 102, and returns the requested data to the requesting entity to satisfy the associated read request. In one embodiment, the read retrieve module 724 writes the requested data to the corresponding VSU 122 of the solid-state storage device 102 by appending the requested data to an append point of a sequential, log-based, cyclic writing structure of the solid-state storage device 102. In a further embodiment, the read retrieve module 724 provides one or more physical addresses corresponding to the append point to the direct mapping module 808 (described below) with the one or more logical addresses of the requested data and the direct mapping module 808 adds and/or updates the mapping structure with the mapping of logical and physical addresses for the requested data.
In one embodiment, the read miss module 722 detects a partial miss, where the corresponding VSU 122 of the solid-state storage device 102 stores one portion of the requested data but does not store another. A partial miss, in various embodiments, may be the result of eviction of the unstored data, a block I/O request for noncontiguous data, or the like. The read miss module 722, in one embodiment, reads the missing data or “hole” data from the backing store 118 and returns both the portion of the requested data from the VSU 122 and the portion of the requested data from the backing store 118 to the requesting entity. In one embodiment, the read miss module 722 stores the missing data retrieved from the backing store 118 in the corresponding VSU 122 of the solid-state storage device 102.
In one embodiment, the destage module 704 writes data from the solid-state storage device 102 to the backing store 118, destaging or cleaning the data. In certain embodiments, the destage module 704 destages data in cooperation with or under direction from the cache management module 606 based on cache management information from one or more clients 120. Data that is stored in a cache unit VSU 122 of the solid-state storage device 102 that is not yet stored in the backing store 118 is referred to as “dirty” data. Once the backing store 118 stores data, the data is referred to as “clean.” The destage module 704 cleans data in cache unit VSUs 122 of the solid-state storage device 102 by writing the data to the backing store 118. The destage module 704, in one embodiment, may determine an address for the data in the backing store 118 based on a write request corresponding to the data. In a further embodiment, the destage module 704 determines an address for the data in the backing store 118 based on a logical address of the data in a VSU 122 of the solid-state storage device 102, based on the mapping structure of the direct mapping module 808 (described below), or the like. In another embodiment, the destage module 704 uses the reverse mapping module 804 (described below) to determine an address for the data in the backing store 118 based on a physical address of the data in the solid-state storage device 102.
The destage module 704, in one embodiment, writes data to the backing store 118 based on a write policy. In one embodiment, the destage module 704 uses a write-back write policy, and does not immediately write data of a write request to the backing store 118 upon receiving the write request. Instead, the destage module 704, in one embodiment, performs an opportunistic or “lazy” write, writing data to the backing store 118 when the data is evicted from a cache unit VSU 122 of the solid-state storage device 102, when the solid-state storage device 102 and/or the direct cache module 116 has a light load, when available storage capacity in the solid-state storage device 102 (or a VSU 122) falls below a threshold, or the like. In a write-back embodiment, the destage module 704 reads data from a cache unit VSU 122 of the solid-state storage device 102, writes the data to the backing store 118, and sets an indicator that the backing store 118 stores the data, in response to successfully writing the data to the backing store 118. Setting the indicator that the backing store 118 stores the data alerts the storage space recovery module 806 (described below) that the data may be cleared from the solid-state storage device 102 and/or alerts the eviction module 706 that the data may be evicted from the solid-state storage device 102.
In one embodiment, the destage module 704 sets an indicator that the backing store 118 stores data by marking the data as clean in the solid-state storage device 102. In a further embodiment, the destage module 704 may set an indicator that the backing store 118 stores data by communicating an address of the data to the direct mapping module 808 (described below), sending a request to the direct mapping module 808 to update an indicator in a logical to physical mapping or other mapping structure, or the like.
In one embodiment, the destage module 704 maintains a separate data structure indicating which data in the solid-state storage device 102 is clean and which data is dirty. In another embodiment, the destage module 704 references indicators in a mapping of logical addresses to physical media addresses, such as a mapping structure maintained by the direct mapping module 808, to determine which data in the solid-state storage device 102 is clean and which data is dirty.
In another embodiment, instead of cleaning data according to a write-back write policy, the destage module 704 uses a write-through policy, performing a synchronous write to the backing store 118 for each write request that the cache fulfillment module 702 receives. The destage module 704, in one embodiment, transitions from a write-back to a write-through write policy in response to a predefined error condition, such as an error or failure of the solid-state storage device 102, or the like.
The eviction module 706, in one embodiment, evicts data from cache unit VSUs 122 of the solid-state storage device 102 in cooperation with or under direction from the cache management module 606 based on cache management information from one or more clients 120. In certain embodiments, the cache management module 606 and/or the eviction module 706 may evict data based on a cache eviction policy. The cache eviction policy, in one embodiment, is based on a combination or a comparison of one or more cache eviction factors, including cache management information from clients 120. In one embodiment, the cache eviction factors include data priority information, garbage collection responses, physical storage capacity allocations, and/or other cache management information from a client 120. For example, the cache management module 606 may use the eviction module 706 to selectively evict data from multiple cache unit VSUs 122 to maintain a priority of the cache unit VSUs 122, to enforce a physical storage capacity allocation, to evict data selected by a client 120, or the like.
In certain embodiments, the cache eviction factors include wear leveling of the physical storage media 110. In another embodiment, the cache eviction factors include a determined reliability of a section of the physical storage media 110. In a further embodiment, the cache eviction factors include a failure of a section of the physical storage media 110. The cache eviction factors, in one embodiment, include a least recently used (“LRU”) block of data. In another embodiment, the cache eviction factors include a frequency of access of a block of data, i.e. how “hot” or “cold” a block of data is. In one embodiment, the cache eviction factors include a position of a block of data in the physical storage media 110 relative to other “hot” data. One of skill in the art, in light of this specification, will recognize other cache eviction factors suitable for use in the cache eviction policy.
In one embodiment, the direct mapping module 808 (described below) determines one or more of the cache eviction factors based on a history of access to the mapping structure. The direct mapping module 808, in a further embodiment, identifies areas of high frequency, “hot,” use and/or low frequency, “cold,” use by monitoring accesses of branches or nodes in the mapping structure. The direct mapping module 808, in a further embodiment, determines a count or frequency of access to a branch, directed edge, or node in the mapping structure. In one embodiment, a count associated with each node of a b-tree like mapping structure may be incremented for each I/O read operation and/or each I/O write operation that visits the node in a traversal of the mapping structure. Of course, separate read counts and write counts may be maintained for each node. Certain counts may be aggregated to different levels in the mapping structure in other embodiments. The eviction module 706, in one embodiment, evicts data from cache unit VSUs 122 of the solid-state storage device 102 intelligently and/or opportunistically based on activity in the mapping structure monitored by the direct mapping module 808, based on information about the physical storage media 110, and/or based on other cache eviction factors.
The cache interface module 602, in one embodiment, uses cache management information from the clients 120 to increase the efficiency of the solid-state storage device 102, to reduce cache misses, to make intelligent eviction decisions, and the like, based on the preferences, needs, and use cases of individual clients 120. One example of a benefit of sharing information between the clients 120 and the cache management module 606, in certain embodiments, is that write amplification can be reduced. As described below, in one embodiment, the storage space recovery module 806 copies any valid data in an erase block forward to the current append point of the log-based append-only writing structure of the solid-state storage device 102 before recovering the physical storage capacity of the erase block.
By cooperating with the cache management module 606 and/or with the eviction module 706, in one embodiment, the storage space recovery module 806 may clear certain valid data from an erase block without copying the data forward (for example because a client 120 has indicated that the data may be evicted), reducing write amplification, increasing available physical storage capacity and efficiency. Those of skill in the art, in light of this disclosure, will appreciate a variety of other examples and scenarios in which the modules responsible for managing the non-volatile storage media 110 that uses a log-based append-only writing structure can leverage the cache management information available to the direct cache module 116 from clients 120.
In another example, the cache management module 606, the eviction module 706, and the storage space recovery module 806, in one embodiment, cooperate such that selection of one or more blocks of data by the eviction module 706 is influenced by the Uncorrectable Bit Error Rates (UBER), Correctable Bit Error Rates (BER), Program/Erase (PE) cycle counts, read frequency, or other non-volatile solid state storage specific attributes of the region of the solid-state storage media 110 in the solid-state storage device 102 that presently holds the valid data. High BER, UBER, PEs may be used as factors to increase the likelihood that the eviction module 706 will evict a particular block range stored on media having those characteristics, while respecting cache management information from clients 120.
FIG. 8 is a schematic block diagram illustrating one embodiment of a storage controller 104. The storage controller 104, in the depicted embodiment, includes a forward mapping module 802, a reverse mapping module 804, and a storage space recovery module 806, which are described below. At least a portion of one or more of the forward mapping module 802, the reverse mapping module 804, and the storage space recovery module 806 may be located within one or more of the host device 114, the solid-state storage media 110, the storage controller 104, and a computing device separate from the host device 114, the solid-state storage media 110, and the storage controller 104. In general, the storage controller 104 allows the direct cache module 116 to cache data for the backing store 118 in one or more cache unit VSUs 122 without an extra cache mapping layer. Instead of using a cache mapping layer, in one embodiment, the direct mapping module 808 directly maps logical addresses of the backing store 118 to logical addresses of the solid-state storage device 102 (and/or associated VSUs 122) using the same mapping structure that maps the logical addresses of the solid-state storage device 102 to the physical storage media 110 of the solid-state storage device 102.
In one embodiment, the forward mapping module 802 and the reverse mapping module 804 work in conjunction with the direct mapping module 808, described below. The forward mapping module 802 and the reverse mapping module 804 may be part of the direct mapping module 808, may be separate and work together with the direct mapping module 808, or the like.
The storage controller 104, in the depicted embodiment, includes a forward mapping module 802 that uses a forward map to identify one or more physical addresses of data of a data segment. The physical addresses are identified from one or more logical addresses of the data segment, which are identified in a storage request directed to the solid-state storage media 110. For example, a storage request may include a request to read data stored in the solid-state storage media 110. The storage request to read data includes a logical address or logical identifier associated with the data stored on the solid-state storage media 110. The read request may include a logical or virtual address of a file from which the data segment originated, which may be interpreted that the read request is a request to read an entire data segment associated with the logical or virtual address. In one embodiment, storage requests are directed to specific VSUs 122, which may each have separate logical address spaces. In a further embodiment, the cache management module 606 may map logical addresses of each VSU 122 to the single logical address space of the solid-state storage device 102, prior to sending storage requests for the VSUs 122 to the storage controller 104.
The read request, in another example, includes a logical address along with an offset as well a data length of the data requested in the read request. For example, if a data segment is 20 blocks, a read request may include an offset of 16 blocks (i.e. start at block 16 of 20) and a data length of 5 so that the read request reads the last 5 blocks of the data segment. The read request may include an offset and data length also in a request to read an entire data segment or to read from the beginning of a data segment. Other requests may also be included in a storage request, such as a status request. Other types and other forms of storage requests are contemplated within the scope of the present invention and will be recognized by one of skill in the art.
The forward mapping module 802 includes a forward map that maps of one or more logical addresses to one or more physical addresses of data stored in the solid-state storage media 110. The logical addresses correspond to one or more data segments relating to the data stored in the solid-state storage media 110. The forward mapping module 802 may maintain a single mapping structure for the solid-state storage device 102, including mappings for each VSU 122, or may maintain a separate mapping structure for each VSU 122. The one or more logical addresses typically include discrete addresses within a logical address space where the logical addresses sparsely populate the logical address space. For a logical address of a data segment, data length information may also be associated with the logical address and may also be included in the forward map. The data length typically corresponds to the size of the data segment. Combining a logical address and data length information associated with the logical address may be used to facilitate reading a particular portion within a data segment.
Often logical addresses used to identify stored data represent a very small number of logical addresses that are possible within a name space or range of possible logical addresses. Searching this sparsely populated space may be cumbersome. For this reason, the forward map is typically a data structure that facilitates quickly traversing the forward map to find a physical address based on a logical address. For example, the forward map may include a B-tree, a content addressable memory (“CAM”), a binary tree, a hash table, or other data structure that facilitates quickly searching a sparsely populated space or range. By using a forward map that quickly searches a sparsely populated logical namespace or address space, the storage controller 104 provides an efficient way to determine one or more physical addresses from a logical address, even for a plurality of VSUs 122.
While the forward map may be optimized, or at least designed, for quickly determining a physical address from a logical address, typically the forward map is not optimized for locating all of the data within a specific region of the solid-state storage media 110. For this reason, the storage controller 104, in the depicted embodiment, includes a reverse mapping module 804 that uses a reverse map to determine a logical address of a data segment from a physical address. The reverse map is used to map the one or more physical addresses to one or more logical addresses and can be used by the reverse mapping module 804 or other process to determine a logical address from a physical address. The reverse map beneficially maps the solid-state storage media 110 into erase regions such that a portion of the reverse map spans an erase region of the solid-state storage media 110 erased together during a storage space recovery operation. The storage space recovery operation (or garbage collection operation) recovers erase regions for future storage of data. By organizing the reverse map by erase region, the storage space recovery module 806 can efficiently identify an erase region for storage space recovery and identify valid data. The storage space recovery module 806 is discussed in more detail below.
The physical addresses in the reverse map are associated or linked with the forward map so that if logical address A is mapped to physical address B in the forward map, physical address B is mapped to logical address A in the reverse map. In one embodiment, the forward map includes physical addresses that are linked to entries in the reverse map. In another embodiment, the forward map includes pointers to physical addresses in the reverse map or some other intermediate list, table, etc. One of skill in the art will recognize other ways to link physical addresses to the forward map and reverse map.
In one embodiment, the reverse map includes one or more source parameters. The source parameters are typically received in conjunction with a storage request and include at least one or more logical addresses. The source parameters may also include data lengths associated with data of a data segment received in conjunction with a storage request. The source parameters, in one embodiment, may indicate which VSU 122 the data belongs too. In another embodiment, the reverse map does not include source parameters in the form of logical addresses or data lengths and the source are stored with data of the data segment stored on the solid-state storage media 110. In this embodiment, the source parameters may be discovered from a physical address in the reverse map which leads to the source parameters stored with the data. Said differently, the reverse map may use the primary logical-to-physical map rather than the secondary-logical-to-physical map.
Storing the source parameters with the data is advantageous in a sequential storage device because the data stored in the solid-state storage media 110 becomes a log that can be replayed to rebuild the forward and reverse maps. This is due to the fact that the data is stored in a sequence matching when storage requests are received, and thus the source data serves a dual role; rebuilding the forward and reverse maps and determining a logical address from a physical address.
The storage controller 104, in the depicted embodiment, includes a storage space recovery module 806 that uses the reverse map to identify valid data in an erase region prior to an operation to recover the erase region (also referred to as a garbage collection operation). The identified valid data is moved to another erase region prior to the recovery operation, unless a client 120 has indicated that the valid data is evictable over the cache interface 112. By organizing the reverse map by erase region, the storage space recovery module 806 can scan through a portion of the reverse map corresponding to an erase region to quickly identify valid data or to determine a quantity of valid data in the erase region. An erase region may include an erase block, a fixed number of pages, etc. erased together. The reverse map may be organized so that once the entries for a particular erase region are scanned, the contents of the erase region are known.
By organizing the reverse map by erase region, searching the contents of an erase region is more efficient than searching a B-tree, binary tree, or other similar structure used for logical-to-physical address searches. Searching forward map in the form of a B-tree, binary tree, etc. is cumbersome because the B-tree, binary tree, etc. would frequently have to be searched in its entirety to identify all of the valid data of the erase region. The reverse may include a table, data base, or other structure that allows entries for data of an erase region to be stored together to facilitate operations on data of an erase region.
In one embodiment, the forward map and the reverse map are independent of a file structure, a name space, a directory, etc. that organize data for the requesting device transmitting the storage request, such as a file server or client operating in a server or the host device 114. By maintaining the forward map and the reverse map separate from any file server of the requesting device, the storage controller 104 is able to emulate, for each VSU 122, a random access, logical block storage device storing data as requested by the storage request.
Use of the forward map and reverse map allows the storage controller 104 to appear to be storing data in specific VSUs 122 and at specific locations as directed by a storage request while actually storing data sequentially in the solid-state storage media 110, intermingling the data of different VSUs 122. Beneficially, the storage controller 104 overcomes problems that random access causes for solid-state storage, such as flash memory, by emulating logical block storage while actually storing data sequentially. The storage controller 104 also allows flexibility because one storage request may be a logical block storage request while a second storage request may be an object storage request, file storage request, etc. Maintaining independence from file structures, namespaces, etc. of the requesting device provides great flexibility as to which type of storage requests may be serviced by the storage controller 104.
In one embodiment, the storage space recovery module 806 performs a garbage collection operation to recover storage capacity of physical storage media 110 corresponding to data that is marked as invalid, such as data cleaned by the destage module 704 and/or evicted by the eviction module 706. The storage space recovery module 806, in certain embodiments, cooperates with the cache command module 604 and/or the cache management module 606, so that the cache command module 604 may send garbage collection notifications to clients 120 as described above and so that the storage space recovery module 806 may select data to retain and copy forward based on cache management information from the clients 120.
The storage space recovery module 806, in one embodiment, recovers storage capacity of physical storage media corresponding to data that the destage module 704 has cleaned and that the eviction module 706 has evicted, or that has been otherwise marked as invalid. In one embodiment, the storage space recovery module 806 allows clean data to remain in the solid-state storage device 102 as long as possible until the eviction module 706 evicts the data or the data is otherwise marked as invalid, to decrease the number of cache misses.
In one embodiment, the storage space recovery module 806 recovers storage capacity of physical storage media corresponding to invalid data opportunistically. For example, the storage space recovery module 806 may recover storage capacity in response to a lack of available storage capacity, a percentage of data marked as invalid reaching a predefined threshold level, a consolidation of valid data, an error detection rate for a section of physical storage media reaching a threshold value, performance crossing a threshold value, a scheduled garbage collection cycle, identifying a section of the physical storage media 110 with a high amount of invalid data, identifying a section of the physical storage media 110 with a low amount of wear, or the like.
In one embodiment, the storage space recovery module 806 relocates valid data that is in a section of the physical storage media 110 in the solid-state storage device 102 that the storage space recovery module 806 is recovering to preserve the valid data. In one embodiment, the storage space recovery module 806 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, or other physical storage media, 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 storage space recovery module 806, upon recovering a section of the physical storage media 110, allows the solid-state storage device 102 to re-use the section of the physical storage media 110 to store different data. In one embodiment, the storage space recovery module 806 adds the recovered section of physical storage media to an available storage pool for the solid-state storage device 102, or the like. The storage space recovery module 806, in one embodiment, erases existing data in a recovered section. In a further embodiment, the storage space recovery module 806 allows the solid-state storage device 102 to overwrite existing data in a recovered section. Whether or not the storage space recovery module 806, in one embodiment, erases existing data in a recovered section may depend on the nature of the physical storage media. For example, Flash media requires that cells be erased prior to reuse where magnetic media such as hard drives does not have that requirement. In an embodiment where the storage space recovery module 806 does not erase data in a recovered section, but allows the solid-state storage device 102 to overwrite data in the recovered section, the storage space recovery module 806, in certain embodiments, may mark the data in the recovered section as unavailable to service read requests so that subsequent requests for data in the recovered section return a null result or an empty set of data until the solid-state storage device 102 overwrites the data.
In one embodiment, the storage space recovery module 806 recovers storage capacity of the solid-state storage device 102 one or more storage divisions at a time. A storage division, in one embodiment, is an erase block or other predefined division. For flash memory, an erase operation on an erase block writes ones to every bit in the erase block. This is a lengthy process compared to a program operation which starts with a location being all ones, and as data is written, some bits are changed to zero. However, where the solid-state storage 110 is not flash memory or has flash memory where an erase cycle takes a similar amount of time as other operations, such as a read or a program, the eviction module 706 may erase the data of a storage division as it evicts data, instead of the storage space recovery module 806.
In one embodiment, allowing the eviction module 706 to mark data as invalid rather than actually erasing the data and allowing the storage space recovery module 806 to recover the physical media associated with invalid data, increases efficiency because, as mentioned above, for flash memory and other similar storage an erase operation takes a significant amount of time. Allowing the storage space recovery module 806 to operate autonomously and opportunistically within the solid-state storage device 102 provides a way to separate erase operations from reads, writes, and other faster operations so that the solid-state storage device 102 operates very efficiently.
In one embodiment, the storage space recovery module 806 is integrated with and/or works in conjunction with the cache management module 606, the destage module 704, and/or the eviction module 706. For example, the storage space recovery module 806, in one embodiment, clears data from the solid-state storage device 102 in response to an indicator that the storage device stores the data (i.e. that the destage module 704 has cleaned the data) based on a cache eviction policy (i.e. in response to the eviction module 706 evicting the data based on cache management information from the cache management module 606). The eviction module 706, in one embodiment, evicts data by marking the data as invalid, as described above. In other embodiments, the eviction module 706 may evict data by erasing the data, overwriting the data, trimming the data, deallocating physical storage media associated with the data, or otherwise clearing the data from the solid-state storage device 102.
The direct mapping module 808, in one embodiment, directly maps logical or physical addresses of the backing store 118 to logical addresses of one or more cache unit VSUs 122 of the solid-state storage device 102 and directly maps logical addresses of the one or more cache unit VSUs 122 of the solid-state storage device 102 to logical addresses of the backing store 118. As used herein, direct mapping of addresses means that for a given address in a first address space there is exactly one corresponding address in a second address space with little or no translation or manipulation of the address to get from an address in the first address space to the corresponding address in the second address space. The direct mapping module 808, in a further embodiment, maps addresses of the backing store 118 to logical addresses of one or more cache unit VSUs 122 of the solid-state storage device 102 such that each backing store 118 address has a one to one relationship with a logical address of the one or more cache unit VSUs 122 of the solid-state storage device 102. The direct mapping module 808 may be part of, be integrated with, work in cooperation with, and/or perform similar functions to the forward mapping module 802, as described above.
As described above, in certain embodiments, logical addresses of the VSUs 122 are independent of physical storage addresses of the solid-state storage media 110 for the solid-state storage device 102, making the physical storage addresses of the solid-state storage media 110 fully associative with any backing stores 118 associated with cache unit VSUs 122 of the solid-state storage device 102. Because the solid-state storage media 110 is fully associative with any associated backing stores 118, any physical storage block of the solid-state storage device 102 may store data associated with any storage device address of a backing store 118.
Cache unit VSUs 122 of the solid-state storage device 102, in one embodiment, are logically directly mapped and physically fully associative, combining the benefits of both cache types. The direct mapping module 808 maps each storage block of a backing store 118 to a distinct unique logical address of a cache unit VSU 122 of the solid-state storage device 102 and associated distinct unique entry in the mapping structure, which may be associated with any distinct storage address of the solid-state storage media 110. This means that the direct mapping module 808 maps a storage block of a backing store 118 (represented by an LBA or other address) consistently to the same distinct unique logical address of a cache unit VSU 122 of the solid-state storage device 102 while any distinct storage address of the solid-state storage media 110 may store the associated data, depending on a location of an append point of a sequential log-based writing structure, or the like.
The combination of logical direct mapping and full physical associativity that the direct mapping module 808 provides, in one embodiment, precludes cache collisions from occurring because logical addresses of a cache unit VSU 122 are not shared and any storage block of the solid-state storage media 110 may store data for any address of a backing store 118 and/or for any VSU 122, providing caching flexibility and optimal cache performance. Instead of overwriting data due to cache collisions, in one embodiment, the storage space recovery module 806 and/or the eviction module 706 may clear invalid or old data from the solid-state storage device 102 to free storage capacity for caching data. Further, because the direct mapping module 808 maps storage device addresses of the backing store 118 to logical addresses of a cache unit VSU 122 directly, in certain embodiments, the solid-state storage device 102 provides fully associative physical storage media 110 without the processing overhead and memory consumption of a separate cache map, cache index, cache tags, or other lookup means traditionally associated with fully associative caches, eliminating a cache translation layer, even for multiple cache unit VSUs 122. Instead of a separate cache translation layer, the direct mapping module 808 (which may be embodied by the logical-to-physical translation layer 510 described above and/or the forward mapping module 802) and the associated single mapping structure serve as both a cache index or lookup structure and as a storage address mapping layer.
In one embodiment, the direct mapping module 808 maps addresses of a backing store 118 directly to logical addresses of a cache unit VSU 122 so that the addresses of the backing store 118 and the logical addresses of the cache unit VSU 122 are equal or equivalent. In one example of this embodiment, the addresses of the backing store 118 and the logical addresses of the cache unit VSU 122 share a lower range of the logical address space of the cache unit VSU 122, such as 0-232, or the like. In embodiments where the direct mapping module 808 maps addresses of a backing store 118 as equivalents of logical addresses of a cache unit VSU 122, the direct mapping module 808 may use the addresses of the backing store 118 and the logical addresses of the cache unit VSU 122 interchangeably, substituting one for the other without translating between them. Because the direct mapping module 808 directly maps addresses of a backing store 118 to logical addresses of a cache unit VSU 122, an address of an I/O request directly identifies both an entry in the mapping structure for a logical address of the cache unit VSU 122 and an associated address of the backing store 118. In one embodiment, logical block addresses of a backing store 118 are used to index both the logical address space of the cache unit VSU 122 and the logical address space of the backing store 118. This is enabled by the direct mapping module 808 presenting an address space to the host device 114 that is the same size or larger than the address space of the associated backing store 118.
In one embodiment, the direct mapping module 808 maps logical addresses of a VSU 122 (and associated addresses of the backing store 118 in case of a cache unit VSU 122) to physical addresses and/or locations on the physical storage media 110 of the solid-state storage device 102. In a further embodiment, the direct mapping module 808 uses a single mapping structure to map addresses of a backing store 118 to logical addresses of a cache unit VSU 122 and to map logical addresses of the cache unit VSU 122 to locations on the physical storage media 110 of the solid-state storage device 102. The direct mapping module 808 references the single mapping structure to determine whether or not a cache unit VSU 122 of the solid-state storage device 102 stores data associated with an address of an I/O request. An address of an I/O request may comprise an address of the backing store 118, a logical address of a cache unit VSU 122, or the like.
The single mapping structure, in various embodiments, may include a B-tree, B*-tree, B+-tree, a CAM, a binary tree, a hash table, an index, an array, a linked-list, a look-up table, or another mapping data structure. Use of a B-tree as the mapping structure in certain embodiments, is particularly advantageous where the logical address space presented to the client 120 is a very large address space (2^64 addressable blocks—which may or may not be sparsely populated). Because B-trees maintain an ordered structure, searching such a large space remains very fast. Example embodiments of a B-tree as a mapping structure are described in greater detail with regard to FIGS. 10 and 11. For example, in one embodiment, the mapping structure includes a B-tree with multiple nodes and each node may store several entries. In the example embodiment, each entry may map a variable sized range or ranges of logical addresses of the solid-state storage device 102 and/or of associated VSUs 122 to a location on the physical storage media 110 of the solid-state storage device 102. Furthermore, the number of nodes in the B-tree may vary as the B-tree grows wider and/or deeper. Caching variable sized ranges of data associated with contiguous and/or non-contiguous ranges of storage device addresses, in certain embodiments, is more efficient than caching fixed size cache lines, as cache unit VSUs 122 of the solid-state storage device 102 may more closely match data use patterns without restrictions imposed by fixed size cache lines.
In one embodiment, a logical address space of the solid-state storage device 102 is divided between logical address spaces of the associated VSUs 122. For example, a sparse logical address space of 2^64 blocks for the solid-state storage device 102 may be divided into 2^32 distinct logical address spaces of 2^32 blocks, accommodating 2^32 uniquely addressed VSUs 122. Each 2^32 block logical address space of a VSU 122, as described above, may be presented to a client 120 selectively as either a sparse address space or as a contiguous block address space. In one embodiment, the clients 120 may address a VSU 122 using the assigned division of the logical address space of the solid-state storage device 102. In another embodiment, the clients 120 may address a VSU 122 using address ranging from 0-N, and the cache management module 606 and/or the direct mapping module 808 map the addresses 0-N to an address space offset for the VSU 122 within the logical address space of the solid-state storage device 102. In this manner, the direct mapping module 808 may use a single mapping structure for the solid-state storage device 102 and the associated VSUs 122.
In another embodiment, the direct mapping module 808 and/or the cache management module 606 may maintain a separate mapping structure for each VSU 122. As described above, in certain embodiments, one or more VSUs 122 may present a sparse logical address space to the one or more clients 120 while one or more other VSUs 122 may present a contiguous block address space to the one or more clients 120. Different mapping structures may be more efficient for different logical address space types. For example, for VSUs 122 presenting a sparse logical address space, the direct mapping module 808 may use a B-tree or other tree based mapping structure and for VSUs 122 presenting a sparse logical address space, the direct mapping module 808 may use a table or array based mapping structure, or the like. In another embodiment, the type of logical address space that a VSU 122 presents is maintained separately from the direct mapping module 808, and the direct mapping module 808 may use a sparsely populated mapping structure for a contiguous block address space or vice versa, with the cache management module 606 and/or the virtual storage unit module 812 presenting the selected logical address space type to clients 120.
As described above, the direct mapping module 808 may maintain and use a single mapping structure to map logical block addresses for a plurality of VSUs 122 to physical storage addresses on the solid-state storage media 110 of the solid-state storage device 102. In a further embodiment, as described above, the direct mapping module 808 may maintain and use a plurality of separate mapping structures to map logical block addresses for a plurality of VSUs 122 to physical storage addresses on the solid-state storage media 110. For example, the direct mapping module 808 may maintain a separate mapping structure for each VSU 122, a separate mapping structure for one or more different types of VSUs 122, a separate mapping structure for each VSU 122 with a contiguous logical address space, or the like. In other embodiments, the direct mapping module 808 may use a single mapping structure to map logical block addresses of VSUs 122 to physical block addresses of a plurality of different solid-state storage devices 102, so that multiple storage devices 102 share a single mapping structure. One of skill in the art, in light of this disclosure, will recognize other arrangements of one or more mapping structures which the direct mapping module 808 may use to map logical block addresses and physical storage locations.
In one embodiment, a mapping structure of the direct mapping module 808 only includes a node or entry for logical addresses that are associated with currently stored data in a VSU 122 of the solid-state storage device 102. In this embodiment, membership in the mapping structure represents membership in a VSU 122 of the solid-state storage device 102. The direct mapping module 808, in one embodiment, adds entries, nodes, and the like to the mapping structure as data is stored in VSUs 122 of and removes entries, nodes, and the like from the mapping structure in response to data being evicted, cleared, trimmed, or otherwise removed from VSUs 122 of the solid-state storage device 102. Similarly, membership in the mapping structure may represent valid allocated blocks on the solid-state storage media 110. The solid-state storage controller 104, in one embodiment, adds entries, nodes, and the like to the mapping structure as data is stored on the solid-state storage media 110 and removes entries, nodes, and the like from the mapping structure in response to data being invalidated cleared, trimmed, or otherwise removed from the solid-state storage media 110. In the case where the mapping structure is shared for both cache management and data storage management on the solid-state storage media, the present invention also tracks whether the data is dirty or not to determine whether the data is persisted on a backing store 118.
Nodes, entries, records, or the like of the mapping structure, in one embodiment, may include information (such as physical addresses, offsets, indicators, etc.) directly, as part of the mapping structure, or may include pointers, references, or the like for locating information in memory, in a table, or in another data structure. The direct mapping module 808, in one embodiment, optimizes the mapping structure by monitoring the shape of the mapping structure, monitoring the size of the mapping structure, balancing the mapping structure, enforcing one or more predefined rules with regard to the mapping structure, ensuring that leaf nodes of the mapping structure are at the same depth, combining nodes, splitting nodes, and/or otherwise optimizing the mapping structure.
The direct mapping module 808, in one embodiment, stores at least a copy of the one or more mapping structures to the solid-state storage media 110 of the solid-state storage device 102 periodically. By storing a mapping structure on the solid-state storage device 102, in a further embodiment, the mapping of addresses of a backing store 118 to the logical addresses of a cache unit VSU 122 and/or the mapping of the logical addresses of the solid-state storage device 102 to locations on the physical storage media 110 of the solid-state storage device 102 are persistent, even if the solid-state storage device 102 is subsequently paired with a different host device 114, the solid-state storage device 102 undergoes an unexpected or improper shutdown, the solid-state storage device 102 undergoes a power loss, or the like. In one embodiment, the backing store 118 is also subsequently paired with the different host device 114 along with the solid-state storage device 102. In a further embodiment, the solid-state storage device 102 rebuilds or restores at least a portion of data from the backing store 118 on a new storage device associated with the different host device 114, based on the one or more mapping structures and data stored on the solid-state storage device 102.
The direct mapping module 808, in one embodiment, reconstructs the one or more mapping structures and included entries by scanning data on the solid-state storage media 110, such as a sequential log-based writing structure or the like, and extracting logical addresses, sequence indicators, and the like from data at physical locations on the solid-state storage media 110. For example, as described above, in certain embodiments the cache fulfillment module 702 stores data of I/O requests in a format that associates the data with sequence indicators for the data and with respective logical addresses of the solid-state storage device 102 for the data. If the mapping structure becomes lost or corrupted, the direct mapping module 808 may use the physical address or location of data on the solid-state storage media 110 with the associated sequence indicators, logical addresses, and/or other metadata stored with the data, to reconstruct entries of the mapping structure. The forward map module 802 described above is another embodiment of the direct mapping module 808.
In one embodiment, the direct mapping module 808 receives one or more addresses of an I/O request, such as logical block addresses of the backing store 118 or the like, from the cache fulfillment module 702 and the direct mapping module 808 references the mapping structure to determine whether or not a cache unit VSU 122 or other VSU 122 of the solid-state storage device 102 stores data associated with the I/O request. The direct mapping module 808, in response to referencing the mapping structure, may provide information from the mapping structure to the cache fulfillment module 702, such as a determination whether a VSU 122 of the solid-state storage device 102 stores data of the I/O request, a physical storage address on the solid-state storage media 110 for data of the I/O request, or the like to assist the cache fulfillment module 702 in satisfying the I/O request. In response to the cache fulfillment module 702 satisfying an I/O request, in certain embodiments, the direct mapping module 808 updates the mapping structure to reflect changes or updates to the solid-state storage device 102 that the cache fulfillment module 702 made to satisfy the I/O request.
In one embodiment, the backing store interface module 810 provides an interface between the solid-state storage controller 104 and the backing store 118. As described above with regard to FIG. 5, in various embodiments, the direct cache module 116 may interact with the solid-state storage device 102 and/or the backing store 118 through a block device interface, a direct interface, a device driver on the host device 114, a storage controller 104, 120, or the like. In one embodiment, the backing store interface module 810 provides the solid-state storage controller 104 (and thereby the direct cache module 116) with access to one or more of these interfaces. For example, the backing store interface module 810 may receive read commands, write commands, and clear (or TRIM) commands from one or more of the cache fulfillment module 702, the direct mapping module 808, the read request module 720, the destage module 704, the storage space recovery module 806, and the like and relay the commands to the solid-state storage device 102 and/or the backing store 118 (through the backing store controller 120 or directly). In a further embodiment, the backing store interface module 810 may translate or format a command into a format compatible with an interface for the backing store 118.
In one embodiment, the backing store interface module 810 has exclusive ownership over the backing store 118 and the solid-state storage controller 104 is an exclusive gateway to accessing the backing store 118. Providing the backing store interface module 810 with exclusive ownership over the backing store 118 and preventing access to the backing store 118 by other routes obviates stale data issues and cache coherency requirements, because all changes to data in the storage device 114 are processed by the solid-state storage controller 104.
In a further embodiment, the backing store interface module 810 does not have exclusive ownership of the backing store 118, and the backing store interface module 810 manages cache coherency for one or more cache unit VSUs 122 associated with the backing store 118. For example, in various embodiments, the backing store interface module 810 may access a common directory with other users of the backing store 118 to maintain coherency, may monitor write operations from other users of the backing store 118, may participate in a predefined coherency protocol with other users of the backing store 118, or the like. In embodiments including multiple cache unit VSUs 122 associated with multiple backing stores 118, the backing store interface module 810 may provide the above described functions for each of the multiple backing stores 118.
In one embodiment, the virtual storage unit module 812 creates and manages a plurality of VSUs 122 in response to virtual storage unit commands from clients 120, either directly or through the direct cache module 116. As described above, in certain embodiments, a plurality of VSUs 122 (which may include a plurality of cache unit VSUs 122), may operate simultaneously on the solid-state storage device 102. The virtual storage unit module 812 may manage VSUs 122 based on management information exchanged with the one or more clients 120 over the storage controller interface 124, or the like.
In one embodiment, the virtual storage unit module 812 supports a create command for creating a new VSU 122. A client 120, in certain embodiments, may specify one or more VSU parameters with the create command, such as one or more size parameters, a name parameter, a logical address space parameter, and/or other parameters. The size of a VSU 122, in one embodiment, may specify a size of a logical address space associated with the VSU 122. In another embodiment, the size of a VSU 122 may specify a usable capacity of the VSU 122 that is presented to a client 120. In a further embodiment, the size of a VSU 122 may specify a physical storage capacity available to the VSU 122, including valid user data from a client 120, invalid data, metadata, and the like. In certain embodiments, a client 120 may specify one or more of a logical address space size, a usable capacity size, and a physical storage capacity size with a create command, or with a resize command as described below. In embodiments where the virtual storage unit module 812 does not support or does not receive a logical address space size, a usable capacity size, and a physical storage capacity size, the virtual storage unit module 812 may use default sizes for the unsupported or un-received sizes.
The virtual storage unit module 812, in one embodiment, supports a delete command. In response to a delete command, the virtual storage unit module 812 removes the VSU 122 from the solid-state storage device 102 such that the removed VSU 122 is logically and physically unavailable to a client 120. In a further embodiment, the virtual storage unit module 812 supports a TRIM command, and the virtual storage unit module 812 clears the contents of a VSU 122 in response to receiving a TRIM command while maintaining the VSU 122 itself and continuing to provide clients 120 with access to the VSU 122 after the TRIM command.
In one embodiment, the virtual storage unit module 812 supports an enumerate command. In response to receiving an enumerate command from a client 120, the virtual storage unit module 812 lists or enumerates the VSUs 122 to the requesting client 120, using VSU identifiers, such as ID numbers, names, or the like. In certain embodiments, the virtual storage unit module 812 implements an access control policy, and enumerates only the VSUs 122 to which the requesting client 120 has been granted access.
The virtual storage unit module 812, in one embodiment, supports a resize command. As described above with regard to the create command, the virtual storage unit module 812 may support one or more of a logical address space size, a usable capacity size, and a physical storage capacity size. In response to receiving a resize command from a client 120, the virtual storage unit module 812 resizes the VSU 122 identified in the resize command according to one or more size parameters included in the resize command.
In one embodiment, the virtual storage unit module 812 presents distinct sparse logical address spaces for each VSU 122 to the one or more cache clients 120. As described above with regard to the direct mapping module 808, in certain embodiments, the distinct sparse logical address spaces may be part of or otherwise mapped to a single sparse logical address space of the solid-state storage device 102, VSUs 122 may selectively present either a sparse logical address space or a contiguous block address space, or the like.
FIG. 9 is a schematic block diagram illustrating another embodiment of a storage controller 104 for efficient mapping of logical and physical addresses. The storage controller 104, in the depicted embodiment, includes a forward mapping module 802, a reverse mapping module 804, a storage space recovery module 806, a direct mapping module 808, a backing store interface module 810, and a virtual storage unit module 812 which are substantially similar to those described above in relation to the storage controller 104 of FIG. 8. The storage controller 104 as depicted also includes a map rebuild module 902, a checkpoint module 904, a map sync module 906, an invalidate module 908, and a map update module 910, which are described below.
The storage controller 104, in the depicted embodiment, includes a map rebuild module 902 that rebuilds the forward map and the reverse map using the source parameters stored with the data. Where data is stored on the solid-state storage media 110 sequentially, by keeping track of the order in which erase regions or erase blocks in the solid-state storage media 110 were filled and by storing source parameters with the data, the solid-state storage media 110 becomes a sequential log. The map rebuild module 902 replays the log by sequentially reading data packets stored on the solid-state storage media 110. Each physical address and data packet length is paired with the source parameters found in each data packet to recreate the forward and reverse maps.
In another embodiment, the storage controller 104 includes a checkpoint module 904 that stores information related to the forward map and the reverse map where the checkpoint is related to a point in time or state of the data storage device. The stored information is sufficient to restore the forward map and the reverse map to a status related to the checkpoint. For example, the stored information may include storing the forward and reverse maps in non-volatile storage, such as on the data storage device, along with some identifier indicating a state or time checkpoint.
For example, a timestamp could be stored with the checkpoint information. The timestamp could then be correlated with a location in the solid-state storage media 110 where data packets were currently being stored at the checkpoint. In another example, state information is stored with the checkpoint information, such as a location in the solid-state storage media 110 where data is currently being stored. One of skill in the art will recognize other checkpoint information that may be stored by the checkpoint module 904 to restore the forward and reverse maps to the checkpoint.
In another embodiment, the storage controller 104 includes a map sync module 906 that updates the forward map and the reverse map from the status related to the checkpoint to a current status by sequentially applying source parameters and physical addresses. The source parameters applied are stored with data that was sequentially stored after the checkpoint. The physical addresses are derived from a location of the data on the solid-state storage media 110.
Beneficially the map sync module 906 restores the forward and reverse maps to a current state from a checkpoint rather than starting from scratch and replaying the entire contents of the solid-state storage media 110. The map sync module 906 uses the checkpoint to go to the data packet stored just after the checkpoint and then replays data packets from that point to a current state where data packets are currently being stored on the solid-state storage media 110. The map sync module 906 typically takes less time to restore the forward and reverse maps than the map rebuild module 902.
In one embodiment, the forward and reverse maps are stored on the solid-state storage media 110 and another set of forward and reverse maps are created to map the stored forward and reverse maps. For example, data packets may be stored on a first storage channel while the forward and reverse maps for the stored data packets may be stored as data on a second storage channel; the forward and reverse maps for the data on the second storage channel may be stored as data on a third storage channel, and so forth. This recursive process may continue as needed for additional forward and reverse maps. The storage channels may be on a single element of solid-state storage media 110 or on separate elements of solid-state storage media 110.
The storage controller 104, in the depicted embodiment, includes an invalidate module 908 that marks an entry for data in the reverse map indicating that data referenced by the entry is invalid in response to an operation resulting in the data being invalidated. The invalidate module 908 may mark an entry invalid as a result of a delete request, a read-modify-write request, eviction from a cache unit VSU 122, or the like. The reverse map includes some type of invalid marker or tag that may be changed by the invalidate module 908 to indicate data associated with an entry in the reverse map is invalid. For example, the reverse map may include a bit that is set by the invalidate module 908 when data is invalid.
In one embodiment, the reverse map includes information for valid data and invalid data stored in the solid-state storage media 110 and the forward includes information for valid data stored in the solid-state storage media 110. Since the reverse map is useful for storage space recovery operations, information indicating which data in an erase block is invalid is included in the reverse map. By maintaining the information indicating invalid data in the reverse map, the forward map, in one embodiment, need only maintain information related to valid data stored on the solid-state storage media 110, thus improving the efficiency and speed of forward lookup.
The storage space recovery module 806 may then use the invalid marker to determine a quantity of invalid data in an erase region by scanning the reverse map for the erase region to determine a quantity of invalid data in relation to a storage capacity of the erase region. The storage space recovery module 806 can then use the determined quantity of invalid data in the erase region to select an erase region for recovery. By scanning several erase regions, or even all available erase regions, the storage space recovery module 806 can use selection criteria, such as highest amount of invalid data in an erase region, to then select an erase region for recovery.
Once an erase region is selected for recovery, in one embodiment the storage space recovery module 806 may then write valid data from the selected erase region to a new location in the solid-state storage media 110. The new location is typically within a page of an erase region where data is currently being stored sequentially. The storage space recovery module 806 may write the valid data using a data pipeline as described in U.S. patent application Ser. No. 11/952,091 entitled “Apparatus, System, and Method for Managing Data Using a Data Pipeline” for David Flynn et al. and filed Dec. 6, 2007, which is hereinafter incorporated by reference.
In one embodiment, the storage space recovery module 806 also updates the reverse map to indicate that the valid data written to the new location is invalid in the selected erase region and updates the forward and reverse maps based on the valid data written to the new location. In another embodiment, the storage space recovery module 806 coordinates with the map update module 910 (described below) to update the forward and reverse maps.
In a preferred embodiment, the storage space recovery module 806 operates autonomously with respect to data storage and retrieval associated with storage requests and other commands. Storage space recovery operations that may be incorporated in the storage space recovery module 806 are described in more detail in the Storage Space Recovery Application referenced above.
In one embodiment, the storage controller 104 includes a map update module 910 that updates the forward map and/or the reverse map in response to contents of the solid-state storage media 110 being altered. In a further embodiment, the map update module 910 receives information linking a physical address of stored data to a logical address from the data storage device based on a location where the data storage device stored the data. In the embodiment, the location where a data packet is stored may not be available until the solid-state storage media 110 stores the data packet.
For example, where data from a data segment is compressed to form a data packet, the size of each data packet may be unknown until after compression. Where the solid-state storage media 110 stores data sequentially, once a data packet is compressed and stored, an append point is set to a location after the stored data packet and a next data packet is stored. Once the append point is known, the solid-state storage media 110 may then report back the physical address corresponding to the append point where the next data packet is stored. The map update module 910 uses the reported physical address and associated data length of the stored data packet to update the forward and reverse maps. One of skill in the art, in light of this disclosure, will recognize other embodiments of a map update module 910 to update the forward and reverse maps based on physical addresses and associated data lengths of data stored on the solid-state storage media 110.
FIG. 10 is a schematic block diagram of an example of a forward map 1004 and a reverse map 1022 in accordance with the present invention. Typically, the storage controller 104 receives a storage request from a client 120 and/or from the direct cache module 116, such as storage request to read an address. For example, the storage controller 104 may receive a logical block storage request 1002 to start reading read address “182” and read 3 blocks. Typically the forward map 1004 stores logical block addresses as virtual/logical addresses along with other virtual/logical addresses so the forward mapping module 802 uses forward map 1004 to identify a physical address from the virtual/logical address “182” of the storage request 1002. In the example, for simplicity only logical addresses that are numeric are shown, but one of skill in the art will recognize that any logical address may be used and represented in the forward map 1004. A forward map 1004, in other embodiments, may include alpha-numerical characters, hexadecimal characters, and the like.
In the example, the forward map 1004 is a simple B-tree. In other embodiments, the forward map 1004 may be a content addressable memory (“CAM”), a binary tree, a hash table, or other data structure known to those of skill in the art. In the depicted embodiment, a B-Tree includes nodes (e.g. the root node 1008) that may include entries of two logical addresses. Each entry, in one embodiment, may include a range of logical addresses. For example, a logical address may be in the form of a logical identifier with a range (e.g. offset and length) or may represent a range using a first and a last address or location. As described above with regard to the forward mapping module 802 and the direct mapping module 808 of FIG. 8, the forward map 1004 may be a single mapping structure for the solid-state storage device 102 (including multiple VSUs 122), or may be for a single VSU 122.
Where a single logical address is included at a particular node, such as the root node 1008, if a logical address 1006 being searched is lower than the logical address of the node, the search will continue down a directed edge 1010 to the left of the node 1008. If the searched logical address 1006 matches the current node 1008 (i.e. is located within the range identified in the node), the search stops and the pointer, link, physical address, etc. at the current node 1008 is identified. If the searched logical address 1006 is greater than the range of the current node 1008, the search continues down directed edge 1012 to the right of the current node 1008. Where a node includes two logical addresses and a searched logical address 1006 falls between the listed logical addresses of the node, the search continues down a center directed edge (not shown) to nodes with logical addresses that fall between the two logical addresses of the current node 1008. A search continues down the B-tree until either locating a desired logical address or determining that the searched logical address 1006 does not exist in the B-tree. As described above, in one embodiment, membership in the B-tree denotes membership in a cache unit VSU 122, and determining that the searched logical address 1006 is not in the B-tree is a cache miss.
In the example depicted in FIG. 10, the forward mapping module 802 searches for logical address “182” 1006 starting at the root node 1008. Since the searched logical address 1006 is lower than the logical address of 205-212 in the root node 1008, the forward mapping module 802 searches down the directed edge 1010 to the left to the next node 1014. The searched logical address “182” 1006 is more than the logical address (072-083) stored in the next node 1014 so the forward mapping module 802 searches down a directed edge 1016 to the right of the node 1014 to the next node 1018. In this example, the next node 1018 includes a logical address of 178-192 so that the searched logical address “182” 1006 matches the logical address 178-192 of this node 1018 because the searched logical address “182” 1006 falls within the range 178-192 of the node 1018.
Once the forward mapping module 802 determines a match in the forward map 1004, the forward mapping module 802 returns a physical address, either found within the node 1018 or linked to the node 1018. In the depicted example, the node 1018 identified by the forward mapping module 802 as containing the searched logical address 1006 includes a link “f” that maps to an entry 1020 in the reverse map 1022.
In the depicted embodiment, for each entry 1020 in the reverse map 1022 (depicted as a row in a table), the reverse map 1022 includes an entry ID 1024, a physical address 1026, a data length 1028 associated with the data stored at the physical address 1026 on the solid-state storage media 110 (in this case the data is compressed), a valid tag 1030, a logical address 1032 (optional), a data length 1034 (optional) associated with the logical address 1032, and other miscellaneous data 1036. The reverse map 1022 is organized into erase blocks (erase regions). In this example, the entry 1020 that corresponds to the selected node 1018 is located in erase block n 1038. Erase block n 1038 is preceded by erase block n−1 1040 and followed by erase block n+1 1042 (the contents of erase blocks n−1 and n+1 are not shown). An erase block may be some erase region that includes a predetermined number of pages. An erase region is an area in the solid-state storage media 110 erased together in a storage recovery operation.
While the entry ID 1024 is shown as being part of the reverse map 1022, the entry ID 1024 may be an address, a virtual link, or other means to tie an entry in the reverse map 1022 to a node in the forward map 1004. The physical address 1026 is an address in the solid-state storage media 110 where data that corresponds to the searched logical address 1006 resides. The data length 1028 associated with the physical address 1026 identifies a length of the data packet stored at the physical address 1026. (Together the physical address 1026 and data length 1028 may be called destination parameters 1044 and the logical address 1032 and associated data length 1034 may be called source parameters 1046 for convenience.) In the example, the data length 1028 of the destination parameters 1044 is different from the data length 1034 of the source parameters 1046 in one embodiment compression the data packet stored on the solid-state storage media 110 was compressed prior to storage. For the data associated with the entry 1020, the data was highly compressible and was compressed from 64 blocks to 1 block.
The valid tag 1030 indicates if the data mapped to the entry 1020 is valid or not. In this case, the data associated with the entry 1020 is valid and is depicted in FIG. 10 as a “Y” in the row of the entry 1020. Typically the reverse map 1022 tracks both valid and invalid data and the forward map 1004 tracks valid data. In the example, entry “c” 1048 indicates that data associated with the entry 1048 is invalid. Note that the forward map 1004 does not include logical addresses associated with entry “c” 1048. The reverse map 1022 typically maintains entries for invalid data so that valid and invalid data can be quickly distinguished during a storage recovery operation.
The depicted reverse map 1022 includes source parameters 1046 for convenience, but the reverse map 1022 may or may not include the source parameters 1046. For example, if the source parameters 1046 are stored with the data, possibly in a header of the stored data, the reverse map 1022 could identify a logical address indirectly by including a physical address 1026 associated with the data and the source parameters 1046 could be identified from the stored data. One of skill in the art will recognize when storing source parameters 1046 in a reverse map 1022 would be beneficial.
The reverse map 1022 may also include other miscellaneous data 1036, such as a file name, object name, source data, etc. One of skill in the art will recognize other information useful in a reverse map 1022. While physical addresses 1026 are depicted in the reverse map 1022, in other embodiments, physical addresses 1026, or other destination parameters 1044, may be included in other locations, such as in the forward map 1004, an intermediate table or data structure, etc.
Typically, the reverse map 1022 is arranged by erase block or erase region so that traversing a section of the map associated with an erase block (e.g. erase block n 1038) allows the storage space recovery module 806 to identify valid data in the erase block 1038 and to quantify an amount of valid data, or conversely invalid data, in the erase block 1038. Arranging an index into a forward map 1004 that can be quickly searched to identify a physical address 1026 from a logical address 1006 and a reverse map 1022 that can be quickly searched to identify valid data and quantity of valid data in an erase block 1038 is beneficial because the index may be optimized for searches and storage recovery operations. One of skill in the art will recognize other benefits of an index with a forward map 1004 and a reverse map 1022.
FIG. 11 depicts one embodiment of a mapping structure 1100, a logical address space 1120 of the solid-state storage device 102, a combined logical address space 1119 that is accessible to a storage client 120, a sequential, log-based, append-only writing structure 1140, and a storage device address space 1170 of a backing store 118. The mapping structure 1100, in one embodiment, is maintained by the direct mapping module 808. The mapping structure 1100, in the depicted embodiment, is a B-tree that is substantially similar to the forward map 1004 described above with regard to FIG. 10, with several additional entries. Further, instead of links that map to entries in a reverse map 1022, the nodes of the mapping structure 1100 include direct references to physical locations in the solid-state storage device 102. The mapping structure 1100, in various embodiments, may be used either with or without a reverse map 1022. As described above with regard to the forward map 1004 of FIG. 10, in other embodiments, the references in the mapping structure 1100 may include alpha-numerical characters, hexadecimal characters, pointers, links, and the like.
The mapping structure 1100, in the depicted embodiment, includes a plurality of nodes. Each node, in the depicted embodiment, is capable of storing two entries. In other embodiments, each node may be capable of storing a greater number of entries, the number of entries at each level may change as the mapping structure 1100 grows or shrinks through use, or the like.
Each entry, in the depicted embodiment, maps a variable length range of logical addresses of the solid-state storage device 102 to a physical location in the storage media 110 for the solid-state storage device 102. In the depicted embodiment, the single mapping structure 1100 includes entries for multiple VSUs 122. A first VSU 122 (configured as a cache unit VSU 122) has a sparse logical address space ranging from logical address “0” 1122 to logical address “N” 1124, with one or more additional VSUs 122 using addresses from logical address “N+1” to logical address “264−1” 1126. Further, while variable length ranges of logical addresses, in the depicted embodiment, are represented by a starting address and an ending address, in other embodiments, a variable length range of addresses may be represented by a starting address and a length, or the like. In one embodiment, the capital letters ‘A’ through ‘M’ represent a logical or physical erase block in the physical storage media 110 of the solid-state storage device 102 that stores the data of the corresponding range of logical addresses. In other embodiments, the capital letters may represent other physical addresses or locations of the solid-state storage device 102. In the depicted embodiment, the capital letters ‘A’ through ‘m’ are also depicted in the writing structure 1140 which represents the physical storage media 110 of the solid-state storage device 102.
In the depicted embodiment, membership in the mapping structure 1100 denotes membership (or storage) in the solid-state storage device 102 (in one of the plurality of VSUs 122). In another embodiment, an entry may further include an indicator of whether the solid-state storage device 102 stores data corresponding to a logical block within the range of logical addresses, data of the reverse map 1022 described above, and/or other data. For example, in one embodiment, the mapping structure 1100 may also map logical addresses of the backing store 118 to physical addresses or locations within the backing store 118, and an entry may include an indicator that the solid-state storage device 102 does not store the data and a physical address or location for the data on the backing store 118. The mapping structure 1100, in the depicted embodiment, is accessed and traversed in a similar manner as that described above with regard to the forward map 1004.
In the depicted embodiment, the root node 1008 includes entries 1102, 1104 with noncontiguous ranges of logical addresses. A “hole” exists at logical address “208” between the two entries 1102, 1104 of the root node. In one embodiment, a “hole” indicates that the solid-state storage device 102 does not store data corresponding to one or more logical addresses corresponding to the “hole.” In one embodiment, a “hole” may exist because the eviction module 706 evicted data corresponding to the “hole” from the solid-state storage device 102. If the eviction module 706 evicted data corresponding to a “hole,” in one embodiment, the backing store 118 still stores data corresponding to the “hole.” In another embodiment, the solid-state storage device 102 and/or the backing store 118 supports block I/O requests (read, write, trim, etc.) with multiple contiguous and/or noncontiguous ranges of addresses (i.e. ranges that include one or more “holes” in them). A “hole,” in one embodiment, may be the result of a single block I/O request with two or more noncontiguous ranges of addresses. In a further embodiment, a “hole” may be the result of several different block I/O requests with address ranges bordering the “hole.”
In FIG. 10, the root node 1008 includes a single entry with a logical address range of “205-212,” without the hole at “208.” If the entry of the root node 1008 were a fixed size cache line of a traditional cache, the entire range of logical addresses “205-212” would be evicted together. Instead, in the embodiment depicted in FIG. 11, the eviction module 706 evicts data of a single logical address “208” and splits the range of logical addresses into two separate entries 1102, 1104. In one embodiment, the direct mapping module 808 may rebalance the mapping structure 1100, adjust the location of a directed edge, root node, or child node, or the like in response to splitting a range of logical addresses. Similarly, in one embodiment, each range of logical addresses may have a dynamic and/or variable length, allowing the solid-state storage device 102 to store dynamically selected and/or variable lengths of logical block ranges.
In the depicted embodiment, similar “holes” or noncontiguous ranges of logical addresses exist between the entries 1106, 1108 of the node 1014, between the entries 1110, 1112 of the left child node of the node 1014, between entries 1114, 1116 of the node 1018, and between entries of the node 1118. In one embodiment, similar “holes” may also exist between entries in parent nodes and child nodes. For example, in the depicted embodiment, a “hole” of logical addresses “060-071” exists between the left entry 1106 of the node 1014 and the right entry 1112 of the left child node of the node 1014.
The “hole” at logical address “003,” in the depicted embodiment, can also be seen in the logical address space 1120 of the solid-state storage device 102 at logical address “003” 1130. The hash marks at logical address “003” 1140 represent an empty location, or a location for which the solid-state storage device 102 does not store data. In the depicted embodiment, storage device address “003” 1180 of the storage device address space 1170 does store data (identified as ‘b’), indicating that the eviction module 706 evicted data from logical address “003” 1130 of the solid-state storage device 102. The “hole” at logical address 1134 in the logical address space 1120, however, has no corresponding data in storage device address 1184, indicating that the “hole” is due to one or more block I/O requests with noncontiguous ranges, a trim or other deallocation command to both the solid-state storage device 102 and the backing store 118, or the like.
The “hole” at logical address “003” 1130 of the logical address space 1120, however, in one embodiment, is not viewable or detectable to a storage client. In the depicted embodiment, the combined logical address space 1119 represents the data that is available to a storage client, with data that is stored in the solid-state storage device 102 and data that is stored in the backing store 118 but not in the solid-state storage device 102. As described above, the read miss module 722 of FIG. 7 handles misses and returns requested data to a requesting entity. In the depicted embodiment, if a storage client requests data at logical address “003” 1130, the read miss module 722 will retrieve the data from the backing store 118, as depicted at address “003” 1180 of the storage device address space 1170, and return the requested data to the storage client. The requested data at logical address “003” 1130 may then also be placed back in the solid-state storage device 102 and thus logical address 1130 would indicate ‘b’ as present in the solid-state storage device 102.
For a partial miss, the read miss module 722 may return a combination of data from both the solid-state storage device 102 and the backing store 118. For this reason, the combined logical address space 1119 includes data ‘b’ at logical address “003” 1130, and the “hole” in the logical address space 1120 of the solid-state storage device 102 is transparent. In the depicted embodiment, the combined logical address space 1119 is the size of the logical address space 1120 of the solid-state storage device 102 and is larger than the storage device address space 1180. In another embodiment, the direct cache module 116 may size the combined logical address space 1119 as the size of the storage device address space 1180, or as another size.
The logical address space 1120 of the solid-state storage device 102, in the depicted embodiment, is larger than the physical storage capacity and corresponding storage device address space 1170 of the backing store 118, while the logical address space of the first VSU 122 from “0” 1122 to “N” 1124 is equal to the storage device address space 1170 of the backing store. In the depicted embodiment, the solid-state storage device 102 has a 64 bit logical address space 1120 beginning at logical address “0” 1122 and extending to logical address “264−1” 1126. The storage device address space 1170 begins at storage device address “0” 1172 and extends to storage device address “N” 1174. Storage device address “N” 1174, in the depicted embodiment, corresponds to logical address “N” 1124 in the logical address space 1120 of the solid-state storage device 102, which is also the end of the logical address space of the first VSU 122. Because the storage device address space 1170 corresponds to only a subset of the logical address space 1120 of the solid-state storage device 102, the rest of the logical address space 1120 (beyond “N” 1124) is shared with additional VSUs 122, or the like.
For example, in the depicted embodiment, the first range of logical addresses “000-002” 1128 stores data corresponding to the first range of storage device addresses “000-002” 1178. Data corresponding to logical address “003” 1130, as described above, was evicted from the solid-state storage device 102 forming a “hole” and a potential cache miss. The second range of logical addresses “004-059” 1132 corresponds to the second range of storage device addresses “004-059” 1182. However, the final range of logical addresses 1136 extending from logical address “N” 1124 extends beyond storage device address “N” 1174 and beyond the logical address space of the first VSU 122. No storage device address in the storage device address space 1170 corresponds to the final range of logical addresses 1136. The data corresponding to the final range of logical addresses 1136 is data from a second VSU 122, with a logical address space that begins at logical address “N+1.”
The sequential, log-based, append-only writing structure 1140, in the depicted embodiment, is a logical representation of the physical storage media 110 of the solid-state storage device 102. In a further embodiment, the backing store 118 may use a substantially similar sequential, log-based, append-only writing structure 1140. In certain embodiments, the solid-state storage device 102 stores data from multiple VSUs 122 sequentially, appending data to the writing structure 1140 at an append point 1144. The solid-state storage device 102, in a further embodiment, uses a storage space recovery process, such as the storage space recovery module 806 that re-uses non-volatile storage media 110 storing deallocated/unused logical blocks. Non-volatile storage media storing deallocated/unused logical blocks, in the depicted embodiment, is added to an available storage pool 1146 for the solid-state storage device 102. By evicting and clearing certain data from the solid-state storage device 102, as described above, and adding the physical storage capacity corresponding to the evicted and/or cleared data back to the available storage pool 1146, in one embodiment, the writing structure 1140 is cyclic, ring-like, and has a theoretically infinite capacity.
In the depicted embodiment, the append point 1144 progresses around the log-based, append-only writing structure 1140 in a circular pattern 1142. In one embodiment, the circular pattern 1142 wear balances the solid-state storage media 110, increasing a usable life of the solid-state storage media 110. In the depicted embodiment, the eviction module 706 and/or the storage space recovery module 806 have marked several blocks 1148, 1150, 1152, 1154 as invalid, represented by an “X” marking on the blocks 1148, 1150, 1152, 1154. The storage space recovery module 806, in one embodiment, will recover the physical storage capacity of the invalid blocks 1148, 1150, 1152, 1154 and add the recovered capacity to the available storage pool 1146. In the depicted embodiment, modified versions of the blocks 1148, 1150, 1152, 1154 have been appended to the writing structure 1140 as new blocks 1156, 1158, 1160, 1162 in a read, modify, write operation or the like, allowing the original blocks 1148, 1150, 1152, 1154 to be recovered.
FIG. 12 depicts one embodiment of a method 1200 for caching data. The method 1200 begins and the cache fulfillment module 702 detects 1202 an I/O request for a backing store 118 cached by solid-state storage media 110 of a cache unit VSU 122 of the solid-state storage device 102. The direct mapping module 808 references 1204 a mapping structure to determine whether the cache unit VSU 122 comprises data of the detected 1202 I/O request. The single mapping structure maps each logical block address of the backing store 118 directly to a logical block address of the cache unit VSU 122 and also comprises a fully associative relationship between logical block addresses of the backing store 118 and physical storage addresses of the solid-state storage media 110. The cache fulfillment module 702 satisfies 1206 the detected 1202 I/O request using the solid-state storage device 102 in response to the direct mapping module 808 determining 1204 that the cache unit VSU 122 comprises at least one data block of the detected 1202 I/O request. The cache fulfillment module 702 continues to detect 1202 I/O requests and the method 1200 repeats.
FIG. 13 depicts another embodiment of a method 1300 for caching data. The method 1300 begins and the cache fulfillment module 702 determines 1302 whether there are any I/O requests for a backing store 118 cached by solid-state storage media 110 of a cache unit VSU 122 of the solid-state storage device 102. If the cache fulfillment module 702 does not detect 1302 an I/O request, the cache fulfillment module 702 continues to monitor 1302 I/O requests. If the cache fulfillment module 702 detects 1302 an I/O request, the cache fulfillment module 702 determines 1304 a storage device logical block address for the I/O request.
The direct mapping module 808 references 1306 a mapping structure using the determined 1304 storage device logical block address to determine 1308 whether the cache unit VSU 122 comprises/stores data of the I/O request. If the direct mapping module 808 determines 1308 that the cache unit VSU 122 does not comprise data of the I/O request, the cache fulfillment module 702 stores 1310 data of the I/O request to the cache unit VSU 122 of the solid-state storage device 102 in a manner that associates the data with the determined 1304 logical block address and a sequence indicator for the I/O request, to satisfy the I/O request.
If the direct mapping module 808 determines 1308 that the cache unit VSU 122 comprises at least one data block of the I/O request, the cache fulfillment module 702 satisfies 1312 the I/O request, at least partially, using the cache unit VSU 122 of the solid-state storage device 102. For a write I/O request, the cache fulfillment module 702 may satisfy 1312 the I/O request by storing data of the I/O request to the cache unit VSU 122 of the solid-state storage device 102 sequentially on the solid-state storage media 110 to preserve an ordered sequence of storage operations. For a read I/O request, the cache fulfillment module 702 may satisfy 1312 the I/O request by reading data of the I/O request from the cache unit VSU 122 of the solid-state storage device 102 using a physical storage address of the solid-state storage media 110 associated with the determined 1304 logical block address of the I/O request.
The direct mapping module 808 determines 1314 whether to update the mapping structure to maintain an entry in the mapping structure associating the determined 1304 logical block address and physical storage locations or addresses on the solid-state storage media 110. For example, the direct mapping module 808 may determine 1314 to update the mapping structure if storing 1310 data of the I/O request to the cache unit VSU 122 of the solid-state storage device 102 or otherwise satisfying 1312 the I/O request changed the state of data on the solid-state storage device 102, such as for a write I/O request, a cache miss, a TRIM request, an erase request, or the like.
If the direct mapping module 808 determines 1314 to update the mapping structure, the direct mapping module 808 updates 1316 the mapping structure to map the determined 1304 storage device logical block address for the I/O request directly to a logical block address of the cache unit VSU 122 of the solid-state storage device 102 and to a physical storage address or location of data associated with the I/O request on the solid-state storage media 110 of the solid-state storage device 102. If the direct mapping module 808 determines 1314 not to update the mapping structure, for a read I/O request resulting in a cache hit or the like, the method 1300 continues without the direct mapping module 808 updating 1316 the mapping structure.
The direct mapping module 808 determines 1318 whether to reconstruct the mapping structure, in response to a reconstruction event such as a power failure, a corruption of the mapping structure, an improper shutdown, or the like. If the direct mapping module 808 determines 1318 to reconstruct the mapping structure, the direct mapping module 808 reconstructs 1320 the mapping structure using the logical block addresses and sequence indicators associated with data on the solid-state storage media 110 of the solid-state storage device 102, scanning a sequential, log-based, cyclic writing structure or the like. If the direct mapping module 808 determines 1318 not to reconstruct the mapping structure, the method 1300 skips the reconstruction step 1320 and the cache fulfillment module 702 continues to monitor 1302 I/O requests for the backing store 118.
FIG. 14 depicts one embodiment of a method 1400 for managing a cache unit VSU 122 of a solid-state storage device 102. The method 1400 begins and the cache interface module 602 provides 1402 access to a plurality of VSUs 122 of a solid-state storage device 102 over a cache interface 112. At least one of the VSUs 122, in certain embodiments, comprises a cache unit VSU 122.
The cache command module 604 exchanges 1404 cache management information for the at least one cache unit VSU 122 with one or more cache clients 120 over the cache interface 112. The cache management module 606 manages the at least one cache unit VSU 122 based on the cache management information exchanged with the one or more cache clients 120 and the method 1400 ends.
FIG. 15 depicts another embodiment of a method 1500 for managing a cache unit VSU 122 of a solid-state storage device 102. The method 1500 begins and the cache interface module 602 provides 1502 access to a plurality of VSUs 122 of a solid-state storage device 102 over a cache interface 112, including at least one cache unit VSU 122. The cache command module 604 sends 1504 a garbage collection request to one or more cache clients 120, identifying LBAs of an erase block targeted for garbage collection. The cache command module 604 receives 1506 a garbage collection response from the one or more cache clients 120 indicating which data of the erase block to evict from the at least one cache unit VSU 122. The cache management module 606 selects 1508 data for eviction from the at least one cache unit VSU 122 based on the received 1506 garbage collection response.
The cache command module 604 determines 1510 whether the cache command module 604 has received a command from a client 120 over the cache interface 112. If the cache command module 604 has received a command from a client 120, the cache management module 606 manages 1512 the at least one cache unit VSU 122 based on the received command, otherwise the method 1500 skips the managing 1512 step. The cache management module 606 determines 1514 whether a data error threshold for the solid-state storage device 102 has been satisfied.
If the cache management module 606 determines 1514 that the data error threshold has not been satisfied, the method 1500 continues. If the cache management module 606 determines 1514 that the data error threshold has been satisfied, the cache management module 606 reduces 1516 a storage capacity of the solid-state storage device 102 over time in response to the data errors and the cache command module 604 notifies 1518 the one or more cache clients 120, over the cache interface 112, of the reduced 1516 storage capacity. The method 1500 continues and the cache interface module 602 continues to provide 1502 access to the VSUs 122 over the cache interface 112.
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.

## Claims

1. A method comprising:
providing access to a plurality of virtual storage units of a solid-state storage device over a cache interface, at least one of the virtual storage units comprising a cache unit;
exchanging cache management information for the at least one cache unit with one or more cache clients over the cache interface, the one or more cache clients comprising a user application executing on a host device, wherein exchanging cache management information comprises sending a garbage collection request to the one or more cache clients and receiving a garbage collection response from the one or more cache clients, the garbage collection request identifying one or more logical block addresses of an erase block targeted for a garbage collection process that recovers physical capacity of invalid data from the erase block and copies valid data from the erase block to a different erase block, the garbage collection response identifying which valid data of the one or more logical block addresses for data of the erase block to evict from the at least one cache unit; and
managing the at least one cache unit based on the cache management information exchanged with the one or more cache clients by marking the valid data identified by the garbage collection response as invalid and evicting the invalid data from the at least one cache unit based on the garbage collection response as part of the garbage collection process.

2. The method of claim 1, wherein the cache management information comprises a command received from the one or more cache clients over the cache interface, the command comprising one or more of a cache admission command, a cache eviction command, a cache prefetch command, a cache destage command, a quality-of-service command, a physical capacity allotment command, a TRIM command, and a data priority command.

3. The method of claim 1, wherein the cache management information comprises a message sent to the one or more cache clients over the cache interface, the message comprising one or more of an eviction request and an available storage capacity report.

4. The method of claim 1, wherein the different virtual storage unit commands comprise one or more of a create command, a delete command, an enumerate command, a TRIM command, and a resize command.

5. The method of claim 1, wherein the at least one cache unit comprises a plurality of cache units operating simultaneously on the solid-state storage device.

6. The method of claim 5, wherein at least a portion of the plurality of cache units each present a distinct sparse logical address space to the one or more cache clients.

7. The method of claim 6, wherein the distinct sparse logical address spaces are mapped to a single sparse logical address space of the solid-state storage device.

8. The method of claim 5, wherein data from each of the plurality of cache units is intermingled in a sequential log-based writing structure of the solid-state storage device.

9. The method of claim 1, wherein the cache management information comprises a selection from the one or more cache clients of a logical address space type for the at least one cache unit, the logical address space type comprising one of a sparse logical address space and a contiguous block address space.

10. The method of claim 1, further comprising allocating physical storage capacity of the solid-state storage device according to a prioritization of the plurality of virtual storage units.

11. The method of claim 1, further comprising,
reducing storage capacity of the solid-state storage device over time in response to data errors; and
notifying the one or more cache clients, over the cache interface, of the reduced storage capacity of the solid-state storage device.

12. The method of claim 1, wherein a single mapping structure maps logical block addresses for the plurality of virtual storage units to physical storage addresses on solid-state storage media of the solid-state storage device.

13. The method of claim 12, wherein the plurality of virtual storage units comprise a plurality of cache units and the single mapping structure directly maps the logical block addresses for the plurality of cache units to logical block addresses of one or more backing store devices, the single mapping structure comprising a fully associative relationship between logical block addresses of the one or more backing store devices and the physical storage addresses on the solid-state storage media of the solid-state storage device.

14. A method comprising:
providing access to a plurality of virtual storage units of a solid-state storage device over an interface, the plurality of virtual storage units each presenting a distinct sparse logical address space, wherein data from each of the plurality of virtual storage units is intermingled in a sequential log-based writing structure of the solid-state storage device, the plurality of virtual storage units comprising a plurality of cache units;
mapping, using a single mapping structure, logical block addresses for the plurality of virtual storage units to physical storage addresses on solid-state storage media of the solid-state storage device, such that the distinct sparse logical address spaces of the plurality of virtual storage units share the single mapping structure, the distinct sparse logical address spaces comprising more addresses than a physical storage capacity of the solid-state storage device, the single mapping structure directly mapping the logical block addresses for the plurality of cache units to logical block addresses of one or more backing store devices, the single mapping structure comprising a fully associative relationship between logical block addresses of the one or more backing store devices and the physical storage addresses on the solid-state storage media of the solid-state storage device; and
satisfying input/output (“I/O”) requests for the plurality of virtual storage units using the single mapping structure.

15. The method of claim 14, wherein the plurality of virtual storage units comprise a plurality of cache units and the single mapping structure directly maps the logical block addresses for the plurality of cache units to logical block addresses of one or more backing store devices, the single mapping structure comprising a fully associative relationship between logical block addresses of the one or more backing store devices and the physical storage addresses on the solid-state storage media of the solid-state storage device.

16. The method of claim 14, further comprising,
exchanging management information for the plurality of virtual storage units with one or more clients over the interface; and
managing the plurality of virtual storage units based on the management information exchanged with the one or more clients.

17. An apparatus comprising:
a solid-state storage device comprising a plurality of virtual storage units;
a cache interface module that provides access to the plurality of virtual storage units of the solid-state storage device over a cache interface, at least one of the virtual storage units comprising a cache unit, wherein data from each of the plurality of virtual storage units is intermingled in a sequential log-based writing structure of the solid-state storage device;
a cache command module that exchanges cache management information for the at least one cache unit with one or more cache clients over the cache interface, the one or more cache clients comprising a user application executing on a host device, wherein exchanging cache management information comprises sending a garbage collection request to the one or more cache clients and receiving a garbage collection response from the one or more cache clients, the garbage collection request identifying one or more logical block addresses of an erase block targeted for a garbage collection process that recovers physical capacity of invalid data from the erase block, the garbage collection response identifying which valid data of the one or more logical block addresses of the erase block to evict from the at least one cache unit, the cache management information further comprising different virtual storage unit commands from the one or more cache clients, the different virtual storage unit commands for different virtual storage units; and
a cache management module that manages the at least one cache unit based on the valid data identified by the garbage collection response from the one or more cache clients.

18. The apparatus of claim 17, wherein the cache management module selects data for eviction from the at least one cache unit based on the cache management information.

19. The apparatus of claim 17, wherein the cache management information comprises a command received from the one or more cache clients over the cache interface, the command comprising one or more of a cache admission command, a cache eviction command, a cache prefetch command, a cache destage command, a quality-of-service command, a physical capacity allotment command, a TRIM command, and a data priority command.

20. A system comprising:
a solid-state storage device comprising a plurality of virtual storage units, at least one of the virtual storage units comprising a cache unit;
a cache controller for the solid-state storage device, the cache controller comprising,
a cache interface module that provides access to the plurality of virtual storage units over a cache interface;
a cache command module that exchanges cache management information for the at least one cache unit with one or more cache clients over the cache interface, the one or more cache clients comprising a user application executing on a host computer system, wherein exchanging cache management information comprises sending a garbage collection request to the one or more cache clients and receiving a garbage collection response from the one or more cache clients, the garbage collection request identifying one or more logical block addresses of an erase block targeted for a garbage collection process that recovers physical capacity of invalid data from the erase block, the garbage collection response indicating which valid data of the logical block addresses of the erase block to evict from the at least one cache unit; and
a cache management module that manages the at least one cache unit based on the cache management information exchanged with the one or more cache clients by evicting the valid data indicated by the garbage collection response from the at least one cache unit based on the garbage collection response.

21. The system of claim 20, further comprising a host computer system, wherein the one or more cache clients comprise software clients executing on the host computer system and the cache controller comprises a device driver executing on the host computer system.