Hybrid read voltage calibration in non-volatile random access memory

A computer-implemented method, according to one embodiment, includes: determining a current operating state of a block of memory. The block includes more than one type of page therein, and at least one read voltage is associated with each of the page types. The current operating state of the block is further used to produce a hybrid calibration scheme for the block which identifies a first subset of the read voltages, and a second subset of the read voltages. The read voltages in the second subset are further organized in one or more groupings. A unique read voltage offset value is calculated for each of the read voltages in the first subset, and a common read voltage offset value is also calculated for each grouping of read voltages in the second subset.

BACKGROUND

The present invention relates to data storage systems, and more particularly, this invention relates to calibrating the read voltages of blocks in non-volatile random access memory (NVRAM).

NVRAM is a type of random-access memory which retains information stored thereon even after the power supply is turned off, and includes a number of different forms. Using Flash memory as an example, the performance characteristics of conventional NAND Flash-based solid state drives (SSDs) are fundamentally different from those of traditional hard disk drives (HDDs). Data in conventional SSDs is typically organized in pages of 4, 8, or 16 KB sizes. Moreover, page read operations in SSDs are typically one order of magnitude faster than write operations and latency neither depends on the current nor the previous location of operations.

The raw bit error rate (RBER) of a Flash memory block will typically increase over time due to additional program/erase (P/E) cycling, charge leakage over time (i.e., data retention), and additional charge placed in the cells by read or program operations (i.e., read or program disturb errors, respectively). Typically, a Flash memory block is retired when any page in the block exhibits a code word that reaches a page retirement error count limit. This limit is typically set to be achieved in conjunction with an appropriate error correction code (ECC), resulting in the Uncorrectable Bit Error Rate (UBER) after applying the ECC for a Flash memory block being set to be similar to the UBER in traditional hard disk drives, e.g., at around 10−15, but may be more or less.

Block calibration, which refers to algorithms that adjust the read voltages, has been shown to significantly improve the RBER and therefore enhance endurance and retention, particularly for enterprise-level Flash memory systems using modern three-dimensional (3-D) triple-level-cell (TLC) or quad-level-cell (QLC) NAND Flash memory. Previous attempts to maintain efficient memory performance typically included inspecting the read voltages for each block of memory in a sweeping fashion or by a read voltage shifting algorithm that tracks and corrects the read voltages depending on how the threshold voltage distributions have changed as a result of cycling or retention or other disturbing effects.

SUMMARY

A computer-implemented method, according to one embodiment, is for calibrating read voltages for a block of memory. The computer-implemented method includes: determining a current operating state of a block of memory. The block includes more than one type of page therein, and at least one read voltage is associated with each of the page types. The current operating state of the block is further used to produce a hybrid calibration scheme for the block, where the hybrid calibration scheme identifies a first subset of the read voltages, as well as a second subset of the read voltages. The read voltages in the second subset are further organized in one or more groupings. A unique read voltage offset value is calculated for each of the read voltages in the first subset, and a common read voltage offset value is also calculated for each grouping of read voltages in the second subset. Each of the unique read voltage offset values and each of the common read voltage offset values are stored in a metadata storage area of the given block. Furthermore, the hybrid calibration scheme is saved in the metadata storage area of the given block.

A computer program product, according to another embodiment, is for calibrating read voltages for a block of memory. The computer program product includes a computer readable storage medium having program instructions embodied therewith. The program instructions are further readable and/or executable by a processor to cause the processor to: perform the foregoing method.

A system, according to yet another embodiment, includes: a processor, and logic integrated with and/or executable by the processor. The logic is configured to: perform the foregoing method.

DETAILED DESCRIPTION

The following description discloses several preferred embodiments of data storage systems, as well as operation and/or component parts thereof. It should be appreciated that various embodiments herein can be implemented with a wide range of memory mediums, including for example NVRAM technologies such as NAND Flash memory, NOR Flash memory, phase-change memory (PCM), magnetoresistive RAM (MRAM) and resistive RAM (RRAM). To provide a context, and solely to assist the reader, various embodiments may be described with reference to a type of non-volatile memory. This has been done by way of example only, and should not be deemed limiting on the invention defined in the claims.

In one general embodiment, a computer-implemented method is for calibrating read voltages for a block of memory. The computer-implemented method includes: determining a current operating state of a block of memory. The block includes more than one type of page therein, and at least one read voltage is associated with each of the page types. The current operating state of the block is further used to produce a hybrid calibration scheme for the block, where the hybrid calibration scheme identifies a first subset of the read voltages, as well as a second subset of the read voltages. The read voltages in the second subset are further organized in one or more groupings. A unique read voltage offset value is calculated for each of the read voltages in the first subset, and a common read voltage offset value is also calculated for each grouping of read voltages in the second subset. Each of the unique read voltage offset values and each of the common read voltage offset values are stored in a metadata storage area of the given block. Furthermore, the hybrid calibration scheme is saved in the metadata storage area of the given block.

In another general embodiment, a computer program product is for calibrating read voltages for a block of memory. The computer program product includes a computer readable storage medium having program instructions embodied therewith. The program instructions are further readable and/or executable by a processor to cause the processor to: perform the foregoing method.

In yet another general embodiment, a system includes: a processor, and logic integrated with and/or executable by the processor. The logic is configured to: perform the foregoing method.

FIG. 1illustrates a memory card100, in accordance with one embodiment. It should be noted that although memory card100is depicted as an exemplary non-volatile data storage card in the present embodiment, various other types of non-volatile data storage cards may be used in a data storage system according to alternate embodiments. It follows that the architecture and/or components of memory card100are in no way intended to limit the invention, but rather have been presented as a non-limiting example.

Moreover, as an option, the present memory card100may be implemented in conjunction with features from any other embodiment listed herein, such as those described with reference to the other FIGS. However, such memory card100and others presented herein may be used in various applications and/or in permutations which may or may not be specifically described in the illustrative embodiments listed herein. Further, the memory card100presented herein may be used in any desired environment.

With continued reference toFIG. 1, memory card100includes a gateway102, a general purpose processor (GPP)112(such as an ASIC, FPGA, CPU, etc.) connected to a GPP memory114(which may comprise RAM, ROM, battery-backed DRAM, phase-change memory PC-RAM, MRAM, STT-MRAM, etc., or a combination thereof), and a number of memory controllers108, which include Flash controllers in the present example. Each memory controller108is connected to a plurality of NVRAM memory modules104(which may comprise NAND Flash or other non-volatile memory type(s) such as those listed above) via channels106.

According to various embodiments, one or more of the controllers108may be or include one or more processors, and/or any logic for controlling any subsystem of the memory card100. For example, the controllers108typically control the functions of NVRAM memory modules104such as, data writing, data recirculation, data reading, etc. The controllers108may operate using logic known in the art, as well as any logic disclosed herein, and thus may be considered as a processor for any of the descriptions of non-volatile memory included herein, in various embodiments.

Moreover, the controller108may be configured and/or programmable to perform or control some or all of the methodology presented herein. Thus, the controller108may be considered to be configured to perform various operations by way of logic programmed into one or more chips, modules, and/or blocks; software, firmware, and/or other instructions being available to one or more processors; etc., and combinations thereof.

