US20130254474A1 - System and method for reducing power consumption of memory - Google Patents
System and method for reducing power consumption of memory Download PDFInfo
- Publication number
- US20130254474A1 US20130254474A1 US13/893,739 US201313893739A US2013254474A1 US 20130254474 A1 US20130254474 A1 US 20130254474A1 US 201313893739 A US201313893739 A US 201313893739A US 2013254474 A1 US2013254474 A1 US 2013254474A1
- Authority
- US
- United States
- Prior art keywords
- memory
- logical unit
- refresh
- information handling
- processor
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/32—Means for saving power
- G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
- G06F1/3234—Power saving characterised by the action undertaken
- G06F1/325—Power saving in peripheral device
- G06F1/3275—Power saving in memory, e.g. RAM, cache
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/32—Means for saving power
- G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Definitions
- the present disclosure relates in general to reducing power consumption in information handling systems, and more particularly to reducing power consumption of memory.
- An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information.
- information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated.
- the variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications.
- information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
- DRAM dynamic random access memory
- DRAM is a type of random access memory that stores each bit (or cell) of data in a separate capacitive element within an integrated circuit. Because capacitors leak charge, the information eventually fades unless the capacitor charge is refreshed periodically. Such refreshing of DRAM cells consumes power. As the density and operating frequency of DRAMs increase, so too does the power consumed by DRAMs. Such consumption of power may lead to higher operating temperatures for the DRAMs and the information handling systems in which such DRAMs are present, which may affect operability of an information handling system and its components. In addition, such consumption of power may lead to higher operating costs due to increased energy costs associated with operation, as well as costs associated with cooling systems to mitigate increased temperatures.
- a method for reducing power consumption in memory may include tracking, by an operating system executing on a processor, one or more logical units of a memory system that are in use. The method may also include setting, by the operating system, a variable indicating a portion of the memory system in use based on the logical units of the memory system in use. The method may also include refreshing one or more of the one or more logical units of the memory system based on the variable.
- an information handling system may include a processor, a memory system communicatively coupled to the processor and having one or more logical units, and a computer-readable medium communicatively coupled to the processor and having stored thereon one or more executable instructions.
- the one or more executable instructions may be configured to, when executed by the processor: (i) track one or more logical units of a memory system that are in use; (ii) set a variable indicating a portion of the memory system in use based on the logical units of the memory system in use; and (iii) refresh one or more of the one or more logical units of the memory system based on the variable.
- a method for reducing power consumption in memory may include issuing a command to refresh a particular logical unit of a memory to the exclusion of other logical units of the memory.
- FIG. 1 illustrates a block diagram of an example information handling system incorporating partial memory refresh, in accordance with certain embodiments of the present disclosure
- FIGS. 2A and 2B illustrate a flow chart of example methods for allocating and deallocating banks, in accordance with certain embodiments of the present disclosure
- FIG. 3 illustrates various fields associated with mode register MR 2 of a DRAM according to the JEDEC Specification, in accordance with certain embodiments of the present disclosure
- FIGS. 4A and 4B illustrate a flow chart of example methods for executing reliability, availability, and serviceability (RAS) features in a memory module, in accordance with certain embodiments of the present disclosure
- FIG. 5A illustrates a command format for a refresh command according to the JEDEC Specification, in accordance with certain embodiments of the present disclosure
- FIG. 5B illustrates a command format for a modified refresh command, in accordance with certain embodiments of the present disclosure.
- FIG. 6 illustrates various fields associated with a mode register for use with a partial memory refresh command, in accordance with certain embodiments of the present disclosure.
- FIGS. 1-6 wherein like numbers are used to indicate like and corresponding parts.
- an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes.
- an information handling system may be a personal computer, a PDA, a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price.
- the information handling system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic.
- Additional components or the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display.
- the information handling system may also include one or more buses operable to transmit communication between the various hardware components.
- Computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time.
- Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.
- storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (
- FIG. 1 illustrates a block diagram of a an example information handling system 102 incorporating partial memory refresh, in accordance with certain embodiments of the present disclosure.
- information handling system 102 may comprise a computer chassis or enclosure (e.g., a server chassis holding one or more server blades).
- information handling system 102 may be a personal computer (e.g., a desktop computer or a portable computer).
- information handling system 102 may include a processor 103 , a memory system 104 communicatively coupled to processor 103 , and a storage medium 106 communicatively coupled to processor 103 .
- Processor 103 may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data, and may include, without limitation a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data.
- processor 103 may interpret and/or execute program instructions and/or process data stored and/or communicated by one or more of memory system 104 , storage medium 106 , and/or another component of information handling system 100 .
- Memory system 104 may be communicatively coupled to processor 103 and may comprise any system, device, or apparatus operable to retain program instructions or data for a period of time (e.g., computer-readable media).
- Memory system 104 may comprise random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to information handling system 102 is turned off.
- RAM random access memory
- EEPROM electrically erasable programmable read-only memory
- PCMCIA card PCMCIA card
- flash memory magnetic storage
- opto-magnetic storage or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to information handling system 102 is turned off.
- memory system 104 may comprise dynamic random access memory (DRAM).
- DRAM dynamic random access memory
- memory system 104 may include memory controller 108 , one or more memory modules 116 a - 116 n communicatively coupled to memory controller 108 , and status registers 112 communicatively coupled to memory controller 108 .
- Memory controller 108 may be any system, device, or apparatus configured to manage and/or control memory system 104 .
- memory controller 108 may be configured to read data from and/or write data to memory modules 116 comprising memory system 104 .
- memory controller 108 may be configured to refresh memory modules in embodiments in which memory system 104 comprises DRAM.
- memory controller 108 is shown in FIG. 1 as an integral component of memory system 104 , memory controller 108 may be separate from memory system 104 and/or may be an integral portion of another component of information handling system 102 (e.g., memory controller 108 may be integrated into processor 103 ).
- Each memory module 116 may include any system, device or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media).
- Each memory module 116 may include a dynamic random access memory (DRAM) module (e.g, a dual in-line package (DIP) memory, a Single In-line Pin Package (SIPP) memory, a Single Inline Memory Module (SIMM), a Ball Grid Array (BGA)), or any other suitable memory.
- DRAM dynamic random access memory
- DI dual in-line package
- SIPP Single In-line Pin Package
- SIMM Single Inline Memory Module
- BGA Ball Grid Array
- each memory module 116 may include one or more ranks 118 a - 118 m .
- Each memory rank 118 within a memory module 116 may be a block or area of data created using some or all of the memory capacity of the memory module 116 .
- each rank 118 may be a rank as such term in defined by the Joint Electron Device Engineering Council (JEDEC) Standard for memory devices.
- JEDEC Joint Electron Device Engineering Council
- each rank 118 may include mode registers 120 and one or more memory banks 110 .
- Each memory bank 110 may be a logical unit of storage within memory system 104 , which may be based on physical parameters of the memory module 116 comprising such memory bank 110 .
- Mode registers 120 may include one or more configuration variables and/or parameters associated with memory system 104 . When reading, writing, refreshing, and/or performing other operations associated with memory system 104 , a memory module 116 may carry out such operations based at least in part on configuration parameters and/or variables stored in mode registers 120 .
- mode registers 120 may be defined by a Joint Electron Device Engineering Council (JEDEC) standard for memory devices.
- JEDEC Joint Electron Device Engineering Council
- Status registers 112 may include one or more configuration variables and/or parameters associated with memory system 104 . When reading, writing, refreshing, and/or performing other operations associated with memory system 104 , memory controller 108 may carry out such operations based at least in part on configuration parameters and/or variables stored in status registers 112 . In some embodiments, status registers 112 may include registers similar to mode registers 120 .
- Storage medium 106 may be communicatively coupled to processor 104 .
- Storage medium 106 may include any system, device, or apparatus operable to store information processed by processor 103 .
- Storage medium 106 may include, for example, network attached storage, one or more direct access storage devices (e.g. hard disk drives), and/or one or more sequential access storage devices (e.g. tape drives).
- storage medium 106 may have stored thereon an operating system (OS) 114 .
- OS 114 may be any program of executable instructions, or aggregation of programs of executable instructions, configured to manage and/or control the allocation and usage of hardware resources such as memory, CPU time, disk space, and input and output devices, and provide an interface between such hardware resources and application programs hosted by OS 114 . Active portions of OS 114 may be transferred to memory 104 for execution by processor 103 .
- processor 103 and/or memory controller 108 may manage and control the various banks 110 such that memory refresh operations may be executed with respect to one or more of banks 110 , as described in greater detail below. In some embodiments, some, but not all of the banks 110 will be refreshed, thus decreasing the power consumed in connection with refresh operations as compared to traditional approaches. Examples of such embodiments are described below.
- partial memory refresh may be implemented with minimal or no change to traditional memory controllers and/or JEDEC Specifications, and may be implemented mainly within OS 114 .
- OS 114 may be configured to, when executed by processor 103 , disable bank-level interleaving, and/or any reliability, availability, and serviceability (RAS) features of memory controller 108 (e.g., patrol scrubbing, sparing, mirroring, etc.), which might force multiple partially occupied banks to stay active or generate false error conditions.
- RAS reliability, availability, and serviceability
- OS 114 may further be enabled to, when allocating and/or de-allocating memory, track such memory allocation on a per rank and/or per bank basis (e.g., by storing variables and/or parameters indicative of such usage in status registers 112 or other suitable medium). As memory is allocated and/or de-allocated, OS 114 may update variables and/or parameters stored in status registers 112 indicative of the usage of the various banks 110 . In addition, OS 114 may alter the contents of a mode register to indicate a fraction of the memory being used. As a particular example, mode register MR 2 , as defined by the JEDEC Specification, may be modified by OS 114 to indicate usage of banks 110 .
- OS 114 invokes and terminates programs executing on processor 103 , it may attempt to allocate and de-allocate memory so as to fill active banks 110 before allocating additional banks 110 , thus keeping the number of active banks 110 at a minimum.
- FIG. 2A illustrates a flow chart of an example method 150 for allocating banks 110 , in accordance with certain embodiments of the present disclosure.
- method 150 may begin at step 152 .
- teachings of the present disclosure may be implemented in a variety of configurations of information handling system 102 . As such, the initialization point for method 150 and the order of the steps 152 - 164 comprising method 150 may depend on the implementation chosen.
- operating system 114 may begin the process of allocating a page of memory to a program.
- processor 103 , memory controller 108 , or another component of information handling system 102 may determine if space is available in a presently active bank 110 in a memory module 116 for storage of the allocated page. In some embodiments, such determination may be made by reference to parameters stored in status registers 112 , mode registers 120 , and/or another component of information handling system 102 . If space in available in an active bank 110 , method 150 may proceed to step 156 . Otherwise, method 150 may proceed to step 158 .
- processor 103 in response to a determination that space is available in a presently active bank 110 , processor 103 , memory controller 108 , and/or another component of information handling system 102 may allocate the page to space in an active bank 110 .
- method 150 may end.
- processor 103 in response to a determination that space is not available in a presently active bank 110 , processor 103 , memory controller 108 , and/or another component of information handling system 102 may select a presently idle bank 110 to be made active.
- a mode register 120 may be updated to indicate that the idle bank 110 is to become an active bank 110 .
- memory controller 108 may clear the idle bank 110 .
- memory controller 108 may allocate the page to the formerly idle/now active bank 110 .
- FIG. 2A discloses a particular number of steps to be taken with respect to method 150
- method 150 may be executed with greater or lesser steps than those depicted in FIG. 2A .
- FIG. 2A discloses a certain order of steps to be taken with respect to method 150
- the steps comprising method 150 may be completed in any suitable order.
- Method 150 may be implemented using information handling system 102 or any other system operable to implement method 150 .
- method 150 may be implemented partially or fully in software and/or firmware embodied in computer-readable media.
- FIG. 2B illustrates a flow chart of an example method 180 for deallocating banks 110 , in accordance with certain embodiments of the present disclosure.
- method 180 may begin at step 182 .
- teachings of the present disclosure may be implemented in a variety of configurations of information handling system 102 .
- the initialization point for method 180 and the order of the steps 182 - 186 comprising method 180 may depend on the implementation chosen.
- operating system 114 may deallocate a page from a bank 110 .
- processor 103 , memory controller 108 , or another component of information handling system 102 may determine if all pages within the bank 110 comprising the deallocated page are idle. In some embodiments, such determination may be made by reference to parameters stored in status registers 112 , mode registers 120 , and/or another component of information handling system 102 . If all pages are idle, method 180 may proceed to step 186 . Otherwise, method 180 may end.
- a mode register 120 may be updated to indicate that the bank 110 has become idle. After completion of step 186 , method 180 may end.
- FIG. 2B discloses a particular number of steps to be taken with respect to method 180
- method 180 may be executed with greater or lesser steps than those depicted in FIG. 2B .
- FIG. 2B discloses a certain order of steps to be taken with respect to method 180
- the steps comprising method 180 may be completed in any suitable order.
- Method 180 may be implemented using information handling system 102 or any other system operable to implement method 180 .
- method 180 may be implemented partially or fully in software and/or firmware embodied in computer-readable media.
- FIG. 3 illustrates various fields associated with mode register MR 2 of a DRAM according to the JEDEC Specification, in accordance with certain embodiments of the present disclosure.
- mode register MR 2 includes a three-bit field labeled as PASR or “Partial Array Self-Refresh.”
- PASR Phase Change Register
- FIG. 3 illustrates various fields associated with mode register MR 2 of a DRAM according to the JEDEC Specification, in accordance with certain embodiments of the present disclosure.
- PASR Phase Change Rate Average
- FIG. 3 illustrates various fields associated with mode register MR 2 of a DRAM according to the JEDEC Specification, in accordance with certain embodiments of the present disclosure.
- mode register MR 2 includes a three-bit field labeled as PASR or “Partial Array Self-Refresh.”
- PASR field may indicate to memory controller 108 a fraction (e.g., one-eighth, one-fourth, one-half, three-fourths, all) of the banks 110 that are in use.
- partial memory refresh may be implemented with minimal change to traditional memory controllers and/or little or minimal change to JEDEC Specifications.
- OS 114 may be configured to, when executed by processor 103 , disable bank-level interleaving.
- OS 114 may further be enabled to, when allocating and/or de-allocating memory, track such memory allocation on a per rank and/or per bank basis (e.g., by storing variables and/or parameters indicative of such usage in status registers 112 or other suitable medium).
- memory controller 108 may update variables and/or parameters stored in status registers 112 indicative of the usage of the various banks 110 .
- memory controller 108 may be configured to track a bank-in-use status of each bank 110 .
- bank-in-use information may be stored in status registers 112 or another suitable medium.
- memory controller 108 may also alter contents of a mode register (e.g., mode register MR 2 , as described above with respect to Example Embodiment 1) to indicate usage of banks 110 in according with the existing JEDEC Specification. Accordingly, during self-refresh, only a portion of the memory banks 110 , as indicated by the PASR field, may be refreshed, which may reduce power consumption associated with refresh as compared to traditional approaches.
- mode register e.g., mode register MR 2
- Example Embodiment 2 RAS features of memory controller 108 (e.g., patrol scrubbing, sparing, mirroring, etc.) may be enabled, and memory controller 110 may check the bank-in-use status of each bank 110 before performing such RAS operation, such as depicted in FIGS. 4A and 4B below.
- memory controller 110 may check the bank-in-use status of each bank 110 before performing such RAS operation, such as depicted in FIGS. 4A and 4B below.
- FIG. 4A illustrates a flow chart of an example method 400 for executing certain reliability, availability, and serviceability (RAS) features in a memory module 116 , in accordance with certain embodiments of the present disclosure.
- method 400 may begin at step 402 .
- teachings of the present disclosure may be implemented in a variety of configurations of information handling system 102 . As such, the initialization point for method 400 and the order of the steps 402 - 412 comprising method 400 may depend on the implementation chosen.
- a spare DIMM, spare rank, spare channel, or re-silvering operation may be required by memory controller 108 .
- processor 103 , memory controller 108 , and/or another component of information handling system 102 may determine if all memory cache lines responsive to the required RAS operation have been copied. If it is determined that all memory cache lines responsive to the required RAS operation have been copied, method 400 may end. Otherwise, method 400 may proceed to step 406 .
- processor 103 in response to a determination that not all memory cache lines responsive to the required RAS operation have been copied, processor 103 , memory controller 108 , and/or another component of information handling system may determine the bank status of the current cacheline.
- the bank status may include whether or not the current cacheline is associated with a bank 110 that is presently valid (e.g., presently allocated or active).
- step 408 if it is determined that the bank 110 associated with the cacheline is valid, method 400 may proceed to step 410 . Otherwise, method 400 may proceed to step 412 .
- the cacheline may be written to the spare location.
- a counter may be incremented to indicate that the next cacheline should next be processed in accordance with the steps above. After completion of step 412 , method 400 may proceed again to step 404 .
- FIG. 4A discloses a particular number of steps to be taken with respect to method 400
- method 400 may be executed with greater or lesser steps than those depicted in FIG. 4A .
- FIG. 4A discloses a certain order of steps to be taken with respect to method 400
- the steps comprising method 400 may be completed in any suitable order.
- Method 400 may be implemented using information handling system 102 or any other system operable to implement method 400 .
- method 400 may be implemented partially or fully in software and/or firmware embodied in computer-readable media.
- FIG. 4B illustrates a flow chart of an example method 450 for executing a patrol scrub in a memory module 116 , in accordance with certain embodiments of the present disclosure.
- method 450 may begin at step 452 .
- teachings of the present disclosure may be implemented in a variety of configurations of information handling system 102 . As such, the initialization point for method 450 and the order of the steps 452 - 460 comprising method 450 may depend on the implementation chosen.
- a patrol scrub operation may be required by memory controller 108 .
- processor 103 , memory controller 108 , and/or another component of information handling system may determine whether the bank 110 associated with the patrol scrub operation is presently valid (e.g., presently allocated or active). If it is determined that the bank 110 is valid, method 450 may proceed to step 456 . Otherwise, method 450 may end.
- processor 103 may read the memory location associated with the patrol scrub operation.
- processor 103 , memory controller 108 , and/or another component of information handling system may determine whether or not an error correction code (ECC) associated with the memory location is valid. If it is determined that the ECC is not valid, method 450 may proceed to step 460 . Otherwise, method 450 may end.
- ECC error correction code
- the ECC may be fixed and corrected data may be written back to the memory location.
- FIG. 4B discloses a particular number of steps to be taken with respect to method 450
- method 450 may be executed with greater or lesser steps than those depicted in FIG. 4B .
- FIG. 4B discloses a certain order of steps to be taken with respect to method 450
- the steps comprising method 450 may be completed in any suitable order.
- Method 450 may be implemented using information handling system 102 or any other system operable to implement method 450 .
- method 450 may be implemented partially or fully in software and/or firmware embodied in computer-readable media.
- Example Embodiment 3 may be similar to Example Embodiment 2, except that Example Embodiment 3 defines an enhancement to a command present in traditional approaches.
- the REFRESH command protocol of the JEDEC Specification may be enhanced to enable partial memory refresh.
- FIG. 5A illustrates a command format for a REFRESH command according to the JEDEC Specification.
- a REFRESH command known as a “direct” refresh
- the BA3:0 field is not presently used by the REFRESH command.
- this field of the traditional REFRESH command may be used to indicate a specific bank to be refreshed pursuant to a direct refresh command.
- the JEDEC standard REFRESH command may be modified such that field BA2:0 may be used to indicate the bank to be refreshed.
- Example Embodiment 3 adds partial memory direct refresh to the partial self-refresh functionality described in Example Embodiments 1 and 2.
- Example Embodiment 4 may be similar to Example Embodiment 3, except that Example Embodiment 4 defines a new data register.
- Example Embodiment 4 may define a new JEDEC mode register, as shown in FIG. 4 .
- the new mode register may include a bit for each bank 110 . Accordingly, this new register allows for arbitrary enabling and disabling for each bank 110 , as compared to the more rigid groupings supported by the standard PASR field of mode register MR 2 , as described above. Thus, during self-refresh, a portion of the memory banks 110 , as indicated by the new mode register, may be refreshed, which may reduce power consumption associated with refresh as compared to traditional approaches.
Abstract
Description
- The present disclosure relates in general to reducing power consumption in information handling systems, and more particularly to reducing power consumption of memory.
- As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
- Information handling systems often use memory to store data and/or instructions. Broadly speaking, term memory refers to computer components, devices, and recording media that retain digital data used for processing for some interval of time. A commonly-used type of memory is known as dynamic random access memory (DRAM). DRAM is a type of random access memory that stores each bit (or cell) of data in a separate capacitive element within an integrated circuit. Because capacitors leak charge, the information eventually fades unless the capacitor charge is refreshed periodically. Such refreshing of DRAM cells consumes power. As the density and operating frequency of DRAMs increase, so too does the power consumed by DRAMs. Such consumption of power may lead to higher operating temperatures for the DRAMs and the information handling systems in which such DRAMs are present, which may affect operability of an information handling system and its components. In addition, such consumption of power may lead to higher operating costs due to increased energy costs associated with operation, as well as costs associated with cooling systems to mitigate increased temperatures.
- In accordance with the teachings of the present disclosure, the disadvantages and problems associated with power consumption in memory devices have been substantially reduced or eliminated.
- In accordance with an embodiment of the present disclosure, a method for reducing power consumption in memory may include tracking, by an operating system executing on a processor, one or more logical units of a memory system that are in use. The method may also include setting, by the operating system, a variable indicating a portion of the memory system in use based on the logical units of the memory system in use. The method may also include refreshing one or more of the one or more logical units of the memory system based on the variable.
- In accordance with another embodiment of the present disclosure, an information handling system may include a processor, a memory system communicatively coupled to the processor and having one or more logical units, and a computer-readable medium communicatively coupled to the processor and having stored thereon one or more executable instructions. The one or more executable instructions may be configured to, when executed by the processor: (i) track one or more logical units of a memory system that are in use; (ii) set a variable indicating a portion of the memory system in use based on the logical units of the memory system in use; and (iii) refresh one or more of the one or more logical units of the memory system based on the variable.
- In accordance with a further embodiment of the present disclosure, a method for reducing power consumption in memory, may include issuing a command to refresh a particular logical unit of a memory to the exclusion of other logical units of the memory.
- Other technical advantages will be apparent to those of ordinary skill in the art in view of the following specification, claims, and drawings.
- A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:
-
FIG. 1 illustrates a block diagram of an example information handling system incorporating partial memory refresh, in accordance with certain embodiments of the present disclosure; -
FIGS. 2A and 2B illustrate a flow chart of example methods for allocating and deallocating banks, in accordance with certain embodiments of the present disclosure; -
FIG. 3 illustrates various fields associated with mode register MR2 of a DRAM according to the JEDEC Specification, in accordance with certain embodiments of the present disclosure; -
FIGS. 4A and 4B illustrate a flow chart of example methods for executing reliability, availability, and serviceability (RAS) features in a memory module, in accordance with certain embodiments of the present disclosure; -
FIG. 5A illustrates a command format for a refresh command according to the JEDEC Specification, in accordance with certain embodiments of the present disclosure; -
FIG. 5B illustrates a command format for a modified refresh command, in accordance with certain embodiments of the present disclosure; and -
FIG. 6 illustrates various fields associated with a mode register for use with a partial memory refresh command, in accordance with certain embodiments of the present disclosure. - Preferred embodiments and their advantages are best understood by reference to
FIGS. 1-6 , wherein like numbers are used to indicate like and corresponding parts. - For the purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a PDA, a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components or the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communication between the various hardware components.
- For the purposes of this disclosure, computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.
-
FIG. 1 illustrates a block diagram of a an exampleinformation handling system 102 incorporating partial memory refresh, in accordance with certain embodiments of the present disclosure. In certain embodiments,information handling system 102 may comprise a computer chassis or enclosure (e.g., a server chassis holding one or more server blades). In other embodiments,information handling system 102 may be a personal computer (e.g., a desktop computer or a portable computer). As depicted inFIG. 1 ,information handling system 102 may include aprocessor 103, amemory system 104 communicatively coupled toprocessor 103, and astorage medium 106 communicatively coupled toprocessor 103. -
Processor 103 may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data, and may include, without limitation a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data. In some embodiments,processor 103 may interpret and/or execute program instructions and/or process data stored and/or communicated by one or more ofmemory system 104,storage medium 106, and/or another component ofinformation handling system 100. -
Memory system 104 may be communicatively coupled toprocessor 103 and may comprise any system, device, or apparatus operable to retain program instructions or data for a period of time (e.g., computer-readable media).Memory system 104 may comprise random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power toinformation handling system 102 is turned off. In particular embodiments,memory system 104 may comprise dynamic random access memory (DRAM). - As shown in
FIG. 1 ,memory system 104 may includememory controller 108, one or more memory modules 116 a-116 n communicatively coupled tomemory controller 108, andstatus registers 112 communicatively coupled tomemory controller 108.Memory controller 108 may be any system, device, or apparatus configured to manage and/or controlmemory system 104. For example,memory controller 108 may be configured to read data from and/or write data to memory modules 116 comprisingmemory system 104. Additionally or alternatively,memory controller 108 may be configured to refresh memory modules in embodiments in whichmemory system 104 comprises DRAM. Althoughmemory controller 108 is shown inFIG. 1 as an integral component ofmemory system 104,memory controller 108 may be separate frommemory system 104 and/or may be an integral portion of another component of information handling system 102 (e.g.,memory controller 108 may be integrated into processor 103). - Each memory module 116 may include any system, device or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media). Each memory module 116 may include a dynamic random access memory (DRAM) module (e.g, a dual in-line package (DIP) memory, a Single In-line Pin Package (SIPP) memory, a Single Inline Memory Module (SIMM), a Ball Grid Array (BGA)), or any other suitable memory.
- As depicted in
FIG. 1 , each memory module 116 may include one or more ranks 118 a-118 m. Each memory rank 118 within a memory module 116 may be a block or area of data created using some or all of the memory capacity of the memory module 116. In some embodiments, each rank 118 may be a rank as such term in defined by the Joint Electron Device Engineering Council (JEDEC) Standard for memory devices. - Also as shown in
FIG. 1 , each rank 118 may include mode registers 120 and one ormore memory banks 110. Eachmemory bank 110 may be a logical unit of storage withinmemory system 104, which may be based on physical parameters of the memory module 116 comprisingsuch memory bank 110. - Mode registers 120 may include one or more configuration variables and/or parameters associated with
memory system 104. When reading, writing, refreshing, and/or performing other operations associated withmemory system 104, a memory module 116 may carry out such operations based at least in part on configuration parameters and/or variables stored in mode registers 120. In some embodiments, mode registers 120 may be defined by a Joint Electron Device Engineering Council (JEDEC) standard for memory devices. - Status registers 112 may include one or more configuration variables and/or parameters associated with
memory system 104. When reading, writing, refreshing, and/or performing other operations associated withmemory system 104,memory controller 108 may carry out such operations based at least in part on configuration parameters and/or variables stored in status registers 112. In some embodiments, status registers 112 may include registers similar to mode registers 120. -
Storage medium 106 may be communicatively coupled toprocessor 104.Storage medium 106 may include any system, device, or apparatus operable to store information processed byprocessor 103.Storage medium 106 may include, for example, network attached storage, one or more direct access storage devices (e.g. hard disk drives), and/or one or more sequential access storage devices (e.g. tape drives). As shown inFIG. 1 ,storage medium 106 may have stored thereon an operating system (OS) 114.OS 114 may be any program of executable instructions, or aggregation of programs of executable instructions, configured to manage and/or control the allocation and usage of hardware resources such as memory, CPU time, disk space, and input and output devices, and provide an interface between such hardware resources and application programs hosted byOS 114. Active portions ofOS 114 may be transferred tomemory 104 for execution byprocessor 103. - In operation,
processor 103 and/ormemory controller 108 may manage and control thevarious banks 110 such that memory refresh operations may be executed with respect to one or more ofbanks 110, as described in greater detail below. In some embodiments, some, but not all of thebanks 110 will be refreshed, thus decreasing the power consumed in connection with refresh operations as compared to traditional approaches. Examples of such embodiments are described below. - In accordance with an example embodiment of the present disclosure, partial memory refresh may be implemented with minimal or no change to traditional memory controllers and/or JEDEC Specifications, and may be implemented mainly within
OS 114. In this embodiment,OS 114 may be configured to, when executed byprocessor 103, disable bank-level interleaving, and/or any reliability, availability, and serviceability (RAS) features of memory controller 108 (e.g., patrol scrubbing, sparing, mirroring, etc.), which might force multiple partially occupied banks to stay active or generate false error conditions.OS 114 may further be enabled to, when allocating and/or de-allocating memory, track such memory allocation on a per rank and/or per bank basis (e.g., by storing variables and/or parameters indicative of such usage in status registers 112 or other suitable medium). As memory is allocated and/or de-allocated,OS 114 may update variables and/or parameters stored in status registers 112 indicative of the usage of thevarious banks 110. In addition,OS 114 may alter the contents of a mode register to indicate a fraction of the memory being used. As a particular example, mode register MR2, as defined by the JEDEC Specification, may be modified byOS 114 to indicate usage ofbanks 110. - As
OS 114 invokes and terminates programs executing onprocessor 103, it may attempt to allocate and de-allocate memory so as to fillactive banks 110 before allocatingadditional banks 110, thus keeping the number ofactive banks 110 at a minimum. -
FIG. 2A illustrates a flow chart of anexample method 150 for allocatingbanks 110, in accordance with certain embodiments of the present disclosure. According to one embodiment,method 150 may begin atstep 152. As noted above, teachings of the present disclosure may be implemented in a variety of configurations ofinformation handling system 102. As such, the initialization point formethod 150 and the order of the steps 152-164 comprisingmethod 150 may depend on the implementation chosen. - At
step 152,operating system 114, which may have been loaded intomemory 104, may begin the process of allocating a page of memory to a program. Atstep 154,processor 103,memory controller 108, or another component ofinformation handling system 102 may determine if space is available in a presentlyactive bank 110 in a memory module 116 for storage of the allocated page. In some embodiments, such determination may be made by reference to parameters stored in status registers 112, mode registers 120, and/or another component ofinformation handling system 102. If space in available in anactive bank 110,method 150 may proceed to step 156. Otherwise,method 150 may proceed to step 158. - At
step 156, in response to a determination that space is available in a presentlyactive bank 110,processor 103,memory controller 108, and/or another component ofinformation handling system 102 may allocate the page to space in anactive bank 110. After completion ofstep 154,method 150 may end. - At
step 158, in response to a determination that space is not available in a presentlyactive bank 110,processor 103,memory controller 108, and/or another component ofinformation handling system 102 may select a presentlyidle bank 110 to be made active. Atstep 160, amode register 120 may be updated to indicate that theidle bank 110 is to become anactive bank 110. Atstep 162,memory controller 108 may clear theidle bank 110. Atstep 164,memory controller 108 may allocate the page to the formerly idle/nowactive bank 110. - Although
FIG. 2A discloses a particular number of steps to be taken with respect tomethod 150,method 150 may be executed with greater or lesser steps than those depicted inFIG. 2A . In addition, althoughFIG. 2A discloses a certain order of steps to be taken with respect tomethod 150, thesteps comprising method 150 may be completed in any suitable order. -
Method 150 may be implemented usinginformation handling system 102 or any other system operable to implementmethod 150. In certain embodiments,method 150 may be implemented partially or fully in software and/or firmware embodied in computer-readable media. -
FIG. 2B illustrates a flow chart of anexample method 180 for deallocatingbanks 110, in accordance with certain embodiments of the present disclosure. According to one embodiment,method 180 may begin atstep 182. As noted above, teachings of the present disclosure may be implemented in a variety of configurations ofinformation handling system 102. As such, the initialization point formethod 180 and the order of the steps 182-186 comprisingmethod 180 may depend on the implementation chosen. - Beginning at
step 182,operating system 114 may deallocate a page from abank 110. Atstep 184,processor 103,memory controller 108, or another component ofinformation handling system 102 may determine if all pages within thebank 110 comprising the deallocated page are idle. In some embodiments, such determination may be made by reference to parameters stored in status registers 112, mode registers 120, and/or another component ofinformation handling system 102. If all pages are idle,method 180 may proceed to step 186. Otherwise,method 180 may end. - At
step 186, in response to a determination that all pages within thebank 110 comprising the deallocated page are idle, amode register 120 may be updated to indicate that thebank 110 has become idle. After completion ofstep 186,method 180 may end. - Although
FIG. 2B discloses a particular number of steps to be taken with respect tomethod 180,method 180 may be executed with greater or lesser steps than those depicted inFIG. 2B . In addition, althoughFIG. 2B discloses a certain order of steps to be taken with respect tomethod 180, thesteps comprising method 180 may be completed in any suitable order. -
Method 180 may be implemented usinginformation handling system 102 or any other system operable to implementmethod 180. In certain embodiments,method 180 may be implemented partially or fully in software and/or firmware embodied in computer-readable media. -
FIG. 3 illustrates various fields associated with mode register MR2 of a DRAM according to the JEDEC Specification, in accordance with certain embodiments of the present disclosure. As shown inFIG. 3 , mode register MR2 includes a three-bit field labeled as PASR or “Partial Array Self-Refresh.” By appropriately setting this field as memory pages andbanks 110 are allocated and deallocated in accordance with the methods described above with respect toFIGS. 2A and 2B , such PASR field may indicate to memory controller 108 a fraction (e.g., one-eighth, one-fourth, one-half, three-fourths, all) of thebanks 110 that are in use. Accordingly, during self-refresh, only a portion of thememory banks 110, as indicated by the PASR field, may be refreshed, which may reduce power consumption associated with refresh as compared to traditional approaches. - In accordance with another example embodiment of the present disclosure, partial memory refresh may be implemented with minimal change to traditional memory controllers and/or little or minimal change to JEDEC Specifications. In this embodiment,
OS 114 may be configured to, when executed byprocessor 103, disable bank-level interleaving.OS 114 may further be enabled to, when allocating and/or de-allocating memory, track such memory allocation on a per rank and/or per bank basis (e.g., by storing variables and/or parameters indicative of such usage in status registers 112 or other suitable medium). As memory is allocated and/or de-allocated,memory controller 108 may update variables and/or parameters stored in status registers 112 indicative of the usage of thevarious banks 110. For example,memory controller 108 may be configured to track a bank-in-use status of eachbank 110. Such bank-in-use information may be stored in status registers 112 or another suitable medium. As the bank-in-use status is updated asbanks 110 are allocated and de-allocated,memory controller 108 may also alter contents of a mode register (e.g., mode register MR2, as described above with respect to Example Embodiment 1) to indicate usage ofbanks 110 in according with the existing JEDEC Specification. Accordingly, during self-refresh, only a portion of thememory banks 110, as indicated by the PASR field, may be refreshed, which may reduce power consumption associated with refresh as compared to traditional approaches. - In
Example Embodiment 2, RAS features of memory controller 108 (e.g., patrol scrubbing, sparing, mirroring, etc.) may be enabled, andmemory controller 110 may check the bank-in-use status of eachbank 110 before performing such RAS operation, such as depicted inFIGS. 4A and 4B below. -
FIG. 4A illustrates a flow chart of anexample method 400 for executing certain reliability, availability, and serviceability (RAS) features in a memory module 116, in accordance with certain embodiments of the present disclosure. According to one embodiment,method 400 may begin atstep 402. As noted above, teachings of the present disclosure may be implemented in a variety of configurations ofinformation handling system 102. As such, the initialization point formethod 400 and the order of the steps 402-412 comprisingmethod 400 may depend on the implementation chosen. - At
step 402, a spare DIMM, spare rank, spare channel, or re-silvering operation may be required bymemory controller 108. Atstep 404,processor 103,memory controller 108, and/or another component ofinformation handling system 102 may determine if all memory cache lines responsive to the required RAS operation have been copied. If it is determined that all memory cache lines responsive to the required RAS operation have been copied,method 400 may end. Otherwise,method 400 may proceed to step 406. - At
step 406, in response to a determination that not all memory cache lines responsive to the required RAS operation have been copied,processor 103,memory controller 108, and/or another component of information handling system may determine the bank status of the current cacheline. The bank status may include whether or not the current cacheline is associated with abank 110 that is presently valid (e.g., presently allocated or active). Atstep 408, if it is determined that thebank 110 associated with the cacheline is valid,method 400 may proceed to step 410. Otherwise,method 400 may proceed to step 412. - At
step 410, in response to a determination that a thebank 110 associated with the current cacheline is valid, the cacheline may be written to the spare location. - At
step 412, a counter may be incremented to indicate that the next cacheline should next be processed in accordance with the steps above. After completion ofstep 412,method 400 may proceed again to step 404. - Although
FIG. 4A discloses a particular number of steps to be taken with respect tomethod 400,method 400 may be executed with greater or lesser steps than those depicted inFIG. 4A . In addition, althoughFIG. 4A discloses a certain order of steps to be taken with respect tomethod 400, thesteps comprising method 400 may be completed in any suitable order. -
Method 400 may be implemented usinginformation handling system 102 or any other system operable to implementmethod 400. In certain embodiments,method 400 may be implemented partially or fully in software and/or firmware embodied in computer-readable media. -
FIG. 4B illustrates a flow chart of anexample method 450 for executing a patrol scrub in a memory module 116, in accordance with certain embodiments of the present disclosure. According to one embodiment,method 450 may begin atstep 452. As noted above, teachings of the present disclosure may be implemented in a variety of configurations ofinformation handling system 102. As such, the initialization point formethod 450 and the order of the steps 452-460 comprisingmethod 450 may depend on the implementation chosen. - At
step 452, a patrol scrub operation may be required bymemory controller 108. Atstep 454,processor 103,memory controller 108, and/or another component of information handling system may determine whether thebank 110 associated with the patrol scrub operation is presently valid (e.g., presently allocated or active). If it is determined that thebank 110 is valid,method 450 may proceed to step 456. Otherwise,method 450 may end. - At step 456,
processor 103,memory controller 108, and/or another component of information handling system may read the memory location associated with the patrol scrub operation. Atstep 458,processor 103,memory controller 108, and/or another component of information handling system may determine whether or not an error correction code (ECC) associated with the memory location is valid. If it is determined that the ECC is not valid,method 450 may proceed to step 460. Otherwise,method 450 may end. - At
step 460, in response to a determination that the ECC is not valid, the ECC may be fixed and corrected data may be written back to the memory location. - Although
FIG. 4B discloses a particular number of steps to be taken with respect tomethod 450,method 450 may be executed with greater or lesser steps than those depicted inFIG. 4B . In addition, althoughFIG. 4B discloses a certain order of steps to be taken with respect tomethod 450, thesteps comprising method 450 may be completed in any suitable order. -
Method 450 may be implemented usinginformation handling system 102 or any other system operable to implementmethod 450. In certain embodiments,method 450 may be implemented partially or fully in software and/or firmware embodied in computer-readable media. - Example Embodiment 3 may be similar to
Example Embodiment 2, except that Example Embodiment 3 defines an enhancement to a command present in traditional approaches. For example, the REFRESH command protocol of the JEDEC Specification may be enhanced to enable partial memory refresh. -
FIG. 5A illustrates a command format for a REFRESH command according to the JEDEC Specification. In accordance with the JEDEC Specification, a REFRESH command, known as a “direct” refresh, may cause refresh to occur in abank 110 of a memory module 116 determined by the memory module 116. Notably, the BA3:0 field is not presently used by the REFRESH command. However, this field of the traditional REFRESH command may be used to indicate a specific bank to be refreshed pursuant to a direct refresh command. For example, as shown inFIG. 5B , in an eight-bank memory, the JEDEC standard REFRESH command may be modified such that field BA2:0 may be used to indicate the bank to be refreshed. Accordingly, Example Embodiment 3 adds partial memory direct refresh to the partial self-refresh functionality described inExample Embodiments - Example Embodiment 4 may be similar to Example Embodiment 3, except that Example Embodiment 4 defines a new data register. For example, Example Embodiment 4 may define a new JEDEC mode register, as shown in
FIG. 4 . The new mode register may include a bit for eachbank 110. Accordingly, this new register allows for arbitrary enabling and disabling for eachbank 110, as compared to the more rigid groupings supported by the standard PASR field of mode register MR2, as described above. Thus, during self-refresh, a portion of thememory banks 110, as indicated by the new mode register, may be refreshed, which may reduce power consumption associated with refresh as compared to traditional approaches. - Although the present disclosure has been described in detail, it should be understood that various changes, substitutions, and alterations can be made hereto without departing from the spirit and the scope of the disclosure as defined by the appended claims. As a specific example, although the embodiments above describe enabling refresh on a per bank basis for the purposes of simplicity and exposition, any appropriate level of granularity, whether a larger or smaller granularity than a bank, may be used.
Claims (22)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/893,739 US20130254474A1 (en) | 2009-12-02 | 2013-05-14 | System and method for reducing power consumption of memory |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/629,681 US8468295B2 (en) | 2009-12-02 | 2009-12-02 | System and method for reducing power consumption of memory |
US13/893,739 US20130254474A1 (en) | 2009-12-02 | 2013-05-14 | System and method for reducing power consumption of memory |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/629,681 Continuation US8468295B2 (en) | 2009-12-02 | 2009-12-02 | System and method for reducing power consumption of memory |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130254474A1 true US20130254474A1 (en) | 2013-09-26 |
Family
ID=44069747
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/629,681 Active 2031-06-24 US8468295B2 (en) | 2009-12-02 | 2009-12-02 | System and method for reducing power consumption of memory |
US13/893,739 Abandoned US20130254474A1 (en) | 2009-12-02 | 2013-05-14 | System and method for reducing power consumption of memory |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/629,681 Active 2031-06-24 US8468295B2 (en) | 2009-12-02 | 2009-12-02 | System and method for reducing power consumption of memory |
Country Status (1)
Country | Link |
---|---|
US (2) | US8468295B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9880754B2 (en) | 2014-07-09 | 2018-01-30 | Dell Products, Lp | System and method for enabling transportability of a non volatile dual inline memory module |
US20190108896A1 (en) * | 2017-10-05 | 2019-04-11 | Dell Products L.P. | Systems and methods for providing post-package repair visibility to a host for memory reliability, availability, and serviceability |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8392650B2 (en) | 2010-04-01 | 2013-03-05 | Intel Corporation | Fast exit from self-refresh state of a memory device |
US8484410B2 (en) * | 2010-04-12 | 2013-07-09 | Intel Corporation | Method to stagger self refreshes |
US8650414B2 (en) * | 2010-09-24 | 2014-02-11 | Intel Corporation | Logic device having status and control registers for recording the status and controlling the operation of memory slots such that each memory slot is identified using a bus address and port number |
EP2620838B1 (en) * | 2012-01-26 | 2015-04-22 | ST-Ericsson SA | Automatic partial array self-refresh |
US10157657B2 (en) * | 2012-08-28 | 2018-12-18 | Rambus Inc. | Selective refresh with software components |
KR102011796B1 (en) * | 2012-08-30 | 2019-08-20 | 에스케이하이닉스 주식회사 | Memory device and memory system including the same |
TWI503662B (en) | 2012-12-27 | 2015-10-11 | Ind Tech Res Inst | Memory control device and method |
US10055370B2 (en) * | 2014-07-09 | 2018-08-21 | Advanced Micro Devices, Inc. | Method and apparatis for processor standby |
US10268405B2 (en) * | 2016-03-17 | 2019-04-23 | Mediatek, Inc. | Dynamic rank switching for low power volatile memory |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5737572A (en) * | 1995-06-06 | 1998-04-07 | Apple Computer, Inc. | Bank selection logic for memory controllers |
US20030023825A1 (en) * | 2001-07-30 | 2003-01-30 | Woo Steven C | Consolidation of allocated memory to reduce power consumption |
US20030028711A1 (en) * | 2001-07-30 | 2003-02-06 | Woo Steven C. | Monitoring in-use memory areas for power conservation |
US20060112219A1 (en) * | 2004-11-19 | 2006-05-25 | Gaurav Chawla | Functional partitioning method for providing modular data storage systems |
US20060203589A1 (en) * | 2003-10-31 | 2006-09-14 | Jae-Youl Lee | Self refresh period signal generation device |
US20070106860A1 (en) * | 2005-11-10 | 2007-05-10 | International Business Machines Corporation | Redistribution of memory to reduce computer system power consumption |
US20080049532A1 (en) * | 2006-08-22 | 2008-02-28 | Elpida Memory, Inc. | Semiconductor memory device and refresh control method thereof |
US20090006900A1 (en) * | 2007-06-28 | 2009-01-01 | International Business Machines Corporation | System and method for providing a high fault tolerant memory system |
US20090216939A1 (en) * | 2008-02-21 | 2009-08-27 | Smith Michael J S | Emulation of abstracted DIMMs using abstracted DRAMs |
US20090249169A1 (en) * | 2008-03-28 | 2009-10-01 | Bains Kuljit S | Systems, methods, and apparatuses to save memory self-refresh power |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5901105A (en) | 1995-04-05 | 1999-05-04 | Ong; Adrian E | Dynamic random access memory having decoding circuitry for partial memory blocks |
US6233190B1 (en) | 1999-08-30 | 2001-05-15 | Micron Technology, Inc. | Method of storing a temperature threshold in an integrated circuit, method of modifying operation of dynamic random access memory in response to temperature, programmable temperature sensing circuit and memory integrated circuit |
US6590822B2 (en) | 2001-05-07 | 2003-07-08 | Samsung Electronics Co., Ltd. | System and method for performing partial array self-refresh operation in a semiconductor memory device |
US7426151B2 (en) | 2001-08-14 | 2008-09-16 | Samung Electronics Co., Ltd. | Device and method for performing a partial array refresh operation |
JP4257486B2 (en) * | 2002-02-14 | 2009-04-22 | Okiセミコンダクタ株式会社 | DRAM power supply control device |
KR100474551B1 (en) | 2003-02-10 | 2005-03-10 | 주식회사 하이닉스반도체 | Self refresh apparatus and method |
KR100611774B1 (en) | 2004-06-03 | 2006-08-10 | 주식회사 하이닉스반도체 | Bank based partial array self refresh apparatus in semiconductor memory device and its method |
KR100608370B1 (en) | 2004-11-15 | 2006-08-08 | 주식회사 하이닉스반도체 | Method for refreshing a memory device |
US7342841B2 (en) * | 2004-12-21 | 2008-03-11 | Intel Corporation | Method, apparatus, and system for active refresh management |
KR101183684B1 (en) | 2005-07-13 | 2012-10-18 | 삼성전자주식회사 | DRAM AND Method for Refreshing a Portion of Memory Cell Array |
US7492656B2 (en) | 2006-04-28 | 2009-02-17 | Mosaid Technologies Incorporated | Dynamic random access memory with fully independent partial array refresh function |
US8095725B2 (en) * | 2007-12-31 | 2012-01-10 | Intel Corporation | Device, system, and method of memory allocation |
-
2009
- 2009-12-02 US US12/629,681 patent/US8468295B2/en active Active
-
2013
- 2013-05-14 US US13/893,739 patent/US20130254474A1/en not_active Abandoned
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5737572A (en) * | 1995-06-06 | 1998-04-07 | Apple Computer, Inc. | Bank selection logic for memory controllers |
US20030023825A1 (en) * | 2001-07-30 | 2003-01-30 | Woo Steven C | Consolidation of allocated memory to reduce power consumption |
US20030028711A1 (en) * | 2001-07-30 | 2003-02-06 | Woo Steven C. | Monitoring in-use memory areas for power conservation |
US20060203589A1 (en) * | 2003-10-31 | 2006-09-14 | Jae-Youl Lee | Self refresh period signal generation device |
US20060112219A1 (en) * | 2004-11-19 | 2006-05-25 | Gaurav Chawla | Functional partitioning method for providing modular data storage systems |
US20070106860A1 (en) * | 2005-11-10 | 2007-05-10 | International Business Machines Corporation | Redistribution of memory to reduce computer system power consumption |
US20080049532A1 (en) * | 2006-08-22 | 2008-02-28 | Elpida Memory, Inc. | Semiconductor memory device and refresh control method thereof |
US20090006900A1 (en) * | 2007-06-28 | 2009-01-01 | International Business Machines Corporation | System and method for providing a high fault tolerant memory system |
US20090216939A1 (en) * | 2008-02-21 | 2009-08-27 | Smith Michael J S | Emulation of abstracted DIMMs using abstracted DRAMs |
US20090249169A1 (en) * | 2008-03-28 | 2009-10-01 | Bains Kuljit S | Systems, methods, and apparatuses to save memory self-refresh power |
Non-Patent Citations (1)
Title |
---|
Solaris ZFS Administration Guide > Chapter 11 ZFS Troubleshooting and Pool Recovery > Replacing or Repairing a Damaged Device > Replacing a Device in a ZFS Storage Pool > Viewing Resilvering Status; © 2010, Oracle Corporation; 2 pages * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9880754B2 (en) | 2014-07-09 | 2018-01-30 | Dell Products, Lp | System and method for enabling transportability of a non volatile dual inline memory module |
US20190108896A1 (en) * | 2017-10-05 | 2019-04-11 | Dell Products L.P. | Systems and methods for providing post-package repair visibility to a host for memory reliability, availability, and serviceability |
Also Published As
Publication number | Publication date |
---|---|
US8468295B2 (en) | 2013-06-18 |
US20110131432A1 (en) | 2011-06-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8468295B2 (en) | System and method for reducing power consumption of memory | |
US10365842B2 (en) | System and method for reducing power consumption of memory | |
CN112506422B (en) | Fine granularity refresh | |
TWI614752B (en) | Power conservation by way of memory channel shutdown | |
US7549034B2 (en) | Redistribution of memory to reduce computer system power consumption | |
CN107368433B (en) | Dynamic partial power down of memory-side caches in a level 2 memory hierarchy | |
US9336851B2 (en) | Memory device and method of refreshing in a memory device | |
US20150003172A1 (en) | Memory module including buffer chip controlling refresh operation of memory devices | |
US20120099389A1 (en) | Memory circuits, systems, and modules for performing dram refresh operations and methods of operating the same | |
US9336855B2 (en) | Methods and systems for smart refresh of dynamic random access memory | |
US8244995B2 (en) | System and method for hierarchical wear leveling in storage devices | |
CN105808455B (en) | Memory access method, storage-class memory and computer system | |
US10176107B2 (en) | Methods and systems for dynamic DRAM cache sizing | |
US20130159617A1 (en) | Memory system, and a method of controlling an operation thereof | |
US20220245066A1 (en) | Memory system including heterogeneous memories, computer system including the memory system, and data management method thereof | |
US20140068172A1 (en) | Selective refresh with software components | |
EP4050606A1 (en) | Memory device and operating method thereof | |
US10996876B2 (en) | Systems and methods for dynamically modifying memory namespace allocation based on memory attributes and application requirements | |
Kim et al. | Charge-aware DRAM refresh reduction with value transformation | |
US10732859B2 (en) | Systems and methods for granular non-volatile memory health visibility to a host | |
US8225030B2 (en) | Systems and methods for using a page table in an information handling system comprising a semiconductor storage device | |
US20130311821A1 (en) | Virtual device sparing | |
Agrawal et al. | CLARA: Circular linked-list auto and self refresh architecture | |
US10978133B2 (en) | Memory device and memory system comprising the same | |
US20240078202A1 (en) | Flexible Dual Ranks Memory System To Boost Performance |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: DELL PRODUCTS L.P., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BERKE, STUART ALLEN;SAUBER, WILLIAM;REEL/FRAME:030412/0402 Effective date: 20091130 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: PATENT SECURITY AGREEMENT (TERM LOAN);ASSIGNORS:DELL INC.;APPASSURE SOFTWARE, INC.;ASAP SOFTWARE EXPRESS, INC.;AND OTHERS;REEL/FRAME:031899/0261 Effective date: 20131029 Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, TE Free format text: PATENT SECURITY AGREEMENT (ABL);ASSIGNORS:DELL INC.;APPASSURE SOFTWARE, INC.;ASAP SOFTWARE EXPRESS, INC.;AND OTHERS;REEL/FRAME:031898/0001 Effective date: 20131029 Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, TEXAS Free format text: PATENT SECURITY AGREEMENT (ABL);ASSIGNORS:DELL INC.;APPASSURE SOFTWARE, INC.;ASAP SOFTWARE EXPRESS, INC.;AND OTHERS;REEL/FRAME:031898/0001 Effective date: 20131029 Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS FIRST LIEN COLLATERAL AGENT, TEXAS Free format text: PATENT SECURITY AGREEMENT (NOTES);ASSIGNORS:APPASSURE SOFTWARE, INC.;ASAP SOFTWARE EXPRESS, INC.;BOOMI, INC.;AND OTHERS;REEL/FRAME:031897/0348 Effective date: 20131029 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT (TERM LOAN);ASSIGNORS:DELL INC.;APPASSURE SOFTWARE, INC.;ASAP SOFTWARE EXPRESS, INC.;AND OTHERS;REEL/FRAME:031899/0261 Effective date: 20131029 Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS FI Free format text: PATENT SECURITY AGREEMENT (NOTES);ASSIGNORS:APPASSURE SOFTWARE, INC.;ASAP SOFTWARE EXPRESS, INC.;BOOMI, INC.;AND OTHERS;REEL/FRAME:031897/0348 Effective date: 20131029 |
|
AS | Assignment |
Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: FORCE10 NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: DELL INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: ASAP SOFTWARE EXPRESS, INC., ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: SECUREWORKS, INC., GEORGIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: COMPELLANT TECHNOLOGIES, INC., MINNESOTA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: PEROT SYSTEMS CORPORATION, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: APPASSURE SOFTWARE, INC., VIRGINIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: DELL MARKETING L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 Owner name: CREDANT TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040065/0216 Effective date: 20160907 |
|
AS | Assignment |
Owner name: SECUREWORKS, INC., GEORGIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: CREDANT TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: APPASSURE SOFTWARE, INC., VIRGINIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: FORCE10 NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: PEROT SYSTEMS CORPORATION, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: COMPELLENT TECHNOLOGIES, INC., MINNESOTA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: ASAP SOFTWARE EXPRESS, INC., ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: DELL INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: DELL MARKETING L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040040/0001 Effective date: 20160907 Owner name: DELL MARKETING L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: ASAP SOFTWARE EXPRESS, INC., ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: COMPELLENT TECHNOLOGIES, INC., MINNESOTA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: APPASSURE SOFTWARE, INC., VIRGINIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: FORCE10 NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: PEROT SYSTEMS CORPORATION, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: CREDANT TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: SECUREWORKS, INC., GEORGIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 Owner name: DELL INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040065/0618 Effective date: 20160907 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT, TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MOZY, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MAGINATICS LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: FORCE10 NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SYSTEMS CORPORATION, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL MARKETING L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL INTERNATIONAL, L.L.C., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: CREDANT TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: AVENTAIL LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: ASAP SOFTWARE EXPRESS, INC., ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 |