WO2013110847A1 - Apparatus and method to provide cache move with non-volatile mass memory system - Google Patents

Apparatus and method to provide cache move with non-volatile mass memory system Download PDF

Info

Publication number
WO2013110847A1
WO2013110847A1 PCT/FI2013/050001 FI2013050001W WO2013110847A1 WO 2013110847 A1 WO2013110847 A1 WO 2013110847A1 FI 2013050001 W FI2013050001 W FI 2013050001W WO 2013110847 A1 WO2013110847 A1 WO 2013110847A1
Authority
WO
WIPO (PCT)
Prior art keywords
memory
data
host device
volatile mass
initiator
Prior art date
Application number
PCT/FI2013/050001
Other languages
French (fr)
Inventor
Kimmo J. Mylly
Jani J. Klint
Jani Hyvönen
Tapio Hill
Jukka-Pekka Vihmalo
Matti Floman
Original Assignee
Nokia Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Nokia Corporation filed Critical Nokia Corporation
Priority to KR1020147019265A priority Critical patent/KR102127327B1/en
Priority to CN201380006769.8A priority patent/CN104081366B/en
Priority to KR1020217033814A priority patent/KR102458334B1/en
Priority to EP18213772.9A priority patent/EP3493066B1/en
Priority to CN201810154153.XA priority patent/CN108470007B/en
Priority to KR1020207018006A priority patent/KR102317152B1/en
Priority to JP2014553773A priority patent/JP6193886B2/en
Priority to KR1020227036487A priority patent/KR20220143972A/en
Priority to EP13741595.6A priority patent/EP2795470B1/en
Publication of WO2013110847A1 publication Critical patent/WO2013110847A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G06F3/0607—Improving or facilitating administration, e.g. storage management by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
    • G06F12/023—Free address space management
    • G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
    • G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
    • G06F12/0804—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches with main memory updating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
    • G06F12/0866—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches for peripheral storage systems, e.g. disk cache
    • G06F12/0868—Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
    • G06F12/0888—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches using selective caching, e.g. bypass
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
    • G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • G06F3/0688—Non-volatile semiconductor memory arrays
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C7/00—Arrangements for writing information into, or reading information out from, a digital store
    • G11C7/10—Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers
    • G11C7/1072—Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers for memories with random access ports synchronised on clock signal pulse trains, e.g. synchronous memories, self timed memories
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/10—Providing a specific technical effect
    • G06F2212/1016—Performance improvement
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/10—Providing a specific technical effect
    • G06F2212/1016—Performance improvement
    • G06F2212/1024—Latency reduction
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/10—Providing a specific technical effect
    • G06F2212/1032—Reliability improvement, data loss prevention, degraded operation etc
    • G06F2212/1036—Life time enhancement
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/72—Details relating to flash memory management
    • G06F2212/7202—Allocation control and policies
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/72—Details relating to flash memory management
    • G06F2212/7203—Temporary buffering, e.g. using volatile buffer or dedicated buffer blocks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/72—Details relating to flash memory management
    • G06F2212/7206—Reconfiguration of flash memory system
    • 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

  • Figure 6 shows a block diagram of one exemplary embodiment of the host device when embodied as a wireless communication device.
  • a mass storage memory When a mass storage memory is used in a high volume consumer device, such as a mobile wireless communication device, one important consideration is cost, and one factor affecting the cost is the amount of RAM in the mass storage memory device itself.
  • system context (metadata) would be stored in the flash memory of the mass storage memory device.
  • system context metadata
  • this approach has several associated disadvantages. For example, repeatedly writing the system context (metadata) to the mass storage memory device raises wearing issues that can impact the usable life of the mass storage memory device. Also, writing data to the flash memory can be a relatively slow process.
  • Figure 4 illustrates a further exemplary embodiment described in commonly- assigned US Patent Application No. 12/455,763 that utilizes the host system RAM 14 for the mass storage memory 26 having a built-in file system, such as the FS 26A shown in Figure 2.
  • the host system 10 sends a SHUTDOWN command to the mass storage memory device 20 (operation 4-1).
  • the mass storage memory device 20 allocates RAM 14 from the host 10 and then loads (stores using a RAM WRITE command) all vital 'static' file system-related data (meta-data 24A) into host RAM 14 (operation 4-2).
  • 'Static' data in this context may be, for example, various bitmaps, such as an allocation bitmap in the exFAT or ext3 file systems.
  • the data 14E can be moved to the portion 14G allocated for the mass memory (UFS) to become the data 14E' as described below.
  • UFS mass memory
  • the initiator such as the application program 14B or the OS utility, informs the UFS host controller 13 of the presence of the table of accesses (access list 14F) and the host controller 13 begins the delivery of the commands and any related data to the UFS memory module 20.
  • the UFS host controller 13 transfers this set of (write) commands to the UFS memory module 20.
  • the UFS memory module 20 determines that it is not currently able to handle the data related to the write commands locally in the UFS memory module 20. Note in this regard that there could be, for example, a head of queue indication by the initiator related to the commands to emphasize the urgency for the execution of the write command(s), and the UFS memory module 20 determines that it is not currently able to meet the indicated level of urgency.
  • the UFS memory module 20 moves the data e.g. from the transfer buffer 14D (or 14B/14C) to the reserved separate physical address space (allocated portion 14G) of the system DRAM 14.
  • the move operation and the allocated portion 14G of the system DRAM 14 is controlled by the UFS memory module 20 via the UFS host controller 13.
  • the UFS host controller 13 controls the system DRAM 14, or the system DRAM controller 11, to execute the move of the data 14E from e.g. the transfer buffer 14D to the allocated portion 14G as the data 14E'.
  • the UFS host controller 13 can be assumed to perform this operation e.g. by means of operating as DMA master (of either a dedicated UFS DMA or system DMA) directly and can bypass the host CPU 12.
  • the UFS memory module 20 need not process received access commands sequentially. For example, before processing the write command from the second initiator if another write command having a higher indicated priority arrives from a third initiator, where the write data has also been stored in the allocated portion 14G, the UFS memory module 20 could process the write command from the third initiator and then process the write command from the second initiator.
  • the mass memory module 20 can use header information created by the host CPU 12.
  • the header information can use separate bits for host valid/invalid, reserved and mass memory valid/invalid allocations and can be stored in the system DRAM 14. In this case by modifying the header information (e.g., allocated/ free) the mass memory module 20 could "move" data from host CPU 12 controlled addresses to addresses controlled by the mass memory module 20.
  • Figure 5C shows an embodiment of this invention, as discussed above, where the access list 14F references the data 14B', and the referenced data is then directly moved to the allocated portion (as data 14E') thereby bypassing the transfer buffer 14D (i.e., the data 14B' after being moved directly becomes the data 14E').
  • the data could originate from a source other than the host CPU 12 (e.g., other than from the application processor).
  • the data could originate from an initiator that is embodied as a peripheral device 60 that is connected to the host device 10 either by a wired connection or a wireless connection.
  • the mass memory module 20 instead of moving the data directly from the peripheral device 60 to the mass memory module 20 the mass memory module 20 causes the data to be stored in the system DRAM 14, such as in the allocated portion 14G.
  • the data that originates at the peripheral device 60 is thus temporarily (and transparently to the peripheral device 60) cached in the system DRAM 14.
  • one of the processing capacity bottlenecks of a wireless terminal is the execution memory, especially the memory bus.
  • the execution memory also known as work memory, it is connected to a host ASIC by a bus that has a limited transfer capacity (bandwidth).
  • the host ASIC can contain several memory masters (e.g., processors, accelerators, and DMA engines) and one DRAM controller 11 that provides the external memory bus. At the other end of this bus is the memory device (DRAM component). Memory masters issue read and write requests to the memory.
  • the DRAM is built of several banks (4 to 8 typically) that could operate in parallel. Thus, while parallelism exists at both ends of the memory bus, the memory bus itself is a single- threaded arrangement.
  • the exemplary aspects of this invention include providing a means to fully exploit the memory device by enabling internal operations to be performed locally. This improves the overall memory subsystem performance, enhances CPU capacity by off-loading some operations from the CPU, and decreases power consumption.
  • the exemplary aspects of this invention provide for some elementary operations to be carried out by the memory device through the use of an enhanced command set.
  • At least some elementary in-memory operations are removed from the responsibility of the CPU 12 and transferred to the system DRAM 14, such as to the controller 15 that can be embedded with the system DRAM 14.
  • system DRAM controller 11 or the system DRAM module (control 15) may analyse commands issued for it and initiate a "smart memory” operation such as a memory fill or a memory move operation.
  • the additional functionality added to, for example, the controller 15 may include at least a data fill feature and a data move feature.
  • the additional functionality optionally includes security functions for the system DRAM 14, pack/unpack functions between the system DRAM 14 and the mass memory 26, data transaction functions between the DRAM 14 and the mass memory 26 and, for example, mass memory related error detection and correction and wear levelling functions.
  • a Data Move operation can be a read/write (copy) sequence followed by a Fill operation to the region of system DRAM 14 from which the data was moved (read).
  • the Fill operation could set the memory locations to some predetermined value (e.g., zero), or to a value specified by the Data Move operation command in a manner analogous to the Fill operation discussed above.
  • the Fill operation can be optional, so that the Data Move operation functions as a Data Copy operation (i.e., the data is replicated to another location while the original data is unchanged).
  • a non- limiting example of the implementation of the smart memory functionality at the command level is as follows.
  • LPDDR1 Low Power Double Data Rate
  • JEDEC e.g., see JEDEC Standard, Low Power Double Data Rate (LPDDR) SDRAM Standard, JESD209B, February 2010
  • MRS Mode Register Set
  • Target address fill, move
  • source address move
  • LPDDR2 and LPDDR3 Mode Register Write commands could be used in a similar fashion. It should be understood that conventional LPDDRx solutions allow MRS and MRW operation only from DRAM idle state, but other solutions are technically possible. One such implementation may be to require that the data which is the source or the target of the move or fill operation is located in open DRAM pages.
  • Full command and address delivery may occur in a single or a multiple command sequence - a certain command code may, for example, indicate multicycle delivery via cmd/address/data bus as suits the implementation.
  • the particular implementation dictates the requirements for the data and address granularity, requirements for the memory state prior to and after the smart memory feature operations, whether the memory internally uses some intermediate buffers to move or fill the data or whether open rows (DRAM sense amps) are reserved during the entire operation, any timing requirements, etc.
  • the command could be issued by the, for example, the CPU 12 (e.g., by an OS or file system utility) or by the mass memory host controller 13 and then autonomously executed by the controller 15 associated with the system DRAM 14 or by the DRAM memory controller 11.
  • the CPU 12 e.g., by an OS or file system utility
  • the mass memory host controller 13 e.g., by the mass memory host controller 13 and then autonomously executed by the controller 15 associated with the system DRAM 14 or by the DRAM memory controller 11.
  • FIG. 6 illustrates one non- limiting embodiment of the host device 10 used with the mass storage memory device 20, referred to in Figure 6 simply as a memory card 20.
  • the mass storage memory device 20 can be removable or it can be embedded in the device 10.
  • the host device 10 is embodied as a user equipment (UE), shown in both plan view (left) and sectional view (right).
  • the host device (UE) 10 has a graphical display interface 120 and a user interface 122 illustrated as a keypad but understood as also encompassing touch screen technology at the graphical display interface 120 and voice recognition technology received at a microphone 124.
  • a power actuator 126 controls the device being turned on and off by the user.
  • the exemplary UE 10 may have a camera 128 which is shown as being forward facing (e.g., for video calls) but may alternatively or additionally be rearward facing (e.g., for capturing images and video for local storage).
  • the camera 128 is controlled by a shutter actuator 30 and optionally by a zoom actuator 32 which may alternatively function as a volume adjustment for the speaker(s) 34 when the camera 128 is not in an active mode.
  • image data captured by the camera 128 can be stored in the mass storage memory device 20 under control of a camera application and can thus benefit from the use of the embodiments of this invention.
  • audio data captured by the microphone 124 can be stored in the mass storage memory device 20 under control of an audio application and can thus also benefit from the use of the embodiments of this invention.
  • the antennas 36 may be multi-band for use with other radios in the UE.
  • the operable ground plane for the antennas 36 is shown by shading as spanning the entire space enclosed by the UE housing though in some embodiments the ground plane may be limited to a smaller area, such as disposed on a printed wiring board on which the power chip 38 is formed.
  • the power chip 38 controls power amplification on the channels being transmitted and/or across the antennas that transmit simultaneously where spatial diversity is used, and amplifies the received signals.
  • the power chip 38 outputs the amplified received signal to a radio frequency (RF) chip 40 which demodulates and downconverts the signal for baseband processing.
  • RF radio frequency
  • a baseband (BB) chip 42 detects the signal which is then converted to a bit stream and finally decoded. Similar processing occurs in reverse for signals generated in the host device 10 and transmitted from it.
  • Signals going to and from the camera 128 may pass through an image/video processor 44 that encodes and decodes the various image frames.
  • a separate audio processor 46 may also be present controlling signals to and from the speakers 34 and the microphone 124.
  • the graphical display interface 120 is refreshed from a frame memory 48 as controlled by a user interface chip 50 which may process signals to and from the display interface 20 and/or additionally process user inputs from the keypad 22 and elsewhere.
  • the UE 10 may also include one or more secondary radios such as a wireless local area network radio WLAN 37 and a Bluetooth7 radio 39, which may incorporate an antenna on the chip or be coupled to an antenna off the chip.
  • secondary radios such as a wireless local area network radio WLAN 37 and a Bluetooth7 radio 39, which may incorporate an antenna on the chip or be coupled to an antenna off the chip.
  • various memories such as random access memory RAM, which can include the system DRAM 14, read only memory ROM 45, and in some embodiments removable memory such as the illustrated memory card 20 on which various programs and data may be stored. All of these components within the UE 10 are normally powered by a portable power supply such as a battery 49.
  • the processors 38, 40, 42, 44, 46, 50 may operate in a slave relationship to the main processor (CPU) 12, which may then be in a master relationship to them.
  • Certain embodiments may be disposed across various chips and memories as shown, or disposed within another processor that combines some of the functions described above for Figure 6. Any or all of these various processors of Figure 6 access one or more of the various memories, which may be on chip with the processor or separate from the chip with the processor.
  • the various integrated circuits e.g., chips 38, 40, 42, etc.
  • chips 38, 40, 42, etc. that were described above may be combined into a fewer number than described and, in a most compact case, may all be embodied physically within a single chip.
  • the CPU 12 of the UE 10 (the host device) operates with the memory card 20 (the mass storage memory device) as described above with respect to Figures 5A, 5B and 5C so that the memory card 20 can be extended to use at least a portion of the system Dynamic RAM 14 of the UE 10 as described above.
  • An aspect of the exemplary embodiments of this invention is a method, shown in Figure 7, that includes (7 A) receiving a command (the command can arrive, for example, via a file system layer (SW) and a driver layer (SW) and a host controller (HW)) originating from an initiator (e.g., an application, a file system, a driver or an OS utility) at a controller (e.g., a memory controller) associated with a non-volatile mass memory coupled with a host device.
  • the command is a command to write data that is currently resident in a memory of the host device to the non- volatile mass memory.
  • the memory of the host device may comprise, as non-limiting examples, DRAM, MRAM, PCM (phase change memory), RRAM (resistive random access memory), magnetic random access memory, ferroelectric random access memory and the like.
  • the method further includes (7B) moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non-volatile mass memory.
  • the method further includes (7C) acknowledging to the initiator that the command to write the data to the non- volatile mass memory has been executed In the method described in Figure 7 and the preceding paragraph, further comprising, subsequent to acknowledging, moving the data from the memory of the host device to the non- volatile mass memory.
  • the initiator comprises at least one of an application program, a file system, a driver, and an operating system utility.
  • the initiator is embodied as a peripheral device that is connected with the host device.
  • the memory of the host device comprises a dynamic random access memory, and further comprising autonomously performing an elementary memory operation in the memory of the host device.
  • the elementary memory operation is a data fill operation to set a specified plurality of memory locations to a specified value.
  • the elementary memory operation is a data move operation to move data from a first specified plurality of memory locations to a second specified plurality of memory locations.
  • the data move operation further comprises setting the first specified plurality of memory locations to a predetermined value.
  • FIG. 8 is a logic flow diagram that illustrates the operation of a method, and a result of execution of computer program instructions embodied on a computer readable memory, further in accordance with the exemplary embodiments of this invention.
  • a method performs, at Block 8A, providing a data processing system comprising at least one data processor and at least one memory comprised of dynamic random access memory.
  • a step of autonomously performing an elementary memory operation in the memory is a step of autonomously performing an elementary memory operation in the memory.
  • the elementary memory operation is a data fill operation to set a specified plurality of memory locations to a specified value.
  • the elementary memory operation is a data move operation to move data from a first specified plurality of memory locations to a second specified plurality of memory locations.
  • the data move operation further comprises setting the first specified plurality of memory locations to a predetermined value.
  • the various blocks shown in Figures 7 and 8 may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function(s).
  • the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto.
  • the integrated circuit, or circuits may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor or data processors, a digital signal processor or processors, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this invention.
  • An apparatus in accordance with the exemplary embodiments includes means for sending a command from a host device to a controller associated with a non- volatile mass memory coupled with the host device, the command being a command to write data that is currently resident in a memory of the host device to the non- volatile mass memory; means for moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use by the non-volatile mass memory; and means for acknowledging to the host device that the command to write the data to the non- volatile mass memory has been executed.
  • connection means any connection or coupling, either direct or indirect, between two or more elements, and may encompass the presence of one or more intermediate elements between two elements that are “connected” or “coupled” together.
  • the coupling or connection between the elements can be physical, logical, or a combination thereof.
  • two elements may be considered to be “connected” or “coupled” together by the use of one or more wires, cables and/or printed electrical connections, as well as by the use of electromagnetic energy, such as electromagnetic energy having wavelengths in the radio frequency region, the microwave region and the optical (both visible and invisible) region, as several non- limiting and non-exhaustive examples.