Referring still toFIG. 1, each memory controller108is also connected to a controller memory110which preferably includes a cache which replicates a non-volatile memory structure according to the various embodiments described herein. However, depending on the desired embodiment, the controller memory110may be battery-backed DRAM, phase-change memory PC-RAM, MRAM, STT-MRAM, etc., or a combination thereof.

As previously mentioned, memory card100may be implemented in various types of data storage systems, depending on the desired embodiment.FIG. 2illustrates a data storage system architecture200according to an exemplary embodiment which is in no way intended to limit the invention. Moreover, it should be noted that the data storage system220ofFIG. 2may include various components found in the embodiment ofFIG. 1.

Looking toFIG. 2, the data storage system220comprises a number of interface cards202configured to communicate via I/O interconnections204to one or more processor systems201. The data storage system220may also comprise one or more Redundant Array of Independent Disks (RAID) controllers206configured to control data storage in a plurality of non-volatile data storage cards208. The non-volatile data storage cards208may comprise NVRAM, Flash memory cards, RAM, ROM, and/or some other known type of non-volatile memory.

The I/O interconnections204may include any known communication protocols, such as Fiber Channel (FC), FC over Ethernet (FCoE), Infiniband, Internet Small Computer System Interface (iSCSI), Transport Control Protocol/Internet Protocol (TCP/IP), Peripheral Component Interconnect Express (PCIe), etc., and/or any combination thereof.

The RAID controller(s)206in the data storage system220may perform a parity scheme similar to that employed by RAID-5, RAID-6, RAID-10, or some other suitable parity scheme, as would be understood by one of skill in the art upon reading the present descriptions.

Each processor system201comprises one or more processors210(such as CPUs, microprocessors, etc.), local data storage211(e.g., such as RAM1014ofFIG. 10, ROM1016ofFIG. 10, etc.), and an I/O adapter218configured to communicate with the data storage system220.

Referring again toFIG. 1, memory controllers108and/or other controllers described herein (e.g., RAID controllers206ofFIG. 2) may be able to perform various functions on stored data, depending on the desired embodiment. Specifically, memory controllers may include logic configured to perform any one or more of the following functions, which are in no way intended to be an exclusive list. In other words, depending on the desired embodiment, logic of a storage system may be configured to perform additional or alternative functions, as would be appreciated by one skilled in the art upon reading the present description.

Garbage Collection

Garbage collection in the context of SSD memory controllers of the present description may include the process of identifying blocks of data to be reclaimed for future usage and relocating all pages that are still valid therein. Moreover, depending on the specific controller and/or the respective garbage collection unit of operation, logical erase blocks (LEBs) may be identified for being reclaimed and/or relocated. Typically, one LEB corresponds to one block stripe, but alternative implementations may consider a fixed number of block stripes building a LEB as well.

A physical “block” represents a minimal unit that may be erased on non-volatile memory, e.g., such as NAND Flash memory, and thereby prepared for writing data thereto. However, a typical garbage collection unit of operation is often a multiple of the physical blocks of non-volatile memory, and is also referred to herein as a LEB. This is due to the fact that typically RAID-like parity information is added in LEBs. Therefore, in case of a page or block failure data can only be rebuilt when all blocks in the LEB are still holding data. Accordingly, the individual blocks from the garbage collection unit can only be erased either individually or in a single unit once all still valid data from all blocks in the LEB has been relocated successfully to new locations. Hence, the full garbage collection units are garbage-collected as a single unit. Moreover, the size of the LEB directly affects the garbage collection induced write amplification. The larger the LEB, the more likely it becomes that unrelated data are stored together in the LEB, and therefore more of the LEB data may have to be relocated upon garbage collection selection.

Frequently, blocks from different dies and/or Flash channels are grouped together, such that blocks from the same group can be read or written in parallel, thereby increasing overall bandwidth. It is also possible to combine the previous two methods, and to compose RAID stripes using blocks from different Flash channels that can be accessed in parallel.

It should also be noted that an LEB may include any multiple of the physical memory block, which is a unit of physical erasure. Moreover, the organization of memory blocks into LEBs not only allows for adding RAID-like parity protection schemes among memory blocks from different memory chips, memory planes and/or channels but also allows for significantly enhancing performance through higher parallelism. For instance, multiple non-volatile memory blocks may be grouped together in a RAID stripe. As will be appreciated by one skilled in the art upon reading the present description, RAID schemes generally improve reliability and reduce the probability of data loss.

According to an exemplary embodiment, which is in no way intended to limit the invention, memory controllers (e.g., see108ofFIG. 1) may internally perform a garbage collection. As previously mentioned, the garbage collection may include selecting a LEB to be relocated, after which all data that is still valid on the selected LEB may be relocated (e.g., moved). After the still valid data has been relocated, the LEB may be erased and thereafter, used for storing new data. The amount of data relocated from the garbage collected LEB determines the write amplification. Moreover, an efficient way to reduce the write amplification includes implementing heat segregation.

Heat Segregation

In the present context, the “write heat” of data refers to the rate (e.g., frequency) at which the data is updated (e.g., rewritten with new data). Memory blocks that are considered “hot” tend to have a frequent updated rate, while memory blocks that are considered “cold” have an update rate slower than hot blocks.

Tracking the write heat of a logical page may involve, for instance, allocating a certain number of bits in the logical to physical table (LPT) mapping entry for the page to keep track of how many write operations the page has seen in a certain time period or window. Typically, host write operations increase the write heat whereas internal relocation writes decrease the write heat. The actual increments and/or decrements to the write heat may be deterministic or probabilistic.

Similarly, read heat may be tracked with a certain number of additional bits in the LPT for each logical page. To reduce meta-data, read heat can also be tracked at a physical block level where separate counters per block for straddling and non-straddling reads can be maintained. However, it should be noted that the number of read requests to and/or read operations performed on a memory block may not come into play for heat segregation when determining the heat of the memory block for some embodiments. For example, if data is frequently read from a particular memory block, the high read frequency does not necessarily mean that memory block will also have a high update rate. Rather, a high frequency of read operations performed on a given memory block may denote an importance, value, etc. of the data stored in the memory block.

By grouping memory blocks of the same and/or similar write heat values, write heat segregation may be achieved. In particular, write heat segregating methods may group write hot memory pages together in certain memory blocks while write cold memory pages are grouped together in separate memory blocks. Thus, a write heat segregated LEB tends to be occupied by either write hot or cold data.

The merit of write heat segregation is two-fold. First, performing a garbage collection process on a write hot memory block will prevent triggering the relocation of write cold data as well. In the absence of heat segregation, updates to write hot data, which are performed frequently, also results in the undesirable relocations of all write cold data collocated on the same LEB as the hot data being relocated. Therefore, the write amplification incurred by performing garbage collection is much lower for embodiments implementing write heat segregation.

