Patent Grant
10156999
The invention relates to solid-state drives generally and, more particularly, to a method and/or apparatus for implementing dynamic bandwidth reporting for solid-state drives.
Access to storage is part of conventional server virtualization systems. In server virtualization systems, the servers run virtual machines that allow efficient and cost-effective utilization of an information technology infrastructure. Each server can host multiple virtual machines with a goal to maximize utilization of an underlying hardware infrastructure of central processor units, memory, network interfaces, and storage. Hosting too many virtual machines on a server commonly leads to unacceptable levels of performance degradation for the virtual machines. Hosting a conservative number of virtual machines causes underutilization of the infrastructure.
Hosting considerations related to storage are not straightforward. Two factors with respect to storage infrastructures are capacity and bandwidth. The storage capacity can be allocated on demand and can be thinly provisioned to support a higher number of virtual machines. The storage bandwidth criterion is hard to predict. Various virtual machines generate a wide range of input/output workloads and bandwidth demands. The storage bandwidth is also affected by a presence or absence of caching appliances in the system. If the available storage bandwidth is known dynamically, system software can try to optimally match the demand and availability. Currently, no dynamic and reliable mechanism is known by which the system software knows how much storage bandwidth is available at a given time.
It would be desirable to implement dynamic bandwidth reporting for solid-state drives.
The invention concerns an apparatus including a memory and a controller. The memory may be configured to store data. The controller may have a plurality of tables. The controller is generally configured to process a plurality of input/output requests to read/write to/from the memory, track a plurality of statistics of the memory, index the plurality of tables with the plurality of statistics of the memory to determine a plurality of parameters, compute based on the plurality of parameters a first bandwidth consumed by the controller while servicing the memory with one or more tasks hidden from a host, and report to the host a second bandwidth of the memory that is available to the host based on the first bandwidth consumed by the controller.
Embodiments of the invention will be apparent from the following detailed description and the appended claims and drawings in which:
Embodiments of the present invention include providing dynamic bandwidth reporting for solid-state drives that may (i) estimate a memory bandwidth consumed by a controller performing servicing operations in a drive, (ii) provide a host with an ability to control how the controller gathers drive statistics, (iii) account for hypothetical scenarios in the bandwidth calculations and/or (iv) be implemented as one or more integrated circuits.
A memory bandwidth available for host usage may vary dynamically due to the nature of the media in the memory. The media generally wear down over time and usage, resulting in higher error correction efforts. The media may also be subject to continuous recycling (e.g., garbage collection) and other internal management operations that consume the memory bandwidth at varying amounts over time. The memory generally has a certain amount of media interface bandwidth available based on number of read/write channels present and interface frequency. A varying portion of the available memory bandwidth may be consumed by a memory controller for internal housekeeping purposes. By calculating how much of the memory bandwidth is consumed by the internal housekeeping (or servicing) purposes, the memory controller may report to the host an estimated amount of the memory bandwidth still remaining for the host to use.
Referring to
A signal (e.g., HOSTIO) may be exchanged between the circuit 92 and the circuit 102. The signal HOSTIO may comprise one or more host input/output signals (or components). The components of the signal HOSTIO generally include, but are not limited to, a logical address component used to access data in the circuit 100, a host command component that controls the circuit 100, a write data component that transfers write data from the circuit 92 to the circuit 102 and a read data component that transfers error corrected read data from the circuit 102 to the circuit 92.
A signal (e.g., NVMIO) may be exchanged between the circuit 102 and the circuit 104. The signal NVMIO may comprise one or more nonvolatile memory input/output signals (or components). The components of the signal NVMIO generally include, but are not limited to, a physical address component used to access data in the circuit 104, a memory command component that controls the circuit 104 (e.g., read or write commands), a write codeword component that carries error correction coded and cyclical redundancy check protected write codewords written from the circuit 102 into the circuit 104 and a read codeword component that carries the error correction coded codewords read from the circuit 104 to the circuit 102.
The circuit 92 may implement a host. The host 92 is generally operational to read data from and write data to the circuit 104 via the circuit 102. When reading or writing, the host 92 may transfer a logical address value in the signal HOSTIO to identify which set of data is to be written into or read from the circuit 104. The logical address value is generally within a logical address range of the circuit 100. The logical address value may address individual data units, such as SATA (e.g., serial-advanced technology attachment) sectors.
The circuit 100 may implement a solid-state drive (SSD). The drive 100 is generally operational to store data generated by the host 92 and return the data to the host 92. According to various embodiments, the drive 100 may comprise one or more of: nonvolatile semiconductor devices, such as NAND flash devices, phase change memory (e.g., PCM) devices, or resistive RAM (e.g., ReRAM) devices; portions of a solid-state drive having one or more nonvolatile devices; and any other volatile or nonvolatile storage media.
The circuit 102 may implement a controller. The controller 102 is generally operational to control reading from, writing to, and servicing of the circuit 104. The controller 102 may include an ability to decode the read codewords received from the circuit 104. The resulting decoded data may be presented to the host 92 via the signal HOSTIO and/or re-encoded and written back into the circuit 104 via the signal NVMIO. The controller 102 may also be configured to encode data received from the host 92 and/or decoded from the memory 104 to generate write codewords. The resulting write codewords may be presented to the memory 104 via the signal NVMIO for storage. The controller 102 generally comprises one or more integrated circuits (or chips or die) implementing the controller of one or more solid-state drives, embedded storage, or other suitable control applications.
The circuit 104 may implement a memory comprising the one or more circuits 106a-106n. The circuits 106a-106n may be implemented as memory circuits (or chips, or die, or devices). According to various embodiments, the memory 104 gene′rally comprises one or more nonvolatile semiconductor memory devices. In some embodiments, the memory 104 may include one or more volatile semiconductor memory devices. The memory 104 may be operational to store data in a volatile and/or nonvolatile condition. When data is read from or written to the memory 104, the memory 104 may access a set of memory cells (e.g., multiple bits) identified by an address (e.g., a physical address) in the signal NVMIO. The address is generally within a physical address range of the memory 104. In some embodiments, the memory 104 may be implemented as a volatile memory and/or a nonvolatile memory.
In various embodiments, the circuits 106a-106n may be implemented as NAND flash memory, NOR flash memory, flash memory using polysilicon or silicon nitride technology-based charge storage cells, two-dimensional or three-dimensional technology-based nonvolatile memory, ferromagnetic memory, phase-change memory, racetrack memory, stacked memory, resistive random access memory, magnetic random access memory and similar types of memory devices and/or storage media. However, other nonvolatile memory technologies may be implemented to meet the criteria of a particular application. In some embodiments, the circuits 106a-106n may be implemented as volatile memory circuits and/or nonvolatile memory circuits.
As part of controlling the memory 104, the controller 102 may be configured to process a plurality of input/output requests to read/write to/from the memory 104. The controller 102 may also track multiple statistics of the memory 104, index multiple tables with the statistics of the memory 104 to determine multiple parameters, utilize the multiple parameters to compute a service bandwidth consumed by the controller 102 while servicing the memory 104 with one or more tasks hidden from the host 92, and report to the host 92 an estimated bandwidth of the memory 104 that is available to the host 92 based on the service bandwidth consumed by the controller 102. The estimated bandwidth reported to the host 92 generally indicates an amount of data that may be transferred per second between the host 92 and the controller 102 at one or more latencies. The estimated bandwidth may be reported as a read bandwidth available to the host 92 and a write bandwidth available to the host 92.
In various embodiments, the controller 102 may be configured to report the estimated bandwidth to the host 92 upon the occurrence of one or more conditions. The conditions may include, but are not limited to, a dynamic event, a periodic event, an inquiry from the host 92, a power-on event, a beginning of a recycling (e.g., garbage collection) task, and/or an end of the recycling task. Other conditions may be implemented to meet the design criteria of a particular application.
In some embodiments, the controller 102 may receive one or more instructions from the host 92. The controller 102 may control how one or more of the statistics of the memory 104 are tracked based on the received instructions. In some embodiments, the controller 102 may receive a hypothetical consumption of additional bandwidth by the host 92. The controller 102 may update the estimated bandwidth reported to the host 92 based on the hypothetical consumption.
The statistics (or states) of the memory 104 generally comprise a total amount of time that the memory 104 has been powered, a total number of program/erase cycles that have been performed, a current over-provisioning amount of storage space available, and/or an amount of free storage space currently available. The controller 102 may estimate one or more of the statistics of the memory 104 based on operations that modify a size of user data being transferred between the memory 104 and the controller 102. The data-size modifying operations may include, but are not limited to, a code rate used in an error correction code operation, a compression operation, and/or a trim operation. Other operations may be implemented to meet the design criteria of a particular application.
Referring to
The circuit 110 may implement a host interface circuit. The host interface 110 is generally operational to provide communication with the host 92 via the signal HOSTIO. Other signals may be implemented between the host 92 and host interface 110 to meet the criteria of a particular application. In various embodiments, the host interface 110 may process multiple access operations to/from the host 92.
The circuit 112 may implement a nonvolatile memory (e.g., flash) interface circuit. The memory interface 112 is generally operational to provide communication with the memory 104 via the signal NVMIO. Other signals may be implemented between the memory 104 and memory interface 112 to meet the design criteria of a particular application. In various embodiments, the memory interface 112 may process multiple read/write operations to/from the memory 104.
The circuit 114 may implement a control circuit. The control circuit 114 is generally operational to control writing data received from the host 92 into the memory 104, reading data from the memory 104 for transfer to the host 92, servicing the memory 104, and calculating the estimated bandwidth of the memory 104 available to the host 92. The control circuit 114 generally communicates with the memory 104 via the memory interface 112. The host 92 may communicate with the control circuit 114 via the host interface 110.
The circuit 116 may implement a processor. The processor 116 is generally operational to command and/or assist with the multiple read/write requests and to control one or more reference voltages used in the memory 104 to read data (or codewords). In various embodiments, the processor 116 may be operational to calculate the service bandwidth consumed while servicing the memory 104. The processor 116 may also be operational to calculate the estimated bandwidth of the memory 104 available to the host 92. The service bandwidth may be transferred to the host 92 through the host interface 110.
The circuit 118 may implement one or more lookup tables (LUTs). The LUTs 118 may be operational to store data that transforms the statistics of the memory 104 into the parameters used by the processor 116 to calculate the service bandwidth and the estimated bandwidth. In various embodiments, each LUT 118 may be stored separately. In other embodiments, one or more of the LUTs 118 may be merged together.
The circuit 120 may implement a read/write data path. The data path 120 may be operational to transfer data between the memory 104 and the host 92. The transfers may utilize the host interface 110 to communicate with the host 92, and the memory interface 112 to communicate with the memory 104.
The circuit 122 may implement a cache circuit. The cache 122 may be operational to cache data written to and/or read from the memory 104. In various embodiments, the cache 122 may be arranged as a single layer cache for user data. From time to time, data in the cache 122 may be offloaded to the memory 104. The cache offload operation may consume a significant amount of bandwidth between the controller 102 and the memory 104. The cache 122 may implement a variety of write policies, set associations, and/or replacement policies. The write policies may include, but are not limited to, write-through and write-back (or write-behind). The replacement policies generally include least recently used most recently used, least-frequently used, random replacement, segmented least-recently used and/or pseudo-least-recently used. Other replacement policies may be implemented to meet the design criteria of a particular application. The set associations generally include, but are not limited to, direct mapped, 2-way set associative and/or n-way set associative.
The circuit 124 may implement a flash translation layer (FTL) circuit. The flash translation layer 124 may be operational to perform a logical address to physical address translation using map tables and other related data structures. Since each write generally happens at a new location in the memory 104, the map tables and related data structures may constantly change. The changed or dirty portions of the maps and/or data structures may be periodically written to the memory 104 for nonvolatile storage. The writes generally consume additional bandwidth between the controller 102 and the memory 104. The nonvolatile storage of the maps and data structures may provide robust and fast drive recovery in case of a surprise power failure.
The circuit 126 may implement a recycle circuit. The recycle circuit 126 may be operational to implement a recycling (e.g., garbage collection) operation. The recycling operation may consume a significant amount of the bandwidth between the controller 102 and the memory 104. Before a block is erased, any valid user data present in that block may be moved to another block by the recycling operation. Each page in the memory 104 is erased before new data may be written (or programmed). The erase operation may be performed at a block level, with each block containing many pages. Such recycling of the blocks may be performed at regular intervals to create free space. The rate of the recycling operation, and in turn, an amount of the memory bandwidth consumed generally depends upon an amount of over-provisioned capacity. Higher over-provisioned capacity generally results in a lower garbage collection rate and so a lower memory bandwidth may be consumed by the recycling operation.
The circuit 128 may represent other operations that impact the service bandwidth of the memory 104. For example, some solid-state drive architectures may compress user data. The data compression generally increases the effective over-provisioning level as the user data consumes less space in the memory 104. An actual level of the data compression may depend upon the entropy of the user data being written. The resulting effective over-provisioning level may be a dynamic and complex variable that may have a significant impact on the estimated bandwidth available to the host 92.
Referring to
Referring to
Referring to
The cache, the FTL, the recycling, and other functions and factors together may take up significant amounts of the memory bandwidth in servicing the memory 104. The memory bandwidth consumed may not remain fixed/static over time. An estimated bandwidth (B/W) available for the host 92 to use may be provided by formula 1 as follows:
Host B/W=Flash B/W−(Recycling B/W+FTL B/W+Cache offload B/W+Miscellaneous B/W) (1)
The flash B/W value may be a fixed value of the memory 104 and is generally based on the design of the memory 104. The recycling B/W value may be the service bandwidth consumed by the garbage collection operations. The FTL B/W value may be the service bandwidth consumed by the flash translation layer operations. The cache offload B/W value may be an average service bandwidth consumed while offloading data from the cache 122 to the memory 104. The miscellaneous B/W value may be a sum of other operations that increase the service bandwidth consumed by the controller 102.
The controller 102 may compute the individual terms in formula 1. The computations may be complex and in various embodiments, some approximation may be employed. Some of the factors involved may be programmed in the LUTs 118 as characterization tables. The controller 102 may keep track of the power-on hours value, the program/erase cycle count, and the current over-provisioning level. The parameters may be used as an index in the characterization tables stored in the LUTs 118 to help compute the memory bandwidth used by the internal service functions in the controller 102. Once the service bandwidth is computed, the estimated bandwidth of the memory 104 available to the host 92 may be calculated and reported.
Several (e.g., three) groups may be used in the bandwidth reporting calculations. One group may be the current bandwidth calculations that calculate the current bandwidth being used. Another group may be the remaining available bandwidth that are computed using a combination of one or more selected formulas. Yet another group may be scenario planning bandwidth calculations used in conjunction with the current bandwidth calculation group and the remaining available bandwidth group to estimate bandwidth requirements when a new workload is added.
In general, the host 92 may be interested in the total bandwidth, the current bandwidth, what the bandwidth might be if a new workload is applied, and/or what the new bandwidth may be if a workload is removed. In various embodiments, the estimated bandwidth report to the host 92 may be characterized as an “adjusted” bandwidth and a “raw” bandwidth. If the raw bandwidth is reported, the host 92 may infer the adjusted bandwidth from raw bandwidth. Consider an example when 4,000 bytes (4K) of data is read from the memory 104 by the host 92. The amount of data read from memory 104 to retrieve the 4K of data may vary based on the error correction code rate and/or how many codewords the 4K of data spans. A count of the codewords and respective sizes generally represents the raw bandwidth consumed to read the 4K of data.
Determining the current bandwidth consumed on the drive 100 may be accomplished by collecting bandwidth on the drive 100 over a specified interval. In various embodiments, the interval may be a configuration parameter. In still further embodiments, the interval may be set by the host 92. In still further embodiments, the collection interval may be determined by a sampling interval of the host 92. In various embodiments, the consumed bandwidth information reported generally consists of a read bandwidth, a write bandwidth and a bandwidth consumed by internal operations over the sampling interval for the entire drive 100. Internal operations may include, but are not limited to, the garbage collection, wear leveling, read disturb handling, retention management and maintenance of FTL and media management structures stored on the media.
In various embodiments, the bandwidth consumption may be tracked in both the adjusted and the raw form. The adjusted form of the bandwidth generally consists of the bandwidth as observed by the host 92. The raw bandwidth may consist of actual resources used on the controller 102. Raw data may be tracked to simplify remaining available bandwidth calculations.
The reported bandwidth may be made corresponding to one or more applications executing on the host 92. An identification of bandwidths associated with executing applications is generally based on the regions of storage associated with the applications. In such cases, the utilized storage may be associated with each application. In some embodiments, the associations may be provided from the host 92, as to what application owns what region. In other embodiments, the host 92 may tag requests as being from particular applications.
In various embodiments, the effective over-provisioning may also be reported. The effective over-provisioning may be defined as the percentage of unused space on the drive 100 relative to a formatted capacity of the drive 100 and may consider spare capacity plus trimmed space, unused space, and space containing invalid data. The effective over-provisioning (OP) may be approximated by formula 2 as follows:
Where: the raw capacity may be a raw capacity of the memory 104; the formatted capacity may be a capacity of the drive 100 reported to the host 92; the trimmed data may be data the host 92 has reported to the drive 100 that is no longer in use by the host 92; the average entropy may be an average compressibility of the data across all data stored on the drive 100, if compression is employed by the controller 102; the FTL overhead may be an amount of space on the memory 104 occupied by the FTL structures and statistics; the average code rate may be an average error correction code rate used for data stored on the drive 100; and the average FTL code rate is generally an average error correction code rate used for the FTL structures and statistics. In various embodiments, the effective over-provisioning calculation may take into account overhead for outer codes used to protect against block, plane and/or die failures.
The remaining available bandwidth (BW) computation may be provided by formula 3 as follows:
Remaining Available BW=Total Available BW−Current BW (3)
The remaining available bandwidth is generally an analytical calculation based on a number of factors and inputs. The remaining raw bandwidth and resources may be calculated by subtracting the current raw bandwidth from a total raw bandwidth, a raw flash bandwidth remaining for read and write, a raw flash bus bandwidth remaining, a raw central processor unit (CPU) resources remaining, a raw buffer space and bandwidth remaining, a raw internal bus bandwidth remaining, and a raw host interface bandwidth remaining. The remainder generally represents the remaining resources and bandwidth on the controller 102. Thereafter, based on controller utilization and resources, the following statistics may be use to determine the remaining bandwidth based on a selected workload: CPU utilization; effective over-provisioning (used to compute remaining the write bandwidth); a speed at which free memory space credit is earned may also be considered since distributions may vary; the average code rate and the program/erase cycles that may impact the read bandwidth; and one or more application performance profiles that have been collected at various effective over-provisioning levels and capacities. The profiles may be stored in a table. The host 92 may identify which applications are using what regions along with corresponding profiles.
Various methods may be implemented for calculating and/or estimating the available drive bandwidth. For example, various representative workloads may be run against the drive 100 and the available bandwidths and latencies for the workloads are recorded. The utilization by workload may be scaled from 0% to 100% and subsequently stored in a workload table. Scenario planning may be derived from taking the remaining bandwidth and indexing the workload table to see the effect. The host 92 may find that adding a particular workload could determinately impact current workloads running on the drive 100. The host 92 may also consider a scenario inquiry where a given workload may be moved to determine if a positive impact is provided to other workloads.
Referring to
In the step 172, the controller 102 (e.g., the control circuit 114 and/or the memory interface 112) may process a plurality of read/write operations to/from the memory 104. While processing the read/write operations, the controller 102 may monitor the drive 100 for the occurrence of one or more triggering events in the step 174. If no triggering events (or conditions) are detected, the controller 102 may continue processing the read/write (or input/output) requests in the step 172. The triggering events generally include one or more dynamic events, one or more periodic events, one or more inquiries from the host 92, each power-on event, each beginning of a garbage collection task, and/or each end of the garbage collection task. Other conditions may be implemented to meet the design criteria of a particular application.
When a triggering event is detected, the controller 102 may update the tracking of the one or more statistics of the drive 100 in the step 176. Based on the updated statistics, the controller 102 may compute parameters corresponding to the statistics in the step 178. In the step 180, a service bandwidth consumed by the controller 102 based on the parameters may be computed by the controller 102. Once the service bandwidth is known, the controller 102 may compute the estimated bandwidth and latencies available to the host 92 in the step 182.
A check may be performed in decision step 184 to determine if the host 92 has provided a hypothetical (or “what if”) scenario to the controller 102. If the host 92 has presented a hypothetical condition for the controller 102 to consider, the controller 102 may update the estimated bandwidth and the latencies in the step 186. Once the estimated bandwidth and the latencies have been updated, or if no hypothetical case was received, the controller 102 generally reports the estimated bandwidth and the latencies in the step 188 to the host 92.
In some embodiments, the host 92 may check for the hypothetical effects of additional capacity allocation on bandwidth availability in the drive 100 in current use before an actual allocation of the additional capacity is made. The controller 102 may report back what the estimated bandwidth might be based on the new potential allocation. In various embodiments, the “what if” analysis may include information about additional resource utilizations, including added read/write workloads, to assess the resulting performance of the drive 100. Based on the feedback in the report, the host 92 may take appropriate action to allocate additional capacity from the drive 100, allocate some of the additional capacity from the drive 100, or allocate none of the additional capacity from the drive 100. The dynamic bandwidth reporting feature generally enables such analysis for the host 92 that may be useful for optimal utilization of the storage infrastructure.
Once the bandwidth computations are achieved, the estimated bandwidth of the memory 104 available to the host 92 may be reported to the host 92. In various embodiments, the reporting may be implemented as a vendor specific log page generated by the controller 102 and readable by the host 92. Various host interface protocols, such as nonvolatile memory host controller interface specification express (NVMe), serial attached small computer system interface (SAS), and/or serial-advanced technology attachment (SATA), generally allow the host 92 to read the vendor unique log pages. An example of a vendor unique log page report entry may be provided in Table I as follows:
The value N:0 in the left field generally represents a size of a log entry used for reporting available bandwidth (e.g., N=31 for a 32 bit log entry and may be divided into 16 bits for bandwidth and 16 bits for latency). The value in the middle field may present the estimated bandwidth of the memory 104 that is available to the host 92. The estimated bandwidth may be expressed in units of megabits per second (MBPS) The value in the right field may present the estimated storage latency that the host 92 may expect. The storage latency may be expressed in units of microseconds. Other vendor specific log pages and/or reporting mechanisms may be implemented to meet the design criteria of a particular application.
Referring to
The controller 102 may report the estimated storage bandwidth on demand of the host 92, at periodically events and/or at certain trigger events (or points). Examples of the triggering events may include, but are not limited to, time-based events (e.g., every ten seconds, every minute, every hour, etc.). Examples of non-periodic events may include a power-on condition, and internal events such as a start of garbage collection, an end of garbage collection, and/or a start of a cache offload. Other events may be implemented to meet the design criteria of a particular application.
In the step 202, the controller 102 may receive trigger information from the host 92. The processor 116 may be configured in the step 204 to monitor for the triggering events per the trigger information received from the host 92. In the step 206, the controller 102 generally monitors the drive 100 for occurrences of any one or more of the triggering events (e.g., the step 174 in
Referring to
The controller 102 may receive tracking information from the host 92 in the step 222. The processor 116 may be configured in the step 224 to track the statistics of the memory 104 per the tracking information received from the host 92. In the step 226, the controller 102 generally tracks the statistics of the memory 104 in accordance with the tracking information (e.g., the step 176 in
The statistics of the memory 104 that are tracked may be predefined for the controller 102 (e.g., pre-programmed at manufacturing time). How the statistics are tracked may be programmable by the host 92. For example, the controller 102 may be measuring the service bandwidth consumed for cache offloads over some period of time. Consider a burst of activity by a virtual machine executing on the host 92. The burst may result in a high rate of cache offloads during a window. If the measuring period for the cache offload is long compared with the burst window, the burst may cause a small average increase in the calculated service bandwidth consumed by the controller 102 due to the cache offloads. If the measuring period is about the same length as the burst window, the calculated service bandwidth consumed by the controller 102 may increase significantly during the burst. In some embodiments, the host 92 may want to know the average estimated bandwidth available based on small measuring periods. In other embodiments, the host 92 may want to know the average estimated bandwidth available based on long measuring periods. Different hosts 92 may program the measuring period (how to gather the cache offload statistics) into the controller 102 to meet the design criteria of a particular application.
Referring to
In the step 242, the controller 102 may estimate elements of the service bandwidth consumption based on operations performed within the drive 100. The operations may include, but are not limited to, the code rate used in the error correction code operation, the compression operation, and the trim operation. The controller 102 may measure some statistics of the memory 104 directly in the step 244. The measured statistics may include, but are not limited to, the total amount of time that the memory 104 has been, the total number of program/erase cycles that have been performed, the amount of over-provisioning currently available, and the amount of free space currently available.
Other usages of the bandwidth monitoring may be included in the controller 102 and/or the host 92. For example, in the step 246, the controller 102 or host 92 may store snapshots of the reported storage bandwidth over time. The snapshots may be subsequently used to analyze how the drive 100 is behaving and fine tune the performance and/or develop better techniques to utilize the bandwidth.
The functions and structures illustrated in the diagrams of
Embodiments of the present invention may also be implemented in one or more of ASICs (application specific integrated circuits), FPGAs (field programmable gate arrays), PLDs (programmable logic devices), CPLDs (complex programmable logic device), sea-of-gates, ASSPs (application specific standard products), and integrated circuits. The circuitry may be implemented based on one or more hardware description languages. Embodiments of the present invention may be utilized in connection with flash memory, nonvolatile memory, random access memory, read-only memory, magnetic disks, floppy disks, optical disks such as DVDs and DVD RAM, magneto-optical disks and/or distributed storage systems.
The terms “may” and “generally” when used herein in conjunction with “is(are)” and verbs are meant to communicate the intention that the description is exemplary and believed to be broad enough to encompass both the specific examples presented in the disclosure as well as alternative examples that could be derived based on the disclosure. The terms “may” and “generally” as used herein should not be construed to necessarily imply the desirability or possibility of omitting a corresponding element. As used herein, the term “simultaneously” is meant to describe events that share some common time period but the term is not meant to be limited to events that begin at the same point in time, end at the same point in time, or have the same duration.
While the invention has been particularly shown and described with reference to embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the scope of the invention.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8826270 | Lewis et al. | Sep 2014 | B1 |
| 8830716 | Feekes | Sep 2014 | B2 |
| 8848577 | Saund et al. | Sep 2014 | B2 |
| 20130080699 | Shigeta | Mar 2013 | A1 |
| 20130173843 | Balakrishnan et al. | Jul 2013 | A1 |
| 20130297894 | Cohen | Nov 2013 | A1 |
| 20140095696 | Sala | Apr 2014 | A1 |
| 20140101379 | Tomlin | Apr 2014 | A1 |
| 20140337598 | Rao | Nov 2014 | A1 |
| 20140365719 | Kuzmin et al. | Dec 2014 | A1 |
| 20160210060 | Dreyer | Jul 2016 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20170277444 A1 | Sep 2017 | US |
