Power inrush management of storage devices

Information

  • Patent Grant
  • 9582058
  • Patent Number
    9,582,058
  • Date Filed
    Thursday, December 19, 2013
    11 years ago
  • Date Issued
    Tuesday, February 28, 2017
    8 years ago
Abstract
The various embodiments described herein include systems, methods and/or devices used to enable power inrush management of storage devices (e.g., DIMM devices). In one aspect, the method includes, for at least one storage device populated in a slot of a plurality of storage device slots, the plurality of storage device slots configured to be populated by two or more storage devices: (1) detecting a unique location associated with the storage device, (2) determining a time delay for the storage device in accordance with the unique location associated with the storage device, and (3) delaying at least one power-on operation of the storage device by the time delay for the storage device.
Description
TECHNICAL FIELD

The disclosed embodiments relate generally to memory systems, and in particular, to power inrush management of storage devices (e.g., memory devices).


BACKGROUND

Semiconductor memory devices, including flash memory, typically utilize memory cells to store data as an electrical value, such as an electrical charge or voltage. A flash memory cell, for example, includes a single transistor with a floating gate that is used to store a charge representative of a data value. Flash memory is a non-volatile data storage device that can be electrically erased and reprogrammed. More generally, non-volatile memory (e.g., flash memory, as well as other types of non-volatile memory implemented using any of a variety of technologies) retains stored information even when not powered, as opposed to volatile memory, which requires power to maintain the stored information.


Some storage devices (e.g., memory devices) demand high power during power-on. As a number of storage devices used in a host system increases, power management of the storage devices is important.


SUMMARY

Various implementations of systems, methods and devices within the scope of the appended claims each have several aspects, no single one of which is solely responsible for the attributes described herein. Without limiting the scope of the appended claims, after considering this disclosure, and particularly after considering the section entitled “Detailed Description” one will understand how the aspects of various implementations are used to enable power inrush management of storage devices (e.g., DIMM devices). In one aspect, for at least one storage device populated in a slot of a plurality of storage device slots, the plurality of storage device slots configured to be populated by two or more storage devices, at least one power-on operation of the storage device is delayed by a time delay determined in accordance with a unique location associated with the storage device.





BRIEF DESCRIPTION OF THE DRAWINGS

So that the present disclosure can be understood in greater detail, a more particular description may be had by reference to the features of various implementations, some of which are illustrated in the appended drawings. The appended drawings, however, merely illustrate the more pertinent features of the present disclosure and are therefore not to be considered limiting, for the description may admit to other effective features.



FIG. 1 is a block diagram illustrating an implementation of a data storage system, in accordance with some embodiments.



FIG. 2 is a block diagram illustrating an implementation of a supervisory controller, in accordance with some embodiments.



FIG. 3 is a block diagram illustrating an implementation of a portion of a storage device, in accordance with some embodiments.



FIG. 4 is a block diagram illustrating an implementation of data hardening circuitry, in accordance with some embodiments.



FIG. 5 is a block diagram illustrating an implementation of a data storage system, in accordance with some embodiments.



FIG. 6 illustrates a sequence of charge currents over time, in accordance with some embodiments.



FIGS. 7A-7C illustrate a flowchart representation of a method of power management of a plurality of storage device slots configured to be populated by two or more storage devices, in accordance with some embodiments.





In accordance with common practice the various features illustrated in the drawings may not be drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may not depict all of the components of a given system, method or device. Finally, like reference numerals may be used to denote like features throughout the specification and figures.


DETAILED DESCRIPTION

The various implementations described herein include systems, methods and/or devices for power inrush management of storage devices (e.g., DIMM devices). Some implementations include systems, methods and/or devices to, for at least one storage device populated in a slot of a plurality of storage device slots, the plurality of storage device slots configured to be populated by two or more storage devices, delay at least one power-on operation of the storage device by a time delay determined in accordance with a unique location associated with the storage device.


More specifically, some embodiments include a method of power management of a plurality of storage device slots configured to be populated by two or more storage devices. In some embodiments, the method includes, for at least one storage device populated in a slot of the plurality of storage device slots: (1) detecting a unique location associated with the storage device, (2) determining a time delay for the storage device in accordance with the unique location associated with the storage device, and (3) delaying at least one power-on operation of the storage device by the time delay for the storage device.


In some embodiments, the two or more storage devices include two or more dual in-line memory module (DIMM) devices.


In some embodiments, detecting the unique location associated with the storage device includes monitoring signals used for System Management Bus (SMBus) addressing.


In some embodiments, detecting the unique location associated with the storage device includes monitoring signals used for SMBus addressing and monitoring one or more additional signals.


In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes obtaining the time delay from non-volatile memory in the storage device.


In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes obtaining the time delay from a host system.


In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes using a predefined time interval to determine the time delay.


In some embodiments, the predefined time interval is programmable.


In some embodiments, each storage device of the two or more storage devices includes an energy storage device, and the predefined time interval is less than a charge time to charge the energy storage device to a predefined level.


In some embodiments, each storage device of the two or more storage devices includes an energy storage device, and delaying at least one power-on operation of the storage device by the time delay for the storage device includes delaying charging of the energy storage device by the time delay for the storage device.


In some embodiments, each storage device of the two or more storage devices includes an energy storage device, and delaying at least one power-on operation of the storage device by the time delay for the storage device includes delaying enabling of a power regulator dedicated to providing power to the energy storage device by the time delay for the storage device.


In some embodiments, the energy storage device includes one or more capacitors.


In some embodiments, the storage device includes a plurality of non-volatile memory (NVM) controllers, and the method further includes, for at least one NVM controller of the plurality of NVM controllers, delaying power-on of the NVM controller.


In some embodiments, the storage device includes an independent power domain for each NVM controller of the plurality of NVM controllers, and the independent power domains for the NVM controllers are powered-on at staggered times.


In some embodiments, each NVM controller of the plurality of NVM controllers has an independent reset signal, and the reset signals so the plurality of NVM controllers are released at staggered times.


In another aspect, any of the methods described above are performed by a storage device including: (1) an interface for operatively coupling the storage device with a host system, (2) an energy storage device, (3) a controller with one or more processors and memory, the controller configured to perform and/or control performance of any of the methods described herein. In some embodiments, the storage device includes a plurality of controllers. In some embodiments, the storage device includes a supervisory controller.


In yet another aspect, any of the methods described above are performed by a storage device including an interface for operatively coupling the storage device with a host system and means for performing any of the methods described herein.


In yet another aspect, some embodiments include a non-transitory computer readable storage medium, storing one or more programs for execution by one or more processors of a storage device, the one or more programs including instructions for performing any of the methods described herein.


Numerous details are described herein in order to provide a thorough understanding of the example implementations illustrated in the accompanying drawings. However, some embodiments may be practiced without many of the specific details, and the scope of the claims is only limited by those features and aspects specifically recited in the claims. Furthermore, well-known methods, components, and circuits have not been described in exhaustive detail so as not to unnecessarily obscure more pertinent aspects of the implementations described herein.



FIG. 1 is a block diagram illustrating an implementation of a data storage system 100, in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, data storage system 100 includes storage device 120, which includes host interface 122, supervisory controller 124 (sometimes called power control processor), power fail module 126, power control 127, memory controller 128, one or more non-volatile memory (NVM) controllers 130 (e.g., NVM controller 130-1 through NVM controller 130-m), and non-volatile memory (NVM) (e.g., one or more NVM device(s) 140, 142 such as one or more flash memory devices), and is used in conjunction with computer system 110.


Computer system 110 is coupled with storage device 120 through data connections 101. However, in some embodiments, computer system 110 includes storage device 120 as a component and/or sub-system. Computer system 110 may be any suitable computing device, such as a personal computer, a workstation, a computer server, or any other computing device. Computer system 110 is sometimes called a host or host system. In some embodiments, computer system 110 includes one or more processors, one or more types of memory, optionally includes a display and/or other user interface components such as a keyboard, a touch screen display, a mouse, a track-pad, a digital camera and/or any number of supplemental devices to add functionality. Further, in some embodiments, computer system 110 sends one or more host commands (e.g., read commands and/or write commands) on control line 111 to storage device 120. In some embodiments, computer system 110 is a server system, such as a server system in a data center, and does not have a display and other user interface components.


In some embodiments, storage device 120 includes a single NVM device (e.g., a single flash memory device) while in other embodiments storage device 120 includes a plurality of NVM devices (e.g., a plurality of flash memory devices). In some embodiments, NVM devices 140, 142 include NAND-type flash memory or NOR-type flash memory. Further, in some embodiments, NVM controller 130 is a solid-state drive (SSD) controller. However, one or more other types of storage media may be included in accordance with aspects of a wide variety of implementations. In some embodiments, storage device 120 is or includes a dual in-line memory module (DIMM) device. In some embodiments, storage device 120 is compatible with a DIMM memory slot. For example, in some embodiments, storage device 120 is compatible with a 240-pin DIMM memory slot and is compatible with signaling in accordance with a double data rate type three synchronous dynamic random access memory (DDR3) interface specification.


In some embodiments, storage device 120 includes NVM devices 140, 142 (e.g., NVM devices 140-1 through 140-n and NVM devices 142-1 through 142-k) and NVM controllers 130 (e.g., NVM controllers 130-1 through 130-m). In some embodiments, each NVM controller of NVM controllers 130 include one or more processing units (sometimes called CPUs or processors or microprocessors or microcontrollers) configured to execute instructions in one or more programs (e.g., in NVM controllers 130). NVM devices 140, 142 are coupled with NVM controllers 130 through connections that typically convey commands in addition to data, and, optionally, convey metadata, error correction information and/or other information in addition to data values to be stored in NVM devices 140, 142 and data values read from NVM devices 140, 142. For example, NVM devices 140, 142 can be configured for enterprise storage suitable for applications such as cloud computing, or for caching data stored (or to be stored) in secondary storage, such as hard disk drives. Additionally and/or alternatively, flash memory (e.g., NVM devices 140, 142) can also be configured for relatively smaller-scale applications such as personal flash drives or hard-disk replacements for personal, laptop and tablet computers. Although flash memory devices and flash controllers are used as an example here, in some embodiments storage device 120 includes other non-volatile memory device(s) and corresponding non-volatile memory controller(s).


In some embodiments, storage device 120 also includes host interface 122, supervisory controller 124, power fail module 126, power control 127, and memory controller 128, or a superset or subset thereof. Storage device 120 may include various additional features that have not been illustrated for the sake of brevity and so as not to obscure more pertinent features of the example implementations disclosed herein, and a different arrangement of features may be possible. Host interface 122 provides an interface to computer system 110 through data connections 101.


In some embodiments, supervisory controller 124 (sometimes called power control processor) includes one or more processing units (also sometimes called CPUs or processors or microprocessors or microcontrollers) configured to execute instructions in one or more programs (e.g., in supervisory controller 124). Supervisory controller 124 is typically coupled with host interface 122, power fail module 126, power control 127, memory controller 128, and NVM controllers 130 (connection not shown) in order to coordinate the operation of these components, including supervising and controlling functions such as power up, power down, data hardening, charging energy storage device(s), data logging, and other aspects of managing functions on storage device 120. Supervisory controller 124 is coupled with host interface 122 via serial presence detect (SPD) bus 154 and receives supply voltage line VSPD 156 from the host interface 122. VSPD 156 is typically a standardized voltage (e.g., 3.3 volts). Serial presence detect (SPD) refers to a standardized way to automatically access information about a computer memory module (e.g., storage device 120). In some embodiments, supervisory controller 124 includes circuitry configured to monitor an input voltage (e.g., VSPD 156). In some embodiments, if the memory module has a failure, the failure can be communicated with a host system (e.g., computer system 110) via SPD bus 154.