Secondly, the relative write heat of data can be utilized for wear leveling purposes. For example, write hot data may be placed in healthier (e.g., younger) memory blocks, while write cold data may be placed on less healthy (e.g., older) memory blocks relative to those healthier memory blocks. Thus, the rate at which relatively older blocks are exposed to wear is effectively slowed, thereby improving the overall endurance of a given data storage system implementing write heat segregation.

Write Allocation

Write allocation includes placing data of write operations into free locations of open LEBs. As soon as all pages in a LEB have been written, the LEB is closed and placed in a pool holding occupied LEBs. Typically, LEBs in the occupied pool become eligible for garbage collection. The number of open LEBs is normally limited and any LEB being closed may be replaced, either immediately or after some delay, with a fresh LEB that is being opened.

During performance, garbage collection may take place concurrently with user write operations. For example, as a user (e.g., a host) writes data to a device, the device controller may continuously perform garbage collection on LEBs with invalid data to make space for the new incoming data pages. As mentioned above, the LEBs having the garbage collection being performed thereon will often have some pages that are still valid at the time of the garbage collection operation; thus, these pages are preferably relocated (e.g., written) to a new LEB.

Again, the foregoing functions are in no way intended to limit the capabilities of any of the storage systems described and/or suggested herein. Rather, the aforementioned functions are presented by way of example, and depending on the desired embodiment, logic of a storage system may be configured to perform additional or alternative functions, as would be appreciated by one skilled in the art upon reading the present description.

Referring now toFIG. 3, a system300is illustrated in accordance with one embodiment. As an option, the present system300may be implemented in conjunction with features from any other embodiment listed herein, such as those described with reference to the other FIGS. However, such system300and others presented herein may be used in various applications and/or in permutations which may or may not be specifically described in the illustrative embodiments listed herein. Further, the system300presented herein may be used in any desired environment, e.g., in combination with a controller.

As illustrated, system300includes a write cache302which is coupled to several other components, including garbage collector304. As previously mentioned, garbage collector304may be used to free LEB units by relocating valid data and providing non-volatile memory blocks to be erased for later reuse. Thus, the garbage collector304may reclaim blocks of consecutive physical space, depending on the desired embodiment. According to an exemplary embodiment, block erase units may be used to keep track of and/or complete the erase of non-volatile memory blocks handed over by the garbage collector304.

Write cache302is also coupled to free block manager306which may keep track of free non-volatile memory blocks after they have been erased. Moreover, as would be appreciated by one of ordinary skill in the art upon reading the present description, the free block manager306may build free stripes of non-volatile memory blocks from different lanes (e.g., block-stripes) using the erased free non-volatile memory blocks.

Referring still toFIG. 3, write cache302is coupled to LPT manager308and memory I/O unit310. The LPT manager308maintains the logical-to-physical mappings of logical addresses to physical pages of memory. According to an example, which is in no way intended to limit the invention, the LPT manager308may maintain the logical-to-physical mappings of 4 KiB logical addresses. The memory I/O unit310communicates with the memory chips in order to perform low level operations, e.g., such as reading one or more non-volatile memory pages, writing a non-volatile memory page, erasing a non-volatile memory block, etc.

To better understand the distinction between block-stripes and page-stripes as used herein,FIG. 4Ais a conceptual diagram400, in accordance with one embodiment. LEBs are built from block stripes and typically a single block stripe is used to build a LEB. However, alternative embodiments may use multiple block stripes to form an LEB. As an option, the present conceptual diagram400may be implemented in conjunction with features from any other embodiment listed herein, such as those described with reference to the other FIGS. However, such conceptual diagram400and others presented herein may be used in various applications and/or in permutations which may or may not be specifically described in the illustrative embodiments listed herein. Further, the controller conceptual diagram400presented herein may be used in any desired environment. Thus, the exemplary non-volatile memory controller conceptual diagram400ofFIG. 4Amay be implemented in a cache architecture. However, depending on the desired embodiment, the conceptual diagram400ofFIG. 4Amay be implemented in defining the organization of data stored in non-volatile memory. Accordingly, both implementations are described in turn below.

Looking now toFIG. 4A, the conceptual diagram400includes a set of M+1 aggregated planes labeled “Plane 0” through “Plane M”. An aggregated plane consists of all physical planes with the same plane index on different channels. It should be noted that aggregated planes are also referred to herein simply as planes.

When implemented with data stored in non-volatile memory, each physical plane on a channel may include a large set of blocks, e.g., typically in the order of 1024, 2048 or more. Moreover, one or more physical planes may also include several additional blocks which may be used as replacement blocks for bad blocks (e.g., blocks performing poorly, blocks having undesirable characteristics, etc.).

In each plane of non-volatile memory, a single block from each channel forms a respective block-stripe. It follows that a number of block-stripes supported by a given embodiment of non-volatile memory may be determined by the number of blocks per plane and the number of planes.

In the exploded view of Plane 0, the conceptual diagram400further illustrates a single block-stripe (Block-stripe 0) out of the set of block-stripes supported in the remainder of the planes. Block-stripe 0 of plane 0 is shown as including 11 blocks, one block from each channel labeled “Channel 0” through “Channel 10”. It should be noted that the association of blocks to block-stripe can change over time as block-stripes are typically dissolved after they have been garbage collected. Erased blocks may be placed in free block pools, whereby new block-stripes are assembled from blocks in the free block pools when write allocation requests fresh block-stripes. For example, looking to conceptual diagram400, Block 10 from Channel 0 and Block 41 from Channel 4 are currently associated with the illustrated Block-stripe 0 of Plane 0. Furthermore, the illustrated Block-stripe 0 holds N+1 page-stripes and each block therefore holds N+1 pages labeled “Page 0” through “Page N”.

Cache Architecture

Referring still toFIG. 4A, each block of pages illustrated in the exploded view of aggregated Plane 0 may constitute a unique block from one channel when implemented in a cache architecture. Similarly, each channel contributes a single, individual block which form a block-stripe. For example, looking to conceptual diagram400, Block 10 from Channel 0 includes all pages (Page 0 through Page N) therein, while Block 41 from Channel 4 corresponds to all pages therein, and so on.

In the context of a memory controller, e.g., which may be capable of implementing RAID at the channel level, a block-stripe is made up of multiple blocks which amount to a stripe of blocks. Looking still toFIG. 4A, the multiple blocks of aggregated Plane 0 constitute Block-stripe 0. While all blocks in a block-stripe typically belong to the same aggregated plane, in some embodiments one or more blocks of a block-stripe may belong to different physical planes. It follows that each aggregated plane may include one or more block-stripe. Thus, according to an illustrative embodiment, Block 0 through Block 10 from different physical planes may constitute a block-stripe.

Regardless of whether the conceptual diagram400ofFIG. 4Ais implemented with non-volatile memory and/or a cache architecture, in different embodiments, the number of pages in each block and/or the number of channels in each plane may vary depending on the desired embodiment. According to an exemplary embodiment, which is in no way intended to limit the invention, a block may include 1024 pages, but could include more or less in various embodiments. Analogously, the number of channels per plane and/or the number of planes may vary depending on the desired embodiment.