Abstract

A method includes, in one non-limiting embodiment,receiving a command originating from an initiator at a controller associated with a non-volatile mass memory coupled with a host device, the command being a command to write data that is currently resident in a memory of the host device to thenon-volatile mass memory; moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non-volatile mass memory; and acknowledging to the initiator that the command to write the data to the non-volatile mass memory has been executed.An apparatus configured to perform the method is also described.

Description

APPARATUS AND METHOD TO PROVIDE CACHE MOVE WITH NONVOLATILE MASS MEMORY SYSTEM
TECHNICAL FIELD:
The exemplary and non-limiting embodiments of this invention relate generally to memory storage systems, methods, devices and computer programs and, more specifically, relate to mass memory devices, such as those containing non- volatile flash memory.
BACKGROUND:
This section is intended to provide a background or context to the invention that is recited in the claims. The description herein may include concepts that could be pursued, but are not necessarily ones that have been previously conceived, implemented or described. Therefore, unless otherwise indicated herein, what is described in this section is not prior art to the description and claims in this application and is not admitted to be prior art by inclusion in this section.
The following abbreviations that may be found in the specification and/or the drawing figures are defined as follows:
ASIC application specific integrated circuit
CPU central processing unit
DMA direct memory access
eMMC embedded multimedia card
exFAT extended file allocation table
HW hardware
JEDEC Joint Electron Device Engineering Council
LBA logical block address
MMC MultiMediaCard
MRAM magnetic random access memory
RAM random access memory
SCSI small computer system interface
SD secure digital
SW software
UFS universal flash storage Various types of flash-based mass storage memories currently exist. A basic premise of mass storage memory is to hide the flash technology complexity from the host system. A technology such as eMMC is one example. A managedNAND type of memory can be, for example, an eMMC, SSD, UFS or a microSD.
Figure 1A reproduces Figure 2 from JEDEC Standard, Embedded
MultiMediaCard (eMMC) Product Standard, High Capacity, JESD84-A42, June 2007, JEDEC Solid State Technology Association, and shows a functional block diagram of an eMMC. The JEDEC eMMC includes, in addition to the flash memory itself, an intelligent on-board controller that manages the MMC communication protocol. The controller also handles block-management functions such as logical block allocation and wear leveling. The interface includes a clock (CLK) input. Also included is a command (CMD), which is a bidirectional command channel used for device initialization and command transfers. Commands are sent from a bus master to the device, and responses are sent from the device to the host. Also included is a bidirectional data bus (DAT[7:0]). The DAT signals operate in push-pull mode. By default, after power-up or RESET, only DAT0 is used for data transfer. The memory controller can configure a wider data bus for data transfer using either DAT[3:0] (4-bit mode) or DAT[7:0] (8- bit mode).
One non-limiting example of a flash memory controller construction is described in "A NAND Flash Memory Controller for SD/MMC Flash Memory Card", Chuan-Sheng Lin and Lan-Rong Dung, IEEE Transactions of Magnetics, Vol. 43, No. 2, February 2007, pp. 933-935 (hereafter referred to as Lin et al.) Figure IB reproduces Figure 1 of Lin et al, and shows an overall block diagram of the NAND flash controller architecture for a SD/MMC card. The particular controller illustrated happens to use a w-bit parallel Bose-Chaudhuri-Hocquengham (BCH) error-correction code (ECC) designed to correct random bit errors of the flash memory, in conjunction with a code-banking mechanism.
SUMMARY
In a first aspect thereof the exemplary embodiments of this invention provide a method that comprises receiving a command originating from an initiator at a controller associated with a non- volatile mass memory coupled with a host device, the command being a command to write data that is currently resident in a memory of the host device to the non- volatile mass memory; moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non-volatile mass memory; and acknowledging to the initiator that the command to write the data to the non- volatile mass memory has been executed.
In another aspect thereof the exemplary embodiments of this invention provide an apparatus that comprises a controller associated with a non-volatile memory module connected with a host device and an interface to the non-volatile mass memory module. The controller is configurable to process a command originating with an initiator, where the command is a command to write data that is currently resident in a memory of the host device to the non-volatile mass memory module. The controller is further configurable to move the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non-volatile mass memory module; and to acknowledge to the initiator that the command to write the data to the non- volatile mass memory has been executed.
In another aspect thereof the exemplary embodiments of this invention provide a method that comprises providing a data processing system comprising at least one data processor and at least one memory comprised of dynamic random access memory, and autonomously performing an elementary memory operation in the memory.
In yet another aspect thereof the exemplary embodiments of this invention provide a memory module that comprises a controller; a non- volatile mass memory that is readable and writable by the controller; and an interface for connecting the memory module to a host device. The controller is configurable to receive a command originating from an initiator, where the command being a command to write data that is currently resident in a memory of the host device to the non-volatile mass memory module. The controller is further configurable to initiate the move of the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non-volatile mass memory module; and to acknowledge to the initiator that the command to write the data to the non-volatile mass memory has been executed.
BRIEF DESCRIPTION OF THE DRAWINGS
In the attached Drawing Figures: Figure 1A reproduces Figure 2 from JEDEC Standard, Embedded MultiMediaCard (eMMC) Product Standard, High Capacity, JESD84-A42, June 2007, JEDEC Solid State Technology Association, and shows a functional block diagram of an eMMC.
Figure IB reproduces Figure 1 of Lin et al., and shows an example of an overall block diagram of a NAND flash controller architecture for a SD/MMC card.
Figure 2 is a simplified block diagram of a host device connected with a mass storage memory device, and is helpful in describing the exemplary embodiments of this invention.
Figure 3 is a signal/message flow diagram that describes an embodiment of the invention described in commonly-assigned US Patent Application No.: 12/455,763, where the mass storage memory device of Figure 2 can allocate, use and de-allocate RAM of the host device.
Figure 4 is a signal/message flow diagram that describes another embodiment of the invention described in commonly-assigned US Patent Application No.: 12/455,763, where the mass storage memory device of Figure 2 has a built-in file system.
Figures 5A, 5B and 5C, collectively referred to as Figure 5, show an embodiment of the host device and mass storage memory device of Figure 2 in accordance with embodiments of this invention.
Figure 6 shows a block diagram of one exemplary embodiment of the host device when embodied as a wireless communication device.
Figure 7 is a logic flow diagram that illustrates the operation of a method, and a result of execution of computer program instructions embodied on a computer readable memory, in accordance with the exemplary embodiments of this invention.
Figure 8 is a logic flow diagram that illustrates the operation of a method, and a result of execution of computer program instructions embodied on a computer readable memory, further in accordance with the exemplary embodiments of this invention.
DETAILED DESCRIPTION
Of interest to the ensuing description of the exemplary embodiments of this invention is commonly-assigned US Patent Application No.: 12/455,763, filed 06/04/2009, "Apparatus and Method to Share Host System RAM with Mass Storage Memory RAM", Olli Luukkainen, Kimmo Mylly and Jani Hyvonen (US 2010/0312947 Al), incorporated by reference herein. Before describing in detail the exemplary embodiments of this invention it will be useful to review at least a portion of the description of this commonly-assigned US Patent Application No. 12/455,763.
As is stated, at present most mass storage memories provide LBA-based access, e.g., eMMC and different types of external memory cards such as SD. However, it may also be the case that the entire file system (FS) SW is embedded in the mass storage memory device.
When a mass storage memory is used in a high volume consumer device, such as a mobile wireless communication device, one important consideration is cost, and one factor affecting the cost is the amount of RAM in the mass storage memory device itself.
Another important consideration is performance. The overall performance depends on many factors. For example, for lengthy (time consuming) operations (in particular if the mass storage memory device contains an entire file system SW) there would be an advantage to include a substantial amount of RAM in the mass storage memory device. However, this can have a negative impact on the cost.
It may be the case that system context (metadata) would be stored in the flash memory of the mass storage memory device. However, this approach has several associated disadvantages. For example, repeatedly writing the system context (metadata) to the mass storage memory device raises wearing issues that can impact the usable life of the mass storage memory device. Also, writing data to the flash memory can be a relatively slow process.
Another important consideration is the power efficiency. To provide good power efficiency the mass storage memories are preferably shutdown (powered-off) when not needed (meaning also that the internal RAM of the device is preferably shutdown as well). However, and assuming that the RAM is volatile in nature, then whatever data is stored in the RAM is lost when the power is removed from the RAM. To then perform reinitialization after power-up all needed information (e.g., logical-to- physical mapping information and/or file system structures) need to be restored. A full re-initialization of a LBA mass storage memory may require a substantial (and user-noticeable) amount of time (e.g., up to one second with an SD card), and entire file system initialization (if the file system is resident in the mass storage memory) may take even longer. Therefore, it is desirable to retain internal device context over the power-off/power-on cycle.
Figure 2 shows is a simplified block diagram of a host system or device 10 connected with a mass storage memory 20 via a mass storage memory bus (MSMB) 18. The MSMB 18 may be compatible with any suitable mass memory interface standard such as MMC or UFS, as two non- limiting examples. The MSMB 18 may include signal lines such as those shown in Figure 1A for an eMMC embodiment. The host device 10 includes at least one controller, such as a CPU 12 that operates in accordance with stored program instructions. The program instructions may be stored in a RAM 14 or in another memory or memories. The CPU 12 is connected with the RAM 14 and a MSMB interface (I/F) 16 via at least one internal bus 17. The MSMB interface 16 may include a memory controller (MC), or may be coupled with a MC unit associated with the CPU 12. The host device 10 may be a computer, a cellular phone, a digital camera, a gaming device or a PDA, as several non- limiting examples. Note that the RAM 14 may be any read/write memory or memory device, such as semiconductor memory or a disk-based memory.
The mass storage memory 20 includes a microcontroller or, more simply, a controller 22 that is connected via at least one internal bus 27 with a volatile RAM 24, a non-volatile mass memory 26 (e.g., a multi-gigabyte flash memory mass storage) and a MSMB interface (I/F) 28. The controller 22 operates in accordance with stored program instructions. The program instructions may be stored in the RAM 24 or in a ROM or in the mass memory 26. The mass storage memory 20 may be embodied as an MMC, eMMC or a SD device, as non-limiting examples, and may be external to (plugged into) the host device 10 or installed within the host device 10. Note that the mass memory 26 may, in some embodiments, store a file system (FS) 26A. In this case then the RAM 24 may store FS-related metadata 24A, such as one or more data structures comprised of bit maps, file allocation table data and/or other FS-associated information.
The embodiments of the invention described in commonly-assigned US Patent Application No. 12/455,763 provide a technique to share the RAM 14 of the host device 10 with the mass storage memory device 20. It can be assumed that the host device 10 (e.g., a mobile computer, a cellular phone, a digital camera, a gaming device, a PDA, etc.) has the capability to allocate and de-allocate the RAM 14. The allocation of the RAM 14 may be performed dynamically or it may be performed statically. The allocation of a portion of the RAM may be performed in response to a request received at the host device 10, or at the initiative of the host device 10.
In the embodiments of the invention described in commonly-assigned US Patent Application No. 12/455,763 the RAM 14 allocation is provided for the mass storage memory 20 (connected via the MSMB 18 to the host CPU 12), if the mass storage memory 20 has a need to extend its own RAM 24 space and/or if the mass storage memory 20 has a need for non- volatile RAM (the contents of which are not lost when the mass storage memory 20 is powered-off). The mass storage memory 20 can also read and/or write (R/W) allocated RAM 14 in the host device 10. The allocation/de-allocation and R/W access methods can be implemented by extensions to a command set used to communicate with the mass storage memory 20 via an applicable mass storage memory protocol.
In accordance with certain embodiments of the invention described in commonly- assigned US Patent Application No. 12/455,763 the mass storage memory device 20 is provided with a mechanism to interrupt/send a message to host device 10 to initiate an allocation of space in the RAM 14. The interrupt/message is sent over the MSMB 18, and may be considered as an extension to current command sets. Referring to Figure 3, an allocate memory command is sent during operation 3-1. If the allocation request succeeds (indicated during operation 3-2) the controller 22 is enabled to extend its own RAM 24 with the RAM 14 of the host device 10. The mass storage memory device 20 may store, for example, large tables into the RAM 14 using a RAM WRITE command or it may fetch data from the host device RAM 14 using a RAM READ command. The read or write operation is shown as interleaved operations 3-3, 3-4, 3-5, 3-6, 3-(N-l), 3-N. When the mass storage memory device 20 completes the operation with the RAM 14 it may free the host device RAM 14 using another command that requests that the host 10 RAM memory be de-allocated (operation 3-(N+l)).
Figure 4 illustrates a further exemplary embodiment described in commonly- assigned US Patent Application No. 12/455,763 that utilizes the host system RAM 14 for the mass storage memory 26 having a built-in file system, such as the FS 26A shown in Figure 2. First the host system 10 sends a SHUTDOWN command to the mass storage memory device 20 (operation 4-1). Next the mass storage memory device 20 allocates RAM 14 from the host 10 and then loads (stores using a RAM WRITE command) all vital 'static' file system-related data (meta-data 24A) into host RAM 14 (operation 4-2). 'Static' data in this context may be, for example, various bitmaps, such as an allocation bitmap in the exFAT or ext3 file systems. This data may be processed (e.g., at least one of sorted, arranged and filtered) by the CPU 12 (controller) of the host device, and may include data from a large number of sectors in the mass storage memory 26. Mass memory storage device 20 may then send a shutdown OK indication (operation 4-3). The host 10 can remove power from the mass memory storage device 20, and the device 20 may be physically removed from the MSMB 18. Re-initialization (operations 4-4, 4-5, 4-6) ofthe mass storage memory device 20 is performed when host device 10 needs to get/put certain data from or into the mass storage memory device 20. Re-initialization ofthe mass storage memory 26 (and the file system 26A) may be sped up by using the sorted/arranged/filtered read data from the RAM 14. When the re-initialization operation is completed the mass storage memory device 20 may de-allocate the used RAM 14 in the host device 10, or the RAM 14 may not be de-allocated thereby reserving the RAM space for future use by the mass storage memory device 20.
The allocation of host RAM 14 may occur differently in some embodiments. For example, the host device 10 may allocate RAM 14 dynamically and pass a 'pointer' to the allocated RAM to the mass storage memory device 20. It is then up to the controller 22 of the mass storage memory device 20 how to utilize the allocated host RAM 14. Note that in this embodiment an explicit allocation request from the mass storage memory device 20 may not be sent to the host device 10. Instead, the host device 10 may on its own initiative allocate a portion of the RAM 14, such as when it first detects the presence of the mass memory storage device 20. Of course, subsequent signaling between the mass storage memory device 20 and the host device 10 may be used to change the size of the allocated RAM 14 if the initial allocation is not sufficient for the needs of the controller 22. As another example of RAM 14 allocation, a portion of the RAM 14 may be allocated by the host 10 in a static manner and the mass storage memory device 20 then simply uses the same portion of the RAM 14 each time it needs to extend the RAM 24. In this case the mass storage memory device 20 may already have knowledge of the location/size of the allocated RAM 14, and a pointer is not needed to be sent from the host device 10.
Note that while it may typically be the case that the mass storage memory device
20 will receive an allocation of host memory to store contents of the volatile RAM 24, in general the allocation may be for storing data for any read/write memory contained within the mass storage memory device 20.
Having thus provided an overview of various non-limiting and exemplary embodiments of the invention described in the commonly-assigned US Patent Application No. 12/455,763, a description is now made of the exemplary embodiments of this invention.
In a managedNAND memory (e.g., eMMC, SSD, UFS, microSD) the memory controller (such as the controller 22 shown in Figure 2) takes care of the flash management functions such as bad block management and wear leveling. In a typical low cost implementation there is only a small input/output (10) buffer SRAM in the managedNAND. Embedded in the controller in higher end managedNANDs such as SSDs there may be tens to hundreds of megabits of discrete DRAM as cache. In the future some new memory technologies such as MRAM could serve as very fast non-volatile cache also.
In a modern multi-tasking mobile device environment there may be many different types of accesses from different initiators that are queued to the mass storage at the same time. In the eMMC case the queued accesses would be served one-by-one since the eMMC device can only handle a single thread at a time. In the UFS case it is possible to send the accesses/commands to a UFS device queue. However, even though the commands can be queued this does not ensure that there necessarily are sufficient resources at the UFS device (especially in a cost optimized model) to immediately accommodate all of the data related to the queued accesses.
The above described commonly-assigned US Patent Application No. 12/455,763 provides a model in which the mass storage memory 20 is provided with read/write access to the system DRAM 14. This concept is extended by the exemplary embodiments of this invention to enable the mass storage memory 20 to move data within the system DRAM, either logically (by the use of pointers) or physically. The actual move could occur within the DRAM 14 or the data could travel back and forth over the system DRAM bus 17 (e.g., between the system DRAM 14 and a Mass Memory Host Controller 13 DMA buffer). The Mass Memory Host Controller 13, shown in Figure 5A and described in detail below, can be considered to function in this regard as a DMA master and thus can include its own associated DMA data buffers for this purpose.
The foregoing features can be realized through the use of several embodiments. In a first embodiment a separate physical address space in the system DRAM 14 is reserved for the mass storage memory 20, or a logical space is reserved if the system DRAM 14 operates in a logical address space. The mass storage memory (such as the UFS mass storage memory 20) can utilize this address space freely, and is responsible for the management functions of this address space such as allocation/deallocation functions and other functions.
Reference can be made to Figure 5 where those components described in reference to Figure 2 are numbered accordingly. In Figures 5A, 5B and 5C a portion 14G of the system DRAM 14 is allocated for use by the mass memory module 20 (described here in a non-limiting embodiment as a UFS memory module). The host device 10 includes an application processor that can be embodied as the CPU 12. Included with or coupled to the application processor 12 may be a DRAM controller 11. Also present is the above- mentioned mass memory module (e.g., UFS) host controller 13. The host controller 13 can be embodied as the CPU 12 or it can be embodied as a separate device. Figure 5B shows that the system DRAM 14 stores an operating system (OS) 14A and application programs (applications) 14B. At least some of the applications 14B generate data 14B'. The system DRAM 14 also typically stores a file system cache 14C associated with a file system (part of the OS 14A). In the embodiment of Figure 5B a portion of the system DRAM 14 is allocated as a transfer buffer 14D to which the application data 14B' can be moved to become transfer buffer data 14E. Another portion of the system DRAM 14 is allocated to store an access list 14F. Also included is the DRAM portion 14G that is allocated for the UFS memory module 20, and into which the transfer buffer data 14E can be moved to become data 14E'. The operation of these components shown in Figures 5A, 5B and 5C is now described in further detail.
Assume that a source of data such as an application 14B, or a file system cache, or a file cache entity (as non- limiting examples) has data 14B' to be stored into the mass memory module 20. The data 14B' is moved to the transfer buffer 14D as the transfer data 14E by a file system/driver for subsequent delivery to the mass memory module 20. Optionally, as shown in Figure 5C and discussed in further detail below, the data 14B' could be moved directly from its original location thereby bypassing the transfer buffer 14D. The access list 14F is created in the system DRAM 14 for the application 14B such as by an OS utility and points to the location of the data 14E. Note in this regard that an "application" (if understood here in a conventional sense as a third party application) cannot itself create any access lists. Instead the application creates read/write accesses and functions as an initiator. The access lists are created typically by some OS services/memory subsystem (e.g. some driver layer or some OS utility) based on accesses coming through the file system layer. In effect the access lists are constructed or built for the application. An initiator may be, as a non-limiting example, an application, a file system, a driver or an OS utility.
In accordance with an aspect of this invention the data 14E can be moved to the portion 14G allocated for the mass memory (UFS) to become the data 14E' as described below.
An access may take place by the host device 10 as follows (it is assumed that the host device 10 has already correctly initiated the mass storage memory 20).
(1) An initiator, such as an application program 14B resident in the system DRAM 14 that is being executed by the CPU 12, has built for itself (e.g., by an OS utility) a table of accesses (access list 14F) to the UFS memory module 20 in the system DRAM 14. Assume for this example that the execution of these accesses would exhaust the resources of the UFS memory module 20 for some period of time.
(2) The initiator, such as the application program 14B or the OS utility, informs the UFS host controller 13 of the presence of the table of accesses (access list 14F) and the host controller 13 begins the delivery of the commands and any related data to the UFS memory module 20.
(3) The same or another initiator, such as the same or a different application program 14B, has built for itself another table of write accesses (another access list 14F) to the UFS memory module 20 in the system DRAM 14 and the UFS host controller 13 is informed of the presence of the table of accesses.
(4) The UFS host controller 13 transfers this set of (write) commands to the UFS memory module 20. Assume that the UFS memory module 20 determines that it is not currently able to handle the data related to the write commands locally in the UFS memory module 20. Note in this regard that there could be, for example, a head of queue indication by the initiator related to the commands to emphasize the urgency for the execution of the write command(s), and the UFS memory module 20 determines that it is not currently able to meet the indicated level of urgency. (5) Instead of receiving the data related to the write commands the UFS memory module 20 moves the data e.g. from the transfer buffer 14D (or 14B/14C) to the reserved separate physical address space (allocated portion 14G) of the system DRAM 14. The move operation and the allocated portion 14G of the system DRAM 14 is controlled by the UFS memory module 20 via the UFS host controller 13. The UFS host controller 13 controls the system DRAM 14, or the system DRAM controller 11, to execute the move of the data 14E from e.g. the transfer buffer 14D to the allocated portion 14G as the data 14E'. The UFS host controller 13 can be assumed to perform this operation e.g. by means of operating as DMA master (of either a dedicated UFS DMA or system DMA) directly and can bypass the host CPU 12.
(6) After the physical move of the data 14E to the allocated portion 14G occurs the UFS memory module 20 can respond to the original (write) command as though it had actually moved the data to the non-volatile memory (NVM), i.e., to the mass memory 26. As a result the second initiator can consider that the write command(s) to the mass memory 20 have been executed and can continue its processing operations, even though the write data is currently resident as the data 14E' in the allocated portion 14G of the system DRAM 14.
(7) At some future time the UFS memory module 20 has sufficient resources to process the write command from the second initiator. At this time it independently fetches the data from the system DRAM 14 (from the allocated portion 14G ofthe system DRAM 14) and stores it in the NVM mass memory 26. From the point of view of the initiator or the file system layer of the OS 14A this operation is transparent, and appears as though there is physical DRAM/SRAM cache within the UFS memory module 20. That is, the external allocated portion 14G of the system DRAM 14 can function in a manner analogous to a virtual DRAM/SRAM cache of the UFS memory module 20.
Note that the UFS memory module 20 need not process received access commands sequentially. For example, before processing the write command from the second initiator if another write command having a higher indicated priority arrives from a third initiator, where the write data has also been stored in the allocated portion 14G, the UFS memory module 20 could process the write command from the third initiator and then process the write command from the second initiator.
In another embodiment there need be no specific separate memory addresses reserved in the system DRAM 14 for the mass memory module 20. Instead the mass memory module 20 can have access to any (or almost any) location in the system DRAM 14. In this case instead of moving data physically in the system DRAM 14 the mass memory module 20 can control a list of memory pointers created by the host CPU 12. By modifying the lists of pointers (one list of pointers for host and another for the mass memory module 20) the mass memory module 20 can virtually "move" data from host CPU-controlled logical memory space to space controlled by the mass memory module 20. Note that in this case the transfer buffer 14D will/may still be present, however there is no need for the physical portion 14G allocated for the mass memory module 20.
Alternatively, the mass memory module 20 can use header information created by the host CPU 12. The header information can use separate bits for host valid/invalid, reserved and mass memory valid/invalid allocations and can be stored in the system DRAM 14. In this case by modifying the header information (e.g., allocated/ free) the mass memory module 20 could "move" data from host CPU 12 controlled addresses to addresses controlled by the mass memory module 20.
Either or both of these operations can be mediated by the host controller 13. There can be a read command from an application to an address of which the data is still located in an area of the system DRAM 14 reserved for the non- volatile module 14G, i.e. the data stored earlier was not yet moved by the non-volatile memory module 20 to the non- volatile memory 26. In such a case the memory controller 22 would detect this read command and (instead of truly moving and storing the data into the non-volatile memory 26 before serving the read command) would copy (not move) the data from the memory area 14G to the location reserved for it in the file cache/file system cache 14C/transfer buffer 14D or application area 14B. The target address in the reserved location could be included in the access list 14F so that it is at least known by the host controller 13.
In the alternative embodiments related to modification of lists of pointers and headers correspondingly the above mentioned read case would be realized as copying of the data (related to the read request) to new target location and preparing the pointers/headers by the memory module/host controller so that the copied data will be immediately accessible and under control of the host system 10.
In all of these read-related embodiments it should be appreciated that the read data is copied and the data 14E' still exists and will be written to the non- volatile memory 26 of the memory module 20 as soon as the memory controller 22 has the resources to perform the write operation.
Figure 5C shows an embodiment of this invention, as discussed above, where the access list 14F references the data 14B', and the referenced data is then directly moved to the allocated portion (as data 14E') thereby bypassing the transfer buffer 14D (i.e., the data 14B' after being moved directly becomes the data 14E').
It is also within the scope of the exemplary embodiments for the data to originate from a source other than the host CPU 12 (e.g., other than from the application processor). For example, the data could originate from an initiator that is embodied as a peripheral device 60 that is connected to the host device 10 either by a wired connection or a wireless connection. In this case instead of moving the data directly from the peripheral device 60 to the mass memory module 20 the mass memory module 20 causes the data to be stored in the system DRAM 14, such as in the allocated portion 14G. The data that originates at the peripheral device 60 is thus temporarily (and transparently to the peripheral device 60) cached in the system DRAM 14.
Further in accordance with the exemplary embodiments of this invention the operation of the DRAM 14 is enhanced by providing additional functionality to locally perform operations in the DRAM 14.
By way of introduction, one of the processing capacity bottlenecks of a wireless terminal (e.g., a smartphone) is the execution memory, especially the memory bus. While the execution memory, also known as work memory, is a separate component (e.g., external DRAM), it is connected to a host ASIC by a bus that has a limited transfer capacity (bandwidth).
The means of improving the memory bandwidth are limited. In most cases the cost of several memory buses and memory devices respectively is too high. Also the bus itself takes a major portion of the pin/pad budget of the host ASIC, meaning that at a given pad pitch, the package containing the host ASIC silicon, would became unnecessarily large with multiple buses, creating problems for miniaturization efforts.
A common problem is that the memory bandwidth, or transaction capacity, is not sufficient for many desired use cases. The host ASIC can contain several memory masters (e.g., processors, accelerators, and DMA engines) and one DRAM controller 11 that provides the external memory bus. At the other end of this bus is the memory device (DRAM component). Memory masters issue read and write requests to the memory. The DRAM is built of several banks (4 to 8 typically) that could operate in parallel. Thus, while parallelism exists at both ends of the memory bus, the memory bus itself is a single- threaded arrangement.
The exemplary aspects of this invention include providing a means to fully exploit the memory device by enabling internal operations to be performed locally. This improves the overall memory subsystem performance, enhances CPU capacity by off-loading some operations from the CPU, and decreases power consumption. The exemplary aspects of this invention provide for some elementary operations to be carried out by the memory device through the use of an enhanced command set.
It should be noted that while these aspects of the exemplary embodiments of this invention are described in the context of enhancing the operation of the system DRAM 14 these aspects of the invention could be applied as well to enhancing the operation of the mass storage memory device 20. For example, the resident memory controller 22 of the memory module 20 could be modified so as to provide local autonomous operations within the mass memory 26.
Further in accordance with the exemplary embodiments of this invention some basic, elemental functions such as memory fill and memory move are handled internally to the system DRAM 14. These operations can be handled, for example, by system DRAM memory controller and/or by a control module or function 15 embedded in the system DRAM 14 (shown in Figure 5 A).
In this embodiment the system DRAM 14, with or without assistance ofthe system DRAM memory controller 11, can perform, for example, memory fill and move function(s) independently and autonomously without active intervention/control by the CPU 12. This reduces the CPU 12 and system DRAM bus 17 load due at least to the mass memory module/mass memory host controller 13 controlling the physical data move from the buffer 14B/14D to the allocated portion 14G.
It can be shown that many memory transactions are simple fills of memory address space with data (e.g., zeroes) or moving data chunks from one memory location into another memory location, where the locations can be inside the same physical memory device or inside two different memory devices. This conventionally requires activity at the CPU level, which means that system processing efficiency and power consumption are less than optimal.
In accordance with these further aspects of the invention at least some elementary in-memory operations are removed from the responsibility of the CPU 12 and transferred to the system DRAM 14, such as to the controller 15 that can be embedded with the system DRAM 14.
In this exemplary embodiment the controller 15 functionality includes "smart memory" features. Altematively these smart memory features could be included in the host controller 13 shown in Figure 5 A. Alternatively, and as was mentioned above, these smart memory features could also be included in the system DRAM memory controller 11 functionality for the system DRAM 14 of the host device 10
In these embodiments system DRAM controller 11 or the system DRAM module (control 15) may analyse commands issued for it and initiate a "smart memory" operation such as a memory fill or a memory move operation.
The additional functionality added to, for example, the controller 15 may include at least a data fill feature and a data move feature. The additional functionality optionally includes security functions for the system DRAM 14, pack/unpack functions between the system DRAM 14 and the mass memory 26, data transaction functions between the DRAM 14 and the mass memory 26 and, for example, mass memory related error detection and correction and wear levelling functions.
As an example of the use of the smart memory features, a memory block reset is typically performed by writing zeroes into the memory. In accordance with this invention a 'data fill' function supports at least a Fill operation using any specified bit pattern (e.g., Fill: Data), where Data could be any specified bit pattern such as 'ΟΟΟΟ', Ί 11 Γ, Ό10Γ, etc.
A Data Move operation can be a read/write (copy) sequence followed by a Fill operation to the region of system DRAM 14 from which the data was moved (read). The Fill operation could set the memory locations to some predetermined value (e.g., zero), or to a value specified by the Data Move operation command in a manner analogous to the Fill operation discussed above. The Fill operation can be optional, so that the Data Move operation functions as a Data Copy operation (i.e., the data is replicated to another location while the original data is unchanged).
A non- limiting example of the implementation of the smart memory functionality at the command level is as follows.
Low Power Double Data Rate (LPDDR1 (LP1)) as specified by JEDEC (e.g., see JEDEC Standard, Low Power Double Data Rate (LPDDR) SDRAM Standard, JESD209B, February 2010) does not provide a straightforward method of adding these types of smart features. An exemplary implementation may be to use a sequence of multiple conventional Mode Register Set (MRS) commands (MRS with bank address BAO = BA1 = Ί ' is available) using address pins AO - Ax to deliver the following information to the memory device:
1) Command type (move, fill);
2) Fill data (all 0, all 1, 01 sequence, ...), optional;
3) Target address (fill, move) and source address (move), address depends on implementation;
4) Operation size, granularity depends on implementation.
The number of needed MRS commands in the sequence is dependent on addressing, data granularity and operation size, which are implementation dependant factors. In LPDDR2 and LPDDR3 Mode Register Write commands could be used in a similar fashion. It should be understood that conventional LPDDRx solutions allow MRS and MRW operation only from DRAM idle state, but other solutions are technically possible. One such implementation may be to require that the data which is the source or the target of the move or fill operation is located in open DRAM pages.
It should also be understood that with future DRAM interfaces new dedicated commands are possible to be used for these operations - and these operations could be made much more efficient. Fundamentally from a system viewpoint some or all of the following operations may be delivered to the memory:
1) Deliver command (fillO, filll, ... , fill_pattern, move);
2) Deliver target address (bank, row, column, byte);
3) Deliver source address (bank, row, column, byte);
4) Deliver operation size.
Full command and address delivery may occur in a single or a multiple command sequence - a certain command code may, for example, indicate multicycle delivery via cmd/address/data bus as suits the implementation. The particular implementation dictates the requirements for the data and address granularity, requirements for the memory state prior to and after the smart memory feature operations, whether the memory internally uses some intermediate buffers to move or fill the data or whether open rows (DRAM sense amps) are reserved during the entire operation, any timing requirements, etc.
The command could be issued by the, for example, the CPU 12 (e.g., by an OS or file system utility) or by the mass memory host controller 13 and then autonomously executed by the controller 15 associated with the system DRAM 14 or by the DRAM memory controller 11.
There are a number of advantages and technical effects that can be realized by the use of the exemplary embodiments of this invention as described above. For example, a faster response to the initiator (Host CPU 12, a process, an initiator, an application) can be provided that an access has been served (actually taken into the ManagedNAND side for further processing). This enhances the user experience. Further, no changes need be made to the upper layer software (e.g., file system and/or applications) as moving data occurs at a low layer of hardware/software. Further, the allocated portion 14G of the system DRAM 14 for the ManagedNAND functionality need not be excessively large. For example, for many uses of interest some hundreds of kilobytes could be sufficient as in many cases it would be most advantageous to temporarily cache just small random accesses, and to store directly to the non-volatile mass memory 26 larger sequential accesses. In addition, the use of the further aspects of this invention enable certain elementary memory operations (e.g., fill, move) to be accomplished locally (e.g., within the system DRAM module 14) without active involvement of the CPU 12.
Figure 6 illustrates one non- limiting embodiment of the host device 10 used with the mass storage memory device 20, referred to in Figure 6 simply as a memory card 20. The mass storage memory device 20 can be removable or it can be embedded in the device 10. In this exemplary embodiment the host device 10 is embodied as a user equipment (UE), shown in both plan view (left) and sectional view (right). In Figure 6 the host device (UE) 10 has a graphical display interface 120 and a user interface 122 illustrated as a keypad but understood as also encompassing touch screen technology at the graphical display interface 120 and voice recognition technology received at a microphone 124. A power actuator 126 controls the device being turned on and off by the user. The exemplary UE 10 may have a camera 128 which is shown as being forward facing (e.g., for video calls) but may alternatively or additionally be rearward facing (e.g., for capturing images and video for local storage). The camera 128 is controlled by a shutter actuator 30 and optionally by a zoom actuator 32 which may alternatively function as a volume adjustment for the speaker(s) 34 when the camera 128 is not in an active mode.
As an example, image data captured by the camera 128 can be stored in the mass storage memory device 20 under control of a camera application and can thus benefit from the use of the embodiments of this invention. As another example, audio data captured by the microphone 124 can be stored in the mass storage memory device 20 under control of an audio application and can thus also benefit from the use of the embodiments of this invention.
Within the sectional view of Figure 6 are seen multiple transmit/receive antennas
36 that are typically used for cellular communication. The antennas 36 may be multi-band for use with other radios in the UE. The operable ground plane for the antennas 36 is shown by shading as spanning the entire space enclosed by the UE housing though in some embodiments the ground plane may be limited to a smaller area, such as disposed on a printed wiring board on which the power chip 38 is formed. The power chip 38 controls power amplification on the channels being transmitted and/or across the antennas that transmit simultaneously where spatial diversity is used, and amplifies the received signals. The power chip 38 outputs the amplified received signal to a radio frequency (RF) chip 40 which demodulates and downconverts the signal for baseband processing. A baseband (BB) chip 42 detects the signal which is then converted to a bit stream and finally decoded. Similar processing occurs in reverse for signals generated in the host device 10 and transmitted from it.
Signals going to and from the camera 128 may pass through an image/video processor 44 that encodes and decodes the various image frames. A separate audio processor 46 may also be present controlling signals to and from the speakers 34 and the microphone 124. The graphical display interface 120 is refreshed from a frame memory 48 as controlled by a user interface chip 50 which may process signals to and from the display interface 20 and/or additionally process user inputs from the keypad 22 and elsewhere.
Certain embodiments of the UE 10 may also include one or more secondary radios such as a wireless local area network radio WLAN 37 and a Bluetooth7 radio 39, which may incorporate an antenna on the chip or be coupled to an antenna off the chip. Throughout the apparatus are various memories such as random access memory RAM, which can include the system DRAM 14, read only memory ROM 45, and in some embodiments removable memory such as the illustrated memory card 20 on which various programs and data may be stored. All of these components within the UE 10 are normally powered by a portable power supply such as a battery 49.
The processors 38, 40, 42, 44, 46, 50, if embodied as separate entities in a UE 10, may operate in a slave relationship to the main processor (CPU) 12, which may then be in a master relationship to them. Certain embodiments may be disposed across various chips and memories as shown, or disposed within another processor that combines some of the functions described above for Figure 6. Any or all of these various processors of Figure 6 access one or more of the various memories, which may be on chip with the processor or separate from the chip with the processor. Note that the various integrated circuits (e.g., chips 38, 40, 42, etc.) that were described above may be combined into a fewer number than described and, in a most compact case, may all be embodied physically within a single chip.
In this exemplary embodiment the CPU 12 of the UE 10 (the host device) operates with the memory card 20 (the mass storage memory device) as described above with respect to Figures 5A, 5B and 5C so that the memory card 20 can be extended to use at least a portion of the system Dynamic RAM 14 of the UE 10 as described above.
An aspect of the exemplary embodiments of this invention is a method, shown in Figure 7, that includes (7 A) receiving a command (the command can arrive, for example, via a file system layer (SW) and a driver layer (SW) and a host controller (HW)) originating from an initiator (e.g., an application, a file system, a driver or an OS utility) at a controller (e.g., a memory controller) associated with a non-volatile mass memory coupled with a host device. The command is a command to write data that is currently resident in a memory of the host device to the non- volatile mass memory. The memory of the host device may comprise, as non-limiting examples, DRAM, MRAM, PCM (phase change memory), RRAM (resistive random access memory), magnetic random access memory, ferroelectric random access memory and the like. The method further includes (7B) moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non-volatile mass memory. The method further includes (7C) acknowledging to the initiator that the command to write the data to the non- volatile mass memory has been executed In the method described in Figure 7 and the preceding paragraph, further comprising, subsequent to acknowledging, moving the data from the memory of the host device to the non- volatile mass memory.
In the method described in Figure 7 and the preceding paragraphs, where the data is physically moved to the portion of the memory that is allocated for use at least by the non- volatile mass memory.
In the method described in Figure 7 and the preceding paragraphs, where the data is logically moved to the portion of the memory that is allocated for use at least by the non- volatile mass memory by changing a value of a memory address pointer to the data or a value of a header of the data.
In the method described in Figure 7 and the preceding paragraphs where the data originates with the initiator and where the initiator is resident in the host device.
In the method described in Figure 7 and the preceding paragraph, where the initiator comprises at least one of an application program, a file system, a driver, and an operating system utility.
In the method described in Figure 7 and the preceding paragraphs, where the data originates with the initiator and where the initiator is external to the host device.
In the method described in Figure 7 and the preceding paragraph, where the initiator is embodied as a peripheral device that is connected with the host device.
In the method described in Figure 7 and the preceding paragraphs, where the memory of the host device comprises a dynamic random access memory, and further comprising autonomously performing an elementary memory operation in the memory of the host device.
In the method described in Figure 7 and the preceding paragraph, where the elementary memory operation is a data fill operation to set a specified plurality of memory locations to a specified value.
In the method described in Figure 7 and the preceding paragraphs, where the elementary memory operation is a data move operation to move data from a first specified plurality of memory locations to a second specified plurality of memory locations.
In the method described in Figure 7 and the preceding paragraph, where the data move operation further comprises setting the first specified plurality of memory locations to a predetermined value. In the method described in Figure 7 and the preceding paragraphs, further comprising while the data is resident in the portion of the memory allocated for use at least by the non- volatile mass memory, responding to a read command for the data to read the data resident in the portion of the memory allocated for use by the non- volatile mass memory and copying the read data to an initiator of the read command.
In the method described in Figure 7 and the preceding paragraphs, where moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non-volatile mass memory is initiated by the controller associated with the non- volatile mass memory.
In the method described in Figure 7 and the preceding paragraphs, where the method is performed as a result of execution of computer program instructions by the controller.
Figure 8 is a logic flow diagram that illustrates the operation of a method, and a result of execution of computer program instructions embodied on a computer readable memory, further in accordance with the exemplary embodiments of this invention. In accordance with these exemplary embodiments a method performs, at Block 8A, providing a data processing system comprising at least one data processor and at least one memory comprised of dynamic random access memory. At Block 8B there is a step of autonomously performing an elementary memory operation in the memory.
In the method described in Figure 8 and the preceding paragraph, where the elementary memory operation is a data fill operation to set a specified plurality of memory locations to a specified value.
In the method described in Figure 8 and the preceding paragraphs, where the elementary memory operation is a data move operation to move data from a first specified plurality of memory locations to a second specified plurality of memory locations.
In the method described in Figure 8 and the preceding paragraph, where the data move operation further comprises setting the first specified plurality of memory locations to a predetermined value.
The various blocks shown in Figures 7 and 8 may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function(s). In general, the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the exemplary embodiments of this invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
It should thus be appreciated that at least some aspects of the exemplary embodiments of the inventions may be practiced in various components such as integrated circuit chips and modules, and that the exemplary embodiments of this invention may be realized in an apparatus that is embodied as an integrated circuit. The integrated circuit, or circuits, may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor or data processors, a digital signal processor or processors, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this invention.
An apparatus in accordance with the exemplary embodiments includes means for sending a command from a host device to a controller associated with a non- volatile mass memory coupled with the host device, the command being a command to write data that is currently resident in a memory of the host device to the non- volatile mass memory; means for moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use by the non-volatile mass memory; and means for acknowledging to the host device that the command to write the data to the non- volatile mass memory has been executed.
Various modifications and adaptations to the foregoing exemplary embodiments of this invention may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this invention. It should be noted that the terms "connected," "coupled," or any variant thereof, mean any connection or coupling, either direct or indirect, between two or more elements, and may encompass the presence of one or more intermediate elements between two elements that are "connected" or "coupled" together. The coupling or connection between the elements can be physical, logical, or a combination thereof. As employed herein two elements may be considered to be "connected" or "coupled" together by the use of one or more wires, cables and/or printed electrical connections, as well as by the use of electromagnetic energy, such as electromagnetic energy having wavelengths in the radio frequency region, the microwave region and the optical (both visible and invisible) region, as several non- limiting and non-exhaustive examples.
Furthermore, some of the features of the various non-limiting and exemplary embodiments of this invention may be used to advantage without the corresponding use of other features. As such, the foregoing description should be considered as merely illustrative of the principles, teachings and exemplary embodiments of this invention, and not in limitation thereof.