Power fail module 126 is typically coupled with host interface 122, supervisory controller 124, and power control 127. Power fail module 126 is configured to monitor one or more input voltages (e.g., Vdd 152 and, optionally, VSPD 156 if provided to power fail module 126) provided to storage device 120 by a host system (e.g., computer system 110). In response to detecting a power fail condition (e.g., an under or over voltage event) of an input voltage, power fail module 126 is configured to provide a Vdd PFAIL signal to supervisory controller 124. In some embodiments, in response to detecting the power fail condition, power fail module 126 discharges an energy storage device to provide power to memory controller 128 and NVM controllers 130. Power fail module 126 is described in further detail below with respect to FIGS. 3-4. In response to receiving a PFAIL signal indicating a power fail condition (e.g., a Vdd PFAIL signal from power fail module 126 or a VSPD PFAIL signal from voltage monitoring circuitry within supervisory controller 124), supervisory controller 124 performs one or more operations of a power fail process including, but not limited to, signaling the power fail condition to a plurality of controllers on storage device 120 (e.g., memory controller 128 and NVM controllers 130) via control lines 162 (connection to NVM controllers 130 not shown).


Power control 127 is typically coupled with supervisory controller 124, power fail module 126, memory controller 128, and NVM controllers 130 in order to provide power to these components. In some embodiments, power control 127 includes one or more voltage regulators (sometimes called power regulators) controlled by supervisory controller 124 via control line 164. Furthermore, in some embodiments, power control 127 is configured to remove power from a specified NVM controller 130 in response to a command from supervisory controller 124 via control line 164.


Memory controller 128 is typically coupled with host interface 122, supervisory controller 124, power control 127, and NVM controllers 130. In some embodiments, during a write operation, memory controller 128 receives data via data bus 158 from computer system 110 through host interface 122 and during a read operation, memory controller 128 sends data to computer system 110 through host interface 122 via data bus 158. Further, host interface 122 provides additional data, signals, voltages, and/or other information needed for communication between memory controller 128 and computer system 110. In some embodiments, memory controller 128 and host interface 122 use a defined interface standard for communication, such as double data rate type three synchronous dynamic random access memory (DDR3). In some embodiments, memory controller 128 and NVM controllers 130 use a defined interface standard for communication, such as serial advance technology attachment (SATA). In some other embodiments, the device interface used by memory controller 128 to communicate with NVM controllers 130 is SAS (serial attached SCSI), or other storage interface. In some embodiments, memory controller 128 maps DDR interface commands from the host system (e.g., computer system 1120) to SATA or SAS interface commands for the plurality of controllers (e.g., memory controller 128 and NVM controllers 130). In some embodiments, memory controller 128 includes one or more processing units (also sometimes called CPUs or processors or microprocessors or microcontrollers) configured to execute instructions in one or more programs (e.g., in memory controller 128).



FIG. 2 is a block diagram illustrating an implementation of supervisory controller 124, in accordance with some embodiments. Supervisory controller 124 includes one or more processors 202 (sometimes called CPUs or processing units or microprocessors or microcontrollers) for executing modules, programs and/or instructions stored in memory 206 and thereby performing processing operations, serial presence detect (SPD) module 205 (e.g., non-volatile memory) storing information related to storage device 120 (e.g., a serial number, memory type, supported communication protocol, etc.), memory 206, optionally a digital-to-analog converter (DAC) 204 for converting digital values to an analog signal (e.g., a portion of an integrated or partially integrated DAC/ADC), optionally VSPD monitoring circuitry 203 configured to detect an under or over voltage event as to VSPD (e.g., VSPD 156, FIG. 1), and one or more communication buses 208 for interconnecting these components. Communication buses 208, optionally, include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. In some embodiments, supervisory controller 124 is coupled with host interface 122, power fail module 126, power control 127, memory controller 128, and NVM controllers 130 (e.g., NVM controllers 130-1 through 130-m) by communication buses 208.


Memory 206 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 206, optionally, includes one or more storage devices remotely located from processor(s) 202. Memory 206, or alternately the non-volatile memory device(s) within memory 206, comprises a non-transitory computer readable storage medium. In some embodiments, memory 206, or the computer readable storage medium of memory 206, stores the following programs, modules, and data structures, or a subset or superset thereof:

    • location module 210 that is used for detecting a unique location associated with a storage device (e.g., storage device 120, FIG. 1), optionally including:
      • monitoring module 212 that is used for monitoring signals used for SMBus addressing and/or monitoring one or more additional signals;
    • time delay module 214 that is used for determining a time delay for the storage device in accordance with the unique location associated with the storage device, optionally including:
      • obtaining module 216 that is used for obtaining the time delay from non-volatile memory in the storage device and/or from a host system; and
      • determination module 218 that is used for determining the time delay for the storage device using a predefined time interval to determine the time delay;
    • power-on delay module 220 that is used for delaying at least one power-on operation of the storage device by the time delay for the storage device, optionally including:
      • control module 222 that is used for delaying at least one power-on operation by controlling one or more modules on the storage device (e.g., power fail module 126 and/or power control 127, FIG. 1); and
    • optionally, non-volatile memory 224 for storing information related to the operations of the storage device, optionally including:
      • time delay table 226 for storing a plurality of predefined time delays (e.g., time delays associated with various unique locations); and
      • event log 228 for storing information related to events on the storage device (e.g., the time and occurrence of a power fail condition).


Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 206 may store a subset of the modules and data structures identified above. Furthermore, memory 206 may store additional modules and data structures not described above. In some embodiments, the programs, modules, and data structures stored in memory 206, or the computer readable storage medium of memory 206, include instructions for implementing any of the methods described below with reference to FIGS. 7A-7C.


Although FIG. 2 shows supervisory controller 124 in accordance with some embodiments, FIG. 2 is intended more as a functional description of the various features which may be present in supervisory controller 124 than as a structural schematic of the embodiments described herein. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated.



FIG. 3 is a block diagram illustrating an implementation of a portion of storage device 120, in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, supervisory controller 124 includes one or more processors 202, DAC 204, and, optionally, VSPD monitoring circuitry 203, and power fail module 126 includes voltage monitoring circuitry 302 and data hardening circuitry 308. In some embodiments, DAC 204 is a component of one or more processors 202. In some embodiments, Vdd 152 is a voltage supplied by the host system (e.g., computer system 110, FIG. 1). In some embodiments, Vdd 152 has a target value of 1.5 volts or less (e.g., 1.25 volts, 1.35 volts, or 1.5 volts). For example, for a double data rate type three (DDR3) interface specification, Vdd 152 is 1.25 volts, 1.35 volts or 1.5 volts. In some embodiments, VSPD 156 is a voltage supplied by the host system for a serial presence detect (SPD) functionality. In some embodiments, VSPD 156 has a target value of 3.3 volts. In some embodiments, Vdd 152 supports a higher level of electric power consumption by supervisory controller 124 and/or operation of supervisory controller 124 at a higher performance level than when supervisory controller 124 is powered by VSPD 156.


In some embodiments, voltage monitoring circuitry 302 is configured to detect a power fail condition (e.g., an under or over voltage event) as to an input voltage (e.g., Vdd 152) supplied by a host system (e.g., computer system 110, FIG. 1) and signal the power fail condition (e.g., Vdd PFAIL 314) to supervisory controller 124. In some embodiments, voltage monitoring circuitry 302 includes Vdd monitoring circuitry 304 configured to detect an under or over voltage event as to Vdd 152.


In some embodiments, supervisory controller 124 includes VSPD monitoring circuitry 203 configured to detect an under or over voltage event as to VSPD 156. Although FIG. 3 shows VSPD monitoring circuitry 203 included in supervisory controller 124, in other embodiments, VSPD monitoring circuitry 203 is included in voltage monitoring circuitry 302 in power fail module 126. Further, although VSPD monitoring circuitry 203 and DAC 204 are shown in FIG. 3 as separate modules, in some embodiments, VSPD monitoring circuitry 203 and/or DAC 204 are embedded in processor(s) 202.


In some embodiments, data hardening circuitry 308 is configured to interconnect an energy storage device to provide power to memory controller 128 and NVM controllers 130. Data hardening circuitry 308 is described in more detail below with respect to FIG. 4.



FIG. 4 is a block diagram illustrating an implementation of data hardening circuitry 308, in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, data hardening circuitry 308 includes transistors 402 and 404, boost circuitry 406, and energy storage device 410. In some embodiments, energy storage device 410 is configured to provide power for, or solely for, power fail operations. Further, in some embodiments, the aforementioned power fail operations include “hard power fail” operations, resulting from a detected loss of power, and “soft power fail” operations, performed in accordance with a host command or internally detected condition. In some embodiments, a primary function of a respective power fail operation is to persistently store, in non-volatile memory, data resident in volatile memory at the initiation of the power fail operation.


In some embodiments, Vholdup 408 is a boosted voltage, higher than Vdd 152, and has a target value of 5.7 volts. In some embodiments, Vholdup 408 is used to charge an energy storage device 410 (e.g., one or more hold-up capacitors). Further, in some embodiments, only one of transistors 402, 404 is enabled at any one time. In some embodiments, data hardening circuit 308's energy storage device 410 stores, immediately prior to a power fail condition being detected, at least approximately 30 to 70 mJ of energy per NVM controller 130 in storage device 120.


In some embodiments, supervisory controller 124 or a component thereof (e.g., processor 202) monitors and manages the functionality of data hardening circuitry 308. For example, in response to receiving PFAIL signal 420 indicating a power fail condition, supervisory controller 124 or a component thereof (e.g., processor 202) is configured to perform one or more operations of a power fail process including controlling transistors 402 and 404 so that Vswitched 160 is the voltage from energy storage device 410, and energy storage device 410 is used (sometimes said to be “discharged”) to provide power to storage device 120.


In some embodiments, during regular operation of storage device 120, Vdd 152 is used to supply power to storage device 120. However, during the power fail process, energy storage device 410 is used to provide power to storage device 120. In some embodiments, supervisory controller 124 or a component thereof (e.g., processor 202) controls transistors 402 and 404 via control lines 318 to control Vswitched 160 to be voltage from Vdd 152 (e.g., during regular operation) or voltage from energy storage device 410 (e.g., during the power fail process). For example, during regular operation of storage device 120, transistor 402 is turned on (e.g., to complete the connection between Vdd 152 and Vswitched 160) and transistor 404 is turned off (e.g., to disable the connection between energy storage device 410 and Vswitched 160) so that Vdd 152 is used to supply power to storage device 120. However, during the power fail process, transistor 402 is turned off (e.g., to disable the connection between Vdd 152 and Vswitched 160) and transistor 404 is turned on (e.g., to enable the connection between energy storage device 410 and Vswitched 160) so that energy storage device 410 is used to provide power to storage device 120. Although a single energy storage device 410 is shown in FIG. 4, any energy storage device, including one or more capacitors, one or more inductors, or one or more other passive elements that store energy, may be used to store energy to be used during the power fail process.


In some embodiments, energy storage device 410 is charged using Vholdup 408, a voltage higher than Vdd 152. In some embodiments, Vdd 152 is boosted up to Vholdup 408 using boost circuitry 406 (e.g., 1.35 volts or 1.5 volts is boosted up to 5.7 volts). In some embodiments, boost circuitry 406 is controlled and enabled by supervisory controller 124 (e.g., via processor 202).


Further, in some embodiments, Vswitched 160 is used as an input to keeper circuitry 412, which along with VSPD 156 provides power to processor 202. During the power fail process, Vswitched 160 is provided via keeper circuitry 412 to processor 202 so as to provide power to processor 202. In some embodiments, VSPD 156 provides power to keeper circuitry 412. In some embodiments, logic block 414 (e.g., OR or XOR) determines which of keeper circuitry 412 or VSPD 156 provides power to supervisory controller 124 (e.g., processor 202).


