US10481799B2 - Data storage device and method including receiving an external multi-access command and generating first and second access commands for first and second nonvolatile memories - Google Patents

Data storage device and method including receiving an external multi-access command and generating first and second access commands for first and second nonvolatile memories Download PDF

Info

Publication number
US10481799B2
US10481799B2 US15/436,296 US201715436296A US10481799B2 US 10481799 B2 US10481799 B2 US 10481799B2 US 201715436296 A US201715436296 A US 201715436296A US 10481799 B2 US10481799 B2 US 10481799B2
Authority
US
United States
Prior art keywords
data
command
memory device
nonvolatile memory
storage device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US15/436,296
Other languages
English (en)
Other versions
US20170277432A1 (en
Inventor
Eun Jin Yun
Sil Wan CHANG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Assigned to SAMSUNG ELECTRONICS CO., LTD reassignment SAMSUNG ELECTRONICS CO., LTD ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHANG, SIL WAN, YUN, EUN JIN
Publication of US20170277432A1 publication Critical patent/US20170277432A1/en
Priority to US16/656,221 priority Critical patent/US11182078B2/en
Application granted granted Critical
Publication of US10481799B2 publication Critical patent/US10481799B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/16—Handling requests for interconnection or transfer for access to memory bus
    • G06F13/1668—Details of memory controller
    • G06F13/1684—Details of memory controller using multiple buses
    • 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
    • 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/061—Improving I/O performance
    • 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/06—Addressing a physical block of locations, e.g. base addressing, module addressing, memory dedication
    • G06F12/0646—Configuration or reconfiguration
    • G06F12/0692—Multiconfiguration, e.g. local and global addressing
    • 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/0638—Organizing or formatting or addressing of data
    • 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/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
    • 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/0673—Single storage device
    • G06F3/0679—Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
    • 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
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
    • G06F9/30003—Arrangements for executing specific machine instructions
    • G06F9/3004—Arrangements for executing specific machine instructions to perform operations on memory
    • G06F9/30043—LOAD or STORE instructions; Clear instruction

Definitions

  • Embodiments of the present disclosure relate to a data storage device, and more particularly, to a data storage device and method for increasing transmission efficiency between a host and the data storage device, and a data processing system including the same.
  • a storage device having a large capacity usually includes a plurality of memory devices.
  • a memory device is used to store data.
  • Memory devices are divided into volatile memory devices and non-volatile memory devices.
  • Data duplication or backup is often used to recover data in case of failure in storage devices or in a power supply.
  • Data mirroring is one such data duplication scheme. It is a technique of duplicately storing data in at least one device.
  • a host usually executes a plurality of write commands on a storage device with respect to same data in order to perform data mirroring, or executes a single write command with a single address that is received by the storage device and is translated at the storage device in order to perform duplication.
  • typical data duplication may require a greater number of commands (e.g., twice as many) generated by a host, or may require performing address translation and/or processing at a storage device. Both of these can require additional processing.
  • Some embodiments provide a data storage system, method, and device for increasing data efficiency between a host and data storage device and reducing power consumption.
  • a data storage device includes a first nonvolatile memory device, a second nonvolatile memory device, and a management circuit connected to the first nonvolatile memory device and the second nonvolatile memory device.
  • the management circuit is configured to: receive an external multi-access command, the external multi-access command received from outside the data storage device and including a first address and a second address, based on the external multi-access command and the first address, generate a first internal access command and supply the first internal access command and the first address to the first nonvolatile memory device, and based on the external multi-access command and the second address, generate a second internal access command and supply the second internal access command and the second address to the second nonvolatile memory device.
  • a method of accessing a data storage device includes receiving an external multi-access command at the data storage device from a device external to the data storage device, the external multi-access command including a first address and a second address; supplying a first access command based on the external multi-access command to a first nonvolatile memory, the first access command including the first address; executing a first access operation on the first nonvolatile memory device using the first access command and the first address; supplying a second access command based on the external multi-access command to a second nonvolatile memory, the second access command including the second address; and executing a second access operation on the second nonvolatile memory device using the second access command and the second address.
  • a multi-access method for a data storage device includes initiating a multi-access operation on a host device by generating a multi-access request; performing a mapping operation on the multi-access request to generate a multi-access command, the multi-access command including at least a command type indicator, a duplicate/split flag, and a plurality of addresses; and sending the multi-access command from the host to the data storage device.
  • a multi-access method for a data storage device including a management circuit and a plurality of nonvolatile memory devices includes: receiving an external multi-access command from a device external to the data storage device, the external multi-access command including a command type indicator and at least a first address and a second address; transmitting a first internal multi-access command based on the external multi-access command to a first nonvolatile memory device of the data storage device using the first address; transmitting a second internal multi-access command based on the external multi-access command to a second nonvolatile memory device of the data storage device using the second address; accessing the first nonvolatile memory device using the first address; and accessing the second nonvolatile memory device using the second address.
  • FIG. 1 is a block diagram of a data processing system according to some embodiments
  • FIG. 2 is a block diagram of a host and a data storage device illustrated in FIG. 1 according to some embodiments;
  • FIG. 3 is a block diagram of a memory device cluster illustrated in FIG. 2 according to some embodiments.
  • FIG. 4 is a diagram of the hierarchical structure of a host according to some embodiments.
  • FIGS. 5A and 5B are block diagrams of examples of the data storage device illustrated in FIG. 1 ;
  • FIG. 6 is a flowchart of a multi-access method of a data processing system according to some embodiments.
  • FIG. 7 is a flowchart of a multi-write method of a data processing system according to some embodiments.
  • FIG. 8A is a diagram of a multi-write command such as illustrated in FIG. 7 according to some embodiments.
  • FIG. 8B is a diagram of another multi-write command such as illustrated in FIG. 7 according to other embodiments of the inventive concept;
  • FIG. 9 is a diagram for explaining a multi-write operation of a data processing system according to some embodiments.
  • FIG. 10 is a diagram for explaining a multi-write operation of a data processing system according to other embodiments.
  • FIG. 11 is a flowchart of a multi-read method of a data processing system according to some embodiments.
  • FIG. 12 is a flowchart of a multi-read method of a data processing system according to other embodiments.
  • FIG. 13 is a diagram for explaining a multi-read operation of a data processing system according to some embodiments.
  • FIG. 14 is a diagram for explaining a multi-erase method of a data processing system according to some embodiments.
  • FIG. 15 is a block diagram of a data processing system according to some embodiments.
  • FIGS. 16 and 17 are block diagrams of a data processing system including a data storage device according to some embodiments.
  • first, second, third etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. Unless the context indicates otherwise, these terms are only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section, for example as a naming convention. Thus, a first element, component, region, layer or section discussed below in one section of the specification could be termed a second element, component, region, layer or section in another section of the specification or in the claims without departing from the teachings of the present invention. In addition, in certain cases, even if a term is not described using “first,” “second,” etc., in the specification, it may still be referred to as “first” or “second” in a claim in order to distinguish different claimed elements from each other.
  • orientation, layout, location, shapes, sizes, amounts, or other measures do not necessarily mean an exactly identical orientation, layout, location, shape, size, amount, or other measure, but are intended to encompass nearly identical orientation, layout, location, shapes, sizes, amounts, or other measures within acceptable variations that may occur, for example, due to manufacturing processes.
  • the term “substantially” may be used herein to emphasize this meaning, unless the context or other statements indicate otherwise. For example, items described as “substantially the same,” or “substantially equal,” may be exactly the same or equal, or may be the same or equal within acceptable variations that may occur, for example, due to manufacturing or operational processes.
  • each block, unit and/or module may be implemented by dedicated hardware, or as a combination of dedicated hardware to perform some functions and a processor (e.g., one or more programmed microprocessors and associated circuitry) to perform other functions.
  • each block, unit and/or module of the embodiments may be physically separated into two or more interacting and discrete blocks, units and/or modules without departing from the scope of the inventive concepts. Further, the blocks, units and/or modules of the embodiments may be physically combined into more complex blocks, units and/or modules without departing from the scope of the inventive concepts.
  • FIG. 1 is a block diagram of a data processing system 100 according to some embodiments.
  • FIG. 2 is a block diagram of a host 200 a and a data storage device 300 a illustrated in FIG. 1 according to some embodiments.
  • FIG. 3 is a block diagram of a memory device cluster 400 a illustrated in FIG. 2 according to some embodiments.
  • certain reference numerals or characters such as 200 and 200 a , or 300 or 300 a , are used in different figures to represent items that may be the same, but may be a different embodiment. Thus, when described in connection with different figures, these different corresponding labels may be used in this specification.
  • the data processing system 100 may include the host 200 and the data storage device 300 which may communicate a command and/or data with the host 200 through an interface 110 .
  • the data processing system 100 may be implemented, for example, as a personal computer (PC), a workstation, a data center, an internet data center (IDC), a storage area network (SAN), a network attached storage (NAS), or a mobile computing device, but the inventive concept is not restricted to these examples.
  • the mobile computing device may be a laptop computer, a cellular phone, a smart phone, a tablet PC, a personal digital assistant (PDA), an enterprise digital assistant (EDA), a digital still camera, a digital video camera, a portable multimedia player (PMP), a personal navigation device or portable navigation device (PND), a handheld game console, a mobile internet device (MID), a wearable computer, an internet of things (IoT) device, an internet of everything (IoE) device, a drone, or an e-book, but is not restricted thereto.
  • PDA personal digital assistant
  • EDA enterprise digital assistant
  • PMP portable multimedia player
  • PND personal navigation device
  • MID mobile internet device
  • a wearable computer an internet of things (IoT) device, an internet of everything (IoE) device, a drone, or an e-book, but is not restricted thereto.
  • the interface 110 may be implemented, for example, as a serial advanced technology attachment (SATA) interface, a SATA express (SATAe) interface, a SAS (serial attached small computer system interface (SCSI)), a peripheral component interconnect express (PCIe) interface, a non-volatile memory express (NVMe) interface, an advanced host controller interface (AHCI), or a multimedia card (MMC) interface, but the inventive concept is not restricted to these examples.
  • the interface 110 may transmit electrical signals or optical signals between the host 200 and the data storage device 300 .
  • the host 200 may control a data processing operation (e.g., a write or read operation) of the data storage device 300 through the interface 110 .
  • the host 200 may refer to a host controller.
  • the data storage device 300 may include a management module 310 and a plurality of non-volatile memory (NVM) devices 410 - 1 through 410 - m , where “m” is an integer of at least 2.
  • NVM non-volatile memory
  • a data storage device 300 a illustrated in FIG. 2 may also include a buffer 360 and a power management integrated circuit (PMIC) 370 .
  • PMIC power management integrated circuit
  • the data storage device 300 may be a non-volatile memory device such as a flash-based memory device or a phase-change random access memory (PRAM) device but it is not restricted to these examples.
  • the data storage device 300 may be implemented, for example, as a solid-state drive or solid-state disk (SSD), an embedded SSD (eSSD), a universal flash storage (UFS), an MMC, an embedded MMC (eMMC), or a managed NAND, but the inventive concept is not restricted to these examples.
  • each flash-based memory device may include a memory cell array.
  • the memory cell array may include a plurality of memory cells.
  • the memory cell array may be a two-dimensional or three-dimensional memory cell array.
  • the three-dimensional memory cell array may be monolithically formed at one or more physical levels in an array of memory cells having an active region disposed on or above a silicon substrate and may include a circuit related with the operation of the memory cells.
  • the circuit may be formed in, on, or above the silicon substrate.
  • the term “monolithic” means that layers at each level in an array are directly deposited on layers at an underlying level in the array.
  • the three-dimensional memory cell array may include a vertical NAND string which is vertically oriented so that at least one memory cell is placed on or above another memory cell.
  • the at least one memory cell may include a charge trap layer.
  • the data storage device 300 may be implemented as a hard disk drive (HDD), a PRAM device, a magnetoresistive RAM (MRAM) device, a spin-transfer torque MRAM (STT-MRAM) device, a ferroelectric RAM (FRAM) device, or a resistive RAM (RRAM) device.
  • HDD hard disk drive
  • PRAM PRAM
  • MRAM magnetoresistive RAM
  • STT-MRAM spin-transfer torque MRAM
  • FRAM ferroelectric RAM
  • RRAM resistive RAM
  • the management module 310 which may include various circuit elements and may include an integrated circuit, may be referred to as a management circuit, and may control transfer or process of a command and/or data transmitted among the host 200 and the NVM devices 410 - 1 through 410 - m .
  • the management circuit may be referred to as a NAND management circuit.
  • the management module 310 may be implemented, for example, in an integrated circuit (IC) or a system on chip (SoC).
  • host 200 a may include a bus architecture 210 , a central processing unit (CPU) 220 , a memory 225 , and a first interface 230 .
  • the host 200 a may be external to the data storage device 300 a .
  • the host, 200 a including its various components, and the data storage device 300 a , including its various components, may be configured to perform the various operations and methods described herein.
  • the CPU 220 , the memory 225 , and the first interface 230 may communicate a command and/or data with each other via the bus architecture 210 .
  • the host 200 a includes the bus architecture 210 , the CPU 220 , the memory 225 , and the first interface 230 in the embodiments illustrated in FIG. 2 , the inventive concept is not restricted to the host 200 a illustrated in FIG. 2 .
  • the host 200 may be implemented as an IC, a motherboard, a SoC, an application processor (AP), a mobile AP, a web server, a data server, or a database server, but the inventive concept is not restricted to these examples.
  • the bus architecture 210 may be implemented as an advanced microcontroller bus architecture (AMBA), an advanced high-performance bus (AHB), an advanced peripheral bus (APB), an advanced extensible interface (AXI), an advanced system bus (ASB), AXI coherency extensions (ACE), or a combination thereof, but the inventive concept is not restricted to these examples.
  • AMBA advanced microcontroller bus architecture
  • AHB advanced high-performance bus
  • APIB advanced peripheral bus
  • AXI advanced extensible interface
  • ASB advanced system bus
  • ACE AXI coherency extensions
  • the CPU 220 may generate a write command for controlling a write operation of the data storage device 300 , a read command for controlling a read operation of the data storage device 300 , or an erase command for controlling an erase operation of the data storage device 300 .
  • the write command may include a write address (e.g., a logical address or a physical address).
  • the read command may include a read address (e.g., a logical address or a physical address).
  • the CPU 220 may also generate a multi-write command (N-Write command) for controlling a multi-write operation of the data storage device 300 , a multi-read command (N-Read command) for controlling a multi-read operation of the data storage device 300 , or a multi-erase command (N-Erase command) for controlling a multi-erase operation of the data storage device 300 .
  • N-Write command a multi-write command
  • N-Read command for controlling a multi-read operation of the data storage device 300
  • N-Erase command multi-erase command
  • the N-Write, the N-Read, and the N-Erase commands are each generally referred to as multi-access commands, or external multi-access commands.
  • the external multi-access command is a command that is originally passed between the host 200 and the data storage device 300 in various embodiments, so that a data write, read or erase operation is performed with respect to at least two addresses (e.g., physical addresses) with a single command.
  • the at least two addresses may be associated with and may be transmitted along with a single multi-access command.
  • the multi-access command may include the N-Write, the N-Read, and the N-Erase commands, but the inventive concept is not restricted to these embodiments.
  • Other commands including a plurality of addresses may be described as a multi-access command.
  • the CPU 220 may include at least one core.
  • the memory 225 may store data used for the operation of the CPU 220 , data to be transmitted to the data storage device 300 , or data received from the data storage device 300 .
  • the memory 225 may also store flash translation layer (FTL) code which may be executed by the CPU 220 .
  • FTL code may simply be called FTL.
  • An example hierarchy in the host 200 and the FTL will be described in detail below with reference to FIG. 4 .
  • the first interface 230 may change the format of a command and/or data to be transmitted to the data storage device 300 and may transmit the command and/or data in a changed format to the data storage device 300 through the interface 110 .
  • the first interface 230 may also change the format of a response and/or data received from the data storage device 300 and may transmit the response and/or data in a changed format to the CPU 220 through the bus architecture 210 .
  • the first interface 230 may include a transceiver, which transmits and receives a command and/or data.
  • the structure and operations of the first interface 230 may be configured to be compatible with those of the interface 110 .
  • a management module 310 a illustrated in FIG. 2 may include bus architecture 311 , an internal memory (e.g., static random access memory (SRAM)) 315 , a second interface 320 , a CPU 330 , a buffer controller 340 , and a third interface 350 .
  • the bus architecture 311 of the management module 310 a may be implemented as AMBA, AHB, APB, AXI, ASB, ACE, or a combination thereof, but the inventive concept is not restricted to these examples.
  • the internal memory (here SRAM) 315 may store data used for the operations of the management module 310 a or data generated from a data processing operation (e.g. a write or read operation) performed by the management module 310 a .
  • the internal memory 315 may store a partial code of the FTL which may be executed by the CPU 330 .
  • a partial function (or a code for performing the partial function) of the FTL may be implemented in the host 200 and another partial function (or a code for performing the partial function) of the FTL may be implemented in the management module 310 a of the data storage device 300 .
  • the FTL is not fully implemented on the data storage device 300 . In some cases, no portion of the FTL is implemented on the data storage device 300 .
  • the internal memory 315 may be implemented as random access memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), buffer, buffer memory, cache, or tightly coupled memory (TCM) but is not restricted to these examples.
  • RAM random access memory
  • DRAM dynamic RAM
  • SRAM static RAM
  • TCM tightly coupled memory
  • the second interface 320 may change the format of a response and/or data to be transmitted to the host 200 a and may transmit the response and/or data in a changed format to the host 200 a through the interface 110 .
  • the second interface 320 may also receive a command and/or data from the host 200 a , change the format of the command and/or data, and transmit the command and/or data in a changed format to the CPU 330 and/or the buffer controller 340 .
  • the second interface 320 may include a transceiver which transmits and receives a signal and/or data.
  • the structure and operations of the second interface 320 may be configured to be compatible with those of the interface 110 .
  • the second interface 320 may be, for example, a SATA interface, SATAe interface, SAS, PCIe interface, NVMe interface, AHCI, MMC interface, NAND-type flash memory interface, or NOR-type flash memory interface but is not restricted thereto.
  • the CPU 330 may control the internal memory 315 , the second interface 320 , the buffer controller 340 , and the third interface 350 through the bus architecture 311 .
  • the CPU 330 may include at least one core.
  • the CPU 330 may control the PMIC 370 .
  • the buffer controller 340 may write data to or read data from the buffer 360 according to the control of the CPU 330 .
  • the buffer controller 340 may be referred to as a controller or a buffer manager which may control the write and read operations on the buffer 360 .
  • the third interface 350 may control a data processing operation (e.g. a write or read operation) on the memory device cluster 400 a through channels CHA through CHD according to the control of the CPU 330 .
  • the third interface 350 may be, for example, a SATA interface, SATAe interface, SAS, PCIe interface, NVMe interface, AHCI, MMC interface, NAND-type flash memory interface, or NOR-type flash memory interface, but is not restricted thereto.
  • the buffer 360 may write data received from the host 200 or read data that has been stored according to the control of the buffer controller 340 .
  • the buffer 360 may be implemented as volatile memory such as buffer memory, RAM, SRAM, or DRAM, but the disclosure is not restricted to these examples.
  • the management module 310 and the buffer 360 may be implemented in a single package using package-on-package (PoP), multi-chip package (MCP), or system-in package (SiP), but the disclosure is not restricted to these examples.
  • a first chip including the buffer 360 may be stacked above a second chip including the management module 310 , for example, using stacking terminals such as bumps or balls.
  • the PMIC 370 may control operating voltages applied to the management module 310 , the buffer 360 , and/or the memory device cluster 400 a .
  • the first operating voltage applied to the management module 310 , the second operating voltage applied to the buffer 360 , and the third operating voltage applied to the memory device cluster 400 a may be the same as or different from one another.
  • the memory device cluster 400 a illustrated in FIG. 2 may include a plurality of memory devices 410 - 1 through 410 - m which transmit and receive data through the respective channels CHA through CHD.
  • the memory devices 410 - 1 through 410 - m may include a plurality of memory elements or memory chips CA 0 through CA 2 , CB 0 through CB 2 , CC 0 through CC 2 , and CD 0 through CD 2 , respectively.
  • three memory chips are connected to each of the four channels CHA through CHD in the embodiments illustrated in FIG. 3 , the current embodiments are just an example, and the number of channels and the number of memory chips connected to each channel may be changed.
  • Each memory chip may be, for example, a nonvolatile memory chip, such as a NAND memory.
  • a semiconductor chip refers to a die formed from a wafer and that includes an integrated circuit thereon.
  • Semiconductor chips can be stacked to form semiconductor devices such as chip stacks and/or semiconductor packages. Semiconductor chips may also be referred to as semiconductor devices.
  • the memory elements or memory chips CA 0 through CA 2 , CB 0 through CB 2 , CC 0 through CC 2 , or CD 0 through CD 2 in the memory device 410 - 1 , 410 - 2 , 410 - 3 , or 410 - 4 may be implemented in a single package or mounted on a single module.
  • Each memory chip may include a plurality of blocks; each of the blocks may include a plurality of pages.
  • the first memory device 410 - 1 may be connected to the first channel CHA; the second memory device 410 - 2 may be connected to the second channel CHB; the m-th memory device 410 - m may be connected to the m-th channel CHD.
  • the number of memory devices 410 - 1 through 410 - m and the number of channels may be appropriately determined according to different situations.
  • the number of memory chips or memory elements in each of the memory devices 410 - 1 through 410 - m may also be appropriately determined according to different situations.
  • a channel as used herein may refer to an independent data path which exists between the management module 310 , e.g., the third interface 350 , and a memory device.
  • the data path may include transmission lines which may transfer data and/or control signals.
  • FIG. 4 is a diagram of a hierarchical structure 240 of a host according to some embodiments of the inventive concept.
  • the hierarchical structure 240 may include an application layer 250 , an FTL 260 , and a storage interface layer 270 .
  • the FTL 260 may perform address mapping 261 , garbage collection (GC) 263 , wear-leveling (WL) 265 , and bad block management (BBM) 267 .
  • GC garbage collection
  • WL wear-leveling
  • BBM bad block management
  • performing address mapping 261 includes mapping a logical address to a physical address corresponding to a physical position in the data storage device 300 .
  • the FTL 260 may translate a logical block address into a physical block address corresponding to a physical position in the data storage device 300 using an address translation mapping table (not shown) which links a logical address to a physical address.
  • An address mapping method may be sector mapping, block mapping, or hybrid mapping but is not restricted to these examples.
  • the address mapping may map a logical address (e.g., a single logical address) to a plurality of physical addresses, such as two physical addresses of two different nonvolatile memory devices of the data storage or memory device cluster.
  • Wear leveling (WL) 265 is a technique of managing the data storage device 300 so that a write operation is not concentrated on a particular block in the data storage device 300 , for example, each block has a uniform write count.
  • the FTL 260 may record and manage a write count for each block or page and may perform management so that a write operation is performed based on the write count.
  • Garbage collection (GC) 263 is a technique of equalizing erase counts of the blocks in the data storage device 300 .
  • the BBM 267 may refer to a function or code of managing bad block information of the data storage device 300 .
  • the FTL 260 may be software or firmware code which is stored in the memory 225 of the host 200 and executed in the CPU 220 .
  • the FTL 260 may be implemented as part of an operating system (OS) of the host 200 .
  • OS operating system
  • the FTL 260 may be partially implemented in the host 200 and partially implemented in the data storage device 300 .
  • the address mapping 261 , the GC 263 , and the WL 265 may be implemented in the host 200 and the BBM 267 may be implemented in the data storage device 300 , but the inventive concept is not restricted to this example.
  • the storage interface layer 270 may correspond to the first interface 230 illustrated in FIG. 2 .
  • FIGS. 5A and 5B are block diagrams of examples ( 300 b and 300 c respectively) of the data storage device 300 illustrated in FIG. 1 .
  • the structure and operations of the data storage device 300 b illustrated in FIG. 5A are similar to those of the data storage device 300 a illustrated in FIG. 2 . Therefore, descriptions will be focused on differences between the data storage devices 300 a and 300 b to avoid redundancy.
  • a management module 310 b of the data storage device 300 b illustrated in FIG. 5A may further include an error correction code (ECC) engine 325 , also referred to as an ECC circuit, and/or a data operator 335 .
  • ECC error correction code
  • the ECC engine 325 may correct errors in data to be stored in a memory device cluster 400 b and/or errors in data output from the memory device cluster 400 b .
  • the ECC engine 325 may be implemented anywhere within the management module 310 b .
  • the ECC engine 325 may be implemented within the third interface 350 .
  • the data operator 335 may compress data to be stored in the memory device cluster 400 b and may decompress data output from the memory device cluster 400 b .
  • the data operator 335 may also generate parity data from the data to be stored in the memory device cluster 400 b .
  • Data operator 335 may also therefore more specifically be referred to as a data compression/decompression circuit.
  • the structure and operations of the data storage device 300 c illustrated in FIG. 5B are similar to those of the data storage device 300 a illustrated in FIG. 2 . Therefore, descriptions will be focused on differences between the data storage devices 300 a and 300 c to avoid redundancy. As compared to the management module 310 a of the data storage device 300 a illustrated in FIG. 2 , a management module 310 c of the data storage device 300 c illustrated in FIG. 5B does not include a buffer controller 340 . Accordingly, the data storage device 300 c does not include the buffer 360 .
  • An interface 110 ′ between a host 200 c and the data storage device 300 c may be compatible with a NVM interface (e.g., a NAND interface). Accordingly, the host 200 c may send a command (e.g., a NAND command) and an address (or addresses) to the management module 310 c according to the interface 110 ′ compatible with the NVM interface and may directly transmit data to a memory device cluster 400 c (shown at 130 ).
  • a command e.g., a NAND command
  • an address or addresses
  • the management module 310 c may receive the command and the address (or addresses) from the host 200 c and apply them to the memory device cluster 400 c .
  • the management module 310 c may convert the command and the address(es) received from the host 200 c to be suitable to the memory device cluster 400 c .
  • the command and the address(es) from the host 200 c may be applied to the memory device cluster 400 c via the management module 310 c , but the data may be directly transmitted (shown at 130 ) from the host 200 c to the memory device cluster 400 c without passing through the management module 310 c.
  • FIG. 6 is a flowchart of a multi-access method of the data processing system 100 according to some embodiments of the inventive concept.
  • a host e.g., 200 , 200 a , 200 b , or 200 c
  • sends a multi-access command (N-Access command) to the data storage device (e.g., 300 , 300 a , 300 b , or 300 c ) and the data storage device (e.g., a respective management module 310 , 310 a , 310 b , or 310 c therein) receives the N-Access command in operation S 101 .
  • the data storage device e.g., 300 , 300 a , 300 b , or 300 c
  • receives the N-Access command receives the N-Access command in operation S 101 .
  • the N-Access command designates at least two addresses (e.g., at least two physical block addresses) so that an access operation is performed on the at least two physical block addresses with a single command.
  • the at least two physical block addresses can be different blocks on a same chip, different blocks on different chips, or different blocks on different packages.
  • at least two separate commands or at least two times of a command are usually necessary.
  • the N-Access command originally defined between the host 200 and the data storage device 300 is used, so that an access operation (e.g., a write operation, a read operation, or an erase operation) can be performed on at least two different physical block addresses with a single command.
  • an access operation e.g., a write operation, a read operation, or an erase operation
  • the N-Access command may include an address list Add_list of N addresses (e.g., physical addresses), where N is an integer of at least 2.
  • the N-Access command may or may not include data according to a form or type of a command.
  • the N-Access command will be described in detail with reference to FIGS. 8A and 8B later.
  • the N-Access command may be derived from an initial command generated at the host that includes a single logical address, which may be a destination address.
  • the host may include a flash translation layer that translates a logical address associated with a command initiated at the host (also referred to as a request) into a command that includes two physical addresses.
  • the two physical addresses may be based on the single logical address and the flash translation layer operations, such as described above.
  • the management module 310 of the data storage device 300 may store the N-Access command in the buffer 360 .
  • the management module 310 may convert the N-Access command to an access command NVM_Access suitable to a NVM device (e.g., a NAND flash memory device).
  • the management module 310 may generate and send a first access command NVM_Access including the first physical address PBA 1 to a first NVM device in operation S 103 and may generate and send a second access command NVM_Access including the second physical address PBA 2 to a second NVM device in operation S 105 .
  • Each access command NVM_Access may be a write command NVM_Write, a read command NVM_Read, or an erase command NVM_Erase, but is not restricted thereto.
  • Each access command NVM_Access may be referred to as an internal access command with respect to the data storage device 300 .
  • the management module 310 may send an acknowledgement ACK of the N-Access command to the host 200 in operation S 107 .
  • the data storage device 300 may receive an external multi-access command from a device external to the data storage device (e.g., the host 200 ), wherein the external multi-access command includes a first address and a second address. Based on the external multi-access command, a first access command is supplied to a first nonvolatile memory, the first access command including the first address, and a second access command is supplied to a second nonvolatile memory, the second access command including the second address. A first access operation is then executed on the first nonvolatile memory device using the first access command and the first address, and a second access operation is executed on the second nonvolatile memory device using the second access command and the second address.
  • a device external to the data storage device e.g., the host 200
  • the external multi-access command includes a first address and a second address.
  • FIG. 7 is a flowchart of a multi-write method of the data processing system 100 according to some embodiments of the inventive concept.
  • FIG. 8A is a diagram of a multi-access command, such as the N-Write command illustrated in FIG. 7 according to some embodiments of the inventive concept.
  • FIG. 8B is a diagram of a multi-access command, such as the N-Write command illustrated in FIG. 7 according to other embodiments of the inventive concept.
  • the host 200 sends a multi-access command (N-Write) to the data storage device 300 , and the management module 310 of the data storage device 300 receives the N-Write command from the host 200 in operation S 110 .
  • the multi-access command designates at least two addresses (e.g., physical block addresses) so that an operation is performed on the at least two physical block addresses with a single command.
  • at least two separate commands or at least two times of a command are usually necessary.
  • the multi-access command (e.g., N-Write command) originally defined between the host 200 and the data storage device 300 is used, so that an access operation can be performed on at least two different physical block addresses with a single command.
  • the write command transmitted between the host 200 and the data storage device 300 may include at least two different physical addresses associated with two different respective memory blocks.
  • a command 40 a may include a command identifier 41 , an opcode 42 , a data pointer 43 , a duplicate/split flag 47 , and an address list.
  • the command 40 a may also include an optional compression flag (not shown), and/or a chip address (e.g., chip enable, also not shown).
  • the command identifier 41 may be data uniquely defined to identify a command. For example, each command may be identified with a number so that it can be later matched with corresponding data.
  • a write or erase command from a host may include a command identifier, so that when an acknowledgment is returned to the host, it has the same identifier so that the host knows which command/request the acknowledgment is responsive to.
  • a read command from a host may include a command identifier, so that when data is returned to the host, it has the same identifier so that the host knows which command/request the acknowledgment is responsive to.
  • the opcode 42 may specify an operation corresponding to a command.
  • the operation may be a normal (e.g., single) read operation, a multi-read operation, a normal (e.g., single) write operation, a multi-write operation, etc.
  • the opcode 42 may designate the type of command, so that the management module 310 knows how to process the command. For example, if the opcode is for a normal read (e.g., using a single address), then the management module 310 can appropriately convert the command, address, and any data for a single access. However, if the opcode is for a multi-read, then the management module 310 can convert the command, addresses, and any data for a multi-access.
  • the opcode may also be described herein as a command-type indicator.
  • the data pointer 43 may be address information indicating the position of data in the memory 225 of the host 200 .
  • Data pointers may be connected in a linked list structure, but the inventive concept is not restricted to this embodiment.
  • the management module 310 of the data storage device 300 may read data from or write data to the memory 225 of the host 200 based on the data pointer 43 .
  • the duplicate/split flag 47 may be included to indicate, in the case of multi-access, whether the associated data is duplicate data or split data, or to indicate neither (e.g., if the command is a single-access command).
  • data associated with a write command is to be duplicated and stored at two different physical locations.
  • data associated with a write command may be split so that a portion of it is stored at the first physical location, and the remainder is stored at the second physical location. Though two locations are described, this is an example only, and more locations (e.g., three or more) may be used to duplicate or split data into three or more locations.
  • data can be read that is duplicate data stored in multiple locations, or that alternatively is split data stored in multiple locations.
  • the management module 310 controls how to process the incoming or outgoing command and/or data.
  • the address list may include at least two, (e.g., N) physical addresses.
  • the address list may include a first physical address 44 and a second physical address 45 .
  • Each of the physical addresses 44 and 45 may include a start address (Start_Address) 441 or 451 of physical blocks to which data will be written in the data storage device 300 and the number of physical blocks 443 or 453 .
  • each physical address 44 or 45 may include the Start_Address 441 or 451 and an end address (not shown) of the physical blocks to which data will be written in the data storage device 300 . Consequently, each physical address included in the address list may include, in various forms, information for designating a position of physical blocks to which data will be written.
  • an additional field in the command may indicate a chip address (e.g., in the form of chip enable data).
  • a chip address e.g., in the form of chip enable data.
  • the two chip addresses can be included in the command 40 a .
  • such chip addresses are included in the same field as the Start_Addresses, for example, as additional bits added to the start address.
  • the chip addresses need not be different, however, and may be the same chip address in the case where different physical addresses in the external multi-access command are for different blocks in the same chip.
  • the different physical addresses correspond to the same relative physical address within two different chips, but two different chip addresses.
  • an additional field in the command may include a compression/decompression code. For example, based on whether and how data should be compressed or decompressed in response to a multi-access command, a data compression/decompression code can be used.
  • an N-Write command 40 b may include the command identifier 41 , the opcode 42 , a duplicate/split flag 47 , the address list, and data 46 . Though not shown, it may also include a chip address/chip addresses, and/or a compression/decompression flag.
  • the N-Write command 40 b illustrated in FIG. 8B is similar to the N-Write command 40 a illustrated in FIG. 8A ; thus differences therebetween will be described to avoid redundancy.
  • N-Write command 40 a illustrated in FIG. 8A includes the data pointer 43
  • the N-Write command 40 b illustrated in FIG. 8B includes the data 46 to be written to the data storage device 300 .
  • the N-Write command 40 a or 40 b may have a packet form, but the inventive concept is not restricted to these embodiments.
  • the management module 310 of the data storage device 300 may receive the N-Write command and may also receive and store write data WDAT included in the N-Write command in the buffer 360 .
  • the N-Write command may be a single command including a single command identifier.
  • the management module 310 may read the write data WDAT from the memory 225 of the host 200 , which is designated by the data pointer 43 included in the N-Write command illustrated in FIG. 8A , and may store the write data WDAT in the buffer 360 .
  • the management module 310 converts the N-Write command (an external command) into the write command NVM_Write (e.g., an internal command) suitable to a NVM device (e.g., a NAND flash memory device).
  • NVM_Write e.g., an internal command
  • the management module 310 may generate and send a first write command NVM_Write including the first physical address PBA 1 to the first NVM device in operation S 120 and may generate and send a second write command NVM_Write including the second physical address PBA 2 to the second NVM device in operation S 130 .
  • the first and second NVM devices may be the NVM devices, e.g., 410 - 1 and 410 - 2 , respectively, connected to different channels, e.g., CHA and CHB, respectively, as shown in FIG. 2 . Accordingly, operations S 120 and S 130 may be performed in parallel (e.g., at the same time).
  • First data DAT 1 written to the first NVM device and second data DAT 2 written to the second NVM device are based on the write data WDAT received from the host 200 .
  • the first data DAT 1 and second data DAT 2 may be the data stored in the buffer 360 , and may be supplied to the respective first and second nonvolatile memory devices from the buffer 360 .
  • Each of the first and second data DAT 1 and DAT 2 may be the same as the write data WDAT, may be part of the write data WDAT, may be compressed data of the write data WDAT, or may be parity data of the write data WDAT, but the inventive concept is not restricted to these examples.
  • the compressed data or the parity data of the write data WDAT may be generated by the data operator 335 illustrated in FIG. 5A .
  • the external multi-access command is a multi-write command that includes write data
  • a first part of the write data is included in a first internal access command (e.g., in a first command that is converted by the management module 310 and that uses the first address)
  • a second part of the write data and not the first part of the write data is included in the second internal access command (e.g., in a second command that is converted by the management module 310 and that uses the second address).
  • the duplicate/split flag 47 may indicate split data.
  • the external multi-access command is a multi-write command that includes write data, and all of the write data associated with the multi-write command is included in the first internal access command, and all of the write data associated with the multi-write command is also included in the second internal access command.
  • the duplicate/split flag 47 may indicate duplicate data.
  • a multi-access request may be initiated and generated at the host 200 and may be first processed at the host 200 (e.g., at a flash translation layer of the host), to form a multi-access command.
  • a mapping operation may be performed (e.g., using a mapping table and circuit), which converts a first address, such as a logical address, into two or more second addresses, e.g., physical addresses.
  • the two or more second addresses may be different from each other, and may be selected using flash translation layer controls such as described in connection with FIG. 4 , for example.
  • the multi-access command may then be converted at the data storage device, e.g., by a management module 310 , into separate first and second internal access commands.
  • the host 200 may supply a multi-access command to the data storage device 300 , and the data storage device 300 , via the management module 310 , may supply respective internal multi-access commands based on the command received from the host 200 to a plurality of respective memory devices of the data storage device 300 , for example to different physical addresses of a plurality of memory devices.
  • FIG. 9 is a diagram for explaining a multi-write operation of a data processing system according to some embodiments of the inventive concept.
  • each of the first and second data DAT 1 and DAT 2 may be the same as the write data WDAT received from the host 200 .
  • the management module 310 may store data the same as the write data WDAT received from the host 200 at different physical addresses, i.e., a first physical address and a second physical address according to the opcode 42 and a duplicate/split flag 47 (see FIGS. 8A and 8B ) in a multi-write command (N-Write command).
  • the opcode 42 and duplicate/split flag 47 may be part of the same field.
  • the first physical address may be on a first NVM device (e.g., NAND/PRAM 910 - 1 )
  • the second physical address may be on a second NVM device (e.g., NAND/PRAM 910 - 2 ).
  • a data storage device e.g., SSD
  • duplication or mirroring of the write data WDAT may be carried out.
  • one of the first and second data DAT 1 and DAT 2 is the same as the write data WDAT and the other may be the compressed data or the parity data of the write data WDAT.
  • a compression/decompression flag, and/or even a further parity/error correction flag may indicate as such.
  • the management module 310 may store the write data WDAT received from the host 200 at the first physical address in operation S 120 ( FIG. 7 ) and may store the compressed data or the parity data of the write data WDAT at the second physical address in operation S 130 . It should be noted that when error correction or compression is performed by the management module, it may be performed before the data is duplicated/split, or after the data is duplicated/split.
  • error correction e.g., using error correction code, “ECC”
  • ECC error correction code
  • FIG. 10 is a diagram for explaining a multi-write operation of a data processing system according to other embodiments of the inventive concept.
  • the management module 310 may divide the write data WDAT received from the host 200 into at least two segments DAT 1 ′ and DAT 2 ′ according to the opcode 42 and duplicate/split flag 47 in a multi-write command (N-Write command) and may store the segments DAT 1 ′ and DAT 2 ′ at different physical addresses, i.e., a first physical address and a second physical addresses, respectively (in operations S 120 and S 130 ). As shown in FIG.
  • the first physical address may be on a first NVM device (e.g., NAND/PRAM 1010 - 1 ), and the second physical address may be on a second NVM device (e.g., NAND/PRAM 1010 - 2 ) of a data storage device (e.g., SSD 1010 ).
  • a duplicate/split flag 47 may indicate that a first part of data associated with the multi-access command should be written to a first memory device of the data storage device and not a second memory device of the data storage device, and a second part of the data associated with the multi-access command should be written to the second memory device and not the first memory device.
  • the first segment DAT 1 ′ may be the first half of the write data WDAT and the second segment DAT 2 ′ may be the second half of the write data WDAT.
  • the management module 310 may send the acknowledgement ACK of the N-Write command to the host 200 in operation S 140 .
  • FIG. 11 is a flowchart of a multi-read method of a data processing system according to some embodiments of the inventive concept.
  • the host 200 sends a multi-read command (N-Read) to the data storage device 300 in operation S 210 and the management module 310 of the data storage device 300 receives the N-Read command from the host 200 in operation S 210 .
  • the host may initially generate a multi-read request and convert the multi-read request into a multi-read command including two addresses, for example, using a mapping table and circuit such as described above.
  • the N-Read command designates at least two (e.g., N) physical block addresses so that a read operation is performed on the at least two physical block addresses with a single command.
  • the N-Read command originally defined between the host 200 and the data storage device 300 is used, so that a read operation can be performed on at least two different physical block addresses with a single command, e.g., having a single command identifier.
  • the N-Read command may be similar to the N-Write command illustrated in FIG. 8A or 8B .
  • the N-Read command may include the command identifier 41 , the opcode 42 , the duplicate/split flag 47 , the compress/decompress flag, and the address list 44 and 45 (and an optional chip address field).
  • the N-Read command may be different than the N-Write command in that the N-Read command does not include the data pointer 43 or the data 46 to be written to the data storage device 300 .
  • the management module 310 of the data storage device 300 may receive and store the N-Read command in the buffer 360 .
  • the management module 310 may convert the N-Read command to a read command NVM_Read suitable to an NVM device (e.g., a NAND flash memory device).
  • the management module 310 may generate and send a first read command NVM_Read including the first physical address PBA 1 to the first NVM device in operation S 220 and may generate and send a second read command NVM_Read including the second physical address PBA 2 to the second NVM device in operation S 240 .
  • the first and second NVM devices may be the NVM devices, e.g., 410 - 1 and 410 - 2 , respectively, connected to different channels, e.g., CHA and CHB, respectively, as shown in FIG. 2 . Accordingly, operations S 220 and S 240 may be performed in parallel (e.g., at the same time).
  • the first NVM device may read the first data DAT 1 from the first physical address PBA 1 in response to the first read command NVM_Read and send the first data DAT 1 to the management module 310 in operation S 230 .
  • the second NVM device may read the second data DAT 2 from the second physical address PBA 2 in response to the second read command NVM_Read and send the second data DAT 2 to the management module 310 in operation S 250 .
  • Operations S 230 and S 250 may be performed in parallel.
  • the management module 310 may temporarily store the first and second data DAT 1 and DAT 2 respectively read from the first and second NVM devices in the buffer 360 .
  • the management module 310 may transmit read data RDAT to the host 200 based on the first and second data DAT 1 and DAT 2 in operation S 260 .
  • the read data RDAT transmitted to the host 200 may be a combination of the first and second data DAT 1 and DAT 2 .
  • the host 200 may set the opcode 42 in the N-Read command to a particular value before sending the N-Read command to the data storage device 300 .
  • the data storage device 300 may read the first and second data DAT 1 and DAT 2 from the first and second physical addresses PBA 1 and PBA 2 , respectively, and send the read data RDAT obtained by combining the first and second data DAT 1 and DAT 2 to the host 200 according to the N-Read command in operation S 260 .
  • FIG. 12 is a flowchart of a multi-read method of a data processing system according to other embodiments of the inventive concept.
  • the multi-read method illustrated in FIG. 12 is similar to that illustrated in FIG. 11 ; thus differences therebetween will be mainly described.
  • the read data RDAT transmitted to the host 200 may be either the first data DAT 1 or the second data DAT 2 .
  • the management module 310 may transmit the data that has been read earliest among the data DAT 1 and DAT 2 from the different physical addresses to the host 200 , for example, the data with the faster read speed.
  • the management circuit is configured to select between sending the first data read from the first nonvolatile memory device to the host and sending the second data read from the second nonvolatile memory device to the host based on the data read speed of the first nonvolatile memory device and the data read speed of the second nonvolatile memory device.
  • the management module 310 may compare the first and second data DAT 1 and DAT 2 read from the different physical addresses in operation S 255 .
  • the first and second data DAT 1 and DAT 2 are the same as each other, only one of the first and second data DAT 1 and DAT 2 may be transmitted to the host 200 in operation S 260 ′.
  • both data may be transmitted to the host 200 as recombined, previously split, data.
  • the management module 310 may correct errors in data to be stored in the memory device cluster 400 and/or errors in data output from the memory device cluster 400 using the ECC engine 325 shown in FIG. 5A .
  • the management module 310 may perform a predetermined data process on the first data DAT 1 or the second data DAT 2 . For instance, when the second data DAT 2 is the compressed data of the first data DAT 1 , the management module 310 may decompress the second data DAT 2 to obtained decompressed data. When the second data DAT 2 is the parity data of the first data DAT 1 , the management module 310 may compare the parity data of the first data DAT 1 with the second data DAT 2 that has been read and may transmit the first data DAT 1 as the read data RDAT to the host 200 when the parity data of the first data DAT 1 is the same as the second data DAT 2 .
  • FIG. 13 is a diagram for explaining a multi-read operation of a data processing system according to some embodiments of the inventive concept.
  • an N-Read command may include the address list Add_list including three different physical addresses.
  • the management module 310 of the data storage device 1310 may read first through third data DAT 1 , DAT 2 , and DAT 3 from NVM devices 1310 - 1 , 1310 - 2 , and 1310 - 3 , respectively, having the three different physical addresses, respectively, in response to the N-Read command.
  • the three NVM devices may be different types of devices.
  • the NVM device 1310 - 1 may be three-level cell (TLC) NAND; the NVM device 1310 - 2 may be single-level cell (SLC) NAND; the NVM device 1310 - 3 may be multi-level cell (MLC) NAND.
  • the management module 310 may transmit a combination of the first through third data DAT 1 , DAT 2 , and DAT 3 to the host 200 .
  • the management module 310 may transmit one of the first through third data DAT 1 , DAT 2 , and DAT 3 to the host 200 .
  • data is transferred between the host 200 and an NVM device via the management module 310 .
  • the data may be directly transferred between the host 200 and the NVM device without passing through the management module 310 in other embodiments.
  • FIG. 14 is a diagram for explaining a multi-erase method of a data processing system according to some embodiments of the inventive concept.
  • the host 200 sends a multi-erase command (N-Erase) to the data storage device 300 in operation S 310 and the management module 310 of the data storage device 300 receives the N-Erase command from the host 200 in operation S 310 .
  • the N-Erase command designates at least two physical block addresses so that an erase operation is performed on the at least two physical block addresses with a single command. Similar conversion and flags as described above may be used for the N-Erase command.
  • the N-Erase command originally defined between the host 200 and the data storage device 300 is used, so that an erase operation can be performed on at least two different physical block addresses with a single command.
  • the N-Erase command may be similar to the N-Write command illustrated in FIG. 8A or 8B .
  • the N-Erase command may include the command identifier 41 , the opcode 42 , and the address list 44 and 45 .
  • the N-Erase command may not include the data pointer 43 like an N-Write command or the data 46 to be written to the data storage device 300 , and also may not include a duplicate/split flag 47 or a compression/decompression flag.
  • the management module 310 of the data storage device 300 may receive and store the N-Erase command in the buffer 360 .
  • the management module 310 may convert the N-Erase command to an erase command NVM_Erase suitable to an NVM device (e.g., a NAND flash memory device).
  • the management module 310 may generate and send a first erase command NVM_Erase including the first physical address PBA 1 to the first NVM device in operation S 320 and may generate and send a second erase command NVM_Erase including the second physical address PBA 2 to the second NVM device in operation S 330 .
  • the first and second NVM devices may be the NVM devices, e.g., 410 - 1 and 410 - 2 , respectively, connected to different channels, e.g., CHA and CHB, respectively, as shown in FIG. 2 . Accordingly, operations S 320 and S 330 may be performed in parallel (e.g., at the same time).
  • the first NVM device may erase blocks corresponding to the first physical address PBA 1 in response to the first erase command NVM_Erase.
  • the second NVM device may erase blocks corresponding to the second physical address PBA 2 in response to the second erase command NVM_Erase.
  • the management module 310 may send the acknowledgement ACK of the N-Erase command to the host 200 in operation S 340 .
  • a data storage device can receive an external multi-access command from a device external to the data storage device.
  • the external multi-access command can include a first address and a second address.
  • a first access command (e.g., generated by the data storage device) can be supplied based on the external multi-access command to a first nonvolatile memory of the data storage device.
  • the first access command may include the first address.
  • a first access operation is executed on the first nonvolatile memory device using the first access command and the first address.
  • a second access command (e.g., generated by the data storage device) can be supplied based on the external multi-access command to a second nonvolatile memory.
  • the second access command may include the second address.
  • a second access operation is executed on the second nonvolatile memory device using the second access command and the second address.
  • the multi-access command may include a single command identifier. Further, the first access operation and second access operation can be executed at the same time.
  • a data processing system As described above, data can be written to, read from, or erased from at least two storage regions with a single multi-access command transmitted from the host 200 to the data storage device 300 . Accordingly, as compared to conventional data processing systems typically requiring at least two times of transmission of a command, a data processing system according to some embodiments of the invention enables efficient use of a bandwidth, thereby reducing power consumption.
  • FIG. 15 is a block diagram of a data processing system 500 according to certain embodiments of the inventive concept.
  • the data processing system 500 may include a database 520 , a database server 530 , a second network 540 , and a plurality of client computers 550 and 551 .
  • the database 520 and the database server 530 may be included in a data center 510 .
  • the data center 510 may be an internet data center or a cloud data center.
  • the database 520 may include a plurality of data storage devices 300 .
  • the data storage devices 300 may be installed in racks.
  • the structure and operations of the data storage devices 300 are substantially the same as or similar to those of the data storage devices described above.
  • the database server 530 may control the operations of each of the data storage devices 300 .
  • the database server 530 may perform the function of the host 200 illustrated in FIG. 1 .
  • the database server 530 may be connected to the second network 540 , e.g. an internet or Wi-Fi, via a first network 535 , e.g. a local area network (LAN).
  • the client computers 550 and 551 may be connected to the database server 530 via the second network 540 .
  • FIGS. 16 and 17 are block diagrams of data processing systems 900 and 900 ′ including the data storage device 300 according to some embodiments of the inventive concept.
  • the data processing system 900 may include the data storage device 300 , a power supply 910 , a CPU 920 , a RAM 930 , a user interface 940 , and a system bus 950 which electrically connects the elements 300 , 910 , 920 , 930 , and 940 with one another.
  • the CPU 920 controls the overall operation of the data processing system 900 .
  • the RAM 930 stores information necessary for the operation of the data processing system 900 .
  • the user interface 940 provides an interface between the data processing system 900 and a user.
  • the power supply 910 supplies power to the internal elements, i.e., the CPU 920 , the RAM 930 , the user interface 940 , and the data storage device 300 .
  • the CPU 920 may correspond to the host 200 ; the data storage device 300 may perform an access operation on different physical addresses in response to a multi-access command (N-Access) from the host 200 .
  • N-Access multi-access command
  • the structure of the data processing system 900 ′ illustrated in FIG. 17 is similar to that of the data processing system 900 illustrated in FIG. 16 ; thus differences therebetween will be mainly described to avoid redundancy.
  • the data processing system 900 ′ illustrated in FIG. 17 further includes a redundant array of independent disks (RAID) controller card 960 .
  • RAID redundant array of independent disks
  • a plurality of data storage devices e.g., SSDs 300 - 1 through 300 - k (where “k” is an integer of at least 2)
  • the data processing systems 900 and 900 ′ respectively illustrated in FIGS. 16 and 17 each may be a computer, a PDA, a cellular phone, a smart phone, an MP3 player, a portable multimedia player (PMP), an automotive navigation system, or a mobile internet device (MID) but is not restricted to these examples.
  • a multi-access command originally defined between a host and a data storage device is used to transmit a plurality of addresses and data with a single command, so that data processing efficiency of the data storage device is increased and data transmission efficiency between the host and the data storage device is also increased. As a result, power consumption of the data storage device and a data processing system including the data storage device is reduced.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Software Systems (AREA)
  • Techniques For Improving Reliability Of Storages (AREA)