Claims

CLAIMS What is claimed is:
1. A method, comprising:
receiving a command originating from an initiator at a controller associated with a nonvolatile mass memory coupled with a host device, the command being a command to write data that is currently resident in a memory of the host device to the non-volatile mass memory;
moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non- volatile mass memory; and
acknowledging to the initiator that the command to write the data to the non- volatile mass memory has been executed.
2. The method as in claim 1, further comprising, subsequent to acknowledging, moving the data from the memory of the host device to the non- volatile mass memory.
3. The method of claim 1, where the data is physically moved to the portion of the memory that is allocated for use at least by the non- volatile mass memory.
4. The method of claim 1 , where the data is logically moved to the portion of the memory that is allocated for use at least by the non- volatile mass memory by changing a value of a memory address pointer to the data or a value of a header of the data.
5. The method as in any one of claims 1 -4, where the data originates with the initiator and where the initiator is resident in the host device.
6. The method of claim 5, where the initiator comprises at least one of an application program, a file system, a driver, and an operating system utility.
7. The method as in any one of claims 1 -4, where the data originates with the initiator and where the initiator is external to the host device.
8. The method of claim 7, where the initiator is embodied as a peripheral device that is connected with the host device.
9. The method of claim 1, where the memory of the host device is comprised of dynamic random access memory, and further comprising:
autonomously performing an elementary memory operation in the memory of the host device.
10. The method of claim 9, where the elementary memory operation is a data fill operation to set a specified plurality of memory locations to a specified value.
11. The method of claim 9, where the elementary memory operation is a data move operation to move data from a first specified plurality of memory locations to a second specified plurality of memory locations.
12. The method of claim 11, where the data move operation further comprises setting the first specified plurality of memory locations to a predetermined value.
13. The method of claim 1, further comprising while the data is resident in the portion of the memory allocated for use at least by the non- volatile mass memory, responding to a read command for the data to read the data resident in the portion of the memory allocated for use by the non-volatile mass memory and copying the read data to an initiator of the read command.
14. The method as in claim 1, where moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non- volatile mass memory is initiated .by the controller associated with the non- volatile mass memory.
15. The method as in any one of the preceding claims, performed at least partially as a result of execution of computer program instructions by the controller.
16. An apparatus, comprising:
a controller associated with a non- volatile memory module coupled with a host device; and
an interface to the non- volatile mass memory module;
said controller being configurable to process a command originating with an initiator, the command being a command to write data that is currently resident in a memory of the host device to the non- volatile mass memory module; said controller further configurable to move the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non-volatile mass memory module; and to acknowledge to the initiator that the command to write the data to the non- volatile mass memory has been executed.
17. The apparatus as in claim 16, where said controller is further configured, subsequent to acknowledging that the command to write the data to the non- volatile mass memory module has been executed, to move the data from the memory of the host device to the non- volatile mass memory module.
18. The apparatus as in claim 16, where the data is physically moved to the portion of the memory that is allocated for use at least by the non- volatile mass memory module.
19. The apparatus as in claim 16, where the data is logically moved to the portion of the memory that is allocated for use at least by the non-volatile mass memory module by changing a value of a memory address pointer to the data or a value of a header of the data.
20. The apparatus as in any one of claims 16-19, where the data originates with the initiator and where the initiator is resident in the host device.
21. The apparatus as in claim 20, where the initiator comprises at least one of an application program, a file system, a driver, and an operating system utility.
22. The apparatus as in any one of claims 16-19, where the data originates with the initiator and where the initiator is external to the host device.
23. The apparatus as in claim 22, where the initiator is embodied as a peripheral device that is connected with the host device.
24. The apparatus as in claim 16, where the memory of the host device is comprised of dynamic random access memory, and further comprising a function associated with said memory of said host device to autonomously perform an elementary memory operation in the memory of the host device.
25. The apparatus as in claim 24, where the elementary memory operation is a data fill operation to set a specified plurality of memory locations to a specified value.
26. The apparatus as in claim 24, where the elementary memory operation is a data move operation to move data from a specified first plurality of memory locations to a specified second plurality of memory locations.
27. The apparatus as in claim 26, where the data move operation further comprises setting the first specified plurality of memory locations to a predetermined value.
28. The apparatus of claim 16, further comprising while the data is resident in the portion of the memory allocated for use at least by the non-volatile mass memory module, responding to a read command for the data to read the data resident in the portion of the memory allocated for use by the non- volatile mass memory module, to copy the read data to an initiator of the read command.
29. The apparatus as in claim 16, where moving the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non-volatile mass memory is initiated by the non-volatile mass memory module.
30. The apparatus as in any one of claims 16-29, where the host device is comprised of a mobile device configured to perform bidirectional wireless communications.
31. A method, comprising:
providing a data processing system comprising at least one data processor and at least one memory comprised of dynamic random access memory, and
autonomously performing an elementary memory operation in the memory.
32. The method of claim 31, where the elementary memory operation is a data fill operation to set a specified plurality of memory locations to a specified value.
33. The method of claim 31, where the elementary memory operation is a data move operation to move data from a first specified plurality of memory locations to a second specified plurality of memory locations.
34. The method of claim 33, where the data move operation further comprises setting the first specified plurality of memory locations to a predetermined value.
35. A memory module comprising:
a controller;
a non- volatile mass memory that is readable and writable by the controller; and an interface for connecting the memory module to a host device;
said controller being configurable to receive a command originating from an initiator, the command being a command to write data that is currently resident in a memory of the host device to the non- volatile mass memory module; to initiate the move of the data that is currently resident in the memory of the host device from an original location to a portion of the memory allocated for use at least by the non- volatile mass memory module; and to acknowledge to the initiator that the command to write the data to the non- volatile mass memory has been executed.
36. The memory module as in claim 35, where said controller is further configured, subsequent to acknowledging that the command to write the data to the non- volatile mass memory module has been executed, to move the data from the memory of the host device to the non- volatile mass memory module.
PCT/FI2013/050001 2012-01-26 2013-01-02 Apparatus and method to provide cache move with non-volatile mass memory system WO2013110847A1 (en)