Furthermore, in some embodiments, during a power up sequence, VSPD 156 is provided to storage device 120 before Vdd 152 is provided to storage device 120. This allows devices in storage device 120 (e.g., supervisory controller 124 and, in turn, processor 202) to operate before main power Vdd 152 is provided to storage device 120. In some embodiments, supervisory controller 124 or a component thereof (e.g., processor 202) includes one or more connections 162 used to monitor and control other functions within storage device 120.


For example, in some embodiments, supervisory controller 124 or a component thereof (e.g., processor 202) detects a unique location associated with storage device 120, determines a time delay for storage device 120 in accordance with the unique location associated with storage device 120, and delays at least one power-on operation of storage device 120 (e.g., delays charging of energy storage device 410) by the determined time delay for storage device 120. In some embodiments, delaying at least one power-on operation of storage device 120 by the time delay for storage device 120 includes delaying enabling of a power regulator (e.g., in power control 127, FIG. 1) dedicated to providing power to energy storage device 410 by the time delay for storage device 120.



FIG. 5 is a block diagram illustrating an implementation of a data storage system 500, in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, data storage system 500 includes storage devices 120 (e.g., storage device 120-1 through storage device 120-x) and storage devices 520 (e.g., storage device 520-1 through storage device 520-y), which are used in conjunction with computer system 110. In some embodiments, storage devices 120, 520 each include the features described above with respect to storage device 120 in FIG. 1. In some embodiments, data storage system 500 includes a plurality of groups of storage devices (e.g., two or more, three or more, etc.). In some embodiments, storage devices 120 are in a first group (e.g., Group 1 (502-1)) and storage devices 520 are in a second group (e.g., Group 2 (502-z)). In some embodiments, the first group and the second group have different numbers of storage devices. For example, in some embodiments, a first group includes 8 storage devices (e.g., storage device 120-1 though storage device 120-8) and a second group includes 4 storage devices (e.g., storage device 520-1 through storage device 520-4). In some embodiments, for example, computer system 110 has 16 DIMM device slots, with 12 DIMM devices populated, 8 DIMM devices in a first group (e.g., storage device 120-1 though storage device 120-8) and 4 DIMM devices in a second group (e.g., storage device 520-1 through storage device 520-4). Although not explicitly shown, in some embodiments, data storage system 500 includes one or more additional storage devices grouped in one or more additional groups.


In some embodiments, storage devices 120 include energy storage device 410 (e.g., storage device 120-1 through storage device 120-x include energy storage device 410-1 through energy storage devices 410-x, respectively) and storage devices 520 include energy storage device 524 (e.g., storage device 520-1 through storage device 520-y include energy storage devices 524-1 through energy storage devices 524-y, respectively). In some embodiments, each storage device (e.g., storage devices 120, 520) includes a controller (e.g., a supervisory controller, not shown) to control power-on operations.


Traditional DIMM devices generally do not consume significant power upon initial power up. Further, traditional DIMM devices generally power up at the same time when power is first applied (e.g., by computer system 110). Once all the DIMM devices are powered up, a host system (e.g., computer system 110) can use the DIMM devices and distribute input/output (I/O) operations (e.g., read commands and/or write commands) across the array of DIMM devices. However, the storage devices disclosed herein have data hardening functionality (e.g., DIMM devices including non-volatile memory, such as flash memory), including use energy storage devices (e.g., energy storage device 410, FIG. 4) to store energy for later use, if and when input power (e.g., Vdd 152 and/or VSPD 156, FIG. 1) is lost. In some implementations, for a given storage device (e.g., storage device 120-1), the energy storage device (e.g., energy storage device 410, FIG. 4) is charged prior to the storage device becoming available to the host system (e.g., computer system 110) for certain operations (e.g., read and/or write operations), and this charging can result in high initial charge currents. In a host system (e.g., computer system 110) with multiple storage device slots (e.g., 16 DIMM device slots) populated by multiple storage devices (e.g., 12 DIMM devices populated), power-on operations of the storage devices (e.g., storage devices 120, 520) are important for managing power demands on the host system during power-on (sometimes called power-up) conditions. Furthermore, in some cases, charging the energy storage devices of all the DIMM devices takes longer than charging the energy storage devices of a subset of the DIMM devices. Thus, in some cases, charging the energy storage devices of a subset of the DIMM devices before charging the energy storage devices of other DIMM devices in the data storage system enables the subset of the DIMM devices to become available to the host system (e.g., for read and/or write operations) faster than charging the energy storage devices of all the DIMM devices simultaneously and making all the DIMM devices available to the host system only after charging the energy storage devices of all the DIMM devices in the data storage system.


In some embodiments, data storage system 500 uses a staggered approach to power on storage devices 120, 520 to stagger the high initial charge currents associated with charging each of the energy storage devices. In some embodiments, charging of the energy storage device on each storage device is delayed by a time delay determined in accordance with a unique location associated with each storage device. In an example, the first group includes 8 storage devices (e.g., storage device 120-1 though storage device 120-8) and the storage devices are located in slot 0 though slot 7, respectively (e.g., storage device 120-1 is located in slot 0, storage device 120-2 is located in slot 1, . . . , and storage device 120-8 is located in slot 7). In some embodiments, a general DIMM slot includes three input signals that are normally used for System Management Bus (SMBus) addressing and in some embodiments, each signal has a pull-up resistor on the motherboard of the host system (e.g., computer system 110). The host system sets the state of these three input signals for each slot such that each of the 8 slots (e.g., slot 0 through slot 7) has a unique address (sometimes called slot location). For example, in some embodiments, slot 0 has an address of 000 (in binary), slot 1 has an address of 001, slot 2 has an address of 010, and so on.


In some embodiments, the supervisory controller associated with each storage device detects the unique address associated with the storage device (e.g., the slot location) and determines a time delay for the storage device based on the address. In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes using a predefined time interval to determine the time delay. In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes multiplying the unique address by a predefined time interval to determine the time delay.


For example, in some embodiments, using the example above where storage devices 120-1 through storage devices 120-8 are located in slot 0 through slot 7, respectively, and using a predefined time interval (sometimes called stagger time) of 50 milliseconds (ms) to determine the time delay, supervisory controller 124-1 detects that storage device 120-1 is located in slot 0 with an address of 000 and determines a time delay for storage device 120-1 of 0 ms (i.e., 0*50 ms), accordingly. Similarly, supervisory controller 124-2 detects that storage device 120-2 is located in slot 1 with an address of 001 and determines a time delay for storage device 120-2 of 50 ms (i.e., 1*50 ms), accordingly, supervisory controller 124-3 detects that storage device 120-3 is located in slot 2 with an address of 010 and determines a time delay for storage device 120-3 of 100 ms (i.e., 2*50 ms), accordingly, and so on (e.g., time delay for storage device 120-4 in slot 3 is 150 ms, time delay for storage device 120-5 in slot 4 is 200 ms, time delay for storage device 120-6 in slot 5 is 250 ms, time delay for storage device 120-7 in slot 6 is 300 ms, and time delay for storage device 120-8 in slot 7 is 350 ms). Although 50 ms is used as the predefined time interval in this example, in other embodiments, a shorter or longer predefined time interval may be used. In some embodiments, the predefined time interval is less than a charge time to charge the energy storage device to a predefined level, as discussed in more detail with respect to FIG. 6 below.


In some embodiments, the supervisory controller associated with each storage device detects the address associated with the storage device (e.g., the slot location) and one or more additional signals (e.g., a group number) and determines a time delay for the storage device based on the unique location associated with the storage device (e.g., the address and group number of the storage device). For example, in some embodiments, data storage system 500 has 12 storage devices populated, with 8 storage devices populated in a first group (e.g., storage device 120-1 though storage device 120-8) and 4 storage devices populated in a second group (e.g., storage device 520-1 through storage device 520-4). In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes multiplying the address by a predefined time interval to determine the time delay and further adding a group time delay. For example, in some embodiments, if the predefined time interval is 50 ms, the group time delay for the first group is 0 ms, and the group time delay for the second group is 400 ms, the storage devices in the first group are staggered by 50 ms intervals, starting with 0 ms, and the storage devices in the second group are staggered by 50 ms intervals, starting with 400 ms (e.g., time delay for a storage device=(slot location*predefined time interval)+group time delay). In that example, storage device 120-1 (e.g., located in slot 0 of the first group) has a time delay of 0 ms (i.e., (0*50 ms)+0 ms), storage device 120-2 (e.g., located in slot 1 of the first group) has a time delay of 50 ms (i.e., (1*50 ms)+0 ms), storage device 120-3 (e.g., located in slot 2 of the first group) has a time delay of 100 ms (i.e., (2*50 ms)+0 ms), and so on. Using the same example, storage device 520-1 (e.g., located in slot 0 of the second group) has a time delay of 400 ms (i.e., (0*50 ms)+400 ms), storage device 520-2 (e.g., located in slot 1 of the second group) has a time delay of 450 ms (i.e., (1*50 ms)+400 ms), storage device 520-3 (e.g., located in slot 2 of the second group) has a time delay of 500 ms (i.e., (2*50 ms)+400 ms), and storage device 520-3 (e.g., located in slot 2 of the second group) has a time delay of 500 ms (i.e., (2*50 ms)+400 ms).


In some embodiments, the supervisory controller associated with each storage device obtains a time delay for the storage device from non-volatile memory in the storage device (e.g. in time delay table 226, FIG. 2). For example, in some embodiments, a time delay table stores a plurality of predefined time delays (e.g., time delays associated with various unique locations), and the supervisory controller associated with each storage device uses the time delay associated with the unique location for the storage device. As one example, using the example above, supervisory controller 524-1 detects that storage device 520-1 is located in slot 0 of the second group and obtains the corresponding time delay from a time delay table in non-volatile memory in storage device 520-1. In other embodiments, the supervisory controller associated with each storage device obtains a time delay for the storage device from a host system (e.g., computer system 110).



FIG. 6 illustrates a sequence 600 of charge currents over time, in accordance with some embodiments. In some embodiments, sequence 600 illustrates charge currents associated with charging three energy storage devices in three storage devices, respectively (e.g., energy storage devices 410-1 through 410-3 in storage devices 120-1 through 120-3, FIG. 5). Charge currents 602-a, 602-b, 602-c shown in FIG. 6 have been simplified for illustrative purposes, but generally show that when an energy storage device (e.g., one or more capacitors) is initially charged, the initial charge current is high and then levels off. In some embodiments, charge current 602-a illustrates the charge current associated with charging a first energy storage device (e.g., in storage device 120-1, FIG. 5), charge current 602-b illustrates the charge current associated with charging a second energy storage device (e.g., in storage device 120-2, FIG. 5), and charge current 602-c illustrates the charge current associated with charging a third energy storage device (e.g., in storage device 120-3, FIG. 5). In this example, charge current 602-a begins at time 0, charge current 602-b begins after a time period 604, and charge current 602-c begins after a time period 606. Time period 608 illustrates a charge time to charge the first energy storage device (e.g., in storage device 120-1, FIG. 5) to a predefined level.


Using the example discussed above with respect to FIG. 5, storage device 120-1 is located in slot 0, storage device 120-2 is located in slot 1, and storage device 120-3 is located in slot 2. In this example, sequence 600 illustrates a staggered approach to power on storage devices 120-1 through 120-3 to stagger the high initial charge currents associated with charging each of the energy storage devices. In some embodiments, as discussed above with respect to FIG. 5, using a predefined time interval (e.g., 50 ms) and/or the unique location of each storage device, a controller of each storage device determines the time delay for the storage device (e.g., supervisory controller 124-1 determines a time delay for storage device 120-1 of 0 ms, supervisory controller 124-2 determines a time delay for storage device 120-2 of 50 ms, and supervisory controller 124-3 determines a time delay for storage device 120-3 of 100 ms). In some embodiments, at least one power-on operation of the storage device (e.g., charging of the energy storage device) is delayed by the determined time delay for the storage device. Thus, storage device 120-1 starts charging its energy storage device at time 0 (e.g., at 0 ms), storage device 120-2 starts charging its energy storage device after time period 604 (e.g., at 50 ms), and storage device 120-3 starts charging its energy storage device after time period 606 (e.g., at 100 ms). Further, the energy storage device of storage device 120-1 is charged to a predefined level (e.g., charged to 100%) by time period 608. In some embodiments, the predefined time interval (e.g., time period 604) is less than a charge time to charge an energy storage device to a predefined level (e.g., time period 608). Thus, power-on operations of multiple storage devices may overlap, but the initial high charge current associated with charging the energy storage devices are staggered accordingly.