Referring still toFIG. 4A, all pages in a block-stripe with the same page index denote a page-stripe. For example, Page-stripe 0 includes the first page (Page 0) of each channel in Block-stripe 0 of Plane 0. Similarly, Page-stripe N includes the last page (Page N) of each channel in Block-stripe 0 of Plane 0.

The general storage architecture illustrated in the conceptual diagram400ofFIG. 4Ais also implemented by using 3-D memory structures in some approaches. For instance,FIG. 4Bdepicts a representational view of a 3-D non-volatile memory structure450, in accordance with one embodiment. As an option, the present structure450may be implemented in conjunction with features from any other embodiment listed herein, such as those described with reference to the other FIGS., such asFIG. 4A. However, such structure450and others presented herein may be used in various applications and/or in permutations which may or may not be specifically described in the illustrative embodiments listed herein. Further, the structure450presented herein may be used in any desired environment. ThusFIG. 4B(and the other FIGS.) may be deemed to include any possible permutation.

As shown, each layer452of the 3-D non-volatile memory structure450extends along both the x-axis and the y-axis. Each of these layers452include a plurality of storage components (not shown), such as voltage supply lines, sensor stacks, transistors, etc., which are used to implement the non-volatile memory devices of the general storage architecture illustrated in the conceptual diagram400ofFIG. 4A, e.g., as would be appreciated by one skilled in the art after reading the present description. Moreover, the various layers452are arranged in a stacked fashion along the z-axis in order to increase storage density and efficiency. Cells from different bitlines along a wordline (typically in the x or y dimension ofFIG. 4B) are logically combined to form pages: In TLC, each wordline in a block contains 3 physical pages (e.g., a lower page, an upper page, and an extra page) and a wordline typically belongs to one particular layer in the z dimension (perpendicular to the x-y plane). For a particular block, which is formed from a grid of cells connected by wordlines and bitlines, the number of wordlines residing on the same layer is typically small. Therefore, a block can be formed from wordlines of all layers452. Moreover, wordlines as well as pages in the same block may reside on different layers452.

Again, due to cycling, retention, read disturb, program disturb, etc., or other mechanisms that may be specific to the 3-D NAND Flash technology (e.g., floating gate based or charge trap based technology), process technology, cell and material design, circuit and array architecture, etc., or other specific design factors, the programmed threshold voltage distributions in the memory block may change with writing and erasing data (cycling), reading data (read disturb), time (retention), etc., in a slow or fast manner. In other words, the RBER of Flash memory blocks increases with time and use. As memory blocks are used, each P/E cycle performed on the blocks causes damage of the memory cells, which in turn increases the corresponding RBER.

Block calibration is an important aspect of enhancing endurance and retention for Flash storage systems, e.g., particularly enterprise-level Flash systems, by reducing the RBER experienced. This block calibration corresponds to the read voltages and refers to algorithms that are able to track the changes of the threshold voltage distributions and adjust the read voltages accordingly, thereby significantly reducing the bit errors and improving the performance consistency in the respective device by reducing read tail latency which would otherwise result from error recovery mechanism invocations.

Moreover, adjustments to the read voltages are applied during a read command accordingly. It follows that the threshold voltage represents the voltage required to turn on the transistor of a given Flash memory cell and its value depends on the amount of charge stored during programming. However, the read voltage is a bias voltage, the value of which is typically between the threshold voltage of two adjacent logical states, e.g., as is explained in further detail below inFIG. 5.

Referring momentarily toFIG. 5, a graph500illustrating the threshold voltage shifting phenomenon is illustrated in accordance with an example. The x-axis of the graph500represents the programmed threshold voltage VTH, while the y-axis represents the corresponding cell count of a QLC NAND Flash memory block. In QLC NAND Flash memory, each memory cell stores 4 bits of information, therefore, the VTHdistributions correspond to 16 possible discrete levels (L0, L1, . . . , L15). Moreover, each different type of page in a given block of QLC NAND Flash has a different set of the read voltages which correspond thereto. According to an example, which is in no way intended to limit the invention, a lower page corresponds to the V8 read voltage, an upper page corresponds to the V4 and V12 read voltages, an extra page corresponds to the V2, V6, V10, and V14 read voltages, while a top page corresponds to the V1, V3, V5, V7, V9, V11, V13 and V15 read voltages.

The solid distributions502indicate the VTHlevels after programming. The vertical solid lines504indicate the read voltages (V1, . . . , V15) that are optimal for the VTHdistributions502. The dashed distributions506indicate a negative shift of the VTHlevels due to charge loss over time. Because of this negative shift to lower voltages, the read voltages504are no longer optimal. Indeed, a negative offset must be applied to the read voltages in order to account for the changes of the VTHdistributions from502to506. The vertical dashed lines508indicate the read voltages (V1, . . . , V15) that are optimal during retention for the VTHdistributions in506. In general, each of the 16 levels (L0, L1, . . . , L15) shown in the figure may have a different VTHshift and thus, each of the 15 read voltages (V1, . . . , V15) may have a different optimal shift.

Accordingly, the read voltage shift values (or offset values) are preferably determined shortly after a block has been written to and/or periodically thereafter. The threshold voltage can be considered an index of the cell programmed level (i.e., L0, L1, . . . , L15), as determined by measuring the source-drain current when a control gate bias is applied to the memory cell. Typically, upon a read operation, one or more read voltages between adjacent nominal threshold voltage levels are used to determine the memory cell state. As the threshold voltage value of the memory cell changes (as explained above), the read voltages applied during a read operation are preferably shifted accordingly using a set of offset values to obtain optimal readout conditions and minimize the RBER. Subsequently, the optimal read voltage shift values may be updated periodically, e.g., in a background health check, or on demand, e.g., in the event of high bit error count or ECC failure.

Although increases to RBERs are irreparable for some blocks (e.g., such as those caused by prolonged P/E cycles), increases to RBERs caused by events such as retention and/or read disturbances are transient in the sense that the blocks which are affected are not irreversibly damaged. This unfavorable increase in RBERs is remedied when the corresponding memory blocks recalibrated such that the corresponding read voltages are corrected. In other approaches, blocks experiencing transient RBER increases may be remedied by being erased, programmed, and recalibrated. It is therefore apparent that the RBER of the block depends on the state of the block, which may be determined by the cycling state, the retention state, the read disturb state and/or any combinations thereof. Block recalibration improves the RBER by adjusting the read voltages so that they are optimal under the various changes of the VTHdistributions under permanent effects and/or transient effects.

Ideally, the read voltages for each page in a block of memory are updated individually. However, as the storage capacity of memory increases, the amount of storage consumed by maintaining a read voltage offset value for each page in each block of memory increases as well. For instance, going from 3 bits per cell in TLC NAND Flash memory to 4 bits per cell in QLC NAND Flash memory, each block implements 16 threshold voltage levels (instead of 8 in TLC), and 15 different read voltages (instead of 7 in TLC) to read any of the pages included therein. Moreover, with the improvements in vertical stacking and process technology, the number of layers in every new generation of 3-D NAND Flash increases as well. Subsequently, the number of pages in each block also increases. For example, current 3-D QLC NAND Flash memory may have more than 90 layers and each block may have more than 4000 pages. Thus, if all of these 15 different read voltages in 3-D QLC NAND are calibrated independently (or individually), the amount of metadata involved with storing an individual set of read offset values for each page, or group of pages, in a block and the number of calibration reads per page increases significantly.