Priority Applications (9)

Application Number Priority Date Filing Date Title
KR1020147019265A KR102127327B1 (en) 2012-01-26 2013-01-02 Apparatus and method to provide cache move with nonvolatile mass memory system
CN201380006769.8A CN104081366B (en) 2012-01-26 2013-01-02 The apparatus and method of cache memory movement are provided by nonvolatile mass storage system
KR1020217033814A KR102458334B1 (en) 2012-01-26 2013-01-02 Apparatus and method to provide cache move with nonvolatile mass memory system
EP18213772.9A EP3493066B1 (en) 2012-01-26 2013-01-02 Apparatus and method to provide cache move with non-volatile mass memory system
CN201810154153.XA CN108470007B (en) 2012-01-26 2013-01-02 Apparatus and method for providing cache move with non-volatile mass storage system
KR1020207018006A KR102317152B1 (en) 2012-01-26 2013-01-02 Apparatus and method to provide cache move with nonvolatile mass memory system
JP2014553773A JP6193886B2 (en) 2012-01-26 2013-01-02 Apparatus and method for providing cache migration with a non-volatile mass memory system
KR1020227036487A KR20220143972A (en) 2012-01-26 2013-01-02 Apparatus and method to provide cache move with nonvolatile mass memory system
EP13741595.6A EP2795470B1 (en) 2012-01-26 2013-01-02 Apparatus and method to provide cache move with non-volatile mass memory system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/358,806 US9417998B2 (en) 2012-01-26 2012-01-26 Apparatus and method to provide cache move with non-volatile mass memory system
US13/358,806 2012-01-26

