The present application contains subject matter related to U.S. patent application Ser. No. 13/926,900, filed Jun. 25, 2013, now U.S. Pat. No. 9,244,519, entitled “STORAGE CONTROL SYSTEM WITH POWER THROTTLING MECHANISM AND METHOD OF OPERATION THEREOF”. The subject matter thereof is incorporated herein by reference thereto.
The present invention relates generally to a storage control system and more particularly to a system for power throttling.
Data storage, often called storage or memory, refers to computer components and recording media that retain digital data. Data storage is a core function and fundamental component of consumer and industrial electronics, especially devices such as computers, televisions, cellular phones, mobile devices, and digital video cameras.
Recently, forms of long-term storage other than electromechanical hard disks have become feasible for use in computers. NOT-AND (NAND) flash is one form of non-volatile memory used in solid-state storage devices. The memory cells are arranged in typical row and column fashion with circuitry for accessing individual cells. The memory transistors of those cells are placed to store an analog value that can be interpreted to hold two logical states in the case of Single Level Cell (SLC) or more than two logical states in the case of Multi Level Cell (MLC).
A flash memory cell is light in weight, occupies very little space, and consumes less power than electromechanical disk drives. Construction of a storage system with this type of memory allows for much higher bandwidths and input/output operations per second (IOPS) than typical electromechanical disk drives. More importantly, it is especially rugged and can operate at a much high temperature range. It will withstand without adverse effects repeated drops, each of which would destroy a typical electromechanical hard disk drive. A problem exhibited by flash memory is that it tends to have a limited life in use.
Thus, a need still remains for better data management devices. In view of the increasing demand for data management devices, it is increasingly critical that answers be found to these problems. In view of the ever-increasing commercial competitive pressures, along with growing consumer expectations and the diminishing opportunities for meaningful product differentiation in the marketplace, it is critical that answers be found for these problems. Additionally, the need to reduce costs, improve efficiencies and performance, and meet competitive pressures adds an even greater urgency to the critical necessity for finding answers to these problems.
Solutions to these problems have been long sought but prior developments have not taught or suggested any solutions and, thus, solutions to these problems have long eluded those skilled in the art.
The present invention provides a method of operation of a storage control system, including: receiving a host command from a host system; reading a current value of an electrical power supplied by the host system in response to the host command; and scheduling new operations to be executed in parallel in non-volatile memory devices, the new operations are scheduled when the current value of the electrical power does not exceed a power limit.
The present invention provides a storage control system, including: a host interface module for receiving a host command from a host system; a power measurement module, coupled to the host interface module, for reading a current value of an electrical power supplied by the host system in response to the host command; and a schedule module, coupled to the power measurement module, for scheduling new operations to be executed in parallel in non-volatile memory devices, the new operations are scheduled when the current value of the electrical power does not exceed a power limit.
Certain embodiments of the invention have other steps or elements in addition to or in place of those mentioned above. The steps or elements will become apparent to those skilled in the art from a reading of the following detailed description when taken with reference to the accompanying drawings.
The following embodiments are described in sufficient detail to enable those skilled in the art to make and use the invention. It is to be understood that other embodiments would be evident based on the present disclosure, and that system, process, or mechanical changes may be made without departing from the scope of the present invention.
In the following description, numerous specific details are given to provide a thorough understanding of the invention. However, it will be apparent that the invention may be practiced without these specific details. In order to avoid obscuring the present invention, some well-known circuits, system configurations, and process steps are not disclosed in detail.
The drawings showing embodiments of the system are semi-diagrammatic and not to scale and, particularly, some of the dimensions are for the clarity of presentation and are shown exaggerated in the drawing FIGs.
Where multiple embodiments are disclosed and described having some features in common, for clarity and ease of illustration, description, and comprehension thereof, similar and like features one to another will ordinarily be described with similar reference numerals. The embodiments have been numbered first embodiment, second embodiment, etc. as a matter of descriptive convenience and are not intended to have any other significance or provide limitations for the present invention.
The term “module” referred to herein can include software, hardware, or a combination thereof in the present invention in accordance with the context in which the term is used. For example, the software can be machine code, firmware, embedded code, and application software. Also for example, the hardware can be circuitry, processor, computer, integrated circuit, integrated circuit cores, a microelectromechanical system (MEMS), passive devices, environmental sensors including temperature sensors, or a combination thereof.
The term “bit error rate” (BER) referred to herein is defined as a number of incorrect bits in a data stream stored in a memory device including NAND. The BER can typically be detected within a code word protected by error correction code (ECC). The term “erase block” referred to herein is defined as a group of pages, which is the smallest number of pages that are erased at one time.
The term “error correction code” (ECC) referred to herein is defined as parity data generated over a set of data grouped into a code word. The term “code word” referred to herein is defined as a group of data bytes covered by a single of multiple ECC parity words. The term “power slope” referred to herein is defined as a value derived from making multiple electrical current/power measurements on a drive changes in its power usage. The term “page” referred to herein is defined as a memory component within an erase bock that is programmed as an individual unit. The page is a smallest group of data bytes that are read from or written to in an erase block.
The term “program/erase cycle” (P/E cycle) referred to herein is defined as a base level operation of how data is replaced within an erase block. For example, a memory device including NAND and other memory types can have a limited number of useful P/E cycles. The term “solid state disk drive” (SSD) referred to herein is defined as a type of devices that use non-volatile memories. For example, a drive or an SSD is a type of devices that use a non-volatile memory including NAND flash as a storage medium.
The term “point of load” (POL) referred to herein is defined as a regulator, which creates a load's needed voltage located physically near the load, as opposed to a single, larger regulator that supplies power to all subsystems or loads. The term “single ended” referred to herein is defined as data transferred on one edge of a clock signal. The term “double data rate” referred to herein is defined as data transferred on both rising and falling edges of a clock signal. The term “real time measurements” referred to herein is defined as data collected from hardware, software, or a combination thereof. The real time measurements represent current states of operation and characteristics of a drive.
The term “open loop” referred to herein is defined as run time adjustments made based on pre-formed tables and operation counts, without monitoring hardware current or power. The term “closed loop” referred to herein is defined as run time adjustments made by monitoring operations dynamically as a drive runs. The term “FIFO” referred to herein is defined as a first in first out memory block. The term “ADC” referred to herein is defined as an analog to digital converter. The term “POLL” referred to herein is defined as a sampling used in software to monitor a status of an event.
Currently, power throttling is performed in a very static way. A typical drive is run and the power is measure for a given performance and workload. From a static power measurement, firmware levels are set to limit a number of outstanding operations that can be executed at a given time. This method does not take into account differences in powers consumed between different drives, an amount of time a flash takes to execute a given operation (which changes over the life of a drive), or controller limitations or execution of commands.
In general, predetermined limits are set at design time for firmware to schedule a given number of operations. The current method runs into real difficulties when recycling, wear leveling, general housekeeping, or other functions run in the background change the load on the NAND. The current method also does not take into account the effects of temperature or NAND age when setting these fixed throttling limits.
More dramatically than hard disk drives, an amount of power that an SSD consumes varies with an amount of host (and internal) activity. This power difference in many cases exceeds two times an idle current for the drive. Additionally, the power usage can be very abrupt and cause power spikes that can create supply voltage transients that can overwhelm a host environment or otherwise exceed the regulation capability of the host power system and take other subsystems offline.
Referring now to
The storage control system 100 includes drive level components. The drive level components includes a section for a main power supply unit 102 for providing power supplies to a main memory controller 104 and non-volatile memory devices 106. The main memory controller 104 including a NAND controller includes a processor 108, device controllers (not shown), and memory controllers (not shown). The processor 108 including a central processing unit (CPU) is used to execute a firmware 110.
The device controllers interface with and control the non-volatile memory devices 106 including NAND flash. Although the embodiments described herein refer to using NAND for the non-volatile memory devices 106, it is understood that the embodiments are not limited to using NAND as a memory storage device, which can be monitored and controlled by the main memory controller 104. For example, the non-volatile memory devices 106 include but are not limited to Magnetoresistive random-access memory (MRAM), Ferroelectric RAM (FRAM), and phase-change memory (PCM).
The memory controllers control and interface with a buffer block 112, which is a memory device. For example, in some cases, the buffer block 112 is an external block of memory for tabling and storing data or an array of NAND memory devices. Also for example, the buffer block 112 includes memory and data buffers. Further, for example, the buffer block 112 can include dynamic random access memory (DRAM) or any other volatile memories.
The storage control system 100 includes a number of channels 114 with each of the channels 114 having a number of the non-volatile memory devices 106 including NAND flash devices behind it. There are a number of ways of distributing the data across the channels 114. For example, the data can be distributed using a simple redundant array of independent disks (RAID) 0 stripe. For example,
The main memory controller 104 includes an ECC encoder 116 and an ECC decoder 118. The ECC encoder 116 generates ECC parity data for a set of data grouped into a code word to be stored in the non-volatile memory devices 106. The ECC decoder 118 receives and checks ECC parity data for data from the non-volatile memory devices 106. The main memory controller 104 interfaces with a host system 120.
In this configuration, there is no power feedback from any of the components. The main power supply unit 102 is a self-contained unit that generates and provides power for all of the components of the drive based on a main host power input from the host system 120. The main power supply unit 102 provides a core voltage 122 and an I/O voltage 124 to the main memory controller 104 and the non-volatile memory devices 106.
For illustration purposes, only the powers from the main power supply unit 102 are shown, although it is understood that there can be other power signals in the storage control system 100. For example, the storage control system 100 can include power feedback signals from any of the components and most importantly a bank of the non-volatile memory devices 106 including NAND memory devices.
Referring now to
The control unit 202 can be implemented in a number of different manners. For example, the control unit 202 can be a processor, an embedded processor, a microprocessor, a hardware control logic, a hardware finite state machine (FSM), a digital signal processor (DSP), or a combination thereof.
The control interface 210 can be used for communication between the control unit 202 and other functional units in the main memory controller 104. The control interface 210 can also be used for communication that is external to the main memory controller 104.
The control interface 210 can receive information from the other functional units or from external sources, or can transmit information to the other functional units or to external destinations. The external sources and the external destinations refer to sources and destinations external to the main memory controller 104.
The control interface 210 can be implemented in different ways and can include different implementations depending on which functional units or external units are being interfaced with the control interface 210. For example, the control interface 210 can be implemented with a dedicated hardware including an application-specific integrated circuit (ASIC), a configurable hardware including a field-programmable gate array (FPGA), a discrete electronic hardware, or a combination thereof.
The storage unit 204 can include both hardware and the software 212. For example, the software 212 can include control firmware. The storage unit 204 can include a volatile memory, a nonvolatile memory, an internal memory, an external memory, or a combination thereof. For example, the storage unit 204 can be a nonvolatile storage such as non-volatile random access memory (NVRAM), Flash memory, disk storage, or a volatile storage such as static random access memory (SRAM).
The storage unit 204 can include a storage interface 214. The storage interface 214 can also be used for communication that is external to the main memory controller 104. The storage interface 214 can receive information from the other functional units or from external sources, or can transmit information to the other functional units or to external destinations. The external sources and the external destinations refer to sources and destinations external to the main memory controller 104.
The storage interface 214 can include different implementations depending on which functional units or external units are being interfaced with the storage unit 204. The storage interface 214 can be implemented with technologies and techniques similar to the implementation of the control interface 210.
The memory interface unit 206 can enable external communication to and from the main memory controller 104. For example, the memory interface unit 206 can permit the main memory controller 104 to communicate with the non-volatile memory devices 106 of
The memory interface unit 206 can include a memory interface 216. The memory interface 216 can be used for communication between the memory interface unit 206 and other functional units in the main memory controller 104. The memory interface 216 can receive information from the other functional units or can transmit information to the other functional units.
The memory interface 216 can include different implementations depending on which functional units are being interfaced with the memory interface unit 206. The memory interface 216 can be implemented with technologies and techniques similar to the implementation of the control interface 210.
The host interface unit 208 allows the host system 120 of
The control unit 202 can operate the host interface unit 208 to send control or status information generated by the main memory controller 104 to the host system 120. The control unit 202 can also execute the software 212 for the other functions of the main memory controller 104. The control unit 202 can further execute the software 212 for interaction with the non-volatile memory devices 106 via the memory interface unit 206.
The functional units in the main memory controller 104 can work individually and independently of the other functional units. For illustrative purposes, the main memory controller 104 is described by operation of the main memory controller 104 with the host system 120 and the non-volatile memory devices 106. It is understood that the main memory controller 104, the host system 120, and the non-volatile memory devices 106 can operate any of the modules and functions of the main memory controller 104.
Referring now to
As an SSD goes through different phases of operations including recycling, wear leveling, spare pool and over provisioning resource management, and differing host workloads, the drive can require or utilize differing amounts of power. Most host systems restrict an amount of current, including average and peak currents, which a drive is allowed to use. The embodiments described herein outlines additions and modifications to controller architectures to allow the drive to dynamically adjust its internal operations to limit or throttle average and instantaneous power draws.
There are two methods described herein to construct the dynamic power control mechanism or dynamic current/power throttling for the main memory controller 104. A first method is to employ a set of external circuitry that is added to the main memory controller 104 that allows the firmware 110 of
Any combination of architectures shown by
A firmware version of an implementation of the dynamic power control mechanism includes a number of different options to use the power information. A first option can include a simple sample method that uses an instantaneous electrical current level to determine how many parallel operations to queue up. To prevent a risk associated with possibility of having an overshoot of an electrical current level target, the embodiments described herein employ a running slope measurement to estimate where an electrical current will settle out given a current workload.
Power sampling can be done based on a time trigger or an operational trigger when flash controller jobs are submitted to flash controllers or the main memory controller 104. An electrical current drawn by the non-volatile memory devices 106 and a controller board in general can be translated to a total power consumed by the SSD.
The storage control system 100 of
The current-to-voltage converter 306 generates a current-sense voltage signal 308 and sends it to the main memory controller 104. An increase of the current-sense voltage signal 308 indicates an increase of an electrical power 310 of the storage control system 100. The electrical power 310 represents a total power drawn or consumed by the non-volatile memory devices 106, the main memory controller 104, and other drive level components 312 of the storage control system 100. The electrical power 310 indicates power consumed by the drive level components through different phases of operations in the drive.
The main memory controller 104 monitors the current-sense voltage signal 308 to determine how many parallel operations or controller commands 314 to queue up. The controller commands 314 are control information generated by the main memory controller 104. The controller commands 314 are for storing, accessing, or managing data in the non-volatile memory devices 106.
The current sensor 302 also provides the core voltage 122 to the non-volatile memory devices 106, the main memory controller 104, and any of the drive level components 312. The core voltage 122 can be an analog voltage that is linearly proportional to the electrical current provided by the main power supply unit 102. The core voltage 122 can be a system-level supply or a power supply input to the main memory controller 104 and a number of the non-volatile memory devices 106 including a NAND media array.
Referring now to
Two inputs, an under-current signal 402 and an over-current signal 404, shown in
Since the non-volatile memory devices 106 (or other storage media) do not have an effective way to pause execution of the controller commands 314, the firmware or hardware can use the under-current signal 402 and the over-current signal 404, to determine when the next set of the controller commands 314. The next set of the controller commands 314 can be submitted to the device controllers for controlling the non-volatile memory devices 106. The under-current signal 402 and the over-current signal 404 are external to the main memory controller 104. As a result, a clumping effect of the controller commands 314, which additively cause electrical current spikes, is significantly reduced or eliminated.
As some operations draw more electrical current or power than other operations, the firmware can select, from a queue of the controller commands 314 to be executed, which of the controller commands 314 to group and which of the controller commands 314 to delay. In some cases, just a number of the controller commands 314 are required to be limited for execution.
The firmware can also use the time it takes to transition from under current to over current to determine a rate of change 406 in electrical current requirements for the non-volatile memory devices 106 or media. The firmware can therefore estimate a grouping of a future stream of the controller commands 314. The transition from under current to over current is determined when the under-current signal 402 is asserted to an active state and the over-current signal 404 is subsequently asserted to an active state.
A granularity for power/current compensation allows the SSD or the main memory controller 104 to control the electrical power 310 consumed by the non-volatile memory devices 106 at an operation of a command level versus a sub-operation level. For example, some power/current spikes that occur within a given operation are on the order of 10s of microseconds. Also for example, some power/current spikes occur when a large number of operations are executed in an overlapped or parallel operation and these are on the order of 100s of microseconds to milliseconds of time.
The command level is a method for performing an operation on the non-volatile memory devices 106. For example, the command level including a command to the non-volatile memory devices 106 can be an outstanding erase, a page program, or a read.
These commands can be broken up into pieces at the sub-operation level. For example, the read command can have two parts or sub-operations. One part is instructing the non-volatile memory devices 106 to read values that are stored in the non-volatile memory devices 106 and put them into a shift register. The other part is transferring data out of the shift register in the non-volatile memory devices 106 to the main memory controller 104.
Also for example, and the page program can be split up into two phases or sub-operations. The first phase is transferring data into a shift register in the non-volatile memory devices 106. The second phase is actually programming the non-volatile memory devices 106 with the data stored in the shift register.
The storage control system 100 of
The under-current level comparator 408 and the over-current level comparator 410 compare the current-sense voltage signal 308 to an under-current voltage level 412 and an over-current voltage level 414 to generate the under-current signal 402 and the over-current signal 404, respectively. The under-current signal 402 and the over-current signal 404 are asserted to an active state when the current-sense voltage signal 308 is below and above the under-current voltage level 412 and the over-current voltage level 414, respectively.
The under-current voltage level 412 and the over-current voltage level 414 are the predetermined reference voltage levels. For example, each of the under-current voltage level 412 and the over-current voltage level 414 can be implemented with a voltage divider using a pair of resistors connected together in series, where one end of one of the resistors is connected to power and one end of another of the resistors is connected to ground.
The current sensor 302 also provides the core voltage 122 to the non-volatile memory devices 106. The core voltage 122 is supplied by the main power supply unit 102.
Referring now to
The firmware and the hardware in the main memory controller 104 are implemented to affect input/output (I/O) scheduling of the non-volatile memory devices 106 of
When the average current 502 and the peak current 504 exceed the configurable thresholds, a clipping event occurs. The clipping event refers to a method by which parallel I/O operations or the controller commands 314 are reduced or limited to a configurable maximum value. The hardware or the software calculates a ratio of time 506 when the clipping event occurs. For example, the ratio of time 506 can be calculated to be any value including 95% of the time or just 1% of the time.
Based on the ratio of time 506, the hardware or the software scales back or reduces a number of the parallel I/O operations or the controller commands 314 to control or reduce the average current 502. Based on the ratio of time 506, the hardware or the software scales back or reduces the number of the parallel I/O operations or the controller commands 314 and increases time between launching the parallel I/O operations or the controller commands 314 to the non-volatile memory devices 106 to scale back or reduce the peak current 504.
Throttling of the parallel I/O operations or the controller commands 314 is engaged quickly (or fast attack) and removed slowly (or slow decay). The goal is to be able to have a mode page parameter tweakable or configurable by a user. The mode page parameter includes an average current ceiling 508 and a peak current ceiling 510, which are the configurable thresholds of the average current 502 and the peak current 504, respectively.
When the average current 502 and the peak current 504 exceed the average current ceiling 508 and the peak current ceiling 510, respectively, the number of the parallel I/O operations, the time between launching the parallel I/O operations, or a combination thereof can be controlled. As a result, the average current 502 and the peak current 504 are scaled back to be below the average current ceiling 508 and the peak current ceiling 510, respectively.
The average current 502 can be determined by implementing a series resistor-capacitor circuit using a first resistor 516 and a first capacitor 518 connected together in series. The first resistor 516 and the first capacitor 518 are denoted as R1 and C1, respectively. The sensed current 304 flows through one end of the first resistor 516 and one end of the first capacitor 518 is connected to ground. The average current 502 is at a node where the first resistor 516 and the first capacitor 518 are connected.
The peak current 504 can be determined by implementing an envelope detector or an amplitude demodulator/detector circuit. The envelope detector can be implemented with a diode 520 connected to a parallel resistor-capacitor circuit using a second resistor 522 and a second capacitor 524 connected together in parallel. Another end of the second resistor 522 and another end of the second capacitor 524 are connected together to one end of the diode. The sensed current 304 flows through another end of the diode.
The peak current 504 is at a node where the second resistor 522 and the second capacitor 524 are connected. The peak current 504 is determined based on a sum of branch currents through the second resistor 522 and the second capacitor 524.
Referring now to
The storage control system 100 of
The analog-to-digital converter 602 generates a power level value 604 by converting the current-sense voltage signal 308 from an analog signal to a digital signal. The current-to-voltage converter 306 receives the sensed current 304 from the current sensor 302, which receives the electrical current from the main power supply unit 102 that provides the core voltage 122. The current sensor 302 also provides the core voltage 122 supplied by the main power supply unit 102 to the non-volatile memory devices 106.
The main memory controller 104 samples the power level value 604 to determine how many of the parallel operations or the controller commands 314 to queue up. The main memory controller 104 decreases or increases the number of the parallel operations when the power level value 604 increases or decreases, respectively. The power level value 604 can indicate the full value of the electrical power 310 consumed by the drive level components 312 of
Referring now to
The section includes the analog-to-digital converter 602, the current-to-voltage converter 306, and the current sensor 302. The current sensor 302 monitors the electrical current from the main power supply unit 102 that provides the core voltage 122. The current sensor 302 also provides the core voltage 122 supplied by the main power supply unit 102 to the non-volatile memory devices 106.
The analog-to-digital converter 602 generates a trigger interrupt 702 as an input to the main memory controller 104. The trigger interrupt 702 is asserted to an active state when the power level value 604 is greater than a power threshold 704, which is a predetermined numerical value used as a reference for comparison purposes. When the trigger interrupt 702 is active, the main memory controller 104 reduces the number of the parallel operations or the controller commands 314.
The main memory controller 104 can also sample the power level value 604 to determine how many of the parallel operations or the controller commands 314 to queue up. The main memory controller 104 decreases or increases the number of the parallel operations or the controller commands 314 when the power level value 604 increases or decreases, respectively. The power level value 604 can indicate the full value of the electrical power 310 consumed by the drive level components 312 of
Referring now to
The flow chart shows a simple method for monitoring an instantaneous power usage and scheduling the correct amount of work for backend controllers or the device controllers interfacing with the non-volatile memory devices 106 of
The flow chart is a basic system level flow for how power throttling can be used with the hardware in the embodiments described herein. The flow chart shows how the scheduling software takes into account the power being used by the drive before it schedules new work.
The hardware shown in the previously described figures can be used by the firmware in two different forms or methods. The first method can follow the flow chart. The firmware or the software polls the two inputs (high-level and low-level) and make runtime decisions on how many operations for the non-volatile memory devices 106 to schedule. A second method can have the comparator outputs (high-level and low-level) be used to trigger interrupts that would then be used to change limit values in the controller firmware, which affect the amount of work scheduled for the device controllers.
The main memory controller 104 includes a host interface module 802 for interfacing with and receiving information from the host system 120 of
The main memory controller 104 includes a power measurement module 808 for reading a current value of the electrical power 310 of
The electrical power 310 can be determined based on the current-sense voltage signal 308 of
The power measurement module 808 compares the electrical power 310 to a power limit 812, which is a numerical value that is associated with a maximum amount of energy allowable to be consumed in the drive. The power limit 812 is associated with the over-current voltage level 414 of
If the current value of the electrical power 310 does not exceed or is less than or equal to the power limit 812, the power measurement module 808 requests a schedule module 814 to schedule new operations 816. If the electrical power 310 is greater than the power limit 812, the power measurement module 808 continues to sample the electrical power 310 and compare the electrical power 310 to the power limit 812.
The new operations 816 are tasks that are to be performed for storing, accessing, or managing the non-volatile memory devices 106 in response to the host commands 804 received from the host system 120. The new operations 816 can be at the command level. The new operations 816 can include a group of the controller commands 314 of
The new operations 816 are scheduled using a closed loop method. In other words, the new operations 816 are scheduled such that dynamic run-time adjustments are made by continuously monitoring the SSD's operations while the SSD is in operation. As the SSD goes through different phases of operations including recycling, wear leveling, spare pool and over provisioning resource management, and differing host workloads, the drive can require or utilize differing amounts of the electrical power 310. While the SSD is in operation, the electrical power 310 represents the run-time power usage 810.
The power measurement module 808 employs an instantaneous electrical current or power measurement to determine the electrical power 310 in order to control future electrical current usage. The future electrical current usage is determined by how many of the new operations 816 are to be queued up based on the power limit 812. The future electrical current usage occurs when the new operations are actually executed in the non-volatile memory devices 106.
The instantaneous electrical current or power measurement is a method used to obtain a real-time, immediate reading of the electrical power 310 at a particular instance of time. The particular instance of time is determined based on a time trigger or an operational trigger. For example, the time trigger is an event at a predetermined interval and is used to indicate when to read the electrical power 310. Also for example, the operational trigger is an event when the host commands 804 is received or any of the controller commands 314 is ready to be scheduled.
It has been discovered that scheduling the new operations 816 to be executed in parallel in when the current value of the electrical power 310 does not exceed the power limit 812 provides improved reliability. The reliability is improved because one of the biggest values of the current embodiments that bring to drive operations is the limiting of power spikes not allow by the host system 120, of power levels that are in excess of the capabilities of the host power supply.
It has also been discovered that monitoring the current-sense voltage signal 308 to determine the electrical power 310 provides improved reliability because the monitoring allows a media controller to adjust dynamically the run time power usage of a solid state storage device. As a result, power spikes that create supply voltage transients are eliminated thereby improving the reliability.
It has further been discovered that comparing the current-sense voltage signal 308 to the under-current voltage level 412 of
It has further been discovered that comparing the average current 502 to the average current ceiling 508 and the peak current 504 to the peak current ceiling 510 to determine the electrical power 310 provides improved reliability because the comparing eliminates power spikes that exceed the regulation capability of the host power system thereby improving the reliability.
It has further been discovered that generating the power level value 604 to determine the electrical power 310 and asserting the trigger interrupt 702 of
It has further been discovered that the section of a system level design that is used to measure the electrical power 310 by generating the power level value 604 and the trigger interrupt 702 within the main memory controller 104 significantly reduces the overall footprint for the implementation of the main memory controller 104. Furthermore, the section moved inside the main memory controller 104 also goes a long way to reducing errors due to component changes and hardware construction.
Functions or operations of the main memory controller 104 as described above can be implemented in hardware, software, or a combination thereof. The main memory controller 104 can be implemented with the control unit 202 of
For example, the host interface module 802 can be implemented with the control unit 202 to receive the host commands 804 from the host system 120 and storing the host data 806 in the buffer block 112. Also for example, the power measurement module 808 can be implemented with the control unit 202, the current sensor 302 of
Further, for example, the power measurement module 808 can be implemented with the control unit 202, the current sensor 302, and the current-to-voltage converter 306 to monitor the current-sense voltage signal 308 to determine the electrical power 310. Further, for example, the power measurement module 808 can be implemented with the control unit 202, the under-current level comparator 408, and the over-current level comparator 410 to compare the current-sense voltage signal 308 to the under-current voltage level 412 and the over-current voltage level 414.
Further, for example, the power measurement module 808 can be implemented with the control unit 202 and the current measurement hardware 512 to compare the average current 502 to the average current ceiling 508 and the peak current 504 to the peak current ceiling 510. Further, for example, the power measurement module 808 can be implemented with the control unit 202 and the analog-to-digital converter 602 to generate the power level value 604 by converting the current-sense voltage signal 308 from an analog signal to a digital signal and assert the trigger interrupt 702.
For example, the schedule module 814 can be implemented with the control unit 202 to scheduling the new operations 816 to be executed in parallel in the non-volatile memory devices 106.
The power measurement module 808 can be coupled to the host interface module 802. The schedule module 814 can be coupled to the host interface module 802.
The storage control system 100 is described with module functions or order as an example. The modules can be partitioned differently. For example, the power measurement module 808 and the schedule module 814 can be combined. Each of the modules can operate individually and independently of the other modules.
Furthermore, data generated in one module can be used by another module without being directly coupled to each other. Yet further, the power measurement module 808, the power measurement module 808, and the schedule module 814 can be implemented as hardware accelerators (not shown) within the control unit 202 or can be implemented as hardware accelerators (not shown) in the main memory controller 104 or outside of the main memory controller 104.
The physical transformation of scheduling the new operations 816 to be executed in parallel in the non-volatile memory devices 106 with the new operations 816 scheduled when the current value of the electrical power 310 does not exceed the power limit 812 results in movement in the physical world, such as people using the main memory controller 104 based on the operation of the storage control system 100. As the movement in the physical world occurs, the movement itself creates additional information that is converted back to receiving the host commands 804 from the host system 120 and reading the current value of the electrical power 310 supplied by the host system 120 in response to the host commands 804 for the continued operation of the storage control system 100 and to continue the movement in the physical world.
Referring now to
The rate of change 406 as a dynamic power control is used to limit instantaneous power changes to the electrical power 310 and so in effect smoothing a power response for a gain factor 902 of K. This method is also used to anticipate workload and power usage or a power trend 904 in the future before the controller commands 314 of
A solid line in
The K value can be used in the “Is power limit exceeded?” decision in the flow chart in
There can be any number of the channels 114 available for the main memory controller 104 to issue the controller commands 314 to device controllers. A lower portion of
As an example,
The software can receive a number of the host commands 804 of
The main memory controller 104 can issue the controller commands 314 on channels 4, 5, and 6. Then, there are more of the host commands 804 coming in from the host system 120. In this example, what can happen is that the electrical power 310 can start ramping up. The main memory controller 104 can detect the power trend 904 by calculating the rate of change 406 in the electrical power 310.
In the example described above, after eight of the number of the channels 114 are allocated to perform the workload, some of the controller commands 314 executed in channels 2 and 4 may be finished. The main memory controller 104 does not process an absolute value of the electrical power 310 but instead processes the power trend 904. The power trend 904 is used to indicate whether the sensed current 304 of
If the power trend 904 indicates that the sensed current 304 is starting to ramp up quickly, the main memory controller 104 can throttle back or reduce the number of the controller commands 314. If the power trend 904 indicates that the sensed current 304 is slowly ramping up, the main memory controller 104 can issue more of the controller commands 314 to the non-volatile memory devices 106.
Thus, the main memory controller 104 monitors an amount of change of current, the ramp, or the power trend 904 and determines how many of the parallel operations or the controller commands 314 to issue next. As an example, if the ramp or the power trend 904 is starting to significantly increase, the main memory controller 104 can allocate seven instead of eight of the channels 114.
Referring now to
Accordingly, it has been discovered that the present embodiments thus have numerous aspects. One such aspect is that this architecture lays out a means to allow a media controller to adjust dynamically the run time power usage of a solid state storage device.
Another aspect of the present embodiments is that this architecture allows the instantaneous electrical current (power) measurement as a means to control future electrical current usage.
Another aspect of the present embodiments is that this process allows the instantaneous electrical current (power) measurement as a means to control the instantaneous electrical current usage of a solid state storage device.
Another aspect of the present embodiments is that this invention provides a means for the firmware to better schedule NAND workloads to manage total drive power usage.
Another aspect of the present embodiments is that minimum, maximum, and rate of change of electrical current usage is controlled in real time.
Another aspect of the present embodiments is that this process is applied to several sub-sections of the device or the drive for determining NAND power, DRAM power, or the total drive power.
Another aspect of the present embodiments is a means to control current/power at a macro level.
Another aspect of the present embodiments is a means to control current/power at a micro level.
The concept described in the present embodiments can be used in a solid state drive (SSD). This concept can also be retrofitted into almost any SSD product with a need for an addition of power/current measurement hardware and some interface logic to the controller. Products or systems that can benefit from the present embodiments can include all of the stand-alone form factor SSD devices and the storage devices having multiple SSD devices combined and presented to the host as a single unit.
Thus, it has been discovered that the storage control system of the present invention furnishes important and heretofore unknown and unavailable solutions, capabilities, and functional aspects for a storage control system with power throttling mechanism. The resulting method, process, apparatus, device, product, and/or system is straightforward, cost-effective, uncomplicated, highly versatile, accurate, sensitive, and effective, and can be implemented by adapting known components for ready, efficient, and economical manufacturing, application, and utilization.
Another important aspect of the present invention is that it valuably supports and services the historical trend of reducing costs, simplifying systems, and increasing performance.
These and other valuable aspects of the present invention consequently further the state of the technology to at least the next level.
While the invention has been described in conjunction with a specific best mode, it is to be understood that many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the aforegoing description. Accordingly, it is intended to embrace all such alternatives, modifications, and variations that fall within the scope of the included claims. All matters hithertofore set forth herein or shown in the accompanying drawings are to be interpreted in an illustrative and non-limiting sense.
Number | Name | Date | Kind |
---|---|---|---|
4048481 | Bailey, Jr. et al. | Sep 1977 | A |
4839587 | Flatley et al. | Jun 1989 | A |
5034744 | Obinata | Jul 1991 | A |
5210854 | Beaverton et al. | May 1993 | A |
5311395 | McGaha et al. | May 1994 | A |
5450354 | Sawada et al. | Sep 1995 | A |
5479638 | Assar et al. | Dec 1995 | A |
5784174 | Fujino et al. | Jul 1998 | A |
5790828 | Jost | Aug 1998 | A |
5930504 | Gabel | Jul 1999 | A |
5949785 | Beasley | Sep 1999 | A |
5963983 | Sakakura et al. | Oct 1999 | A |
6034897 | Estakhri et al. | Mar 2000 | A |
6069827 | Sinclair | May 2000 | A |
6091652 | Haehn et al. | Jul 2000 | A |
6275436 | Tobita et al. | Aug 2001 | B1 |
6345367 | Sinclair | Feb 2002 | B1 |
6356447 | Scafidi | Mar 2002 | B2 |
6381176 | Kim et al. | Apr 2002 | B1 |
6381670 | Lee et al. | Apr 2002 | B1 |
6412080 | Fleming et al. | Jun 2002 | B1 |
6529997 | Debiez et al. | Mar 2003 | B1 |
6552581 | Gabara | Apr 2003 | B1 |
6587915 | Kim | Jul 2003 | B1 |
6618249 | Fairchild | Sep 2003 | B2 |
6661503 | Yamaguchi et al. | Dec 2003 | B1 |
6728913 | Parker | Apr 2004 | B1 |
6763424 | Conley | Jul 2004 | B2 |
6775792 | Ulrich et al. | Aug 2004 | B2 |
6778387 | Fairchild | Aug 2004 | B2 |
6850443 | Lofgren et al. | Feb 2005 | B2 |
6854070 | Johnson et al. | Feb 2005 | B2 |
6871304 | Hadjihassan et al. | Mar 2005 | B2 |
6903972 | Lasser et al. | Jun 2005 | B2 |
6906961 | Eggleston et al. | Jun 2005 | B2 |
6975028 | Wayburn et al. | Dec 2005 | B1 |
7082495 | DeWhitt et al. | Jul 2006 | B2 |
7107389 | Inagaki et al. | Sep 2006 | B2 |
7139864 | Bennett et al. | Nov 2006 | B2 |
7233497 | Simon et al. | Jun 2007 | B2 |
7243186 | Liang et al. | Jul 2007 | B2 |
7298888 | Hamar | Nov 2007 | B2 |
7330927 | Reeve et al. | Feb 2008 | B1 |
7333364 | Yu et al. | Feb 2008 | B2 |
7350101 | Nguyen et al. | Mar 2008 | B1 |
7355896 | Li et al. | Apr 2008 | B2 |
7434122 | Jo | Oct 2008 | B2 |
7441067 | Gorobets et al. | Oct 2008 | B2 |
7516267 | Coulson et al. | Apr 2009 | B2 |
7613871 | Tanaka et al. | Nov 2009 | B2 |
7620710 | Kottomtharayil et al. | Nov 2009 | B2 |
7620769 | Lee et al. | Nov 2009 | B2 |
7639532 | Roohparvar et al. | Dec 2009 | B2 |
7661054 | Huffman et al. | Feb 2010 | B2 |
7679948 | Park et al. | Mar 2010 | B2 |
7693422 | Alicherry et al. | Apr 2010 | B2 |
7738502 | Chang et al. | Jun 2010 | B2 |
7743216 | Lubbers et al. | Jun 2010 | B2 |
7818525 | Frost et al. | Oct 2010 | B1 |
7827348 | Lee et al. | Nov 2010 | B2 |
7830164 | Earle et al. | Nov 2010 | B2 |
7853749 | Kolokowsky | Dec 2010 | B2 |
7979614 | Yang | Jul 2011 | B1 |
8000161 | Stan et al. | Aug 2011 | B2 |
8001135 | Perlmutter et al. | Aug 2011 | B2 |
8010738 | Chilton et al. | Aug 2011 | B1 |
8028123 | Kilzer et al. | Sep 2011 | B2 |
8046645 | Hsu et al. | Oct 2011 | B2 |
8051241 | Feldman et al. | Nov 2011 | B2 |
8072805 | Chou et al. | Dec 2011 | B2 |
8095724 | Ji et al. | Jan 2012 | B2 |
8095765 | Asnaashari et al. | Jan 2012 | B2 |
8117396 | Fair et al. | Feb 2012 | B1 |
8127202 | Cornwell et al. | Feb 2012 | B2 |
8145984 | Sommer et al. | Mar 2012 | B2 |
8154921 | Mokhlesi et al. | Apr 2012 | B2 |
8169825 | Shalvi et al. | May 2012 | B1 |
8205028 | Sakarda | Jun 2012 | B1 |
8209677 | Shintani et al. | Jun 2012 | B2 |
8219724 | Caruso et al. | Jul 2012 | B1 |
8219776 | Forhan et al. | Jul 2012 | B2 |
8228701 | Sokolov et al. | Jul 2012 | B2 |
8245101 | Olbrich et al. | Aug 2012 | B2 |
8250621 | Cha | Aug 2012 | B2 |
8254172 | Kan | Aug 2012 | B1 |
8259506 | Sommer et al. | Sep 2012 | B1 |
8289801 | Smith et al. | Oct 2012 | B2 |
8296534 | Gupta et al. | Oct 2012 | B1 |
8332578 | Frickey, Iii et al. | Dec 2012 | B2 |
8363413 | Paquette et al. | Jan 2013 | B2 |
8369141 | Sommer et al. | Feb 2013 | B2 |
8386700 | Olbrich et al. | Feb 2013 | B2 |
8386860 | Tseng et al. | Feb 2013 | B2 |
8397101 | Goss et al. | Mar 2013 | B2 |
8407409 | Kawaguchi | Mar 2013 | B2 |
8464106 | Filor et al. | Jun 2013 | B2 |
8503238 | Wu et al. | Aug 2013 | B1 |
8521981 | Strauss et al. | Aug 2013 | B2 |
8560770 | Haines et al. | Oct 2013 | B2 |
8601203 | Holbrook et al. | Dec 2013 | B2 |
8612669 | Syu et al. | Dec 2013 | B1 |
8612804 | Kang et al. | Dec 2013 | B1 |
8661184 | Wood et al. | Feb 2014 | B2 |
8694811 | Raju et al. | Apr 2014 | B2 |
8725931 | Kang | May 2014 | B1 |
8750052 | Aoki et al. | Jun 2014 | B2 |
8793556 | Northcott et al. | Jul 2014 | B1 |
8799747 | Goss et al. | Aug 2014 | B2 |
8832506 | Griffin et al. | Sep 2014 | B2 |
8862818 | Ozdemir | Oct 2014 | B1 |
8880838 | Kaiser et al. | Nov 2014 | B2 |
8984216 | Fillingim | Mar 2015 | B2 |
9043668 | Goss et al. | May 2015 | B2 |
9063844 | Higgins et al. | Jun 2015 | B2 |
9069468 | Mehra et al. | Jun 2015 | B2 |
9116401 | Kim et al. | Aug 2015 | B2 |
20020056025 | Qiu et al. | May 2002 | A1 |
20020156891 | Ulrich et al. | Oct 2002 | A1 |
20020159285 | Morley et al. | Oct 2002 | A1 |
20030033308 | Patel et al. | Feb 2003 | A1 |
20030046603 | Harari et al. | Mar 2003 | A1 |
20030074592 | Hasegawa | Apr 2003 | A1 |
20030163633 | Aasheim et al. | Aug 2003 | A1 |
20040080985 | Chang et al. | Apr 2004 | A1 |
20040088511 | Bacon et al. | May 2004 | A1 |
20040252670 | Rong et al. | Dec 2004 | A1 |
20050021904 | Iaculo et al. | Jan 2005 | A1 |
20050038792 | Johnson | Feb 2005 | A1 |
20050073884 | Gonzalez et al. | Apr 2005 | A1 |
20050076102 | Chen et al. | Apr 2005 | A1 |
20050144516 | Gonzalez et al. | Jun 2005 | A1 |
20060015683 | Ashmore et al. | Jan 2006 | A1 |
20060020745 | Conley et al. | Jan 2006 | A1 |
20060022054 | Elhamias et al. | Feb 2006 | A1 |
20060080505 | Arai et al. | Apr 2006 | A1 |
20060136682 | Haridas et al. | Jun 2006 | A1 |
20060143365 | Kikuchi | Jun 2006 | A1 |
20060143475 | Herbert et al. | Jun 2006 | A1 |
20060253641 | Gatzemeier et al. | Nov 2006 | A1 |
20060256624 | Eggleston et al. | Nov 2006 | A1 |
20060282644 | Wong | Dec 2006 | A1 |
20060294574 | Cha | Dec 2006 | A1 |
20070050536 | Kolokowsky | Mar 2007 | A1 |
20070061511 | Faber | Mar 2007 | A1 |
20070067598 | Fujimoto | Mar 2007 | A1 |
20070079152 | Winick et al. | Apr 2007 | A1 |
20070083779 | Misaka et al. | Apr 2007 | A1 |
20070226592 | Radke | Sep 2007 | A1 |
20070234004 | Oshima et al. | Oct 2007 | A1 |
20070260811 | Merry et al. | Nov 2007 | A1 |
20070263444 | Gorobets et al. | Nov 2007 | A1 |
20070276973 | Tan et al. | Nov 2007 | A1 |
20080028246 | Witham | Jan 2008 | A1 |
20080046630 | Lasser | Feb 2008 | A1 |
20080052446 | Lasser et al. | Feb 2008 | A1 |
20080082736 | Chow et al. | Apr 2008 | A1 |
20080126720 | Danilak | May 2008 | A1 |
20080183918 | Dhokia et al. | Jul 2008 | A1 |
20080189588 | Tanaka et al. | Aug 2008 | A1 |
20080263289 | Hosoya et al. | Oct 2008 | A1 |
20080313505 | Lee et al. | Dec 2008 | A1 |
20090006900 | Lastras-Montano et al. | Jan 2009 | A1 |
20090019321 | Radke | Jan 2009 | A1 |
20090070651 | Diggs et al. | Mar 2009 | A1 |
20090083587 | Ng et al. | Mar 2009 | A1 |
20090089485 | Yeh | Apr 2009 | A1 |
20090091990 | Park et al. | Apr 2009 | A1 |
20090109786 | Ye et al. | Apr 2009 | A1 |
20090125670 | Keays | May 2009 | A1 |
20090132756 | Hsieh | May 2009 | A1 |
20090138654 | Sutardja | May 2009 | A1 |
20090146721 | Kurooka et al. | Jun 2009 | A1 |
20090157948 | Trichina et al. | Jun 2009 | A1 |
20090164702 | Kern | Jun 2009 | A1 |
20090164710 | Choi et al. | Jun 2009 | A1 |
20090172248 | You | Jul 2009 | A1 |
20090172262 | Olbrich et al. | Jul 2009 | A1 |
20090179707 | Higashino | Jul 2009 | A1 |
20090183183 | Muppirala et al. | Jul 2009 | A1 |
20090228634 | Nakamura et al. | Sep 2009 | A1 |
20090228761 | Perlmutter et al. | Sep 2009 | A1 |
20090259819 | Chen et al. | Oct 2009 | A1 |
20090259896 | Hsu et al. | Oct 2009 | A1 |
20090271562 | Sinclair | Oct 2009 | A1 |
20090287975 | Kim et al. | Nov 2009 | A1 |
20090300238 | Panabaker et al. | Dec 2009 | A1 |
20090323419 | Lee et al. | Dec 2009 | A1 |
20090327581 | Coulson | Dec 2009 | A1 |
20090327591 | Moshayedi | Dec 2009 | A1 |
20100017650 | Chin et al. | Jan 2010 | A1 |
20100023674 | Aviles | Jan 2010 | A1 |
20100050053 | Wilson et al. | Feb 2010 | A1 |
20100082890 | Heo et al. | Apr 2010 | A1 |
20100122019 | Flynn et al. | May 2010 | A1 |
20100128537 | Suhail et al. | May 2010 | A1 |
20100138592 | Cheon | Jun 2010 | A1 |
20100165689 | Rotbard et al. | Jul 2010 | A1 |
20100169541 | Freikorn | Jul 2010 | A1 |
20100172179 | Gorobets et al. | Jul 2010 | A1 |
20100174845 | Gorobets et al. | Jul 2010 | A1 |
20100217898 | Priborsky et al. | Aug 2010 | A1 |
20100217915 | O'Connor et al. | Aug 2010 | A1 |
20100223531 | Fukutomi et al. | Sep 2010 | A1 |
20100228928 | Asnaashari et al. | Sep 2010 | A1 |
20100262792 | Hetzler et al. | Oct 2010 | A1 |
20100262795 | Hetzler et al. | Oct 2010 | A1 |
20100262875 | Hetzler et al. | Oct 2010 | A1 |
20100287328 | Feldman et al. | Nov 2010 | A1 |
20100293367 | Berke et al. | Nov 2010 | A1 |
20100312954 | Jeon et al. | Dec 2010 | A1 |
20100318719 | Keays et al. | Dec 2010 | A1 |
20100325340 | Feldman et al. | Dec 2010 | A1 |
20100332726 | Wang | Dec 2010 | A1 |
20110002224 | Tamura | Jan 2011 | A1 |
20110016239 | Stenfort | Jan 2011 | A1 |
20110055455 | Post et al. | Mar 2011 | A1 |
20110055468 | Gonzalez et al. | Mar 2011 | A1 |
20110066788 | Eleftheriou et al. | Mar 2011 | A1 |
20110072423 | Fukata | Mar 2011 | A1 |
20110078393 | Lin | Mar 2011 | A1 |
20110099342 | Ozdemir | Apr 2011 | A1 |
20110107144 | Ohara | May 2011 | A1 |
20110131365 | Zhang et al. | Jun 2011 | A1 |
20110131447 | Prakash et al. | Jun 2011 | A1 |
20110132000 | Deane et al. | Jun 2011 | A1 |
20110138100 | Sinclair | Jun 2011 | A1 |
20110145473 | Maheshwari | Jun 2011 | A1 |
20110161775 | Weingarten | Jun 2011 | A1 |
20110190963 | Glassl et al. | Aug 2011 | A1 |
20110191522 | Condict et al. | Aug 2011 | A1 |
20110191649 | Lim et al. | Aug 2011 | A1 |
20110209032 | Choi et al. | Aug 2011 | A1 |
20110238892 | Tsai et al. | Sep 2011 | A1 |
20110239088 | Post | Sep 2011 | A1 |
20110258496 | Tseng et al. | Oct 2011 | A1 |
20110314219 | Ulrich et al. | Dec 2011 | A1 |
20110320687 | Belluomini et al. | Dec 2011 | A1 |
20120008401 | Katz et al. | Jan 2012 | A1 |
20120011336 | Saika | Jan 2012 | A1 |
20120023144 | Rub | Jan 2012 | A1 |
20120047318 | Yoon et al. | Feb 2012 | A1 |
20120047320 | Yoo et al. | Feb 2012 | A1 |
20120047409 | Post et al. | Feb 2012 | A1 |
20120066450 | Yochai et al. | Mar 2012 | A1 |
20120079348 | Naeimi | Mar 2012 | A1 |
20120079355 | Patapoutian et al. | Mar 2012 | A1 |
20120096217 | Son et al. | Apr 2012 | A1 |
20120124046 | Provenzano | May 2012 | A1 |
20120124273 | Goss et al. | May 2012 | A1 |
20120151260 | Zimmermann et al. | Jun 2012 | A1 |
20120170365 | Kang et al. | Jul 2012 | A1 |
20120185706 | Sistla et al. | Jul 2012 | A1 |
20120213004 | Yun et al. | Aug 2012 | A1 |
20120216085 | Weingarten et al. | Aug 2012 | A1 |
20120236656 | Cometti | Sep 2012 | A1 |
20120239858 | Melik-Martirosian | Sep 2012 | A1 |
20120254686 | Esumi et al. | Oct 2012 | A1 |
20120266011 | Storer et al. | Oct 2012 | A1 |
20120266048 | Chung et al. | Oct 2012 | A1 |
20120278530 | Ebsen | Nov 2012 | A1 |
20120278531 | Horn | Nov 2012 | A1 |
20120284587 | Yu et al. | Nov 2012 | A1 |
20120297113 | Belluomini et al. | Nov 2012 | A1 |
20120311402 | Tseng et al. | Dec 2012 | A1 |
20120317334 | Suzuki et al. | Dec 2012 | A1 |
20120324191 | Strange et al. | Dec 2012 | A1 |
20120331207 | Lassa et al. | Dec 2012 | A1 |
20130007380 | Seekins et al. | Jan 2013 | A1 |
20130007543 | Goss et al. | Jan 2013 | A1 |
20130054881 | Ellis et al. | Feb 2013 | A1 |
20130060994 | Higgins et al. | Mar 2013 | A1 |
20130061019 | Fitzpatrick et al. | Mar 2013 | A1 |
20130073788 | Post et al. | Mar 2013 | A1 |
20130073797 | Chowdhury | Mar 2013 | A1 |
20130074093 | Gounares et al. | Mar 2013 | A1 |
20130080691 | Weingarten et al. | Mar 2013 | A1 |
20130094289 | Sridharan et al. | Apr 2013 | A1 |
20130100600 | Yin et al. | Apr 2013 | A1 |
20130104005 | Weingarten et al. | Apr 2013 | A1 |
20130124792 | Melik-Martirosian et al. | May 2013 | A1 |
20130151753 | Jeon et al. | Jun 2013 | A1 |
20130198436 | Bandic et al. | Aug 2013 | A1 |
20130205102 | Jones et al. | Aug 2013 | A1 |
20130232290 | Ish et al. | Sep 2013 | A1 |
20130238833 | Vogan et al. | Sep 2013 | A1 |
20130265825 | Lassa | Oct 2013 | A1 |
20130290611 | Biederman | Oct 2013 | A1 |
20130304998 | Palmer | Nov 2013 | A1 |
20130326116 | Goss et al. | Dec 2013 | A1 |
20130332791 | Chu | Dec 2013 | A1 |
20140036589 | Parthasarathy et al. | Feb 2014 | A1 |
20140059359 | Bahirat | Feb 2014 | A1 |
20140108891 | Strasser et al. | Apr 2014 | A1 |
20140129874 | Zaltsman et al. | May 2014 | A1 |
20140158525 | Greene | Jun 2014 | A1 |
20140181370 | Cohen et al. | Jun 2014 | A1 |
20140208174 | Ellis et al. | Jul 2014 | A1 |
20140258769 | Baryudin et al. | Sep 2014 | A1 |
20140372777 | Reller et al. | Dec 2014 | A1 |
Number | Date | Country |
---|---|---|
1 956 489 | Aug 2008 | EP |
1 990 921 | Nov 2008 | EP |
2 498 259 | Sep 2012 | EP |
2012129859 | Jul 2012 | JP |
WO 2009042298 | Apr 2009 | WO |
WO 2011156466 | Dec 2011 | WO |
Entry |
---|
Ulinktech, “ATA Command Table (in Alphabetic Order),” Feb. 6, 2011, https://web.archive.org/web/20110206060820/http://www.ulinktech.com/downloads/AT, 6 pages. |
International Seearch Report dated Mar. 25, 2014, received in International Patent Application No. PCT/US2013/072400, which corresponds to U.S. Appl. No. 13/690,337, 3 pages (Ellis). |
Invitation to Pay Additional Fees dated Jul. 25, 2014, received in International Patent Application No. PCT/US2014/021290, which corresponds to U.S. Appl. No. 13/791,797, 8 pages (Dean). |
International Search Report and Written Opinion dated Jul. 31, 2014, received in International Patent Application No. PCT/US2014/031465, which corresponds to U.S. Appl. No. 13/851,928, 13 pages (Ellis). |
International Search Report and Written Opinion dated Jul. 31, 2014, received in International Patent Application No. PCT/US2014/033876, which corresponds to U.S. Appl. No. 13/861,326, 9 pages (Fitzpatrick). |
International Search Report and Written Opinion dated Aug. 22, 2014, received in International Patent Application No. PCT/US2014/032978, which corresponds to U.S. Appl. No. 14/081,992, 10 pages (Ellis). |
International Search Report and Written Opinion dated Nov. 7, 2014, received in International Patent Application No. PCT/US2014/049732, which corresponds to U.S. Appl. No. 14/334,350, 13 pages (Fitzpatrick). |
International Search Report and Written Opinion dated Oct. 17, 2014, received in International Patent Application No. PCT/US2014/049734, which corresponds to U.S. Appl. No. 14/332,259, 8 pages (Higgins). |
International Search Report and Written Opinion dated Oct. 23, 2014, received in International Patent Application No. PCT/US2014/049736, which corresponds to U.S. Appl. No. 14/446,249 8 pages (Fitzpatrick). |
international Search Report and Written Opinion dated Nov. 5, 2014, received in International Patent Application No. PCT/US2014/049282, which corresponds to U.S. Appl. No. 13/957,407, 12 pages (Fitzpatrick). |
Tseng et al., “Understanding the Impact of Power Loss on Flash Memory,” DAC'11, Jun. 5-10, 2011, San Diego, California, 6 pages. |
Narayanan et al., “Migrating Server Storage to SSDs: Analysis of Tradeoffs,” Computer Systems, Apr. 2009, 12 pages. |
Shiraz et al., “Block Aging Prevention Technique (BAP) for Flash Based Solid State Disks,” 7th International Conference on Emerging Technologies (ICET), Sep. 5, 2011, 6 pages. |
Tai et al, “Prolongation of Lifetime and the Evaluation Method of Dependable SSD,” 25 International Symposium on Defect and Fault Tolerance in VLSI Systems, 2010, NJ, USA, 8 pages. |
Yimo et al “WeLe-RAID: A SSD-Based RAID for System Endurance and Performance,” Jan. 2011, Network and Parallel Computing, Springer, 14 pages. |
International Search Report and Written Opinion dated Jan. 9, 2015, received in International Patent Application No. PCT/US2014/049731, which corresponds to U.S. Appl. No. 14/334,324, 9 pages (Fitzpatrick). |
International Search Report and Written Opinion dated Feb. 18, 2015, received in International Patent Application No. PCT/US2014/065401, which corresponds to U.S. Appl. No. 14/082,031, 9 pages (Higgins). |
International Search Report dated Apr. 15, 2014, received in International Patent Application No. PCT/US2013/078340, which corresponds to U.S. Appl. No. 13/746,542, 11 pages (Ellis). |
Cooke, “Introduction to Flash Memory (T1A),” Flash Memory Summit, Aug. 22, 2008, Micron Technology, Inc., 102 pages. |
Gal et al., “Algorithms and Data Structures for Flash Memories,” ACM Computing Surveys, Jun. 2005, vol. 37, No. 2, 30 pages. |
IBM Corporation, “Systems Management, Work Management,” Version 5, Release 4, 9th Edition, Feb. 2006, pp. 1-21. |
O'Brien “SMART Storage Systems Optimus SAS Enterprise SSD Review,” SMART Storage Systems, Oct. 9, 2012, 44 pages. |
Spanjer, “Flash Management—Why and How?” Smart Modular Technologies, Nov. 2009, http://www.scantec.de/fileadmin/pdf/Smart—Modular/Flash-Management.pdf, 14 pages. |
Texas Instruments, “Power Management IC for Digital Set Top Boxes,” SLVSA10A, Sep. 2009, pp. 1-22. |
International Search Report and Written Opinion dated Dec. 20. 2013, received in PCT/US2013/045282, which corresponds to U.S. Appl. No. 13/493,949, 7 pages (Ellis). |
International Search Report and Written Opinion dated Jun. 12, 2014, received in PCT/US2014/018972, which corresponds to U.S. Appl. No. 13/779,352, 12 pages (Schmier). |
International Search Report and Written Opinion dated May 14, 2014, received in International Patent Application No. PCT/US2014/017168, which corresponds to U.S. Appl. No. 14/076,115 6 pages (Fitzpatrick). |
International Search Report and Written Opinion dated May 14, 2014, received in International Patent Application No. PCT/US2014/017169, which corresponds to U.S. Appl. No. 14/076,148, 6 pages (Fitzpatrick). |
Online Merriam Webster Dictionary, definition of “Distinct” from Jun. 12, 2011, https://web.archive.org/web/20110612181129/http://www2.merriam-webster.com/cgi-bin/mwdictadu?book=Dictionary&va=distinct. |