Moreover, the different pages in a block may exhibit different read offset values mainly attributed to process variations that result in the various cells having differences in their threshold voltage characteristics. One approach to reduce the amount of metadata may be to group pages of the same type, e.g., lower pages or upper pages, and to use a set of read voltage offsets for all members of the same group. A second approach to reduce the amount of metadata may be to use a single offset value for all read voltages that are used when reading a specific page type, e.g., to shift all four read voltages V2, V6, V10 and V14 in tandem by a best common offset for the example of extra pages described above. Such an approach reduces the amount of metadata stored for each extra page, or group of extra pages, in the block from 4 values to 1 value and also reduces the number of calibration reads accordingly.

However, in order for this second approach to be effective, the change of the threshold voltage levels (which are discriminated by the applications of the specific read voltages) is preferably uniform and towards the same direction. For example, all VTHlevels shift to negative values. However, this assumption may not hold under all different states that a block may experience. For example, read disturb stress tends to generate a positive shift to the left-most VTHlevels, while retention tends to generate a negative shift that is higher in the right-most VTHlevels. Moreover, in modern TLC and QLC NAND Flash memories, where the margin between the adjacent VTHlevels is small, a common offset applied to multiple read voltages may not be sufficient to reduce the RBER whereas individual offsets for all or for selected read voltages may be implemented.

It follows that various ones of the embodiments included herein implement a hybrid calibration method, in which select read voltages in a block are calibrated independently and the remaining read voltages are grouped together based on the corresponding page type, and are calibrated according to a best common offset that is applied to all read voltages in the group. For example, the read voltages which correspond to the left-most and right-most VTHlevels, e.g., levels L0, L1, L2, L3 and L12, L13, L14, L15 inFIG. 5, may be more sensitive to various sources of disturbance or noise (e.g., such as retention and/or read disturb) than those read voltages located towards the middle. For instance, it may be appreciated by those skilled in the art that the left-most and right-most VTHlevels in a block may experience a more pronounced shift which also diverges along different directions when the device is subjected to retention and read disturb stress compared to the shift of the middle VTHlevels. As a consequence, it becomes apparent that the corresponding left-most and right-most read voltages may benefit from individual calibration, while the middle read voltages may form one or more voltage groupings and each voltage grouping may be calibrated by using a common best offset without compromising the RBER. Thus, some of the embodiments herein benefit by performing individual voltage calibrations for the read voltages which correspond to the outermost VTHlevels, while applying common voltage calibrations for the read voltages which correspond to the middle VTHlevels. This desirably offers improved RBERs while also keeping the metadata size relatively low, e.g., as will be described in further detail below.

Referring now toFIG. 6, a flowchart of a method600for selecting a hybrid calibration scheme for the read voltages of a block of memory is illustrated in accordance with one embodiment. The method600may be performed in accordance with the present invention in any of the environments depicted inFIGS. 1-5, among others, in various embodiments. For instance, any of the processes included in method600may be performed with respect to blocks of storage space in 3-D TLC NAND Flash, 3-D QLC NAND Flash, etc., or any other desired type of memory. Furthermore, more or less operations than those specifically described inFIG. 6may be included in method600, as would be understood by one of skill in the art upon reading the present descriptions.

Each of the steps of the method600may be performed by any suitable component of the operating environment. For example, in various embodiments, the method600may be partially or entirely performed by a controller (e.g., Flash controller), a processor, a computer, etc., or some other device having one or more processors therein. Thus, in some embodiments, method600may be a computer-implemented method. It should also be noted that the terms computer, processor and controller may be used interchangeably with regards to any of the embodiments herein, such components being considered equivalents in the many various permutations of the present invention.

As shown inFIG. 6, operation602of method600includes advancing to a next block of memory. With respect to the present description, “a next block of memory” may vary depending on the given approach. For instance, upon initiating method600, a next block of memory may simply be a first block of memory. In other approaches, a next block of memory may be a next logical block of memory. Moreover, operation602may progress between the blocks of memory in any desired manner, e.g., sequentially, randomly, using a pattern, etc. Moreover, operation602may be triggered periodically, e.g., every 1 week, by a background process that examines all the NAND blocks, or may be triggered on demand, e.g., in the event of a page read in a block exhibiting a high bit error count or an ECC failure. Moreover, the memory preferably includes NVRAM. For instance, in some approaches the memory includes 3-D TLC NAND Flash, while in other approaches the memory includes 3-D QLC NAND Flash.

Decision604further includes determining whether the given block of memory should be recalibrated. In some approaches, criteria may be implemented which identify when and if a particular block should be recalibrated. For example, a block may be recalibrated after experiencing a predetermined number of P/E cycles (e.g.,500P/E cycles), experiencing an undesirably low performance metric (e.g., the number of bit errors exhibiting a predetermined error count threshold), a predetermined amount of time has passed since a last recalibration, etc. This allows for some reduction in the amount of computing overhead experienced, e.g., as would be appreciated by one skilled in the art after reading the present description.

In response to determining that the given block of memory should not be recalibrated for whatever reason, method600returns to operation602whereby a next block is advanced to before repeating decision604. However, in response to determining that the given block of memory should be recalibrated, method600proceeds to operation606. There, operation606includes determining a current operating state of the given block of memory. This operating state may be determined based on various types of available information. For example, block statistics including a P/E cycling counter value, a read-disturb counter value, a retention timer, an open/close block state, a number of programmed pages in the block, etc. may be used to determine the current operating state of the block. It should also be noted that the block includes more than one type of page therein (e.g., upper page, lower page, extra page, top page), and at least one read voltage is associated with each of the page types, e.g., as would be appreciated by one skilled in the art after reading the present description.

An illustrative list of current operating states a given block of memory may be experiencing includes, but is in no way limited to, a retention state, a read-disturb state, a cycling state, an open and/or closed state (e.g., if part or all of the pages in the block have been programmed), etc., and/or any combination thereof. Each of the operating states a block may be experiencing may be utilized to identify which of the read voltages would benefit most from an individual recalibration, and which read voltages may be grouped together and be recalibrated using a common offset value. In other words, the operating state of a block may give insight into how the VTHlevels have changed, or may be expected to change, and thus how the corresponding read voltages should be adjusted to account for those VTHchanges. The more critical read voltages may thereby be given additional attention during the recalibration process in an effort to improve the overall RBER by applying individual offset recalibration, while the read voltages that can be grouped together are recalibrated by a common offset in an effort to reduce metadata and improve performance.