FIGS. 7A-7C illustrate a flowchart representation of a method 700 of power management of a plurality of storage device slots configured to be populated by two or more storage devices, in accordance with some embodiments. At least in some embodiments, method 700 is performed by a storage device (e.g., storage device 120, FIG. 1) or one or more components of the storage device (e.g., supervisory controller 124, power fail module 126, memory controller 128, and/or NVM controllers 130, FIG. 1), where the storage device is operatively coupled with a host system (e.g., computer system 110, FIG. 1). In some embodiments, method 700 is governed by instructions that are stored in a non-transitory computer readable storage medium and that are executed by one or more processors of a device, such as the one or more processors 202 of supervisory controller 124, as shown in FIG. 2.


For at least one storage device populated in a slot of a plurality of storage device slots, the plurality of storage device slots configured to be populated by two or more storage devices (702), the storage device (e.g., storage device 120, FIG. 1) detects (704) a unique location associated with the storage device. As described above with respect to FIG. 5, in some embodiments, the unique location associated with the storage device includes an address (or a slot location), while in other embodiments, the unique location associated with the storage device includes an address or a slot location (e.g., slot location 0) and one or more other location indicators (e.g., a group number). For example, in some embodiments, the unique location associated with storage device 120-2 (FIG. 5) is slot location 1 of group number 1, as described above with respect to FIG. 5. In some embodiments, a location module (e.g., location module 210, FIG. 2) is used to detect a unique location associated with the storage device, as described above with respect to FIG. 2.


In some embodiments, detecting the unique location associated with the storage device includes monitoring (706) signals used for System Management Bus (SMBus) addressing. As described above with respect to FIG. 5, in some embodiments, a general DIMM slot includes three input signals that are normally used for SMBus addressing. In some embodiments, each signal has a pull-up resistor on the motherboard of a host system (e.g., computer system 110, FIG. 1), and the host system sets the state of these three input signals for each slot such that each slot (e.g., slot 0 through slot 7) has a unique address (or a slot location). For example, in some embodiments, the monitored signals used for SMBus addressing for storage device 120-2 (FIG. 5) indicate an address (e.g., 001) or a slot location (e.g., slot location 1), as described above with respect to FIG. 5. In some embodiments, a monitoring module (e.g., monitoring module 212, FIG. 2) is used to monitor signals used for SMBus addressing, as described above with respect to FIG. 2.


In some embodiments, detecting the unique location associated with the storage device includes monitoring (708) signals used for SMBus addressing and monitoring one or more additional signals. In some embodiments, the one or more additional signals include one or more location indicators (e.g., a group number). In some embodiments, for example, the signals used for SMBus addressing (e.g., three input signals) provide unique addresses (e.g., slot locations) for eight storage devices. In some embodiments, where more than eight storage devices are populated in the plurality of storage device slots, one or more storage devices are grouped in a first group and one or more other storage devices are grouped in a second group, and detecting the unique address includes monitoring signals used for SMBus addressing and monitoring a respective group number. For example, in some embodiments, the monitored signals used for SMBus addressing and the monitored one or more additional signals for storage device 120-2 (FIG. 5) indicate an address of 001 (e.g., slot location 1) and a group number of 1 (e.g., storage device 120-2 is in the first group). In some embodiments, a monitoring module (e.g., monitoring module 212, FIG. 2) is used to monitor signals used for SMBus addressing and monitor one or more additional signals, as described above with respect to FIG. 2.


In some embodiments, the storage device determines (710) a time delay for the storage device in accordance with the unique location associated with the storage device. In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes determining the time delay for the storage device in accordance with the address (or the slot location) of the storage device. Using the example above, in some embodiments, determining the time delay for storage device 120-2 (FIG. 5) in accordance with the unique location associated with storage device 120-2 includes determining the time delay for storage device 120-2 in accordance with its address (e.g., 001 or slot location 1). In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes determining the time delay for the storage device in accordance with the address (or the slot location) of the storage device and in accordance with one or more location indicators (e.g., group number) of the storage device. Using the example above, in some embodiments, determining the time delay for storage device 120-2 (FIG. 5) in accordance with the unique location associated with storage device 120-2 includes determining the time delay for storage device 120-2 in accordance with the address (e.g., 001) and the group number (e.g., 1) of the storage device 120-2. In some embodiments, a time delay module (e.g., time delay module 214, FIG. 2) is used to determine a time delay for the storage device in accordance with the unique location associated with the storage device, as described above with respect to FIG. 2.


In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes obtaining (712) the time delay from non-volatile memory in the storage device. In some embodiments, the time delay (sometimes called stagger time) for the storage device is stored in non-volatile memory of the storage device (e.g., in time delay table 226 of supervisory controller 124, FIG. 2). In some embodiments, supervisory controller 124 obtains the time delay associated with the unique location for the storage device. As one example, using the example above, supervisory controller 224-2 detects that storage device 120-2 is located in slot 1 of the first group and obtains the corresponding time delay from non-volatile memory in storage device 120-2. In some embodiments, an obtaining module (e.g., obtaining module 216, FIG. 2) is used to obtain the time delay from non-volatile memory in the storage device, as described above with respect to FIG. 2.


In some embodiments, the non-volatile memory stores a single predefined time interval. In some embodiments, a time delay table (e.g., time delay table 226, FIG. 2) stores a plurality of predefined time delays (e.g., time delays associated with various unique locations). In some embodiments, the plurality of predefined time delays is not sequential (e.g., 0 ms, 100 ms, 50 ms, and 150 ms for slots 0 through 3). In some embodiments, the predefined time delays are not evenly spaced (e.g., 0 ms, 50 ms, 100 ms, 200 ms, 250, 350 ms, etc.).


In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes obtaining (714) the time delay from a host system (e.g., computer system 110, FIGS. 1 and 5). In some embodiments, the time delay is obtained from the host system through a host interface (e.g., host interface 222, FIG. 1). In some embodiments, for example, storage device 120-2 obtains a time delay of 50 ms from a host system (e.g., computer system 110, FIG. 5). In some embodiments, the time delay obtained from the host system corresponds to a predefined time interval used to determine the time delay for the two or more storage devices. In some embodiments, an obtaining module (e.g., obtaining module 216, FIG. 2) is used to obtain the time delay from a host system, as described above with respect to FIG. 2.


In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes using (716) a predefined time interval (e.g., a stagger time) to determine the time delay. In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes multiplying the unique address by a predefined time interval to determine the time delay. For example, in some embodiments, using the example described above with respect to FIG. 5, where storage devices 120-1 through 120-8 are located in slot 0 through slot 7, respectively, and where the predefined time interval is 50 ms, storage device 120-2 is located in slot 1 with an address of 001 and determines a time delay for storage device 120-2 of 50 ms (i.e., 1*50 ms). In some embodiments, determining the time delay for the storage device in accordance with the unique location associated with the storage device includes multiplying the address by a predefined time interval to determine the time delay and further adding a group time delay. For example, in some embodiments, using the example described above with respect to FIG. 5, where storage devices 520-1 through 520-4 are located in slot 0 through slot 3, respectively, where storage devices 520 are in a second group, and where the predefined time interval is 50 ms and the group time delay for the second group is 400 ms, storage device 520-2 is located in slot 1 with an address of 001 and storage device 520-2 is located in the second group. Thus, in that example, the time delay (e.g., time delay=(slot location*predefined time interval)+group time delay) for storage device 520-2 is 450 ms (i.e., (1*50 ms)+400 ms). In some embodiments, a determination module (e.g., determination module 218, FIG. 2) is used to use a predefined time interval (e.g., a stagger time) to determine the time delay, as described above with respect to FIG. 2.


In some embodiments, the predefined time interval is (718) programmable. In some embodiments, the predefined time interval is programmable by a host system (e.g., computer system 110, FIG. 1). In some embodiments, one or more time delays associated with one or more predefined time intervals are stored in non-volatile memory of the storage device (e.g., in time delay table 226, FIG. 2). For example, for a predefined time interval of 50 ms, time delays of 0 ms, 50 ms, 100 ms, 150 ms, etc. are stored for slot location 0, slot location 1, slot location 2, slot location 3, and so on, and for a predefined time interval of 80 ms, time delays of 0 ms, 80 ms, 160 ms, 240 ms, etc. are stored for slot location 0, slot location 1, slot location 2, slot location 3, and so on. In some embodiments, when a host system selects the desired predefined time interval, the storage device uses the corresponding set of time delays. For example, for storage device 120-2 in slot location 1 (FIG. 5), if the predefined time interval is programmed to be 50 ms, the time delay for slot location 1 is 50 ms, and if the predefined time interval is programmed to be 80 ms, the time delay for slot location 1 is 80 ms. In some embodiments, the predefined time interval is programmable by a host system and the storage device computes time delay on the fly.


In some embodiments, each storage device of the two or more storage devices includes an energy storage device, and the predefined time interval is (720) less than a charge time to charge the energy storage device to a predefined level. For example, in some embodiments, referring to FIG. 6, the predefined time interval (e.g., time period 604) is less than a charge time to charge the energy storage device to a predefined level (e.g., time period 608). Thus, in the embodiments where the predefined time interval is less than the charge time, charging of a first storage device (e.g., storage device 120-1, FIG. 5) overlaps with charging of a second storage device (e.g., storage device 120-2, FIG. 5), as shown in FIG. 6 (e.g., charge current 602-a overlaps with charge current 602-b).


In other embodiments, the predefined time interval is equal to a charge time to charge the energy storage device to a predefined level. For example, if the predefined time interval is equal to the charge time, in FIG. 6, charge current 602-b would begin at time period 608 (e.g., time period 604 is equal to time period 608) and would not overlap with charge current 602-a (and would not overlap with charge current 602-c). Thus, in the embodiments where the predefined time interval is equal to the charge time, charging of a first storage device (e.g., storage device 120-1, FIG. 5) does not overlap with charging of a second storage device (e.g., storage device 120-2, FIG. 5).


In some embodiments, the energy storage device includes (722) one or more capacitors. For example, in some embodiments, the energy storage device includes a single capacitor, while in other embodiments, the energy storage device includes a plurality of capacitors. In some embodiments, the energy storage device includes one or more inductors. In some embodiments, the energy storage device includes one or more other passive elements that store energy.


In some embodiments, two or more storage devices of the storage devices populating the plurality of storage device slots have the same time delay. For example, in some embodiments, where six storage device slots are populated, first and second storage devices both have a first time delay, third and fourth storage devices both have a second time delay, and fifth and sixth storage devices both have a third time delay. In some embodiments, a number of storage devices that have a same time delay is programmable.


In some embodiments, the storage device delays (724) at least one power-on operation of the storage device by the time delay for the storage device. In some embodiments, when only one storage device is populated in the plurality of storage device slots, the time delay is zero and power-on of the storage device is not delayed. Using the example above where storage device 120-2 (FIG. 5) is located in slot 1 and the time delay for storage device 120-2 is determined to be 50 ms, at least one power-on operation of storage device 120-2 is delayed by 50 ms. In some embodiments, a power-on delay module (e.g., power-on delay module 220, FIG. 2) of the storage device is used to delay at least one power-on operation of the storage device by the time delay for the storage device, as described above with respect to FIG. 2.