Publications (1)

Publication Number Publication Date
WO2013110847A1 true WO2013110847A1 (en) 2013-08-01

Family

ID=48871320

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2013/050001 WO2013110847A1 (en) 2012-01-26 2013-01-02 Apparatus and method to provide cache move with non-volatile mass memory system

Country Status (6)

Country Link
US (3) US9417998B2 (en)
EP (2) EP2795470B1 (en)
JP (3) JP6193886B2 (en)
KR (4) KR102458334B1 (en)
CN (2) CN104081366B (en)
WO (1) WO2013110847A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016514320A (en) * 2013-03-15 2016-05-19 インテル・コーポレーション Memory system
JP2016118945A (en) * 2014-12-22 2016-06-30 ソニー株式会社 Memory controller, storage device, and information processing system
US11262936B2 (en) 2015-10-30 2022-03-01 Sony Corporation Memory controller, storage device, information processing system, and memory control method

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8156415B1 (en) * 2007-12-26 2012-04-10 Marvell International Ltd. Method and system for command queuing in disk drives
US8307180B2 (en) 2008-02-28 2012-11-06 Nokia Corporation Extended utilization area for a memory device
US8370717B1 (en) 2008-04-08 2013-02-05 Marvell International Ltd. Method and apparatus for flexible buffers in an XOR engine
US8874824B2 (en) 2009-06-04 2014-10-28 Memory Technologies, LLC Apparatus and method to share host system RAM with mass storage memory RAM
US9081665B2 (en) * 2012-02-02 2015-07-14 OCZ Storage Solutions Inc. Apparatus, methods and architecture to increase write performance and endurance of non-volatile solid state memory components
US9311226B2 (en) 2012-04-20 2016-04-12 Memory Technologies Llc Managing operational state data of a memory module using host memory in association with state change
TWI459201B (en) * 2012-04-27 2014-11-01 Toshiba Kk Information processing device
JP2013242694A (en) * 2012-05-21 2013-12-05 Renesas Mobile Corp Semiconductor device, electronic device, electronic system, and method of controlling electronic device
JP6191021B2 (en) * 2013-02-20 2017-09-06 パナソニックＩｐマネジメント株式会社 Access device, information recording device, and access system
KR20150041873A (en) * 2013-10-10 2015-04-20 에스케이하이닉스 주식회사 Data processing system
US9880971B2 (en) * 2013-12-20 2018-01-30 Rambus Inc. Memory appliance for accessing memory
US9092362B1 (en) * 2014-03-13 2015-07-28 NXGN Data, Inc. Programmable data write management system and method for operating the same in a solid state drive
US10824335B2 (en) 2014-07-14 2020-11-03 Western Digital Technologies, Inc. Device and method to store predicted data at a host memory
US9767045B2 (en) 2014-08-29 2017-09-19 Memory Technologies Llc Control for authenticated accesses to a memory device
US10101918B2 (en) * 2015-01-21 2018-10-16 Sandisk Technologies Llc Systems and methods for generating hint information associated with a host command
CN107430879B (en) * 2015-05-08 2020-07-21 桑迪士克科技有限责任公司 Data mapping for non-volatile storage
KR102337044B1 (en) * 2015-07-27 2021-12-09 에스케이하이닉스 주식회사 Semiconductor device and semiconductor system
US10203888B2 (en) * 2015-12-18 2019-02-12 Intel Corporation Technologies for performing a data copy operation on a data storage device with a power-fail-safe data structure
CN107515723B (en) * 2016-06-16 2020-04-24 伊姆西Ip控股有限责任公司 Method and system for managing memory in a storage system
US10354716B2 (en) * 2016-09-16 2019-07-16 Aspiring Sky Co. Limited SRAM based memory structures and methods thereof
US10304418B2 (en) * 2016-09-27 2019-05-28 Intel Corporation Operating system transparent system memory abandonment
US10785301B2 (en) * 2017-08-03 2020-09-22 Toshiba Memory Corporation NVM express over fabrics
US10620870B2 (en) 2017-12-08 2020-04-14 Intel Corporation Data storage device with bytewise copy
BR112020014967A2 (en) 2018-01-24 2020-12-22 Ntt Docomo, Inc. TERMINAL AND RADIOCOMMUNICATION METHOD FOR A TERMINAL
US10782916B2 (en) * 2018-08-08 2020-09-22 Micron Technology, Inc. Proactive return of write credits in a memory system
US10910048B1 (en) * 2020-01-16 2021-02-02 Micron Technology, Inc. Extended memory communication
US11287987B2 (en) 2020-03-04 2022-03-29 Micron Technology, Inc. Coherency locking schemes
CN114303137A (en) * 2020-08-07 2022-04-08 美光科技公司 Memory overlay using host memory buffers
US11449419B2 (en) * 2020-08-17 2022-09-20 Micron Technology, Inc. Disassociating memory units with a host system
CN113760189B (en) * 2021-08-19 2024-04-09 上海卫星工程研究所 Load data filling and storing method and system

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1094392A1 (en) * 1999-10-22 2001-04-25 Sun Microsystems, Inc. Method and apparatus for interfacing with a secondary storage system
US7480749B1 (en) * 2004-05-27 2009-01-20 Nvidia Corporation Main memory as extended disk buffer memory
US20090157950A1 (en) * 2007-12-14 2009-06-18 Robert David Selinger NAND flash module replacement for DRAM module
US20090198872A1 (en) 2008-02-05 2009-08-06 Spansion Llc Hardware based wear leveling mechanism
US20100037012A1 (en) * 2007-12-28 2010-02-11 Hirokuni Yano Semiconductor Storage Device, Method of Controlling the Same, Controller and Information Processing Apparatus
US20100115193A1 (en) * 2005-07-18 2010-05-06 Palm, Inc. System and method for improving data integrity and memory performance using non-volatile media
US20110208914A1 (en) 2008-08-21 2011-08-25 Infinidat Ltd. Storage system and method of operating thereof