For example, it may be determined that the left-most read voltages in a block experiencing a read-disturb state would benefit most from (e.g., are more critical for) individual recalibration. This can be explained by the fact that read-disturb stress mainly affects the left-most VTHlevels along the read voltage distribution (e.g., as seen inFIG. 5), while the middle and right-most VTHlevels may experience a moderate or a low disturbance. Accordingly, the read voltages corresponding to the left-most VTHlevels are preferably recalibrated independently, while at least some of the remaining read voltages are recalibrated together as a group, e.g., by applying a best fit common read voltage offset value. According to another example, it may be determined that the right-most read voltages in a block experiencing a retention state are more critical for individual recalibration. This can be explained by the fact that during retention the negative shift is more pronounced for the right-most VTHlevels while the middle and left-most VTHlevels may experience a moderate or a low negative shift. Accordingly, the read voltages corresponding to the right-most VTHlevels are preferably calibrated independently, while at least some of the remaining read voltages are recalibrated together as group, e.g., by applying a best common offset value.

It follows that a hybrid calibration scheme preferably identifies a first and second subset of the read voltages which correspond to the different types of pages in a given block. The read voltages are preferably separated such that those in the first subset are more critical according to the operating state of the block and therefore warrant individual recalibration, while the read voltages in the second subset include those read voltages which are less critical (e.g., at least in comparison to the read voltages included in the first subset) and can be recalibrated using a common offset. Read voltages that are included in the second subset are preferably further organized in one or more read voltage groupings. For example, read voltages in the second subset which are used for reading pages of the same type (e.g., lower pages, upper pages, extra pages, top pages, etc.) are preferably grouped together to form read voltage groupings. Accordingly, a same read voltage offset value may be applied to each of the read voltages included in a same read voltage grouping, e.g., as will soon become apparent.

Recalibrating two or more read voltages together typically produces a common read voltage offset value which is applied to each of the two or more read voltages. However, depending on the operating state of the block, these two or more read voltages may be less critical to read errors and thus a common read voltage offset value may therefore be a good approximation of the desired read voltage offset value for each of these read voltages. Thus, the recalibration scheme is able to reduce the total amount of metadata stored in memory for each block and the total amount of read operations that are performed during recalibration without compromising the overall RBER. It follows that by pairing a given block with a current operating state, operation606is able to determine valuable information about how the VTHlevels therein have changed or at least are expected to change. Given this information, the current operating state provides insight into which of the read voltages would benefit most from experiencing individual read voltage recalibration and which of the read voltages can be grouped together and recalibrated using a common read voltage offset value.

Proceeding to operation608, the current operating state of the block is used to produce a hybrid calibration scheme for the block. In other words, the current operating state of a block is used to identify and/or compute a hybrid calibration scheme which may be applied to the block to recalibrate the pages included therein. As mentioned above, a hybrid calibration scheme preferably identifies a first subset of read voltages in a block which are more critical and therefore would more greatly benefit from experiencing individual recalibration, in addition to a second subset of read voltages in the block which can be grouped together and recalibrated by a common read voltage offset value. The read voltages identified in the first subset may thereby be recalibrated individually to reduce the chance of experiencing read errors, while the read voltages identified in the second subset are recalibrated together by using a common offset to reduce the amount of metadata that is stored for each block of memory and also to reduce the number of calibration reads.

In an attempt to reduce the overall calibration metadata overhead, the number of unique read voltage offset values that may be stored for the pages in a word-line, or group of word-lines, may be less than the total number of read voltages that the NAND chip uses, i.e., 15 read voltages for QLC NAND Flash memory. For instance, if “K” represents the number of unique read voltage offset values that may be stored for the pages in a word-line, or group of word-lines, and “N” represents the total number of read voltages, then K<N. According to an example, which is in no way intended to limit the invention, N=15 and K=10. Such a constraint is considered when the hybrid calibration scheme is selected or computed in608. In one example that is in no way intended to be limiting, a total of K=10 read voltage offset values may be stored in metadata storage for the pages of a word-line, or group of word-lines, in a block. In this example, a hybrid calibration scheme may determine that from the N=15 read voltages V1, V2, . . . , V15 as seen inFIG. 5, 7specific read voltages (e.g., V1, V2, V3, V8, V13, V14 and V15) are preferably calibrated individually, while the remaining read voltages are used to form 3 different read voltage groupings depending on the different page types that these remaining voltages are used for. For instance, V4 and V12 form a first read voltage grouping, V6 and V10 form a second read voltage grouping, and V5, V7, V9 and V11 form a third read voltage grouping. Moreover, each of these read voltage grouping is calibrated by a common offset value.

The decision on which read voltages are to be recalibrated independently and which are to be grouped and be recalibrated by a common read voltage offset value may be static in some approaches, while in other approaches the decision is made dynamically. In other words, in some approaches the hybrid calibration schemes are predetermined (e.g., based on lab measurements) and stored in memory (e.g., in a lookup table). It follows that each of the predetermined hybrid calibration schemes may be correlated with a current operating state. Accordingly, the process of producing a hybrid calibration scheme for the block may simply involve matching the current operating state of the block with a corresponding one of a number of predetermined hybrid calibration schemes for the block.

However, in other approaches the hybrid calibration schemes are dynamically produced based on performance information that is available. For instance, using the current operating state of the block to produce a hybrid calibration scheme for a block in some approaches includes computing the hybrid calibration scheme for the block using available statistics associated with the current operating state of the block. An illustrative list of statistics associated with the current operating state of the block that may be used to compute a hybrid calibration scheme includes, but is not limited to, a P/E counter, a read disturb counter, a retention timer, a retention metric, a cycling level, read disturb system counters, etc., or any other type of statistics which are available and/or which would be apparent to one skilled in the art after reading the present description.

Given a selected configuration, an algorithm, often called read-level shifting algorithm, may be implemented to calculate the read voltage offset values. According to some approaches, the read-level shifting algorithm may be an iterative algorithm that finds a desired offset value by searching the available space towards the direction of increasing or decreasing values that reduces the error count and selecting the offset value that minimizes the error count. According to other approaches, the read-level shifting algorithm may be an extensive search algorithm that searches all or a subset of the available offset values.

With continued reference toFIG. 6, method600proceeds to operation610which includes calculating a unique read voltage offset value for each of the read voltages in the first subset. As mentioned above, the first subset of the read voltages is identified based on the hybrid voltage calibration scheme produced in608. Moreover, a read-level shifting algorithm may be employed. As mentioned above, the read voltages included in the first subset are those identified as being more susceptible to producing read errors. Moreover, each of the read voltages in the first subset correspond to a page type. Further, as mentioned previously, one approach to reduce the calibration metadata may be to group pages (of the same page type) with similar RBER characteristics in the same group and use the same set of read voltage offset values for all pages in the group. Therefore, operation610is repeated for all pages, or group of pages, in the block, i.e., a unique read voltage offset value for each of the read voltages in the first subset is calculated for each page, or group of pages, in the block depending on the page type of the page, or the group of pages.

Moreover, operation612includes calculating a common read voltage offset value for each grouping of read voltages in the second subset. As mentioned above, the read voltages identified in the second subset include those read voltages identified as being less susceptible to producing read errors. Moreover, each of the read voltages organized in a given read voltage grouping corresponds to a same page type. Therefore, the read voltages identified in the second subset and which are included in a same read voltage grouping (e.g., which correspond to a same page type) are recalibrated together to reduce the amount of metadata that is stored for each block of memory. Moreover, a read-level shifting algorithm may be employed.