In some embodiments, each storage device of the two or more storage devices includes (726) an energy storage device (e.g., energy storage device 410, FIG. 4). Delaying at least one power-on operation of the storage device by the time delay for the storage device includes delaying charging of the energy storage device by the time delay for the storage device. Using the example above where storage device 120-2 (FIG. 5) is located in slot 1 and the time delay for storage device 120-2 is determined to be 50 ms, charging of the energy storage device on storage device 120-2 (not shown) is delayed by 50 ms. In some embodiments, a control module (e.g., control module 222, FIG. 2) is used to delay charging of the energy storage device by the time delay for the storage device, as described above with respect to FIG. 2.


In some embodiments, each storage device of the two or more storage devices includes (728) an energy storage device. Delaying at least one power-on operation of the storage device by the time delay for the storage device includes delaying enabling of a power regulator (e.g., in power control 127, FIG. 1) dedicated to providing power to the energy storage device (e.g., energy storage device 410, FIG. 4) by the time delay for the storage device. In some embodiments, supervisory controller 124 (FIG. 1) generates separate signals for each power regulator for storage device 120 and controls when each of the power regulators is powered on (e.g., through control line 164, FIG. 1). In some embodiments, a control module (e.g., control module 222, FIG. 2) is used to delay enabling of a power regulator dedicated to providing power to the energy storage device by the time delay for the storage device, as described above with respect to FIG. 2.


In some embodiments, the two or more storage devices include (730) two or more dual in-line memory module (DIMM) devices. In some embodiments, the two or more storage devices include two or more non-volatile memory DIMM devices. In some embodiments, the two or more storage devices include two or more devices compatible with DIMM device slots. For example, in some embodiments, the two or more storage devices are compatible with 240-pin DIMM memory slots using a DDR3 interface specification. In some embodiments, the two or more storage devices include two or more single in-line memory module (SIMM) devices or two or more other types of storage devices.


In some embodiments, the storage device includes (732) a plurality of non-volatile memory (NVM) controllers (e.g., NVM controllers 130, FIG. 1), and for at least one NVM controller (e.g., NVM controller 130-2) of the plurality of NVM controllers, the storage device delays power-on of the NVM controller. In some embodiments, delaying power-on of the NVM controller includes determining a unique identifier for the NVM controller, determining a time delay for the NVM controller in accordance with the unique identifier, and delaying power-on (e.g., delaying reset) of the NVM controller by the time delay. For example, if storage device 120 includes two NVM controllers (e.g., NVM controller 130-1 and NVM controller 130-2), in some embodiments, storage device 120 delays power-on for at least one NVM controller (e.g., NVM controller 130-2). In some embodiments, delaying power-on for at least one NVM controller staggers the power-on for the plurality of NVM controllers in the storage device, which staggers their startup power demand and corresponding inrush currents. In some embodiments, staggering power-on for the plurality of NVM controllers is accomplished in a similar manner as staggering power-on for two or more storage devices, as described above (e.g., delay times are stored in non-volatile memory, delay times are obtained from a host system, and/or delay times are computed on the fly using a predefined time interval and/or a unique identifier). In some embodiments, a power-on delay module (e.g., power-on delay module 220, FIG. 2) is used to, for at least one NVM controller of the plurality of NVM controllers, delay power-on of the NVM controller, as described above with respect to FIG. 2.


In some embodiments, the storage device includes (734) an independent power domain for each NVM controller of the plurality of NVM controllers (e.g., NVM controllers 130, FIG. 1), and the independent power domains for the NVM controllers are powered-on at staggered times. In some embodiments, separate and independent power domains (e.g., separate and independent voltage regulators in power control 127, FIG. 1) for each NVM controller of the plurality of NVM controllers allows the storage device to stagger power-on for the plurality of NVM controllers on the storage device. As discussed above, in some embodiments, a supervisory controller (e.g., supervisory controller 124, FIG. 1) generates separate signals for each voltage regulator for the storage device and controls when each of the voltages regulators is powered on (e.g., through control line 164, FIG. 1). In some embodiments, a control module (e.g., control module 222, FIG. 2) is used to power-on the independent power domains for the NVM controllers at staggered times, as described above with respect to FIG. 2.


In some embodiments, each NVM controller of the plurality of NVM controllers (e.g., NVM controllers 130, FIG. 1) has (736) an independent reset signal, and the reset signals of the plurality of NVM controllers are released at staggered times. In some embodiments, if the storage device uses a single power domain for the plurality of NVM controllers on the storage device, the storage device staggers power-on for the plurality of NVM controllers on the storage device by staggering the reset signals to each NVM controller. In some implementations, the reset signals to the NVM controllers are released at staggered times. The staggered timing of the releasing of the reset signals to each NVM controller effectively staggers the startup power demands of the NVM controllers and corresponding inrush currents. In some embodiments, a control module (e.g., control module 222, FIG. 2) is used to release the reset signals of the plurality of NVM controllers at staggered times, as described above with respect to FIG. 2.


In some embodiments, a storage device includes a plurality of non-volatile memory (NVM) controllers (e.g., NVM controllers 130, FIG. 1), and for at least one NVM controller (e.g., NVM controller 130-2) of the plurality of NVM controllers, the storage device delays power-on of the NVM controller, as discussed above with respect to operation 732. For example, in some embodiments, the storage device delays power-on of at least one NVM controller relative to power-on of another NVM controller of the storage device. In this example, the time delay for the storage device, determined in accordance with the unique location associated with the storage device, determines a time delay for power-on of a first NVM controller of the storage device, while at least one other NVM controller of the storage device is powered on with a different, larger, time delay. For example, each NVM controller of the storage device is assigned a time delay offset in accordance with a unique identifier of the NVM controller (e.g., an internal bus address, or memory mapped address).


In some embodiments, a data storage system 100 (FIG. 1) includes a single storage device 120 having a plurality of non-volatile memory (NVM) controllers (e.g., NVM controllers 130, FIG. 1). In some embodiments, the storage device 120 delays power-on of at least one NVM controller relative to power-on of another NVM controller of the storage device. For example, each NVM controller of the storage device is assigned a time delay offset and is powered on at a time corresponding to its assigned time delay offset. For example, each NVM controller of the storage device is assigned a time delay offset in accordance with a unique identifier of the NVM controller (e.g., an internal bus address, or memory mapped address).


It will be understood that, although the terms “first,” “second,” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first NVM controller could be termed a second NVM controller, and, similarly, a second NVM controller could be termed a first NVM controller, without changing the meaning of the description, so long as all occurrences of the “first NVM controller” are renamed consistently and all occurrences of the “second NVM controller” are renamed consistently. The first NVM controller and the second NVM controller are both NVM controllers, but they are not the same NVM controller.


The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the claims. As used in the description of the embodiments and the appended claims, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.


As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in accordance with a determination” or “in response to detecting,” that a stated condition precedent is true, depending on the context. Similarly, the phrase “if it is determined [that a stated condition precedent is true]” or “if [a stated condition precedent is true]” or “when [a stated condition precedent is true]” may be construed to mean “upon determining” or “in response to determining” or “in accordance with a determination” or “upon detecting” or “in response to detecting” that the stated condition precedent is true, depending on the context.


The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain principles of operation and practical applications, to thereby enable others skilled in the art.

Claims
  • 1. A method of power management of a storage system having a plurality of storage device slots configured to be populated by two or more storage devices, the method comprising: for at least one storage device populated in a slot of the plurality of storage device slots: detecting a unique location associated with the storage device;determining a time delay for the storage device in accordance with the unique location associated with the storage device; anddelaying at least one power-on operation of the storage device by the time delay for the storage device;wherein detecting the unique location associated with the storage device includes monitoring signals used for System Management Bus (SMBus) addressing.
  • 2. The method of claim 1, wherein the two or more storage devices include two or more dual in-line memory module (DIMM) devices.
  • 3. The method of claim 1, wherein detecting the unique location associated with the storage device further includes monitoring one or more additional signals.
  • 4. The method of claim 1, wherein the two or more storage devices are grouped in two or more groups, and the time delay for a respective storage device corresponding to a respective group number is determined in accordance with the respective group number.
  • 5. The method of claim 1, wherein determining the time delay for the storage device in accordance with the unique location associated with the storage device includes using a predefined time interval to determine the time delay.
  • 6. The method of claim 5, wherein the predefined time interval is programmable.
  • 7. The method of claim 1, wherein each storage device of the two or more storage devices includes an energy storage device, and delaying at least one power-on operation of the storage device by the time delay for the storage device includes delaying charging of the energy storage device by the time delay for the storage device.
  • 8. The method of claim 7, wherein the energy storage device includes one or more capacitors.
  • 9. The method of claim 1, wherein each storage device of the two or more storage devices includes an energy storage device, and delaying at least one power-on operation of the storage device by the time delay for the storage device includes delaying enabling of a power regulator dedicated to providing power to the energy storage device by the time delay for the storage device.
  • 10. The method of claim 1, wherein the storage device includes a plurality of non-volatile memory (NVM) controllers, the method further comprising: for at least one NVM controller of the plurality of NVM controllers, delaying power-on of the NVM controller.
  • 11. The method of claim 10, wherein the storage device includes an independent power domain for each NVM controller of the plurality of NVM controllers, and the independent power domains for the NVM controllers are powered-on at staggered times.
  • 12. The method of claim 10, wherein each NVM controller of the plurality of NVM controllers has an independent reset signal, and the reset signals of the plurality of NVM controllers are released at staggered times.
  • 13. A method of power management of a storage system having a plurality of storage device slots configured to be populated by two or more storage devices, the method comprising: for at least one storage device populated in a slot of the plurality of storage device slots: detecting a unique location associated with the storage device;determining a time delay for the storage device in accordance with the unique location associated with the storage device; anddelaying at least one power-on operation of the storage device by the time delay for the storage device;wherein the time delay determined for the storage device in accordance with the unique location associated with the storage device corresponds to a time delay obtained from non-volatile memory in the storage device.
  • 14. A storage device of a storage system, comprising: an interface for operatively coupling the storage device with a host system distinct from the storage system;an energy storage device; anda controller with one or more processors and memory, the controller configured to: detect a unique location associated with the storage device;determine a time delay for the storage device in accordance with the unique location associated with the storage device; anddelay at least one power-on operation of the storage device by the time delay for the storage device;wherein the controller is configured to monitor, for detecting the unique location associated with the storage device, signals used for System Management Bus (SMBus) addressing.
  • 15. The storage device of claim 14, wherein the storage device includes a dual in-line memory module (DIMM) device.
  • 16. The storage device of claim 14, wherein the controller is configured to delay charging of the energy storage device by the time delay for the storage device.
  • 17. The storage device of claim 14, wherein the controller is configured to delay enabling of a power regulator dedicated to providing power to the energy storage device by the time delay for the storage device.
  • 18. The storage device of claim 14, wherein the storage device includes a plurality of non-volatile memory (NVM) controllers, and the storage device is configured to: for at least one NVM controller of the plurality of NVM controllers, delay power-on of the NVM controller.
  • 19. A non-transitory computer readable storage medium, storing one or more programs for execution by one or more processors of a storage device of a storage system, the one or more programs including instructions for: detecting a unique location associated with the storage device;determining a time delay for the storage device in accordance with the unique location associated with the storage device; anddelaying at least one power-on operation of the storage device by the time delay for the storage device;wherein detecting the unique location associated with the storage device includes monitoring signals used for System Management Bus (SMBus) addressing.
RELATED APPLICATION

This application claims priority to U.S. Provisional Patent Application Ser. No. 61/910,159, filed Nov. 29, 2013, entitled “Power Inrush Management of Storage Devices,” which is hereby incorporated by reference in its entirety.