Family Cites Families (216)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA1293819C (en) 1986-08-29 1991-12-31 Thinking Machines Corporation Very large scale computer
JPS6464073A (en) 1987-09-03 1989-03-09 Minolta Camera Kk Image memory
JP2661224B2 (en) 1988-12-23 1997-10-08 株式会社リコー Memory expansion method
US5781753A (en) 1989-02-24 1998-07-14 Advanced Micro Devices, Inc. Semi-autonomous RISC pipelines for overlapped execution of RISC-like instructions within the multiple superscalar execution units of a processor having distributed pipeline control for speculative and out-of-order execution of complex instructions
JP3038781B2 (en) 1989-04-21 2000-05-08 日本電気株式会社 Memory access control circuit
US5680570A (en) 1991-06-12 1997-10-21 Quantum Corporation Memory system with dynamically allocatable non-volatile storage capability
JP3407317B2 (en) * 1991-11-28 2003-05-19 株式会社日立製作所 Storage device using flash memory
WO1993018461A1 (en) * 1992-03-09 1993-09-16 Auspex Systems, Inc. High-performance non-volatile ram protected write cache accelerator system
EP1152409B1 (en) 1994-06-07 2006-08-09 Hitachi Global Storage Technologies Japan, Ltd. Information storing device
US5710931A (en) 1994-09-07 1998-01-20 Canon Kabushiki Kaisha Suspension state control for information processing devices such as battery powered computers
JP3687115B2 (en) 1994-10-27 2005-08-24 ソニー株式会社 Playback device
JPH08161216A (en) * 1994-12-09 1996-06-21 Toshiba Corp Information processor provided with high-speed memory clear function
US5586291A (en) * 1994-12-23 1996-12-17 Emc Corporation Disk controller with volatile and non-volatile cache memories
EP0749063A3 (en) 1995-06-07 1999-01-13 International Business Machines Corporation Method and apparatus for suspend/resume operation in a computer
IT235879Y1 (en) 1995-06-14 2000-07-18 Olivetti & Co Spa KEYBOARD FOR DATA INTRODUCTION WITH TRACK POSITIONER
US6393492B1 (en) 1995-11-03 2002-05-21 Texas Instruments Incorporated Method and arrangement for operating a mass memory storage peripheral computer device connected to a host computer
US5802069A (en) * 1995-11-13 1998-09-01 Intel Corporation Implementing mass storage device functions using host processor memory
US5822553A (en) 1996-03-13 1998-10-13 Diamond Multimedia Systems, Inc. Multiple parallel digital data stream channel controller architecture
US5838873A (en) 1996-05-31 1998-11-17 Thomson Consumer Electronics, Inc. Packetized data formats for digital data storage media
US5805882A (en) 1996-07-19 1998-09-08 Compaq Computer Corporation Computer system and method for replacing obsolete or corrupt boot code contained within reprogrammable memory with new boot code supplied from an external source through a data port
US5933626A (en) 1997-06-12 1999-08-03 Advanced Micro Devices, Inc. Apparatus and method for tracing microprocessor instructions
US6226710B1 (en) 1997-11-14 2001-05-01 Utmc Microelectronic Systems Inc. Content addressable memory (CAM) engine
JP4310821B2 (en) 1997-12-24 2009-08-12 ソニー株式会社 Information recording apparatus and method
JP3990485B2 (en) 1997-12-26 2007-10-10 株式会社ルネサステクノロジ Semiconductor nonvolatile memory device
JPH11259357A (en) * 1998-03-09 1999-09-24 Seiko Epson Corp Semiconductor integrated device and nonvolatile memory writing system
US6173425B1 (en) 1998-04-15 2001-01-09 Integrated Device Technology, Inc. Methods of testing integrated circuits to include data traversal path identification information and related status information in test data streams
US6067300A (en) 1998-06-11 2000-05-23 Cabletron Systems, Inc. Method and apparatus for optimizing the transfer of data packets between local area networks
JP2000057039A (en) 1998-08-03 2000-02-25 Canon Inc Method and device for controlling access, file system and information processor
US6721288B1 (en) 1998-09-16 2004-04-13 Openwave Systems Inc. Wireless mobile devices having improved operation during network unavailability
CA2345123A1 (en) 1998-09-28 2000-04-06 T Squared G Incorporated Multibyte random access mass storage/memory system
US6279114B1 (en) 1998-11-04 2001-08-21 Sandisk Corporation Voltage negotiation in a single host multiple cards system
JP2001006379A (en) 1999-06-16 2001-01-12 Fujitsu Ltd Flash memory having copying and transfer functions
US7889544B2 (en) 2004-04-05 2011-02-15 Super Talent Electronics, Inc. High-speed controller for phase-change memory peripheral device
US6513094B1 (en) * 1999-08-23 2003-01-28 Advanced Micro Devices, Inc. ROM/DRAM data bus sharing with write buffer and read prefetch activity
JP2001067786A (en) 1999-08-30 2001-03-16 Matsushita Electric Ind Co Ltd Recording and reproducing device
US6757797B1 (en) * 1999-09-30 2004-06-29 Fujitsu Limited Copying method between logical disks, disk-storage system and its storage medium
KR20020050270A (en) 1999-11-09 2002-06-26 토토라노 제이. 빈센트 Dynamically adjusting a processor's operational parameters according to its environment
US20060075395A1 (en) 2004-10-01 2006-04-06 Lee Charles C Flash card system
US7552251B2 (en) * 2003-12-02 2009-06-23 Super Talent Electronics, Inc. Single-chip multi-media card/secure digital (MMC/SD) controller reading power-on boot code from integrated flash memory for user storage
US6609182B1 (en) 2000-01-20 2003-08-19 Microsoft Corporation Smart hibernation on an operating system with page translation
JP3955712B2 (en) 2000-03-03 2007-08-08 株式会社ルネサステクノロジ Semiconductor device
US6785764B1 (en) 2000-05-11 2004-08-31 Micron Technology, Inc. Synchronous flash memory with non-volatile mode register
US20020000931A1 (en) 2000-04-14 2002-01-03 Mark Petronic User interface for a two-way satellite communication system
US6721843B1 (en) 2000-07-07 2004-04-13 Lexar Media, Inc. Flash memory architecture implementing simultaneously programmable multiple flash memory banks that are host compatible
JP2002023962A (en) 2000-07-07 2002-01-25 Fujitsu Ltd Disk device and its controlling method
JP3965874B2 (en) 2000-07-17 2007-08-29 セイコーエプソン株式会社 Recording method for printing on recording medium using two liquids, recorded matter printed by this recording method, and recording apparatus comprising means for executing this recording method
US6804763B1 (en) 2000-10-17 2004-10-12 Igt High performance battery backed ram interface
US6801994B2 (en) * 2000-12-20 2004-10-05 Microsoft Corporation Software management systems and methods for automotive computing devices
US6510488B2 (en) 2001-02-05 2003-01-21 M-Systems Flash Disk Pioneers Ltd. Method for fast wake-up of a flash memory system
US6779045B2 (en) * 2001-03-21 2004-08-17 Intel Corporation System and apparatus for increasing the number of operations per transmission for a media management system
US6990571B2 (en) 2001-04-25 2006-01-24 Intel Corporation Method for memory optimization in a digital signal processor
US6732221B2 (en) * 2001-06-01 2004-05-04 M-Systems Flash Disk Pioneers Ltd Wear leveling of static areas in flash memory
US6920540B2 (en) * 2001-10-22 2005-07-19 Rambus Inc. Timing calibration apparatus and method for a memory device signaling system
JP2003150445A (en) * 2001-11-13 2003-05-23 Fujitsu Ltd Computer system having external storage device
US6842829B1 (en) * 2001-12-06 2005-01-11 Lsi Logic Corporation Method and apparatus to manage independent memory systems as a shared volume
US6754129B2 (en) 2002-01-24 2004-06-22 Micron Technology, Inc. Memory module with integrated bus termination
US7085866B1 (en) 2002-02-19 2006-08-01 Hobson Richard F Hierarchical bus structure and memory access protocol for multiprocessor systems
FI115562B (en) 2002-03-27 2005-05-31 Nokia Corp Method and system for determining power consumption in connection with electronic device and electronic device
US6892311B2 (en) 2002-05-08 2005-05-10 Dell Usa, L.P. System and method for shutting down a host and storage enclosure if the status of the storage enclosure is in a first condition and is determined that the storage enclosure includes a critical storage volume
WO2003102783A1 (en) 2002-05-31 2003-12-11 Nokia Corporation Method and memory adapter for handling data of a mobile device using non-volatile memory
JP2004062928A (en) 2002-07-25 2004-02-26 Hitachi Ltd Magnetic disk drive and storage system
JP4111789B2 (en) 2002-09-13 2008-07-02 富士通株式会社 Semiconductor memory device control method and semiconductor memory device
US6901298B1 (en) 2002-09-30 2005-05-31 Rockwell Automation Technologies, Inc. Saving and restoring controller state and context in an open operating system
WO2004034676A1 (en) * 2002-10-08 2004-04-22 Koninklijke Philips Electronics N.V. Integrated circuit and method for establishing transactions
US20040088474A1 (en) 2002-10-30 2004-05-06 Lin Jin Shin NAND type flash memory disk device and method for detecting the logical address
WO2004042505A2 (en) 2002-10-31 2004-05-21 Ring Technology Enterprises, Llc Methods and systems for a storage system
US7949777B2 (en) 2002-11-01 2011-05-24 Avid Technology, Inc. Communication protocol for controlling transfer of temporal data over a bus between devices in synchronization with a periodic reference signal
US7290093B2 (en) 2003-01-07 2007-10-30 Intel Corporation Cache memory to support a processor's power mode of operation
US7181574B1 (en) 2003-01-30 2007-02-20 Veritas Operating Corporation Server cluster using informed prefetching
FI117489B (en) 2003-02-07 2006-10-31 Nokia Corp A method for indicating a memory card, a system using a memory card, and a memory card
TWI220733B (en) * 2003-02-07 2004-09-01 Ind Tech Res Inst System and a method for stack-caching method frames
ATE531047T1 (en) 2003-03-19 2011-11-15 Nxp Bv UNIVERSAL STORAGE WITH UNIT FOR STORING A USER/APPLICATION PROFILE
US7233335B2 (en) 2003-04-21 2007-06-19 Nividia Corporation System and method for reserving and managing memory spaces in a memory resource
US6981123B2 (en) 2003-05-22 2005-12-27 Seagate Technology Llc Device-managed host buffer
US7822105B2 (en) 2003-09-02 2010-10-26 Sirf Technology, Inc. Cross-correlation removal of carrier wave jamming signals
US20050071570A1 (en) * 2003-09-26 2005-03-31 Takasugl Robin Alexis Prefetch controller for controlling retrieval of data from a data storage device
US7321958B2 (en) * 2003-10-30 2008-01-22 International Business Machines Corporation System and method for sharing memory by heterogeneous processors
US7120766B2 (en) * 2003-12-22 2006-10-10 Inernational Business Machines Corporation Apparatus and method to initialize information disposed in an information storage and retrieval system
US20050204113A1 (en) 2004-03-09 2005-09-15 International Business Machines Corp. Method, system and storage medium for dynamically selecting a page management policy for a memory controller
JP4402997B2 (en) 2004-03-26 2010-01-20 株式会社日立製作所 Storage device
EP1870814B1 (en) 2006-06-19 2014-08-13 Texas Instruments France Method and apparatus for secure demand paging for processor devices
JP2005309653A (en) 2004-04-20 2005-11-04 Hitachi Global Storage Technologies Netherlands Bv Disk device and cache control method
EP1743251A1 (en) * 2004-04-26 2007-01-17 Koninklijke Philips Electronics N.V. Integrated circuit and method for issuing transactions
EP1746510A4 (en) 2004-04-28 2008-08-27 Matsushita Electric Ind Co Ltd Nonvolatile storage device and data write method
US7958292B2 (en) 2004-06-23 2011-06-07 Marvell World Trade Ltd. Disk drive system on chip with integrated buffer memory and support for host memory access
JP4768237B2 (en) * 2004-06-25 2011-09-07 株式会社東芝 Portable electronic device and method for controlling portable electronic device
US7380095B2 (en) 2004-06-30 2008-05-27 Intel Corporation System and method for simulating real-mode memory access with access to extended memory
US8490102B2 (en) 2004-07-29 2013-07-16 International Business Machines Corporation Resource allocation management using IOC token requestor logic
US7334107B2 (en) * 2004-09-30 2008-02-19 Intel Corporation Caching support for direct memory access address translation
US8843727B2 (en) * 2004-09-30 2014-09-23 Intel Corporation Performance enhancement of address translation using translation tables covering large address spaces
CN101111825A (en) * 2004-12-06 2008-01-23 Teac宇航技术公司 System and method for erasing nonvolatile recording medium
US20060120235A1 (en) * 2004-12-06 2006-06-08 Teac Aerospace Technologies System and method of erasing non-volatile recording media
US20060119602A1 (en) * 2004-12-07 2006-06-08 Fisher Andrew J Address based graphics protocol
US7243173B2 (en) 2004-12-14 2007-07-10 Rockwell Automation Technologies, Inc. Low protocol, high speed serial transfer for intra-board or inter-board data communication
US7275140B2 (en) 2005-05-12 2007-09-25 Sandisk Il Ltd. Flash memory management method that is resistant to data corruption by power loss
KR100706246B1 (en) 2005-05-24 2007-04-11 삼성전자주식회사 Memory card capable of improving read performance
JP2006343923A (en) 2005-06-08 2006-12-21 Fujitsu Ltd Disk recording device
US20060288130A1 (en) * 2005-06-21 2006-12-21 Rajesh Madukkarumukumana Address window support for direct memory access translation
US7571295B2 (en) 2005-08-04 2009-08-04 Intel Corporation Memory manager for heterogeneous memory control
JP4305429B2 (en) 2005-08-18 2009-07-29 トヨタ自動車株式会社 In-wheel suspension
JP2007052717A (en) 2005-08-19 2007-03-01 Fujitsu Ltd Data transfer device and method
JP4685567B2 (en) 2005-09-15 2011-05-18 株式会社日立製作所 Service providing system by information processing device
KR100673013B1 (en) * 2005-09-21 2007-01-24 삼성전자주식회사 Memory controller and data processing system with the same
CN110047528A (en) 2005-09-30 2019-07-23 考文森智财管理公司 Multiple independent serial link memories
JP4903415B2 (en) * 2005-10-18 2012-03-28 株式会社日立製作所 Storage control system and storage control method
US7783845B2 (en) 2005-11-14 2010-08-24 Sandisk Corporation Structures for the management of erase operations in non-volatile memories
JP2007156597A (en) 2005-12-01 2007-06-21 Hitachi Ltd Storage device
US20070136523A1 (en) 2005-12-08 2007-06-14 Bonella Randy M Advanced dynamic disk memory module special operations
US20070147115A1 (en) 2005-12-28 2007-06-28 Fong-Long Lin Unified memory and controller
US7492368B1 (en) 2006-01-24 2009-02-17 Nvidia Corporation Apparatus, system, and method for coalescing parallel memory requests
US20070226795A1 (en) 2006-02-09 2007-09-27 Texas Instruments Incorporated Virtual cores and hardware-supported hypervisor integrated circuits, systems, methods and processes of manufacture
JP4167695B2 (en) 2006-03-28 2008-10-15 株式会社Ｓｎｋプレイモア Game machine
US7925860B1 (en) 2006-05-11 2011-04-12 Nvidia Corporation Maximized memory throughput using cooperative thread arrays
KR101443002B1 (en) 2006-05-23 2014-09-23 컨버전트 인텔렉츄얼 프로퍼티 매니지먼트 인코포레이티드 Apparatus and method for establishing device identifiers for serially interconnected devices
US7753281B2 (en) * 2006-06-01 2010-07-13 Hewlett-Packard Development Company, L.P. System and method of updating a first version of a data file in a contactless flash memory device
JP4182993B2 (en) 2006-06-30 2008-11-19 Ｔｄｋ株式会社 MEMORY CONTROLLER, FLASH MEMORY SYSTEM HAVING MEMORY CONTROLLER, AND FLASH MEMORY CONTROL METHOD
JP2009545783A (en) 2006-07-31 2009-12-24 株式会社東芝 Nonvolatile memory system and data read / write control method thereof
US9798528B2 (en) 2006-09-13 2017-10-24 International Business Machines Corporation Software solution for cooperative memory-side and processor-side data prefetching
US20080081609A1 (en) 2006-09-29 2008-04-03 Motorola, Inc. Method and system for associating a user profile to a sim card
US8935302B2 (en) 2006-12-06 2015-01-13 Intelligent Intellectual Property Holdings 2 Llc Apparatus, system, and method for data block usage information synchronization for a non-volatile storage volume
TWM317043U (en) 2006-12-27 2007-08-11 Genesys Logic Inc Cache device of the flash memory address transformation layer
EP2122473B1 (en) 2007-01-10 2012-12-05 Mobile Semiconductor Corporation Adaptive memory system for enhancing the performance of an external computing device
KR100849182B1 (en) 2007-01-22 2008-07-30 삼성전자주식회사 Semiconductor card package and method of forming the same
US8312559B2 (en) 2007-01-26 2012-11-13 Hewlett-Packard Development Company, L.P. System and method of wireless security authentication
KR100881052B1 (en) 2007-02-13 2009-01-30 삼성전자주식회사 System for searching mapping table of flash memory and method for searching therefore
US20080235477A1 (en) * 2007-03-19 2008-09-25 Rawson Andrew R Coherent data mover
JP2008250961A (en) 2007-03-30 2008-10-16 Nec Corp Storage medium control device, data storage device, data storage system, method and control program
ATE519320T1 (en) * 2007-05-07 2011-08-15 Vorne Ind Inc METHOD AND SYSTEM FOR EXPANDING THE CAPACITIES OF IMPLEMENTED DEVICES VIA NETWORK CLIENTS
US9396103B2 (en) * 2007-06-08 2016-07-19 Sandisk Technologies Llc Method and system for storage address re-mapping for a memory device
JP5220747B2 (en) * 2007-07-31 2013-06-26 パナソニック株式会社 Nonvolatile storage device and nonvolatile storage system
US8166238B2 (en) 2007-10-23 2012-04-24 Samsung Electronics Co., Ltd. Method, device, and system for preventing refresh starvation in shared memory bank
US7730248B2 (en) 2007-12-13 2010-06-01 Texas Instruments Incorporated Interrupt morphing and configuration, circuits, systems and processes
US8892831B2 (en) * 2008-01-16 2014-11-18 Apple Inc. Memory subsystem hibernation
CN101981545B (en) * 2008-01-31 2014-08-20 甲骨文国际公司 System and method for transactional cache
US8209463B2 (en) 2008-02-05 2012-06-26 Spansion Llc Expansion slots for flash memory based random access memory subsystem
US8180975B2 (en) 2008-02-26 2012-05-15 Microsoft Corporation Controlling interference in shared memory systems using parallelism-aware batch scheduling
JP4672742B2 (en) 2008-02-27 2011-04-20 株式会社東芝 Memory controller and memory system
US8307180B2 (en) 2008-02-28 2012-11-06 Nokia Corporation Extended utilization area for a memory device
JP4643667B2 (en) 2008-03-01 2011-03-02 株式会社東芝 Memory system
US8775718B2 (en) 2008-05-23 2014-07-08 Netapp, Inc. Use of RDMA to access non-volatile solid-state memory in a network storage system
KR101456976B1 (en) * 2008-06-09 2014-11-03 삼성전자 주식회사 Memory test device and testing method for memory
US8099522B2 (en) 2008-06-09 2012-01-17 International Business Machines Corporation Arrangements for I/O control in a virtualized system
CN102067091A (en) * 2008-06-17 2011-05-18 Nxp股份有限公司 Multiprocessor system with mixed software hardware controlled cache management
US9223642B2 (en) * 2013-03-15 2015-12-29 Super Talent Technology, Corp. Green NAND device (GND) driver with DRAM data persistence for enhanced flash endurance and performance
US8166229B2 (en) 2008-06-30 2012-04-24 Intel Corporation Apparatus and method for multi-level cache utilization
US8139430B2 (en) * 2008-07-01 2012-03-20 International Business Machines Corporation Power-on initialization and test for a cascade interconnect memory system
CN101667103B (en) 2008-09-01 2011-05-04 智微科技股份有限公司 Disk array 5 controller and access method
US8103830B2 (en) 2008-09-30 2012-01-24 Intel Corporation Disabling cache portions during low voltage operations
US8181046B2 (en) * 2008-10-29 2012-05-15 Sandisk Il Ltd. Transparent self-hibernation of non-volatile memory system
US8316201B2 (en) * 2008-12-18 2012-11-20 Sandisk Il Ltd. Methods for executing a command to write data from a source location to a destination location in a memory device
US8639874B2 (en) 2008-12-22 2014-01-28 International Business Machines Corporation Power management of a spare DRAM on a buffered DIMM by issuing a power on/off command to the DRAM device
US8094500B2 (en) * 2009-01-05 2012-01-10 Sandisk Technologies Inc. Non-volatile memory and method with write cache partitioning
US8832354B2 (en) * 2009-03-25 2014-09-09 Apple Inc. Use of host system resources by memory controller
CN101571835B (en) * 2009-03-26 2011-01-26 浙江大学 Realization method for changing Cache group associativity based on requirement of program
US8572344B2 (en) * 2009-05-04 2013-10-29 Hewlett-Packard Development Company, L.P. Storage device erase command having a control field controllable by a requestor device
US8719652B2 (en) * 2009-05-12 2014-05-06 Stec, Inc. Flash storage device with read disturb mitigation
US8250282B2 (en) 2009-05-14 2012-08-21 Micron Technology, Inc. PCM memories for storage bus interfaces
US8180981B2 (en) * 2009-05-15 2012-05-15 Oracle America, Inc. Cache coherent support for flash in a memory hierarchy
US8533437B2 (en) * 2009-06-01 2013-09-10 Via Technologies, Inc. Guaranteed prefetch instruction
US8874824B2 (en) 2009-06-04 2014-10-28 Memory Technologies, LLC Apparatus and method to share host system RAM with mass storage memory RAM
US8244981B2 (en) * 2009-07-10 2012-08-14 Apple Inc. Combined transparent/non-transparent cache
JP2011022657A (en) * 2009-07-13 2011-02-03 Fujitsu Ltd Memory system and information processor
JP2011028537A (en) * 2009-07-27 2011-02-10 Buffalo Inc Method to speed up access to external storage device and external storage system
US8266481B2 (en) * 2009-07-29 2012-09-11 Stec, Inc. System and method of wear-leveling in flash storage
US8453021B2 (en) * 2009-07-29 2013-05-28 Stec, Inc. Wear leveling in solid-state device
US20110258372A1 (en) * 2009-07-29 2011-10-20 Panasonic Corporation Memory device, host device, and memory system
JP2011039849A (en) * 2009-08-12 2011-02-24 Canon Inc Information processing device, control method therefor, and program
US8667225B2 (en) 2009-09-11 2014-03-04 Advanced Micro Devices, Inc. Store aware prefetching for a datastream
US9952977B2 (en) 2009-09-25 2018-04-24 Nvidia Corporation Cache operations and policies for a multi-threaded client
CN102576333B (en) 2009-10-05 2016-01-13 马维尔国际贸易有限公司 Data cache in nonvolatile memory
JP2011082911A (en) * 2009-10-09 2011-04-21 Sony Corp Peripheral device, and device connection system
JP5526697B2 (en) * 2009-10-14 2014-06-18 ソニー株式会社 Storage device and memory system
KR101602939B1 (en) 2009-10-16 2016-03-15 삼성전자주식회사 Nonvolatile memory system and method for managing data thereof
US8452946B2 (en) * 2009-12-17 2013-05-28 Intel Corporation Methods and apparatuses for efficient load processing using buffers
US8255617B2 (en) 2010-01-26 2012-08-28 Seagate Technology Llc Maintaining data integrity in a data storage device
US8364886B2 (en) 2010-01-26 2013-01-29 Seagate Technology Llc Verifying whether metadata identifies a most current version of stored data in a memory space
US9128718B1 (en) 2010-03-29 2015-09-08 Amazon Technologies, Inc. Suspend using internal rewriteable memory
US8291172B2 (en) 2010-04-27 2012-10-16 Via Technologies, Inc. Multi-modal data prefetcher
JP4988007B2 (en) * 2010-05-13 2012-08-01 株式会社東芝 Information processing apparatus and driver
WO2011148223A1 (en) * 2010-05-27 2011-12-01 Sandisk Il Ltd Memory management storage to a host device
KR101734204B1 (en) 2010-06-01 2017-05-12 삼성전자주식회사 Flash memory device and system including program sequencer and program method thereof
US8397101B2 (en) 2010-06-03 2013-03-12 Seagate Technology Llc Ensuring a most recent version of data is recovered from a memory
US8826051B2 (en) 2010-07-26 2014-09-02 Apple Inc. Dynamic allocation of power budget to a system having non-volatile memory and a processor
US8938574B2 (en) 2010-10-26 2015-01-20 Lsi Corporation Methods and systems using solid-state drives as storage controller cache memory
TWI417727B (en) * 2010-11-22 2013-12-01 Phison Electronics Corp Memory storage device, memory controller thereof, and method for responding instruction sent from host thereof
EP2652623B1 (en) * 2010-12-13 2018-08-01 SanDisk Technologies LLC Apparatus, system, and method for auto-commit memory
GB2486738B (en) 2010-12-24 2018-09-19 Qualcomm Technologies Int Ltd Instruction execution
US20120179874A1 (en) 2011-01-07 2012-07-12 International Business Machines Corporation Scalable cloud storage architecture
US20120209413A1 (en) 2011-02-14 2012-08-16 Microsoft Corporation Background Audio on Mobile Devices
US8694764B2 (en) 2011-02-24 2014-04-08 Microsoft Corporation Multi-phase resume from hibernate
CN102156629A (en) * 2011-05-04 2011-08-17 苏州国芯科技有限公司 Method for extending 32-bit instructions
US8706955B2 (en) 2011-07-01 2014-04-22 Apple Inc. Booting a memory device from a host
US9645758B2 (en) 2011-07-22 2017-05-09 Sandisk Technologies Llc Apparatus, system, and method for indexing data of an append-only, log-based structure
US9141394B2 (en) 2011-07-29 2015-09-22 Marvell World Trade Ltd. Switching between processor cache and random-access memory
TWI521343B (en) 2011-08-01 2016-02-11 Toshiba Kk An information processing device, a semiconductor memory device, and a semiconductor memory device
JP5762930B2 (en) * 2011-11-17 2015-08-12 株式会社東芝 Information processing apparatus and semiconductor memory device
EP2631916B1 (en) * 2011-09-06 2015-08-26 Huawei Technologies Co., Ltd. Data deletion method and apparatus
US8719464B2 (en) * 2011-11-30 2014-05-06 Advanced Micro Device, Inc. Efficient memory and resource management
US20130145055A1 (en) * 2011-12-02 2013-06-06 Andrew Kegel Peripheral Memory Management
CN103975287B (en) 2011-12-13 2017-04-12 英特尔公司 Enhanced system sleep state support in servers using non-volatile random access memory
DE112011105984T5 (en) 2011-12-20 2014-09-18 Intel Corporation Dynamic partial shutdown of a memory-side buffer in a two-level memory hierarchy
US9069551B2 (en) 2011-12-22 2015-06-30 Sandisk Technologies Inc. Systems and methods of exiting hibernation in response to a triggering event
US8879346B2 (en) 2011-12-30 2014-11-04 Intel Corporation Mechanisms for enabling power management of embedded dynamic random access memory on a semiconductor integrated circuit package
CN102609378B (en) 2012-01-18 2016-03-30 中国科学院计算技术研究所 A kind of message type internal storage access device and access method thereof
US9311226B2 (en) 2012-04-20 2016-04-12 Memory Technologies Llc Managing operational state data of a memory module using host memory in association with state change
JP2014044490A (en) 2012-08-24 2014-03-13 Toshiba Corp Host device and memory device
US9116820B2 (en) 2012-08-28 2015-08-25 Memory Technologies Llc Dynamic central cache memory
EP2923358A4 (en) 2012-11-20 2016-06-29 Charles I Peddle Solid state drive architectures
US9229854B1 (en) * 2013-01-28 2016-01-05 Radian Memory Systems, LLC Multi-array operation support and related devices, systems and software
US9652376B2 (en) 2013-01-28 2017-05-16 Radian Memory Systems, Inc. Cooperative flash memory control
KR102074329B1 (en) 2013-09-06 2020-02-06 삼성전자주식회사 Storage device and data porcessing method thereof
US10248587B2 (en) * 2013-11-08 2019-04-02 Sandisk Technologies Llc Reduced host data command processing
WO2015089488A1 (en) 2013-12-12 2015-06-18 Memory Technologies Llc Channel optimized storage modules
CN103761988B (en) * 2013-12-27 2018-01-16 华为技术有限公司 Solid state hard disc and data movement method
US10249351B2 (en) * 2016-11-06 2019-04-02 Intel Corporation Memory device with flexible internal data write control circuitry
KR20180055297A (en) * 2016-11-16 2018-05-25 삼성전자주식회사 Memory device and memory system performing unmap read

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1094392A1 (en) * 1999-10-22 2001-04-25 Sun Microsystems, Inc. Method and apparatus for interfacing with a secondary storage system
US7480749B1 (en) * 2004-05-27 2009-01-20 Nvidia Corporation Main memory as extended disk buffer memory
US20100115193A1 (en) * 2005-07-18 2010-05-06 Palm, Inc. System and method for improving data integrity and memory performance using non-volatile media
US20090157950A1 (en) * 2007-12-14 2009-06-18 Robert David Selinger NAND flash module replacement for DRAM module
US20100037012A1 (en) * 2007-12-28 2010-02-11 Hirokuni Yano Semiconductor Storage Device, Method of Controlling the Same, Controller and Information Processing Apparatus
US20090198872A1 (en) 2008-02-05 2009-08-06 Spansion Llc Hardware based wear leveling mechanism
US20110208914A1 (en) 2008-08-21 2011-08-25 Infinidat Ltd. Storage system and method of operating thereof

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHUAN-SHENG LIN; LAN-RONG DUNG: "A NAND Flash Memory Controller for SD/MMC Flash Memory Card", IEEE TRANSACTIONS OF MAGNETICS, vol. 43, no. 2, February 2007 (2007-02-01), pages 933 - 935, XP002712018, DOI: doi:10.1109/TMAG.2006.888520

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016514320A (en) * 2013-03-15 2016-05-19 インテル・コーポレーション Memory system
JP2016118945A (en) * 2014-12-22 2016-06-30 ソニー株式会社 Memory controller, storage device, and information processing system
US11262936B2 (en) 2015-10-30 2022-03-01 Sony Corporation Memory controller, storage device, information processing system, and memory control method