US15/436,296 2016-03-25 2017-02-17 Data storage device and method including receiving an external multi-access command and generating first and second access commands for first and second nonvolatile memories Active US10481799B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/656,221 US11182078B2 (en) 2016-03-25 2019-10-17 Method of accessing a data storage device using a multi-access command

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2016-0036386 2016-03-25
KR20160036386 2016-03-25

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/656,221 Continuation US11182078B2 (en) 2016-03-25 2019-10-17 Method of accessing a data storage device using a multi-access command

Publications (2)

Publication Number Publication Date
US20170277432A1 US20170277432A1 (en) 2017-09-28
US10481799B2 true US10481799B2 (en) 2019-11-19

Family

ID=59814261

Family Applications (2)

Application Number Title Priority Date Filing Date
US15/436,296 Active US10481799B2 (en) 2016-03-25 2017-02-17 Data storage device and method including receiving an external multi-access command and generating first and second access commands for first and second nonvolatile memories
US16/656,221 Active 2037-05-12 US11182078B2 (en) 2016-03-25 2019-10-17 Method of accessing a data storage device using a multi-access command

Family Applications After (1)

Application Number Title Priority Date Filing Date
US16/656,221 Active 2037-05-12 US11182078B2 (en) 2016-03-25 2019-10-17 Method of accessing a data storage device using a multi-access command

Country Status (4)

Country Link
US (2) US10481799B2 (zh)
KR (1) KR102387968B1 (zh)
CN (1) CN107229417B (zh)
DE (1) DE102017104448A1 (zh)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10248330B2 (en) * 2017-05-30 2019-04-02 Seagate Technology Llc Data storage device with buffer tenure management
US11592991B2 (en) 2017-09-07 2023-02-28 Pure Storage, Inc. Converting raid data between persistent storage types
US10789020B2 (en) 2017-06-12 2020-09-29 Pure Storage, Inc. Recovering data within a unified storage element
US11609718B1 (en) 2017-06-12 2023-03-21 Pure Storage, Inc. Identifying valid data after a storage system recovery
US10552090B2 (en) * 2017-09-07 2020-02-04 Pure Storage, Inc. Solid state drives with multiple types of addressable memory
CN116431072A (zh) 2017-06-12 2023-07-14 净睿存储股份有限公司 集成到大容量存储设备的可访问快速耐久存储
US10459809B2 (en) * 2017-06-30 2019-10-29 Intel Corporation Stacked memory chip device with enhanced data protection capability
KR102410671B1 (ko) * 2017-11-24 2022-06-17 삼성전자주식회사 스토리지 장치, 스토리지 장치를 제어하는 호스트 장치, 및 스토리지 장치의 동작 방법
KR102637166B1 (ko) * 2018-04-17 2024-02-16 삼성전자주식회사 대용량 데이터를 저장하는 네트워크 스토리지 장치
CN110389904A (zh) * 2018-04-20 2019-10-29 北京忆恒创源科技有限公司 具有压缩的ftl表的存储设备
KR102513919B1 (ko) * 2018-11-05 2023-03-27 에스케이하이닉스 주식회사 메모리 시스템
CN113168385A (zh) * 2018-08-03 2021-07-23 御眼视觉技术有限公司 访问动态存储器模块
KR102527265B1 (ko) * 2018-08-23 2023-05-02 에스케이하이닉스 주식회사 데이터 저장 장치 및 동작 방법, 이를 포함하는 스토리지 시스템
KR20200076431A (ko) * 2018-12-19 2020-06-29 삼성전자주식회사 메모리 컨트롤러 및 메모리 시스템의 동작 방법, 및 메모리 시스템
CN110007853B (zh) * 2019-01-30 2022-06-28 镕铭微电子(济南)有限公司 一种Nandflash命令处理方法、装置、终端及存储介质
KR20200100309A (ko) 2019-02-18 2020-08-26 삼성전자주식회사 메모리 장치 및 시스템
US20220188028A1 (en) * 2019-03-12 2022-06-16 Intel Corporation Computational data storage systems
CN109992444A (zh) * 2019-03-25 2019-07-09 深圳忆联信息系统有限公司 一种基于硬件的端对端数据保护方法、装置、计算机设备及存储介质
CN111913892B (zh) * 2019-05-09 2021-12-07 北京忆芯科技有限公司 使用cmb提供开放通道存储设备
CN112306378B (zh) * 2019-08-01 2024-04-09 兆易创新科技集团股份有限公司 用户数据搬移的恢复方法、装置、电子设备及存储介质
US11017842B2 (en) 2019-08-29 2021-05-25 Micron Technology, Inc. Copy data in a memory system with artificial intelligence mode
US11720413B2 (en) * 2020-06-08 2023-08-08 Samsung Electronics Co., Ltd. Systems and methods for virtualizing fabric-attached storage devices
DE102021004288A1 (de) * 2020-09-15 2022-03-17 Löwenstein Medical Technology S.A. Verfahren und System zur Datenübertragung bei Beatmungsgeräten
US20230153037A1 (en) * 2021-11-17 2023-05-18 Microchip Technology Incorporated System and Method for a Storage Controller Card with Redundant Boot Storage

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6317805B1 (en) 1998-12-18 2001-11-13 Emc Corporation Data transfer interface having protocol conversion device and upper, lower, middle machines: with middle machine arbitrating among lower machine side requesters including selective assembly/disassembly requests
US6505268B1 (en) 1996-12-20 2003-01-07 Compaq Computer Corporation Data distribution in a disk array
US20050289218A1 (en) 2004-06-28 2005-12-29 Rothman Michael A Method to enable remote storage utilization
US20060262608A1 (en) * 2005-05-18 2006-11-23 Edward Babb Performing multiple read operations via a single read command
US20090006745A1 (en) 2007-06-28 2009-01-01 Cavallo Joseph S Accessing snapshot data image of a data mirroring volume
US20100229032A1 (en) * 2009-03-06 2010-09-09 Samsung Electronics Co., Ltd. Solid state disk device and related data storing and reading methods
US20110022783A1 (en) * 2009-07-24 2011-01-27 Stec, Inc. Flash storage with increased throughput
US20110093659A1 (en) * 2009-10-16 2011-04-21 Samsung Electronics Co., Ltd. Data storage device and data storing method thereof
US20120084484A1 (en) * 2010-09-30 2012-04-05 Apple Inc. Selectively combining commands for a system having non-volatile memory
US8307151B1 (en) 2009-11-30 2012-11-06 Micron Technology, Inc. Multi-partitioning feature on e-MMC
US8489852B2 (en) 2009-07-06 2013-07-16 Samsung Electronics Co., Ltd. Method and system for manipulating data
US8650362B2 (en) 2009-04-17 2014-02-11 Violin Memory Inc. System for increasing utilization of storage media
US20140281361A1 (en) 2013-03-15 2014-09-18 Samsung Electronics Co., Ltd. Nonvolatile memory device and related deduplication method
US8954662B2 (en) 2009-03-20 2015-02-10 OCZ Storage Solutions Inc. SSD controller, and method for operating an SSD controller
US8966580B2 (en) 2008-05-01 2015-02-24 Sandisk Il Ltd. System and method for copying protected data from one secured storage device to another via a third party
US9063903B2 (en) * 2011-09-22 2015-06-23 Kabushiki Kaisha Toshiba Memory system provided with NAND flash memory and method including simultaneously writing data to first and second memory arrays
US20160266821A1 (en) * 2015-03-11 2016-09-15 Sandisk Technologies Inc. Multichip Dual Write
US20180011635A1 (en) * 2016-07-08 2018-01-11 SK Hynix Inc. Memory system and operating method thereof

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8341332B2 (en) * 2003-12-02 2012-12-25 Super Talent Electronics, Inc. Multi-level controller with smart storage transfer manager for interleaving multiple single-chip flash memory devices
US7519754B2 (en) * 2005-12-28 2009-04-14 Silicon Storage Technology, Inc. Hard disk drive cache memory and playback device
KR101226685B1 (ko) 2007-11-08 2013-01-25 삼성전자주식회사 수직형 반도체 소자 및 그 제조 방법.
KR101691092B1 (ko) 2010-08-26 2016-12-30 삼성전자주식회사 불휘발성 메모리 장치, 그것의 동작 방법, 그리고 그것을 포함하는 메모리 시스템
US8553466B2 (en) 2010-03-04 2013-10-08 Samsung Electronics Co., Ltd. Non-volatile memory device, erasing method thereof, and memory system including the same
US9536970B2 (en) 2010-03-26 2017-01-03 Samsung Electronics Co., Ltd. Three-dimensional semiconductor memory devices and methods of fabricating the same
KR101682666B1 (ko) 2010-08-11 2016-12-07 삼성전자주식회사 비휘발성 메모리 장치, 그것의 채널 부스팅 방법, 그것의 프로그램 방법 및 그것을 포함하는 메모리 시스템
JP2012119038A (ja) * 2010-12-02 2012-06-21 Toshiba Corp 不揮発性半導体メモリ及び記憶装置
US8819328B2 (en) * 2010-12-30 2014-08-26 Sandisk Technologies Inc. Controller and method for performing background operations
US8700834B2 (en) * 2011-09-06 2014-04-15 Western Digital Technologies, Inc. Systems and methods for an enhanced controller architecture in data storage systems
KR20140031515A (ko) * 2012-09-03 2014-03-13 삼성전자주식회사 메모리 컨트롤러 및 상기 메모리 컨트롤러를 포함하는 전자장치
US9395924B2 (en) * 2013-01-22 2016-07-19 Seagate Technology Llc Management of and region selection for writes to non-volatile memory
US10073626B2 (en) * 2013-03-15 2018-09-11 Virident Systems, Llc Managing the write performance of an asymmetric memory system
KR101632002B1 (ko) 2014-09-25 2016-06-21 엘지전자 주식회사 이동단말기 및 그 제어방법

Patent Citations (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6505268B1 (en) 1996-12-20 2003-01-07 Compaq Computer Corporation Data distribution in a disk array
US6317805B1 (en) 1998-12-18 2001-11-13 Emc Corporation Data transfer interface having protocol conversion device and upper, lower, middle machines: with middle machine arbitrating among lower machine side requesters including selective assembly/disassembly requests
US20050289218A1 (en) 2004-06-28 2005-12-29 Rothman Michael A Method to enable remote storage utilization
US20060262608A1 (en) * 2005-05-18 2006-11-23 Edward Babb Performing multiple read operations via a single read command
US20090006745A1 (en) 2007-06-28 2009-01-01 Cavallo Joseph S Accessing snapshot data image of a data mirroring volume
US8966580B2 (en) 2008-05-01 2015-02-24 Sandisk Il Ltd. System and method for copying protected data from one secured storage device to another via a third party
US20100229032A1 (en) * 2009-03-06 2010-09-09 Samsung Electronics Co., Ltd. Solid state disk device and related data storing and reading methods
US8954662B2 (en) 2009-03-20 2015-02-10 OCZ Storage Solutions Inc. SSD controller, and method for operating an SSD controller
US8650362B2 (en) 2009-04-17 2014-02-11 Violin Memory Inc. System for increasing utilization of storage media
US20150032942A1 (en) 2009-04-17 2015-01-29 Violin Memory, Inc. System for increasing utilization of storage media
US8489852B2 (en) 2009-07-06 2013-07-16 Samsung Electronics Co., Ltd. Method and system for manipulating data
US20110022783A1 (en) * 2009-07-24 2011-01-27 Stec, Inc. Flash storage with increased throughput
US20110093659A1 (en) * 2009-10-16 2011-04-21 Samsung Electronics Co., Ltd. Data storage device and data storing method thereof
US8307151B1 (en) 2009-11-30 2012-11-06 Micron Technology, Inc. Multi-partitioning feature on e-MMC
US20120084484A1 (en) * 2010-09-30 2012-04-05 Apple Inc. Selectively combining commands for a system having non-volatile memory
US9063903B2 (en) * 2011-09-22 2015-06-23 Kabushiki Kaisha Toshiba Memory system provided with NAND flash memory and method including simultaneously writing data to first and second memory arrays
US20140281361A1 (en) 2013-03-15 2014-09-18 Samsung Electronics Co., Ltd. Nonvolatile memory device and related deduplication method
US20160266821A1 (en) * 2015-03-11 2016-09-15 Sandisk Technologies Inc. Multichip Dual Write
US20180011635A1 (en) * 2016-07-08 2018-01-11 SK Hynix Inc. Memory system and operating method thereof

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Korea Information Science Society, Rhee et al., "Implementation and Performance Analysis of a NAND Controller for ONFI NAND Flash Memory," pp. 135-138, Mar. 2013, KIISE Transactions on Computing Practices (KTCP).
Resnick et al., "Proposing an Abstracted Interface and Protocol for Computer Systems." Jul. 7, 2014, pp. 1-10, Sandia National Laboratories, SAND2014-15795.

Also Published As

Publication number Publication date
CN107229417B (zh) 2022-03-22
US20200050363A1 (en) 2020-02-13
KR20170114255A (ko) 2017-10-13
US11182078B2 (en) 2021-11-23
DE102017104448A1 (de) 2017-09-28
KR102387968B1 (ko) 2022-04-20
US20170277432A1 (en) 2017-09-28
CN107229417A (zh) 2017-10-03

Similar Documents

Publication Publication Date Title
US11182078B2 (en) Method of accessing a data storage device using a multi-access command
US10324639B2 (en) Data storage device having multiple solid state drives for data duplication, and data processing system including the same
US10579279B2 (en) Data storage device and data processing system having the same
US9996282B2 (en) Method of operating data storage device and method of operating system including the same
US10114550B2 (en) Data storage device and data processing system including the data storage device
KR102506135B1 (ko) 데이터 저장 장치와 이를 포함하는 데이터 처리 시스템
KR102592803B1 (ko) 데이터 저장 장치 및 그것의 동작 방법
US20160291869A1 (en) Data storage device and data processing system including the same
KR102417182B1 (ko) 데이터 저장 장치와 이를 포함하는 데이터 처리 시스템
US10416886B2 (en) Data storage device that reassigns commands assigned to scale-out storage devices and data processing system having the same
US20180267895A1 (en) Memory system
US11048625B2 (en) Memory system and operating method thereof
US10503406B2 (en) Data storage device and data processing system having the same
US20220229775A1 (en) Data storage device and operating method thereof
US11782638B2 (en) Storage device with improved read latency and operating method thereof
US10331366B2 (en) Method of operating data storage device and method of operating system including the same
CN113805793A (zh) 存储装置及其操作方法
US20230154529A1 (en) Storage controller and storage device including the same
US20170031633A1 (en) Method of operating object-oriented data storage device and method of operating system including the same
US20240143509A1 (en) Data Storage Device and Method for Handling Write Commands in Zoned Storage
US20230146540A1 (en) Storage device and an operating method of a storage controller thereof
US10915265B2 (en) Controller, operating method thereof and memory system for controlling a buffer

Legal Events

Date Code Title Description
AS Assignment

Owner name: SAMSUNG ELECTRONICS CO., LTD, KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:YUN, EUN JIN;CHANG, SIL WAN;SIGNING DATES FROM 20161213 TO 20161214;REEL/FRAME:041933/0951

STPP Information on status: patent application and granting procedure in general

Free format text: EX PARTE QUAYLE ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO EX PARTE QUAYLE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4