Operation612is repeated for all pages, or group of pages, in the block, i.e., a common read voltage offset value for each of the read voltage groupings in the second subset is calculated for each page, or group of pages, in the block depending on the page type of the page, or the group of pages.t should also be noted that the process of calculating a unique read voltage offset value for a given read voltage may be performed using any processes which would be apparent to one skilled in the art after reading the present description.

As previously mentioned, the read voltages which are included in the same grouping preferably correspond to the same type of page. In other words, all read voltages in a given read voltage group may correspond to pages which are of the same type, e.g., upper page type. For example, each of the read voltages included in a first read voltage grouping correspond to lower pages, while each of the read voltages included in a second read voltage grouping correspond to upper pages, each of the read voltages included in a third read voltage grouping correspond to extra pages, and each of the read voltages included in a fourth read voltage grouping correspond to top pages. It follows that calculating a common read voltage offset value for each read voltage grouping in the second subset may involve calculating a read voltage offset value for each of the read voltages, and determining a mean value, a median value, a weighted average, etc. for the given read voltage grouping, or may involve searching through a number of read voltage offset values and determining which offset value results in the minimum number of errors when applied as a common offset to all the read voltages in the same voltage grouping.

As noted herein, a read-level shifting algorithm that aims to adjust the read voltages is based on an iterative procedure that examines a number of candidate offsets and selects the one that minimizes the number of read errors. The candidate offsets may be fixed (e.g., predetermined), calculated dynamically based on different information (e.g. current and/or next positive or negative offsets), based on an algorithm such as line-search, etc. It follows that for any read voltage, or group of read voltages, a read-level shifting algorithm will use the most recent value that was calculated and stored for the particular block in the previous calibration round as a starting offset value.

For instance, when a hybrid calibration scheme is employed, the initial read voltage offset values for the level-shifting algorithm are preferably configured properly. For instance, assume a new group of voltages is defined for a given page, or group of pages, in a block, where some of the voltages are previous members of the group and some voltages that were previously calibrated independently are new members of the group. Here, the new group includes voltages that have a different offset based on the previous calibration round. Accordingly, a new common read voltage offset value is preferably determined as a common current offset for the new voltage grouping.

Looking toFIG. 7, a table700which presents an exemplary rule which may be applied to each group of read voltages is illustrated in accordance with one embodiment which is in no way intended to limit the invention. As an option, the present rule defined in table700may be implemented in conjunction with features from any other embodiment listed herein, such as those described with reference to the other FIGS., such asFIG. 6. However, such rule in table700and others presented herein may be used in various applications and/or in permutations which may or may not be specifically described in the illustrative embodiments listed herein. Further, the rule in table700presented herein may be used in any desired environment.

As shown, each read voltage Vn for n=1:15 of a new configuration inherits a read voltage offset value from a previous configuration. Thus, if the read voltage was previously calibrated individually, it inherits the previous unique read voltage offset value, whereas if the read voltage was previously included in a read voltage group, it inherits the previous common read voltage offset value of the group. This inherited read voltage offset value is used to calculate the new starting read voltage offset value for the level-shifting algorithm depending on the new configuration. The table700further identifies that if a given read voltage was previously calibrated individually and is also calibrated individually according to the new configuration, the new read voltage offset value remains the same as the previous read voltage offset value. However, if a given read voltage was previously calibrated individually and in the new configuration is included in a read voltage grouping, an average of the read voltage offset values for the read voltages in the same grouping formed in the new configuration is calculated and applied.

Furthermore, if a given read voltage was previously included in a read voltage grouping, but is now calibrated individually in the new configuration, the previous common read voltage offset value for the voltages in the same grouping of the previous configuration is maintained. However, if a given read voltage was previously included in a read voltage grouping, and is now included in a new read voltage grouping in the new configuration, an average of the read voltage offset values for the voltages in the new page grouping is calculated and applied.

Referring back toFIG. 6, operation614includes saving (e.g., storing) each of the unique read voltage offset values and each of the common read voltage offset values in the metadata storage area of the given block. Moreover, operation616includes saving (e.g., storing) the hybrid calibration scheme produced in operation608in the metadata storage area of the given block. The saved configuration of the hybrid calibration scheme may be an identifier from a list of hybrid calibration schemes or any identifier that encodes information about which of the read voltages are calibrated independently and which are forming voltage groupings and calibrated with a common offset.

The information saved in the metadata storage area during operations614and616is used when the memory controller needs to access any of the pages in a given block. For example, the controller may need to access an extra page that may further belong to a group of extra pages in a given block. Before accessing the given extra page, the memory controller retrieves from the metadata storage area of the given block the set of read voltage offset values corresponding to the given group of extra pages according to the latest calibration round. In addition, the controller retrieves from the metadata storage area the hybrid configuration scheme of the given block. Based on the hybrid configuration scheme and the set of read voltage offset values, the controller sends the respective commands to change the settings of read voltage values used for reading a page of extra page type in the NAND Flash chip. The new settings of read voltage values correspond to the desired values according to the current operating state of the given block, thus maximizing the probability for the controller to perform a read access with a low RBER. After sending the above mentioned commands, the controller sends the respective commands to read the given extra page.

It follows that various ones of the embodiments included herein are able to achieve efficient processes of selecting a hybrid calibration scheme for the read voltages for blocks of memory (e.g., NAND Flash memory). Some of these embodiments store more than one bit per cell based on a hybrid scheme that identifies which of the multiple read voltages will be calibrated by receiving a single individual offset and which voltages will be grouped together and be calibrated by a single common offset. This distinction between individual offsets and common offsets is based on the state of the block to be calibrated in preferred approaches, e.g., a retention state, a read disturb state, a cycling state, etc. Moreover, the voltages that are grouped together into one or more voltage groupings correspond to the same type of pages, i.e., lower pages, upper pages, extra pages, top pages, etc.

Referring now toFIG. 8an example of a number of different predetermined hybrid calibration schemes organized in a table800. It follows that the table800may be implemented in conjunction with features from any other embodiment listed herein, such as those described with reference to the other FIGS., such asFIG. 6. For instance, each of the predetermined hybrid calibration schemes in the table800may correspond to a particular current block operating state and be implemented as desired.

However, such table800and others presented herein may be used in various applications and/or in permutations which may or may not be specifically described in the illustrative embodiments listed herein. Further, the table800presented herein may be used in any desired environment. ThusFIG. 8(and the other FIGS.) may be deemed to include any possible permutation.

As shown, the table800includes three different predetermined hybrid calibration schemes802,804,806, each of which correspond to a different block operating state. Table800refers to a QLC NAND Flash memory with N=15 read voltages (i.e., V1, . . . , V15). Each of the different predetermined hybrid calibration schemes802,804,806also involve storing K=10 (K<N) different read voltage offset values (i.e., Δ1, . . . , Δ10) in metadata for each word-line, or group of word-lines, in a given block. Some of these read voltage offset values correspond to an independent calibration type as noted in the “offset type” column by a “independent” indicator, while other ones of the read voltage offset values correspond to voltage grouping and calibration by a common offset value as noted in the “offset type” column by a “common” indicator. The read voltages that are grouped and calibrated by a common read offset value are shown in the column “read voltages”.

Here, the first predetermined hybrid calibration schemes802corresponds to a generic block operating state in that it may be applied to circumstances which generally involve cycling, retention and read disturb states. Another of the predetermined hybrid calibration schemes804corresponds to a read disturb block operating state in that it may be applied to blocks which are currently experiencing read disturb states of higher stress. Furthermore, another of the predetermined hybrid calibration schemes806corresponds to a retention block operating state in that it may be applied to blocks which are currently experiencing retention states of longer duration. The predetermined hybrid calibration schemes outlined in table800may be stored in memory (e.g., in a lookup table) and applied to blocks based on their current operating state according to any of the approaches described herein.

It should also be noted that none of the particular configurations included in any of the approaches included herein are intended to be limiting. For instance, the number and/or type of pages included in a given block of memory, the number and/or values of the read voltages, the number and/or values of the threshold voltage levels, etc. included in any of the approaches included herein are in no way intended to be limiting, but rather have been presented by way of example only.

FIG. 9illustrates a network architecture900, in accordance with one embodiment. As shown inFIG. 9, a plurality of remote networks902are provided including a first remote network904and a second remote network906. A gateway901may be coupled between the remote networks902and a proximate network908. In the context of the present network architecture900, the networks904,906may each take any form including, but not limited to a LAN, a WAN such as the Internet, public switched telephone network (PSTN), internal telephone network, etc.

In use, the gateway901serves as an entrance point from the remote networks902to the proximate network908. As such, the gateway901may function as a router, which is capable of directing a given packet of data that arrives at the gateway901, and a switch, which furnishes the actual path in and out of the gateway901for a given packet.

Further included is at least one data server914coupled to the proximate network908, and which is accessible from the remote networks902via the gateway901. It should be noted that the data server(s)914may include any type of computing device/groupware. Coupled to each data server914is a plurality of user devices916. Such user devices916may include a desktop computer, laptop computer, handheld computer, printer, and/or any other type of logic-containing device. It should be noted that a user device911may also be directly coupled to any of the networks, in some embodiments.

A peripheral920or series of peripherals920, e.g., facsimile machines, printers, scanners, hard disk drives, networked and/or local data storage units or systems, etc., may be coupled to one or more of the networks904,906,908. It should be noted that databases and/or additional components may be utilized with, or integrated into, any type of network element coupled to the networks904,906,908. In the context of the present description, a network element may refer to any component of a network.

According to some embodiments, methods and systems described herein may be implemented with and/or on virtual systems and/or systems which emulate one or more other systems, such as a UNIX system which virtually hosts a MICROSOFT WINDOWS environment, etc. This virtualization and/or emulation may be enhanced through the use of VMWARE software, in some embodiments.

FIG. 10shows a representative hardware environment associated with a user device916and/or server914ofFIG. 9, in accordance with one embodiment.FIG. 10illustrates a typical hardware configuration of a processor system1000having a central processing unit1010, such as a microprocessor, and a number of other units interconnected via a system bus1012, according to one embodiment. In some embodiments, central processing unit1010may include any of the approaches described above with reference to the one or more processors210ofFIG. 2.

The processor system1000shown inFIG. 10includes a Random Access Memory (RAM)1014, Read Only Memory (ROM)1016, and an I/O adapter1018. According to some embodiments, which are in no way intended to limit the invention, I/O adapter1018may include any of the approaches described above with reference to I/O adapter218ofFIG. 2. Referring still to processor system1000ofFIG. 10, the aforementioned components1014,1016,1018may be used for connecting peripheral devices such as storage subsystem1020to the bus1012. In some embodiments, storage subsystem1020may include a similar and/or the same configuration as data storage system220ofFIG. 2. According to an example, which is in no way intended to limit the invention, storage subsystem1020may include non-volatile data storage cards, e.g., having NVRAM memory cards, RAM, ROM, and/or some other known type of non-volatile memory, in addition to RAID controllers as illustrated inFIG. 2.

With continued reference toFIG. 10, a user interface adapter1022for connecting a keyboard1024, a mouse1026, a speaker1028, a microphone1032, and/or other user interface devices such as a touch screen, a digital camera (not shown), etc., to the bus1012.

Processor system1000further includes a communication adapter1034which connects the processor system1000to a communication network1035(e.g., a data processing network) and a display adapter1036which connects the bus1012to a display device1038.

Moreover,FIG. 11illustrates a storage system1100which implements high level (e.g., SSD) storage tiers in combination with lower level (e.g., magnetic tape) storage tiers, according to one embodiment. Note that some of the elements shown inFIG. 11may be implemented as hardware and/or software, according to various embodiments. The storage system1100may include a storage system manager1112for communicating with a plurality of media on at least one higher storage tier1102and at least one lower storage tier1106. However, in other approaches, a storage system manager1112may communicate with a plurality of media on at least one higher storage tier1102, but no lower storage tier. The higher storage tier(s)1102preferably may include one or more random access and/or direct access media1104, such as hard disks, nonvolatile memory (NVM), NVRAM), solid state memory in SSDs, Flash memory, SSD arrays, Flash memory arrays, etc., and/or others noted herein or known in the art. According to illustrative examples,FIGS. 3-4show exemplary architectures of SSD systems which may be used as a higher storage tier1102depending on the desired embodiment.

Referring still toFIG. 11, the lower storage tier(s)1106preferably includes one or more lower performing storage media1108, including sequential access media such as magnetic tape in tape drives and/or optical media, slower accessing HDDs, slower accessing SSDs, etc., and/or others noted herein or known in the art. One or more additional storage tiers1116may include any combination of storage memory media as desired by a designer of the system1100. Thus, the one or more additional storage tiers1116may, in some approaches, include a SSD system architecture similar or the same as those illustrated inFIGS. 1-2. Also, any of the higher storage tiers1102and/or the lower storage tiers1106may include any combination of storage devices and/or storage media.

The storage system manager1112may communicate with the storage media1104,1108on the higher storage tier(s)1102and lower storage tier(s)1106through a network1110, such as a storage area network (SAN), as shown inFIG. 11, or some other suitable network type. The storage system manager1112may also communicate with one or more host systems (not shown) through a host interface1114, which may or may not be a part of the storage system manager1112. The storage system manager1112and/or any other component of the storage system1100may be implemented in hardware and/or software, and may make use of a processor (not shown) for executing commands of a type known in the art, such as a central processing unit (CPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc. Of course, any arrangement of a storage system may be used, as will be apparent to those of skill in the art upon reading the present description.

According to some embodiments, the storage system (such as1100) may include logic configured to receive a request to open a data set, logic configured to determine if the requested data set is stored to a lower storage tier1106of a tiered data storage system1100in multiple associated portions, logic configured to move each associated portion of the requested data set to a higher storage tier1102of the tiered data storage system1100, and logic configured to assemble the requested data set on the higher storage tier1102of the tiered data storage system1100from the associated portions.