US Referenced Citations (522)
Number Name Date Kind
4173737 Skerlos et al. Nov 1979 A
4888750 Kryder et al. Dec 1989 A
4916652 Schwarz et al. Apr 1990 A
5129089 Nielsen Jul 1992 A
5270979 Harari et al. Dec 1993 A
5329491 Brown et al. Jul 1994 A
5381528 Brunelle Jan 1995 A
5404485 Ban Apr 1995 A
5488702 Byers et al. Jan 1996 A
5519847 Fandrich et al. May 1996 A
5530705 Malone, Sr. Jun 1996 A
5537555 Landry et al. Jul 1996 A
5551003 Mattson et al. Aug 1996 A
5636342 Jeffries Jun 1997 A
5657332 Auclair et al. Aug 1997 A
5666114 Brodie et al. Sep 1997 A
5708849 Coke et al. Jan 1998 A
5765185 Lambrache et al. Jun 1998 A
5890193 Chevallier Mar 1999 A
5930188 Roohparvar Jul 1999 A
5936884 Hasbun et al. Aug 1999 A
5943692 Marberg et al. Aug 1999 A
5946714 Miyauchi Aug 1999 A
5982664 Watanabe Nov 1999 A
6000006 Bruce et al. Dec 1999 A
6006345 Berry, Jr. Dec 1999 A
6016560 Wada et al. Jan 2000 A
6018304 Bessios Jan 2000 A
6044472 Crohas Mar 2000 A
6070074 Perahia et al. May 2000 A
6104304 Clark et al. Aug 2000 A
6119250 Nishimura et al. Sep 2000 A
6138261 Wilcoxson et al. Oct 2000 A
6182264 Ott Jan 2001 B1
6192092 Dizon et al. Feb 2001 B1
6260120 Blumenau et al. Jul 2001 B1
6295592 Jeddeloh Sep 2001 B1
6311263 Barlow et al. Oct 2001 B1
6408394 Vander Kamp Jun 2002 B1
6412042 Paterson et al. Jun 2002 B1
6442076 Roohparvar Aug 2002 B1
6449625 Wang Sep 2002 B1
6484224 Robins et al. Nov 2002 B1
6516437 Van Stralen et al. Feb 2003 B1
6564285 Mills et al. May 2003 B1
6678788 O'Connell Jan 2004 B1
6728879 Atkinson Apr 2004 B1
6757768 Potter et al. Jun 2004 B1
6775792 Ulrich et al. Aug 2004 B2
6810440 Micalizzi, Jr. et al. Oct 2004 B2
6836808 Bunce et al. Dec 2004 B2
6836815 Purcell et al. Dec 2004 B1
6842436 Moeller Jan 2005 B2
6865650 Morley et al. Mar 2005 B1
6871257 Conley et al. Mar 2005 B2
6895464 Chow et al. May 2005 B2
6934755 Saulpaugh et al. Aug 2005 B1
6966006 Pacheco Nov 2005 B2
6978343 Ichiriu Dec 2005 B1
6980985 Amer-Yahia et al. Dec 2005 B1
6981205 Fukushima et al. Dec 2005 B2
6988171 Beardsley et al. Jan 2006 B2
7020017 Chen et al. Mar 2006 B2
7024514 Mukaida et al. Apr 2006 B2
7028165 Roth et al. Apr 2006 B2
7032123 Kane et al. Apr 2006 B2
7043505 Teague et al. May 2006 B1
7076598 Wang Jul 2006 B2
7100002 Shrader Aug 2006 B2
7102860 Wenzel Sep 2006 B2
7111293 Hersh et al. Sep 2006 B1
7126873 See et al. Oct 2006 B2
7133282 Sone Nov 2006 B2
7155579 Neils et al. Dec 2006 B1
7162678 Saliba Jan 2007 B2
7173852 Gorobets et al. Feb 2007 B2
7184446 Rashid et al. Feb 2007 B2
7212440 Gorobets May 2007 B2
7269755 Moshayedi et al. Sep 2007 B2
7275170 Suzuki Sep 2007 B2
7295479 Yoon et al. Nov 2007 B2
7328377 Lewis et al. Feb 2008 B1
7426633 Thompson et al. Sep 2008 B2
7486561 Mokhlesi Feb 2009 B2
7516292 Kimura et al. Apr 2009 B2
7523157 Aguilar, Jr. et al. Apr 2009 B2
7527466 Simmons May 2009 B2
7529466 Takahashi May 2009 B2
7533214 Aasheim et al. May 2009 B2
7546478 Kubo Jun 2009 B2
7566987 Black Jul 2009 B2
7571277 Mizushima Aug 2009 B2
7574554 Tanaka et al. Aug 2009 B2
7596643 Merry, Jr. et al. Sep 2009 B2
7669003 Sinclair et al. Feb 2010 B2
7681106 Jarrar et al. Mar 2010 B2
7685494 Varnica et al. Mar 2010 B1
7707481 Kirschner et al. Apr 2010 B2
7761655 Mizushima et al. Jul 2010 B2
7765454 Passint Jul 2010 B2
7774390 Shin Aug 2010 B2
7809836 Mihm et al. Oct 2010 B2
7840762 Oh et al. Nov 2010 B2
7870326 Shin et al. Jan 2011 B2
7890818 Kong et al. Feb 2011 B2
7913022 Baxter Mar 2011 B1
7925960 Ho et al. Apr 2011 B2
7934052 Prins et al. Apr 2011 B2
7945825 Cohen et al. May 2011 B2
7954041 Hong et al. May 2011 B2
7971112 Murata Jun 2011 B2
7974368 Shieh et al. Jul 2011 B2
7978516 Olbrich et al. Jul 2011 B2
7996642 Smith Aug 2011 B1
8006161 Lestable et al. Aug 2011 B2
8032724 Smith Oct 2011 B1
8041884 Chang Oct 2011 B2
8042011 Nicolaidis et al. Oct 2011 B2
8069390 Lin Nov 2011 B2
8190967 Hong et al. May 2012 B2
8250380 Guyot Aug 2012 B2
8254181 Hwang et al. Aug 2012 B2
8259506 Sommer et al. Sep 2012 B1
8261020 Krishnaprasad et al. Sep 2012 B2
8312349 Reche et al. Nov 2012 B2
8385117 Sakurada et al. Feb 2013 B2
8412985 Bowers et al. Apr 2013 B1
8429436 Fillingim et al. Apr 2013 B2
8438459 Cho et al. May 2013 B2
8453022 Katz May 2013 B2
8510499 Banerjee Aug 2013 B1
8531888 Chilappagari et al. Sep 2013 B2
8554984 Yano et al. Oct 2013 B2
8627117 Johnston Jan 2014 B2
8634248 Sprouse et al. Jan 2014 B1
8694854 Dar et al. Apr 2014 B1
8724789 Altberg et al. May 2014 B2
8832384 de la Iglesia Sep 2014 B1
8874992 Desireddi et al. Oct 2014 B2
8885434 Kumar Nov 2014 B2
8898373 Kang et al. Nov 2014 B1
8909894 Singh et al. Dec 2014 B1
8910030 Goel Dec 2014 B2
8923066 Subramanian et al. Dec 2014 B1
9043517 Sprouse et al. May 2015 B1
9128690 Lotzenburger et al. Sep 2015 B2
9329789 Chu et al. May 2016 B1
20010026949 Ogawa et al. Oct 2001 A1
20010050824 Buch Dec 2001 A1
20020024846 Kawahara et al. Feb 2002 A1
20020032891 Yada et al. Mar 2002 A1
20020036515 Eldridge et al. Mar 2002 A1
20020083299 Van Huben et al. Jun 2002 A1
20020099904 Conley Jul 2002 A1
20020116651 Beckert et al. Aug 2002 A1
20020122334 Lee et al. Sep 2002 A1
20020152305 Jackson et al. Oct 2002 A1
20020162075 Talagala et al. Oct 2002 A1
20020165896 Kim Nov 2002 A1
20030041299 Kanazawa et al. Feb 2003 A1
20030043829 Rashid et al. Mar 2003 A1
20030079172 Yamagishi et al. Apr 2003 A1
20030088805 Majni et al. May 2003 A1
20030093628 Matter et al. May 2003 A1
20030163594 Aasheim et al. Aug 2003 A1
20030163629 Conley et al. Aug 2003 A1
20030188045 Jacobson Oct 2003 A1
20030189856 Cho et al. Oct 2003 A1
20030198100 Matsushita et al. Oct 2003 A1
20030204341 Guliani et al. Oct 2003 A1
20030212719 Yasuda et al. Nov 2003 A1
20030225961 Chow et al. Dec 2003 A1
20040024957 Lin et al. Feb 2004 A1
20040024963 Talagala et al. Feb 2004 A1
20040057575 Zhang et al. Mar 2004 A1
20040062157 Kawabe Apr 2004 A1
20040073829 Olarig Apr 2004 A1
20040085849 Myoung et al. May 2004 A1
20040114265 Talbert Jun 2004 A1
20040143710 Walmsley Jul 2004 A1
20040148561 Shen et al. Jul 2004 A1
20040153902 Machado et al. Aug 2004 A1
20040158775 Shibuya et al. Aug 2004 A1
20040167898 Margolus et al. Aug 2004 A1
20040181734 Saliba Sep 2004 A1
20040199714 Estakhri et al. Oct 2004 A1
20040210706 In et al. Oct 2004 A1
20040237018 Riley Nov 2004 A1
20050060456 Shrader et al. Mar 2005 A1
20050060501 Shrader Mar 2005 A1
20050073884 Gonzalez et al. Apr 2005 A1
20050108588 Yuan May 2005 A1
20050114587 Chou et al. May 2005 A1
20050138442 Keller, Jr. et al. Jun 2005 A1
20050144358 Conley et al. Jun 2005 A1
20050144361 Gonzalez et al. Jun 2005 A1
20050144367 Sinclair Jun 2005 A1
20050144516 Gonzalez et al. Jun 2005 A1
20050154825 Fair Jul 2005 A1
20050172065 Keays Aug 2005 A1
20050172207 Radke et al. Aug 2005 A1
20050193161 Lee et al. Sep 2005 A1
20050201148 Chen et al. Sep 2005 A1
20050210348 Totsuka Sep 2005 A1
20050231765 So et al. Oct 2005 A1
20050249013 Janzen et al. Nov 2005 A1
20050251617 Sinclair et al. Nov 2005 A1
20050257120 Gorobets et al. Nov 2005 A1
20050273560 Hulbert et al. Dec 2005 A1
20050281088 Ishidoshiro et al. Dec 2005 A1
20050289314 Adusumilli et al. Dec 2005 A1
20060010174 Nguyen et al. Jan 2006 A1
20060039196 Gorobets et al. Feb 2006 A1
20060039227 Lai et al. Feb 2006 A1
20060053246 Lee Mar 2006 A1
20060062054 Hamilton et al. Mar 2006 A1
20060069932 Oshikawa et al. Mar 2006 A1
20060085671 Majni et al. Apr 2006 A1
20060087893 Nishihara et al. Apr 2006 A1
20060103480 Moon et al. May 2006 A1
20060107181 Dave et al. May 2006 A1
20060136570 Pandya Jun 2006 A1
20060136655 Gorobets et al. Jun 2006 A1
20060136681 Jain et al. Jun 2006 A1
20060156177 Kottapalli et al. Jul 2006 A1
20060184738 Bridges et al. Aug 2006 A1
20060195650 Su et al. Aug 2006 A1
20060209592 Li et al. Sep 2006 A1
20060224841 Terai et al. Oct 2006 A1
20060244049 Yaoi et al. Nov 2006 A1
20060259528 Dussud et al. Nov 2006 A1
20060265568 Burton Nov 2006 A1
20060291301 Ziegelmayer Dec 2006 A1
20070011413 Nonaka et al. Jan 2007 A1
20070033376 Sinclair et al. Feb 2007 A1
20070058446 Hwang et al. Mar 2007 A1
20070061597 Holtzman et al. Mar 2007 A1
20070076479 Kim et al. Apr 2007 A1
20070081408 Kwon et al. Apr 2007 A1
20070083697 Birrell et al. Apr 2007 A1
20070088716 Brumme et al. Apr 2007 A1
20070091677 Lasser et al. Apr 2007 A1
20070101096 Gorobets May 2007 A1
20070106679 Perrin et al. May 2007 A1
20070113019 Beukema et al. May 2007 A1
20070133312 Roohparvar Jun 2007 A1
20070147113 Mokhlesi et al. Jun 2007 A1
20070150790 Gross et al. Jun 2007 A1
20070156842 Vermeulen et al. Jul 2007 A1
20070157064 Falik et al. Jul 2007 A1
20070174579 Shin Jul 2007 A1
20070180188 Fujibayashi et al. Aug 2007 A1
20070180346 Murin Aug 2007 A1
20070191993 Wyatt Aug 2007 A1
20070201274 Yu et al. Aug 2007 A1
20070204128 Lee et al. Aug 2007 A1
20070208901 Purcell et al. Sep 2007 A1
20070234143 Kim Oct 2007 A1
20070245061 Harriman Oct 2007 A1
20070245099 Gray et al. Oct 2007 A1
20070263442 Cornwall et al. Nov 2007 A1
20070268754 Lee et al. Nov 2007 A1
20070277036 Chamberlain et al. Nov 2007 A1
20070279988 Nguyen Dec 2007 A1
20070291556 Kamei Dec 2007 A1
20070294496 Goss et al. Dec 2007 A1
20070300130 Gorobets Dec 2007 A1
20080013390 Zipprich-Rasch Jan 2008 A1
20080019182 Yanagidaira et al. Jan 2008 A1
20080022163 Tanaka et al. Jan 2008 A1
20080028275 Chen et al. Jan 2008 A1
20080043871 Latouche et al. Feb 2008 A1
20080052446 Lasser et al. Feb 2008 A1
20080052451 Pua et al. Feb 2008 A1
20080056005 Aritome Mar 2008 A1
20080059602 Matsuda et al. Mar 2008 A1
20080071971 Kim et al. Mar 2008 A1
20080077841 Gonzalez et al. Mar 2008 A1
20080077937 Shin et al. Mar 2008 A1
20080086677 Yang et al. Apr 2008 A1
20080112226 Mokhlesi May 2008 A1
20080141043 Flynn et al. Jun 2008 A1
20080144371 Yeh et al. Jun 2008 A1
20080147714 Breternitz et al. Jun 2008 A1
20080147964 Chow et al. Jun 2008 A1
20080147998 Jeong Jun 2008 A1
20080148124 Zhang et al. Jun 2008 A1
20080163030 Lee Jul 2008 A1
20080168191 Biran et al. Jul 2008 A1
20080168319 Lee et al. Jul 2008 A1
20080170460 Oh et al. Jul 2008 A1
20080180084 Dougherty et al. Jul 2008 A1
20080209282 Lee et al. Aug 2008 A1
20080229000 Kim Sep 2008 A1
20080229003 Mizushima et al. Sep 2008 A1
20080229176 Arnez et al. Sep 2008 A1
20080270680 Chang Oct 2008 A1
20080282128 Lee et al. Nov 2008 A1
20080285351 Shlick et al. Nov 2008 A1
20080313132 Hao et al. Dec 2008 A1
20080320110 Pathak Dec 2008 A1
20090003046 Nirschl et al. Jan 2009 A1
20090003058 Kang Jan 2009 A1
20090019216 Yamada et al. Jan 2009 A1
20090031083 Willis et al. Jan 2009 A1
20090037652 Yu et al. Feb 2009 A1
20090070608 Kobayashi Mar 2009 A1
20090116283 Ha et al. May 2009 A1
20090125671 Flynn et al. May 2009 A1
20090144598 Yoon et al. Jun 2009 A1
20090158288 Fulton et al. Jun 2009 A1
20090168525 Olbrich et al. Jul 2009 A1
20090172258 Olbrich et al. Jul 2009 A1
20090172259 Prins et al. Jul 2009 A1
20090172260 Olbrich et al. Jul 2009 A1
20090172261 Prins et al. Jul 2009 A1
20090172262 Olbrich et al. Jul 2009 A1
20090172308 Prins et al. Jul 2009 A1
20090172335 Kulkarni et al. Jul 2009 A1
20090172499 Olbrich et al. Jul 2009 A1
20090193058 Reid Jul 2009 A1
20090204823 Giordano et al. Aug 2009 A1
20090207660 Hwang et al. Aug 2009 A1
20090213649 Takahashi et al. Aug 2009 A1
20090222708 Yamaga Sep 2009 A1
20090228761 Perlmutter et al. Sep 2009 A1
20090235128 Eun et al. Sep 2009 A1
20090249160 Gao et al. Oct 2009 A1
20090251962 Yun et al. Oct 2009 A1
20090268521 Ueno et al. Oct 2009 A1
20090292972 Seol et al. Nov 2009 A1
20090296466 Kim et al. Dec 2009 A1
20090296486 Kim et al. Dec 2009 A1
20090310422 Edahiro et al. Dec 2009 A1
20090319864 Shrader Dec 2009 A1
20100002506 Cho et al. Jan 2010 A1
20100008175 Sweere et al. Jan 2010 A1
20100011261 Cagno et al. Jan 2010 A1
20100020620 Kim et al. Jan 2010 A1
20100037012 Yano et al. Feb 2010 A1
20100054034 Furuta et al. Mar 2010 A1
20100061151 Miwa et al. Mar 2010 A1
20100091535 Sommer et al. Apr 2010 A1
20100103737 Park Apr 2010 A1
20100110798 Hoei et al. May 2010 A1
20100115206 de la Iglesia et al. May 2010 A1
20100118608 Song et al. May 2010 A1
20100138592 Cheon Jun 2010 A1
20100153616 Garratt Jun 2010 A1
20100161936 Royer et al. Jun 2010 A1
20100174959 No et al. Jul 2010 A1
20100185807 Meng et al. Jul 2010 A1
20100199027 Pucheral et al. Aug 2010 A1
20100199125 Reche Aug 2010 A1
20100199138 Rho Aug 2010 A1
20100202196 Lee et al. Aug 2010 A1
20100202239 Moshayedi et al. Aug 2010 A1
20100208521 Kim et al. Aug 2010 A1
20100257379 Wang et al. Oct 2010 A1
20100262889 Bains Oct 2010 A1
20100281207 Miller et al. Nov 2010 A1
20100281342 Chang et al. Nov 2010 A1
20100306222 Freedman et al. Dec 2010 A1
20100332858 Trantham Dec 2010 A1
20100332863 Johnston Dec 2010 A1
20110010514 Benhase et al. Jan 2011 A1
20110022779 Lund et al. Jan 2011 A1
20110022819 Post et al. Jan 2011 A1
20110051513 Shen et al. Mar 2011 A1
20110066597 Mashtizadeh et al. Mar 2011 A1
20110066806 Chhugani et al. Mar 2011 A1
20110072207 Jin et al. Mar 2011 A1
20110072302 Sartore Mar 2011 A1
20110078407 Lewis Mar 2011 A1
20110078496 Jeddeloh Mar 2011 A1
20110083060 Sakurada et al. Apr 2011 A1
20110099460 Dusija et al. Apr 2011 A1
20110113281 Zhang et al. May 2011 A1
20110122691 Sprouse May 2011 A1
20110131444 Buch et al. Jun 2011 A1
20110138260 Savin Jun 2011 A1
20110173378 Filor et al. Jul 2011 A1
20110179249 Hsiao Jul 2011 A1
20110199825 Han et al. Aug 2011 A1
20110205823 Hemink et al. Aug 2011 A1
20110213920 Frost et al. Sep 2011 A1
20110222342 Yoon et al. Sep 2011 A1
20110225346 Goss et al. Sep 2011 A1
20110228601 Olbrich et al. Sep 2011 A1
20110231600 Tanaka et al. Sep 2011 A1
20110239077 Bal et al. Sep 2011 A1
20110264843 Haines et al. Oct 2011 A1
20110271040 Kamizono Nov 2011 A1
20110283119 Szu et al. Nov 2011 A1
20110289125 Guthery Nov 2011 A1
20110320733 Sanford et al. Dec 2011 A1
20120011393 Roberts et al. Jan 2012 A1
20120017053 Yang et al. Jan 2012 A1
20120023144 Rub Jan 2012 A1
20120026799 Lee Feb 2012 A1
20120054414 Tsai et al. Mar 2012 A1
20120063234 Shiga et al. Mar 2012 A1
20120072639 Goss et al. Mar 2012 A1
20120096217 Son et al. Apr 2012 A1
20120110250 Sabbag et al. May 2012 A1
20120117317 Sheffler May 2012 A1
20120117397 Kolvick et al. May 2012 A1
20120124273 Goss et al. May 2012 A1
20120131286 Faith et al. May 2012 A1
20120151124 Baek et al. Jun 2012 A1
20120151253 Horn Jun 2012 A1
20120151294 Yoo et al. Jun 2012 A1
20120173797 Shen Jul 2012 A1
20120173826 Takaku Jul 2012 A1
20120185750 Hayami Jul 2012 A1
20120195126 Roohparvar Aug 2012 A1
20120203804 Burka et al. Aug 2012 A1
20120203951 Wood et al. Aug 2012 A1
20120210095 Nellans et al. Aug 2012 A1
20120216079 Fai et al. Aug 2012 A1
20120233391 Frost et al. Sep 2012 A1
20120236658 Byom et al. Sep 2012 A1
20120239858 Melik-Martirosian Sep 2012 A1
20120239868 Ryan et al. Sep 2012 A1
20120239976 Cometti et al. Sep 2012 A1
20120246204 Nalla et al. Sep 2012 A1
20120259863 Bodwin et al. Oct 2012 A1
20120275466 Bhadra et al. Nov 2012 A1
20120278564 Goss et al. Nov 2012 A1
20120284574 Avila et al. Nov 2012 A1
20120284587 Yu et al. Nov 2012 A1
20120297122 Gorobets Nov 2012 A1
20130007073 Varma Jan 2013 A1
20130007343 Rub et al. Jan 2013 A1
20130007381 Palmer Jan 2013 A1
20130007543 Goss et al. Jan 2013 A1
20130024735 Chung et al. Jan 2013 A1
20130031438 Hu et al. Jan 2013 A1
20130036418 Yadappanavar et al. Feb 2013 A1
20130038380 Cordero et al. Feb 2013 A1
20130047045 Hu et al. Feb 2013 A1
20130058145 Yu et al. Mar 2013 A1
20130070527 Sabbag et al. Mar 2013 A1
20130073784 Ng et al. Mar 2013 A1
20130073798 Kang et al. Mar 2013 A1
20130073924 D'Abreu et al. Mar 2013 A1
20130079942 Smola Mar 2013 A1
20130086131 Hunt et al. Apr 2013 A1
20130086132 Hunt et al. Apr 2013 A1
20130094288 Patapoutian et al. Apr 2013 A1
20130103978 Akutsu Apr 2013 A1
20130110891 Ogasawara et al. May 2013 A1
20130111279 Jeon et al. May 2013 A1
20130111298 Seroff et al. May 2013 A1
20130117606 Anholt et al. May 2013 A1
20130121084 Jeon et al. May 2013 A1
20130124792 Melik-Martirosian et al. May 2013 A1
20130124888 Tanaka et al. May 2013 A1
20130128666 Avila et al. May 2013 A1
20130132647 Melik-Martirosian May 2013 A1
20130132652 Wood et al. May 2013 A1
20130159609 Haas et al. Jun 2013 A1
20130176784 Cometti et al. Jul 2013 A1
20130179646 Okubo et al. Jul 2013 A1
20130191601 Peterson et al. Jul 2013 A1
20130194865 Bandic et al. Aug 2013 A1
20130194874 Mu et al. Aug 2013 A1
20130232289 Zhong et al. Sep 2013 A1
20130238576 Binkert et al. Sep 2013 A1
20130254498 Adachi et al. Sep 2013 A1
20130254507 Islam et al. Sep 2013 A1
20130258738 Barkon et al. Oct 2013 A1
20130265838 Li Oct 2013 A1
20130282955 Parker et al. Oct 2013 A1
20130290611 Biederman et al. Oct 2013 A1
20130297613 Yu Nov 2013 A1
20130301373 Tam Nov 2013 A1
20130304980 Nachimuthu et al. Nov 2013 A1
20130314988 Desireddi et al. Nov 2013 A1
20130343131 Wu et al. Dec 2013 A1
20130346672 Sengupta et al. Dec 2013 A1
20140013027 Jannyavula Venkata et al. Jan 2014 A1
20140013188 Wu et al. Jan 2014 A1
20140025864 Zhang et al. Jan 2014 A1
20140032890 Lee et al. Jan 2014 A1
20140063905 Ahn et al. Mar 2014 A1
20140067761 Chakrabarti et al. Mar 2014 A1
20140071761 Sharon et al. Mar 2014 A1
20140075133 Li et al. Mar 2014 A1
20140082261 Cohen et al. Mar 2014 A1
20140082310 Nakajima Mar 2014 A1
20140082456 Li et al. Mar 2014 A1
20140082459 Li et al. Mar 2014 A1
20140095775 Talagala et al. Apr 2014 A1
20140101389 Nellans et al. Apr 2014 A1
20140115238 Xi et al. Apr 2014 A1
20140122818 Hayasaka et al. May 2014 A1
20140122907 Johnston May 2014 A1
20140136762 Li et al. May 2014 A1
20140136883 Cohen May 2014 A1
20140136927 Li et al. May 2014 A1
20140143505 Sim et al. May 2014 A1
20140153333 Avila et al. Jun 2014 A1
20140157065 Ong Jun 2014 A1
20140173224 Fleischer et al. Jun 2014 A1
20140181458 Loh et al. Jun 2014 A1
20140201596 Baum et al. Jul 2014 A1
20140223084 Lee et al. Aug 2014 A1
20140244578 Winkelstraeter Aug 2014 A1
20140258755 Stenfort Sep 2014 A1
20140269090 Flynn et al. Sep 2014 A1
20140310494 Higgins et al. Oct 2014 A1
20140359044 Davis et al. Dec 2014 A1
20140359381 Takeuchi et al. Dec 2014 A1
20150023097 Khoueir et al. Jan 2015 A1
20150032967 Udayashankar et al. Jan 2015 A1
20150037624 Thompson et al. Feb 2015 A1
20150153799 Lucas Jun 2015 A1
20150153802 Lucas et al. Jun 2015 A1
20150212943 Yang et al. Jul 2015 A1
20150268879 Chu Sep 2015 A1
20150286438 Simionescu et al. Oct 2015 A1
Foreign Referenced Citations (16)
Number Date Country
1 299 800 Apr 2003 EP
1465203 Oct 2004 EP
1 990 921 Nov 2008 EP
2 386 958 Nov 2011 EP
2 620 946 Jul 2013 EP
WO 2007036834 Apr 2007 WO
WO 2007080586 Jul 2007 WO
WO 2008075292 Jun 2008 WO
WO 2008121553 Oct 2008 WO
WO 2008121577 Oct 2008 WO
WO 2009028281 Mar 2009 WO
WO 2009032945 Mar 2009 WO
WO 2009058140 May 2009 WO
WO 2009084724 Jul 2009 WO
WO 2009134576 Nov 2009 WO
WO 2011024015 Mar 2011 WO
Non-Patent Literature Citations (64)
Entry
Invitation to Pay Additional Fees dated Feb. 13, 2015, received in International Patent Application No. PCT/US2014/063949, which corresponds to U.S. Appl. No. 14/135,433, 6 pages (Delpapa).
International Search Report and Written Opinion dated Jan. 21, 2015, received in International Application No. PCT/US2014/059748, which corresponds to U.S. Appl. No. 14/137,511, 13 pages (Dancho).
International Search Report and Written Opinion dated Feb. 18, 2015, received in International Application No. PCT/US2014/066921, which corresponds to U.S. Appl. No. 14/135,260, 13 pages (Fitzpatrick).
Barr, Introduction to Watchdog Timers, Oct. 2001, 3 pgs.
Canim, Buffered Bloom ilters on Solid State Storage, ADMS*10, Singapore, Sep. 13-17, 2010, 8 pgs.
Kang, A Multi-Channel Architecture for High-Performance NAND Flash-Based Storage System, J. Syst. Archit., 53, 9, Sep. 2007, 15 pgs.
Kim, A Space-Efficient Flash Translation Layer for CompactFlash Systems, May 2002, 10 pgs.
Lu, A Forest-structured Bloom Filter with Flash Memory, MSST 2011, Denver, CO, May 23-27, 2011, article, 6 pgs.
Lu, A Forest-structured Bloom Filter with Flash Memory, MSST 2011, Denver, CO, May 23-27, 2011, presentation slides, 25 pgs.
McLean, Information Technology—AT Attachment with Packet Interface Extension, Aug. 19, 1998, 339 pgs.
Park, A High Performance Controller for NAND Flash-Based Solid State Disk (NSSD), Feb. 12-16, 2006, 4 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88133, Mar. 19, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88136, Mar. 19, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88146, Feb. 26, 2009, 10 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88154, Feb. 27, 2009, 8 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88164, Feb. 13, 2009, 6 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88206, Feb. 18, 2009, 8 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88217, Feb. 19, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88229, Feb. 13, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88232, Feb. 19, 2009, 8 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88236, Feb. 19, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US2011/028637, Oct. 27, 2011, 11 pgs.
Pliant Technology, Supplementary ESR, 08866997.3, Feb. 23, 2012, 6 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/042764, Aug. 31, 2012, 12 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/042771, Mar. 4, 2013, 14 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/042775, Sep. 26, 2012, 8 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/059447, Jun. 6, 2013, 12 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/059453, Jun. 6, 2013, 12 pgs.
Sandisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/059459, Feb. 14, 2013, 9 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/065914, May 23, 2013, 7 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/065916, Apr. 5, 2013, 7 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/065919, Jun. 17, 2013, 8 pgs.
SanDisk Enterprise IP LLC, Notification of the Decision to Grant a Patent Right for Patent for Invention, CN 200880127623.8, Jul. 4, 2013, 1 pg.
SanDisk Enterprise IP LLC, Office Action, CN 200880127623.8, Apr. 18, 2012, 12 pgs.
SanDisk Enterprise IP LLC, Office Action, CN 200880127623.8, Dec. 31, 2012, 9 pgs.
SanDisk Enterprise IP LLC, Office Action, JP 2010-540863, Jul. 24, 2012, 3 pgs.
Watchdog Timer and Power Savin Modes, Microchip Technology Inc., 2005, 14 pgs.
Zeidman, 1999 Verilog Designer's Library, 9 pgs.
Ashkenazi et al., “Platform independent overall security architecture in multi-processor system-on-chip integrated circuits for use in mobile phones and handheld devices,” ScienceDirect, Computers and Electrical Engineering 33 (2007), 18 pages.
Lee et al., “A Semi-Preemptive Garbage Collector for Solid State Drives,” Apr. 2011, IEEE, pp. 12-21.
Office Action dated Feb. 17, 2015, received in Chinese Patent Application No. 201210334987.1, which corresponds to U.S. Appl. No. 12/082,207, 9 pages (Prins).
International Search Report and Written Opinion dated May 4, 2015, received in International Patent Application No. PCT/US2014/065987, which corresponds to U.S. Appl. No. 14/135,400, 12 pages (George).
International Search Report and Written Opinion dated Mar. 17, 2015, received in International Patent Application No. PCT/US2014/067467, which corresponds to U.S. Appl. No. 14/135,420, 13 pages (Lucas).
International Search Report and Written Opinion dated Apr. 20, 2015, received in International Patent Application No. PCT/US2014/063949, which corresponds to U.S. Appl. No. 14/135,433, 21 pages (Delpapa).
International Search Report and Written Opinion dated Mar. 9, 2015, received in International Patent Application No. PCT/US2014/059747, which corresponds to U.S. Appl. No. 14/137,440, 9 pages (Fitzpatrick).
International Search Report and Written Opinion dated Jul. 25, 2014, received in International Patent Application No. PCT/US2014/029453, which corresponds to U.S. Appl. No. 13/963,444, 9 pages (Frayer).
International Search Report and Written Opinion dated Mar. 7, 2014, received in International Patent Application No. PCT/US2013/074772, which corresponds to U.S. Appl. No. 13/831,218, 10 pages (George).
International Search Report and Written Opinion dated Mar. 24, 2014, received in International Patent Application No. PCT/US2013/074777, which corresponds to U.S. Appl. No. 13/831,308, 10 pages (George).
International Search Report and Written Opinion dated Mar. 7, 2014, received in International Patent Application No. PCT/US2013/074779, which corresponds to U.S. Appl. No. 13/831,374, 8 pages (George).
Bayer, “Prefix B-Trees”, IP.com Journal, IP.com Inc., West Henrietta, NY, Mar. 30, 2007, 29 pages.
Bhattacharjee et al., “Efficient Index Compression in DB2 LUW”, IBM Research Report, Jun. 23, 2009, http://domino.research.ibm.com/library/cyberdig.nsf/papers/40B2C45876D0D747852575E100620CE7/$File/rc24815.pdf, 13 pages.
Oracle, “Oracle9i: Database Concepts”, Jul. 2001, http://docs.oracle.com/cd/A91202—01/901—doc/server.901/a88856.pdf, 49 pages.
International Search Report and Written Opinion dated Jun. 8, 2015, received in International Patent Application No. PCT/US2015/018252, which corresponds to U.S. Appl. No. 14/339,072, 9 pages (Busch).
International Search Report and Written Opinion dated Jun. 2, 2015, received in International Patent Application No. PCT/US2015/018255, which corresponds to U.S. Appl. No. 14/336,967, 14 pages (Chander).
International Search Report and Written Opinion dated Jun. 30, 2015, received in International Patent Application No. PCT/US2015/023927, which corresponds to U.S. Appl. No. 14/454,687, 11 pages (Kadayam).
International Search Report and Written Opinion dated Jul. 23, 2015, received in International Patent Application No. PCT/US2015/030850, which corresponds to U.S. Appl. No. 14/298,843, 12 pages (Ellis).
Office Action dated Dec. 8, 2014, received in Chinese Patent Application No. 201180021660.2, which corresponds to U.S. Appl. No. 12/726,200, 7 pages (Olbrich).
Office Action dated Jul. 31, 2015, received in Chinese Patent Application No. 201180021660.2, which corresponds to U.S. Appl. No. 12/726,200, 9 pages (Olbrich).
International Search Report and Written Opinion dated Sep. 14, 2015, received in International Patent Application No. PCT/US2015/036807, which corresponds to U.S. Appl. No. 14/311,152, 9 pages (Higgins).
IBM Research—Zurich, “The Fundamental Limit of Flash Random Write Performance: Understanding, Analysis and Performance Modeling,” Mar. 31, 2010, pp. 1-15.
Gasior, “Gigabyte's i-Ram storage device, Ram disk without the fuss,” The Tech Report, p. 1, Jan. 25, 2006, 5 pages.
Oestreicher et al., “Object Lifetimes in Java Card,” 1999, USENIX, 10 pages.
International Preliminary Report on Patentability dated May 24, 2016, received in International Patent Application No. PCT/US2014/065987, which corresponds to U.S. Appl. No. 14/135,400, 9 pages (George).
Office Action dated Apr. 25, 2016, received in Chinese Patent Application No. 201280066282.4, which corresponds to U.S. Appl. No. 13/602,047, 8 pages (Tai).
Related Publications (1)
Number Date Country
20150153800 A1 Jun 2015 US
Provisional Applications (1)
Number Date Country
61910159 Nov 2013 US