Also Published As

Publication number Publication date
US10877665B2 (en) 2020-12-29
KR20140116408A (en) 2014-10-02
US11797180B2 (en) 2023-10-24
KR20210130829A (en) 2021-11-01
EP3493066B1 (en) 2023-03-01
EP3493066A1 (en) 2019-06-05
KR102127327B1 (en) 2020-06-29
CN104081366B (en) 2018-03-27
US20170038975A1 (en) 2017-02-09
US20130198434A1 (en) 2013-08-01
KR20220143972A (en) 2022-10-25
JP2015511350A (en) 2015-04-16
JP6442009B2 (en) 2018-12-19
US20210191618A1 (en) 2021-06-24
CN108470007A (en) 2018-08-31
US9417998B2 (en) 2016-08-16
JP2019061699A (en) 2019-04-18
EP2795470A4 (en) 2015-09-30
EP2795470A1 (en) 2014-10-29
CN108470007B (en) 2022-06-17
KR102317152B1 (en) 2021-10-27
KR102458334B1 (en) 2022-10-24
JP6193886B2 (en) 2017-09-06
JP2018022497A (en) 2018-02-08
KR20200079558A (en) 2020-07-03
EP2795470B1 (en) 2019-03-06
JP6817273B2 (en) 2021-01-20
CN104081366A (en) 2014-10-01

Similar Documents

Publication Publication Date Title
US11797180B2 (en) Apparatus and method to provide cache move with non-volatile mass memory system
US11782647B2 (en) Managing operational state data in memory module
US11733869B2 (en) Apparatus and method to share host system RAM with mass storage memory RAM

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13741595

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20147019265

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2013741595

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2014553773

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE