Technology for issuing commands on selected memory devices

By using device status, mode register mask bits, or additional identifiers in non-volatile memory devices to dynamically adjust device status or mask bits, the problem of needing to modify identifiers to select memory device subgroups in the prior art is solved, thereby improving selection efficiency and resource utilization.

CN108694020BActive Publication Date: 2026-11-17INTEL CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN201810213458.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2017-03-31
Filing Date
2018-03-15
Publication Date
2026-11-17
Estimated Expiration
2038-03-15

AI Technical Summary

Technical Problem

Existing technologies require modifying the identifier of each memory device when selectively selecting subgroups of memory devices, leading to inefficiency and resource waste.

Method used

Subgroups of memory devices can be selected by dynamically adjusting the device state or mask bits using device state, mode register mask bits, or additional identifiers in non-volatile memory devices, avoiding modification of identifiers.

Benefits of technology

It enables efficient selection of memory device subgroups, reduces waste of resources and energy, and improves operational efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN108694020B_ABST
    Figure CN108694020B_ABST
Patent Text Reader

Abstract

Techniques for issuing commands on selected memory devices include an apparatus comprising a data storage controller and a plurality of non-volatile, in-bit write, byte- or block-addressable memory devices. The memory devices are arranged in one or more blocks, and the memory devices in each block are connected to the same communication channel. The data storage controller selects a subgroup of the plurality of memory devices in the block without modifying the identifier of each memory device and issues commands to operate on the data in the selected subgroup.
Need to check novelty before this filing date? Find Prior Art

Description

Background Technology

[0001] Some data storage devices include multiple non-volatile memory devices arranged in one or more arrays. The non-volatile memory devices in a given array are connected to the same communication channel, which receives commands to manipulate data on the memory devices in the array. Selectively selecting a subgroup of memory devices on the same communication channel typically requires modifying the identifier of each memory device in the subgroup, and then selecting the memory device with the modified identifier. Attached Figure Description

[0002] The concepts described herein are illustrated in the accompanying drawings by way of example rather than limitation. For the purposes of simplicity and clarity, the elements shown in the drawings are not necessarily drawn to scale. Where deemed appropriate, reference numerals are repeated in the drawings to indicate corresponding or similar elements.

[0003] Figure 1 It is a simplified block diagram of at least one embodiment of a data storage device for executing commands on a selected subgroup of memory devices;

[0004] Figure 2 It can be made by Figure 1 A simplified block diagram of at least one embodiment of the environment established by the data storage controller;

[0005] Figure 3 It can be made by Figure 1 and Figure 2 A simplified flowchart of at least one embodiment of a method for selecting a subgroup executed by a data storage controller;

[0006] Figure 4 It can be made by Figure 1 and Figure 2 A simplified flowchart of at least one embodiment of a method for reading data executed by a data storage controller;

[0007] Figure 5 It can be made by Figure 1 and Figure 2 A simplified flowchart of at least one embodiment of a method for writing data executed by a data storage controller; and

[0008] Figure 6 It includes Figure 1 and Figure 2 A simplified block diagram of at least one embodiment of a computing device for data storage devices. Detailed Implementation

[0009] While the concepts of this disclosure are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and will be described in detail herein. However, it should be understood that there is no intention to limit the concepts of this disclosure to the specific forms disclosed, but rather it is intended to cover all modifications, equivalents, and alternatives consistent with this disclosure and the appended claims.

[0010] References to "an embodiment," "embodiment," "illustrative embodiment," etc., in the specification indicate that the described embodiment may include specific features, structures, or characteristics; however, each embodiment may or may not include specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, it is assumed that implementing such a feature, structure, or characteristic in conjunction with other embodiments is within the knowledge of those skilled in the art, whether or not the embodiment is explicitly described. Furthermore, it should be recognized that items included in the list in the form of "at least one A, B, and C" can represent (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C). Similarly, items listed in the form of "at least one of A, B, or C" can represent (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0011] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried on or stored on a transient or non-transitory machine-readable (e.g., computer-readable) storage medium, which may be read and executed by one or more processors. The machine-readable storage medium may be embodied in any storage device, mechanism, or other physical structure for storing or transmitting information in a machine-readable form (e.g., non-volatile or volatile memory, optical disc, or other media device).

[0012] In the accompanying drawings, some structural or methodological features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. In some embodiments, such features may be arranged in a different manner and / or order than those shown in the schematic drawings. Furthermore, including a structural or methodological feature in a particular drawing does not imply that such a feature is necessary in all embodiments, and in some embodiments, it may not be included or may be combined with other features.

[0013] like Figure 1The illustrative data storage device 100 shown, for executing commands on selected memory devices, includes a data storage controller 102 and a memory 116, which schematically includes non-volatile memory 118 and volatile memory 120. As discussed more specifically below, in use, the data storage controller 102 is configured to select a subgroup of one or more non-volatile memory devices for performing data operations (e.g., read, write, refresh, etc.).

[0014] The data storage controller 102 of the data storage device 100 can be embodied as any type of control device, circuitry, or combination of hardware devices capable of writing to, reading from, locating, and replacing data in the non-volatile memory 118. In an illustrative embodiment, the data storage controller 102 includes a processor or processing circuitry 104, local memory 106, a host interface 108, selection logic 110, a buffer 112, and memory control logic 114. It should be appreciated that in other embodiments, the data storage controller 102 may include additional devices, circuitry, and / or components typically found in the drive controller of a solid-state drive.

[0015] Processor 104 may be embodied as any type of processor capable of performing the functions described herein. For example, processor 104 may be embodied as a single-core or multi-core processor, a digital signal processor, a field-programmable gate array (FPGA), a microcontroller, or other processor or processing / control circuitry. Similarly, local processor 106 may be embodied as any type of volatile and / or non-volatile memory or data storage device capable of performing the functions described herein. In an illustrative embodiment, local processor 106 stores firmware and / or other instructions executable by processor 104 to perform the functions described for data storage controller 102. In some embodiments, processor 104 and local processor 106 may form part of a system-on-a-chip (SoC) and be integrated onto a single integrated circuit chip along with other components of data storage controller 102.

[0016] The host interface 108 may also be embodied as a collection of any type of hardware processor, processing circuitry, input / output circuitry, and / or components capable of facilitating communication between the data storage device 100 and a host device or service (e.g., a host application). That is, the host interface 108 embodies or establishes an interface for accessing data stored on the data storage device 100 (e.g., stored in memory 116). To this end, the host interface 108 may be configured to utilize any suitable communication protocols and / or technologies for facilitating communication with the data storage device 100, depending on the type of data storage device. For example, in some embodiments, the host interface 108 may be configured to communicate with the host device or service using Serial Advanced Technology Attachment (SATA), Fast Peripheral Component Interconnect (PCIe), Serial Attached SCSI (SAS), Universal Serial Bus (USB), and / or other communication protocols and / or technologies.

[0017] In an illustrative embodiment, selection logic 110 is embodied as dedicated circuitry and / or devices configured to select one or more non-volatile memory devices of non-volatile memory 118 of memory 116 to form a subgroup for executing commands. Selection logic 110 may be embodied as a coprocessor, an application-specific integrated circuit (ASIC), or other dedicated circuitry or devices. In such embodiments, selection logic 110 provides a hardware-accelerated implementation of the selection-related operations described herein. In other embodiments, at least a portion of selection logic 110 may be embodied as firmware or other processor-executable instructions.

[0018] The buffer 112 of the data storage controller 102 is embodied as a volatile memory used by the data storage controller 102 to temporarily store data read from or written to the memory 116. The specific size of the buffer 112 may depend on the total storage size of the memory 116. The memory control logic 114 is schematically embodied as hardware circuitry and / or one or more devices configured to control read / write access to data at specific storage locations in the memory 116.

[0019] The non-volatile memory 118 can be embodied as any type of data storage device capable of storing data persistently (even in the event of a power interruption to the non-volatile memory 118). For example, in an illustrative embodiment, the non-volatile memory 118 is embodied as one or more non-volatile memory devices 122. The non-volatile memory device 122 is illustratively embodied as a byte- or block-addressable, write-in-place non-volatile memory device. In an illustrative embodiment, the non-volatile memory devices 122 are arranged in blocks (ranks). It should be understood that the non-volatile memory devices 122 in each block are connected to the same communication channel, as discussed in more detail below. However, in other embodiments, the non-volatile memory 118 may be embodied as a memory device using chalcogenide phase change materials (e.g., chalcogenide glass), or any other type of byte- or block-addressable, write-in-place non-volatile memory, ferroelectric random access memory (FeTRAM), nanowire-based non-volatile memory, phase change memory (PCM), memory incorporating memristor technology, magnetoresistive random access memory (MRAM), or any combination of spin-transfer torque (STT)-MRAM.

[0020] The volatile memory 120 can be embodied as any type of data storage device capable of storing data when power is supplied to it. For example, in the illustrative embodiment, the volatile memory 120 is embodied as one or more volatile memory devices, and is periodically referred to as volatile memory 120 hereinafter. It is understood that in other embodiments, the volatile memory 120 can be embodied as other types of non-persistent data storage devices. The volatile memory device of the volatile memory 120 is illustratively embodied as a dynamic random access memory (DRAM) device, but can be embodied as other types of volatile memory devices and / or memory technologies capable of storing data when power is supplied to it.

[0021] Now for reference Figure 2In use, the data storage device 100 can establish an environment 200. The illustrative environment 200 includes a data manager 210, a command issuer 220, and an interface manager 230. The data manager 210 further includes a device selector 212. Additionally, the command issuer 220 further includes a data reader 222, a data writer 224, and a refresher 226. Furthermore, the illustrative environment 200 includes subgroup data 240, which can be embodied as arbitrary data indicating one or more subgroups and memory devices associated with each subgroup (e.g., within each subgroup). The subgroup data 240 can be accessed by modules and / or submodules of the data storage controller 102. Each component of the environment 200 can be embodied as firmware, software, hardware, or a combination thereof. For example, the logic and other components of the environment 200 can form part of, or be otherwise established by, the data storage controller 102 or other hardware components of the data storage device 100. Thus, in some embodiments, any one or more of the components of environment 200 may be embodied as a collection of circuits or electrical devices (e.g., data manager circuit 210, device selector circuit 212, command issuer circuit 220, data reader circuit 222, data writer circuit 224, refresher circuit 226, interface manager circuit 230, etc.).

[0022] Data manager 210 is configured to control which non-volatile memory device 122 in non-volatile memory 118 is selected to execute a command. Data manager 210 can be embodied in hardware, firmware, software, virtualized hardware, emulation architecture, and / or combinations thereof as discussed above. For this purpose, data manager 210 includes device selector 212. Device selector 212 is configured to select a subgroup of non-volatile memory devices 122 to execute a command. Specifically, as described above, in the illustrative embodiment, non-volatile memory 118 is embodied as a plurality of non-volatile memory devices 122 arranged in blocks. The non-volatile memory devices 122 in each block are connected via a communication channel. Because the non-volatile memory devices 122 in a block share the same communication channel, all non-volatile memory devices 122 in the same block respond to and execute commands, unless device selector 212 defines a subgroup of non-volatile memory devices 122 in the block for executing a command. In an illustrative embodiment, device selector 212 is configured to form a subgroup of non-volatile memory devices 122 within the same block for executing commands (e.g., read or write) by selecting (i.e., adding or removing) one or more non-volatile memory devices 122 within the same block. It should be appreciated that selectively adding or removing non-volatile memory devices 122 from the same block for executing commands reduces the memory and energy usage overhead that would otherwise result from using all non-volatile memory devices 122 in the block for command execution.

[0023] The present invention includes a method for selecting one or more non-volatile memory devices 122 in a block without modifying the assigned identifier of each of the non-volatile memory devices 122.

[0024] Equipment status

[0025] In some embodiments, the device selector 212 is configured to create a subgroup of one or more non-volatile memory devices 122 within a block based on the device state of each non-volatile memory device 122. In such embodiments, each non-volatile memory device 122 includes a device state indicating whether to select or deselect a non-volatile memory device 122 to execute a command. This allows the device selector 212 to select or deselect a non-volatile memory device 122 by changing its device state without modifying its unique identifier. In such embodiments, only the subgroup of non-volatile memory devices 122 that is in a selected state responds to a command.

[0026] For example, device selector 212 can add non-volatile memory device 122 to a subgroup by selecting an identifier for non-volatile memory device 122. If the selected identifier matches non-volatile memory device 122 within the block, the device state of non-volatile memory device 122 changes to a selected state. If the selected identifier does not match non-volatile memory device 122 within the block, the device state of non-volatile memory device 122 does not change. For example, if non-volatile memory device 122 is in a selected state, the device state remains selected, and if non-volatile memory device 122 is in a deselected state, the device state remains deselected.

[0027] Similarly, device selector 212 can remove non-volatile memory device 122 from a subgroup by selecting an identifier for non-volatile memory device 122. If the selected identifier matches a non-volatile memory device 122 within the block, the device state of non-volatile memory device 122 changes to a deselected state. If the selected identifier does not match a non-volatile memory device 122 within the block, the device state of non-volatile memory device 122 remains unchanged. For example, if non-volatile memory device 122 is in a selected state, the device state remains selected, and if non-volatile memory device 122 is in a deselected state, the device state remains deselected.

[0028] Mode register mask bits

[0029] In some embodiments, device selector 212 is configured to create a subgroup of one or more non-volatile memory devices 122 within a block based on one or more mode register bits of each non-volatile memory device 122. In such embodiments, each non-volatile memory device 122 includes at least two mode register mask bits, including a read command mask bit and a write command mask bit. The mode register mask bits allow device selector 212 to select one or more non-volatile memory devices 122 to perform read and / or write commands by clearing the corresponding mode register mask bits of the non-volatile memory device 122. Furthermore, device selector 212 can set one or more mode register mask bits of the non-volatile memory device 122 to remove the non-volatile memory device 122 from the subgroup associated with the corresponding command.

[0030] For example, device selector 212 can add non-volatile memory device 122 to a subgroup for executing read commands by clearing the read command mask bit of non-volatile memory device 122. In such an embodiment, only the subgroup of non-volatile memory devices 122 with their read command mask bits cleared responds to the read command. It should be understood that even if the selected identifier matches the identifier of non-volatile memory device 122, non-volatile memory devices 122 with their set read command mask bits will not respond to the read command. Similarly, device selector 212 can add non-volatile memory device 122 to a subgroup for executing write commands by clearing the write command mask bit of non-volatile memory device 122. In such an embodiment, only the subgroup of non-volatile memory devices 122 with their write command mask bits cleared responds to the write command. It should be recognized that even if the selected identifier matches the identifier of the non-volatile memory device 122, the non-volatile memory device 122 with the set write command mask bit does not respond to a write command. In such an embodiment, the device selector 212 can remove the non-volatile memory device 122 from the subgroup by setting the read command mask bit of the non-volatile memory device 122. The non-volatile memory device 122 with the set read command mask bit does not respond to a read command, and the non-volatile memory device 122 with the set write command mask bit does not respond to a write command.

[0031] For example, in an illustrative embodiment, non-volatile memory 118 includes eleven non-volatile memory devices 122 arranged in a block. Each non-volatile memory device 122 includes at least two identifiers: a primary identifier and an assigned identifier. All primary identifiers of the non-volatile memory devices 122 in the same block are either selected or deselected. The assigned identifier is a unique identifier assigned to each of the non-volatile memory devices 122 in the block. During initial setup, the primary identifiers of all eleven memory devices 122 are selected, and the read command mask bits are cleared for the first nine memory devices 122 (i.e., assigned identifiers 1 to 9), but the read command mask bits are set for the tenth and eleventh memory devices. In other words, the data storage controller 102 can read data from the first nine memory devices, but the tenth and eleventh memory devices are blocked and do not respond to read commands. Furthermore, the write command mask bits are cleared for the first ten memory devices (i.e., the assigned identifiers 1 to 10), but the write command mask bits are set for the eleventh memory device. In other words, the data storage controller 102 can write data to the first ten memory devices, but the eleventh memory device is blocked and does not respond to write commands.

[0032] In such an example, if the data storage controller 102 (e.g., from host 250) receives a read command for reading data from the tenth memory device 122, the device selector 212 is configured to clear the read command mask bit for the tenth memory device. This allows the data storage controller 102 to read data from the tenth memory device 122 as well as from the first nine memory devices 122 in response to receiving the read command. Furthermore, if the data storage controller 102 receives a write command for writing data to the eleventh memory device 122, the device selector 212 is configured to clear the write command mask bit for the eleventh memory device 122. This allows the data storage controller 102 to write data to the eleventh memory device 122 as well as from the first ten memory devices 122 in response to receiving the write command.

[0033] It should be recognized that, in some embodiments, the command can be a read command, a write command, a refresh read command, and a refresh write command. In such embodiments, a refresh read command forces the non-volatile memory device 122 to execute a read command, regardless of the state of the read command mask bits of the non-volatile memory device 122. Similarly, a refresh write command forces the non-volatile memory device 122 to execute a write command, regardless of the state of the write command mask bits of the non-volatile memory device 122. Therefore, refresh commands take precedence over other commands.

[0034] Additional identifiers

[0035] In some embodiments, the device selector 212 is configured to create a subgroup of one or more non-volatile memory devices 122 within a block based on an additional identifier for each non-volatile memory device 122. In such embodiments, an additional identifier is assigned to each non-volatile memory device 122 to identify the non-volatile memory device 122 to be added to or removed from the subgroup. For example, each non-volatile memory device 122 may include a primary identifier for refresh or other commands, a first assigned identifier for read operations, and a second assigned identifier for write operations.

[0036] Command issuer 220 is configured to manage reading data from and writing data to a subgroup of non-volatile memory devices 122 within non-volatile memory 118. This command issuer can be embodied in hardware, firmware, software, virtualized hardware, emulation architecture, and / or combinations thereof. For this purpose, command issuer 220 includes a data reader 222, a data writer 224, and a refresher 226.

[0037] Data reader 222 is configured to read data from a selected subgroup of nonvolatile memory devices 122 in response to a read command. To this end, data reader 222 is configured to determine the subgroup of nonvolatile memory devices 122 based on the received read command. As discussed above, a subgroup of nonvolatile memory devices 122 includes one or more nonvolatile memory devices 122 within the same block. In some embodiments, the read command may identify one or more nonvolatile memory devices 122 from which data reader 222 is requested to read data. In some embodiments, data reader 222 may select the subgroup of nonvolatile memory devices 122 based on subgroup data 240 associated with parameters of the received read command, such as the context of the received read command, the type of data to be read (e.g., text, image, video, audio), the amount of data to be read, and / or an identifier of the software (e.g., process, application, etc.) associated with the read command. Subgroup data 240 includes various subgroups of one or more nonvolatile memory devices 122.

[0038] Data writer 224 is configured to write data to a selected subgroup (selected subgroup) of nonvolatile memory devices 122 in response to a write command. To this end, data writer 224 is configured to determine the subgroup of nonvolatile memory devices 122 based on the received write command. As discussed above, the subgroup of nonvolatile memory devices 122 includes one or more nonvolatile memory devices 122 within the same block. In some embodiments, the write command may identify one or more nonvolatile memory devices 122 in which data writer 224 is requested to write data. In some embodiments, data writer 224 may select the subgroup of nonvolatile memory devices 122 based on subgroup data 240 associated with parameters of the received write command, such as the context of the received write command, the type of data to be written (e.g., text, image, video, audio), the amount of data to be written, and / or an identifier of the software (e.g., process, application, etc.) associated with the write command.

[0039] Refresher 226 is configured to execute a requested command to all non-volatile memory devices 122 in the block in response to a refresh command. For example, the refresh command could be a refresh read command. In such a case, in response to a refresh read command, refresher 226 could force the reading of data from all non-volatile memory devices 122 in the block, regardless of the state of each non-volatile memory device 122 (e.g., selected / deselected device state, read command mask bit state, selected identifier). Similarly, the refresh command could be a refresh write command. In such a case, in response to a refresh write command, refresher 226 could force the writing of data to all non-volatile memory devices 122 in the block, regardless of the state of each non-volatile memory device 122 (e.g., selected / deselected device state, write command mask bit state, selected identifier).

[0040] Interface manager 230 is configured to process various instructions, including, but not limited to, data storage instructions and data read instructions received from host 250. Interface manager 230 may be embodied as an application, service, and / or other device. In some embodiments, interface manager 230 may also be configured to process other instructions, including Self-Monitoring, Analysis, and Reporting Technology (“SMART”) instructions and other instructions defined in the Fast Non-Volatile Memory (“NVMe”) specification. To process the various instructions, interface manager 230 is configured to identify received instructions and any data and / or parameters associated with those instructions, and to send those items to data manager 210. For example, in response to a read instruction, interface manager 230 sends data read by data manager 210 to host 250. Conversely, in response to write and / or erase instructions, interface manager 230 sends the result of the instruction to host 250, such as an acknowledgment of receipt or completion of the instruction.

[0041] Now for reference Figure 3 In use, the data storage controller 102 of the data storage device 100 can execute method 300 for executing commands on a subgroup of non-volatile memory devices 122. Method 300 begins at block 302, where the data storage controller 102 determines whether a command has been received from the host 250 to execute the received command on one or more non-volatile memory devices 122 in the block. As discussed above, in the illustrative embodiment, the command may be a read command, a write command, a refresh read command, or a refresh write command. If the data storage controller 102 determines that no command has been received, method 300 loops back to block 302 to continue waiting for a command from the host 250. However, if the data storage controller 102 determines that a command has been received, method 300 proceeds to block 304.

[0042] In block 304, based on the received command, the data storage controller 102 determines which non-volatile memory devices 122 to select to execute the received command operation. To this end, in block 306, the data storage controller 102 can identify the received command and any device data associated with the received command. As discussed above, in some embodiments, the device data for each command can specify one or more non-volatile memory devices 122 within a block to execute the command. Alternatively, in block 308, in other embodiments, the data storage controller 102 can determine one or more non-volatile memory devices 122 based on the parameters of the command.

[0043] In block 310, based on the received command, data storage controller 102 determines whether to create a subgroup comprising the selected non-volatile memory devices 122. If data storage controller 102 determines, based on the received command, not to create a subgroup, method 300 jumps forward to block 320. For example, if data storage controller 102 determines that the received command is requested to apply to all non-volatile memory devices 122 in the block, then data storage controller 102 determines that no subgroup needs to be created. In some embodiments, based on the parameters of the command and the selected non-volatile memory devices 122, data storage controller 102 can select a subgroup according to subgroup data 240.

[0044] However, if the data storage controller 102 determines to create a subgroup based on the selected non-volatile memory devices 122, method 300 proceeds to block 312. In block 312, the data storage controller 102 creates the subgroup based on the selected non-volatile memory devices 122. To this end, in some embodiments, in block 314, the data storage controller 102 may set the device state of each of the selected non-volatile memory devices 122 to a selected state. In some embodiments, in block 316, the data storage controller 102 may clear the read or write command mask bit of each of the selected non-volatile memory devices 122 to zero. In other embodiments, in block 318, the data storage controller 102 may create the subgroup of selected non-volatile memory devices 122 by using identifiers of the selected non-volatile memory devices 122. For example, as discussed above, each non-volatile memory device 122 may include at least three different identifiers for read, write, and refresh or miscellaneous commands. The data storage controller 102 can create a subgroup of the selected non-volatile memory devices 122 for a read command operation by recognizing the read identifier of each of the selected non-volatile memory devices 122. It should be understood that the created subgroups can be stored in subgroup data 240.

[0045] In block 320, the data storage controller 102 issues a received command to the selected non-volatile memory device 122 for execution. In block 322, if the issued command is a read command, the data storage controller 102 reads data from the selected subgroup of non-volatile memory devices 122. In block 324, if the issued command is a write command, the data storage controller 102 writes data to the selected subgroup of non-volatile memory devices 122. In block 326, if the issued command is a refresh read command, the data storage controller 102 reads data from the selected non-volatile memory device 122, regardless of the state of the non-volatile memory device 122 (e.g., selected / deselected device state, read command mask bit state, selected identifier). In block 328, if the issued command is a refresh write command, the data storage controller 102 writes data to the selected non-volatile memory device 122, regardless of the state of the non-volatile memory device 122 (e.g., the selected / deselected device state, the state of the write command mask bits, the selected identifier). It should be understood that, depending on the received command, the selected non-volatile memory device 122 can be a subgroup of non-volatile memory devices 122 in a block or all non-volatile memory devices 122 in a block. Furthermore, it should be understood that while read, write, and refresh commands are described as examples of commands that can be issued to the selected memory device 122, in other embodiments, other commands can be issued to the selected memory device 122.

[0046] Now for reference Figure 4 In use, the data reader 222 of the data storage controller 102 can execute method 400 for reading data from a subgroup of selected non-volatile memory devices 122 in response to receiving a read command. Method 400 begins at block 402, where the data storage controller 102 determines whether a read command has been received from the host 250. If the data reader 222 determines that a read command has not yet been received, method 400 loops back to block 402 to continue waiting for a read command. However, if the data reader 222 determines that a read command has been received, method 400 proceeds to block 404.

[0047] In block 404, data reader 222 determines whether each non-volatile memory device 122 in the block is part of a selected subgroup of non-volatile memory devices 122. To this end, in some embodiments, in block 406, data reader 222 may determine whether a read command mask bit of the non-volatile memory device 122 is cleared (e.g., equal to zero). In such embodiments, if the non-volatile memory device 122 has a cleared read command mask bit, data reader 222 determines that the non-volatile memory device 122 is part of the selected subgroup. In some embodiments, in block 408, data reader 222 may determine whether the device state of the non-volatile memory device 122 is in a selected state. In such embodiments, if the non-volatile memory device 122 is in a selected state, data reader 222 determines that the non-volatile memory device 122 is part of the selected subgroup. In other embodiments, in block 410, data reader 222 may determine whether a read identifier of nonvolatile memory device 122 matches one of the selected identifiers indicated in a read command. In such an embodiment, if the read identifier of nonvolatile memory device 122 matches one of the selected identifiers, data reader 222 determines that nonvolatile memory device 122 is part of the selected subgroup.

[0048] If, in block 412, data reader 222 determines that non-volatile memory device 122 is part of the selected subgroup, method 400 proceeds to block 414 to read data from non-volatile memory device 122. However, if, in block 412, data reader 222 determines that non-volatile memory device 122 is not part of the selected subgroup, method 400 loops back to block 402 to continue waiting for another read command. It should be understood that, in the illustrative embodiment, method 400 is executed concurrently for each memory device 122 in the block.

[0049] Now for reference Figure 5 In use, the data writer 224 of the data storage controller 102 can execute method 500 for writing data to a subgroup of selected non-volatile memory devices 122 in response to receiving a write command. Method 500 begins at block 502, where the data storage controller 102 determines whether a write command has been received from the host 250. If the data writer 224 determines that a write command has not yet been received, method 500 loops back to block 502 to continue waiting for a write command. However, if the data writer 224 determines that a write command has been received, method 500 proceeds to block 504.

[0050] In block 504, data writer 224 determines whether each non-volatile memory device 122 in the block is part of a selected subgroup of non-volatile memory devices 122. To this end, in some embodiments, in block 506, data writer 224 may determine whether a write command mask bit for a given non-volatile memory device 122 is cleared (e.g., equal to zero). In such embodiments, if a non-volatile memory device 122 has a cleared write command mask bit, data writer 224 determines that the non-volatile memory device 122 is part of a selected subgroup. In some embodiments, in block 508, data writer 224 may determine whether the device state of the non-volatile memory device 122 is in a selected state. In such embodiments, if the non-volatile memory device 122 is in a selected state, data writer 224 determines that the non-volatile memory device 122 is part of a selected subgroup. In other embodiments, in block 510, data writer 224 may determine whether the write identifier of non-volatile memory device 122 matches one of the selected identifiers indicated in the write command. In such an embodiment, if the write identifier of non-volatile memory device 122 matches one of the selected identifiers, then data writer 224 determines that non-volatile memory device 122 is part of the selected subgroup.

[0051] If, in block 512, data writer 224 determines that non-volatile memory device 122 is part of the selected subgroup, method 500 proceeds to block 514 to write data to non-volatile memory device 122. However, if, in block 512, data writer 224 determines that non-volatile memory device 122 is not part of the selected subgroup, method 500 loops back to block 502 to continue waiting for another write command. It should be understood that, in the illustrative embodiment, method 500 is executed concurrently for each memory device 122 in the block.

[0052] Now for reference Figure 6 In some embodiments, the data storage device 100 may be incorporated into or form part of the computing device 600. The computing device 600 may be embodied in any type of computing device in which the data storage device 100 can be used. For example, the computing device 600 may be embodied in a smartphone, tablet computer, notebook computer, laptop computer, netbook, or ultrabook. TM Wearable computing devices, smart glasses, head-mounted computing devices, cellular phones, desktop computers, smart devices, personal digital assistants, mobile internet devices, servers, data storage devices, and / or any other computing / communication devices. Figure 6The illustrative computing device 600 shown includes a processor 610, an input / output (“I / O”) subsystem 612, and a main memory 614. It should be recognized that in some embodiments, the computing device 600 may include other or additional components, such as a peripheral device 620, or in other embodiments, components typically found in typical computing devices (e.g., various input / output devices and / or other components). Furthermore, in some embodiments, one or more of the illustrative components may be incorporated into another component, or otherwise form part of another component. For example, in some embodiments, memory 614 or a portion thereof may be incorporated into processor 610.

[0053] Processor 610 may be embodied as any type of processor capable of performing the functions described herein. For example, processor 610 may be embodied as a single-core or multi-core processor, a digital signal processor, a microcontroller, or other processor or processing / control circuitry. Similarly, memory 614 may be embodied as any type of volatile or non-volatile memory or data storage device capable of performing the functions described herein. In operation, memory 614 may store various data and software used during the operation of computing device 600, such as operating systems, applications, programs, libraries, and drivers. Memory 614 is communicatively coupled to processor 610 via I / O subsystem 612, which may be embodied as circuitry and / or components for facilitating input / output operations with processor 610, memory 614, and other components of computing device 600. For example, the I / O subsystem 612 may be embodied as or otherwise include a memory controller hub, an input / output control hub, firmware devices, communication links (i.e., point-to-point links, bus links, wires, cables, light guides, printed circuit board traces, etc.) and / or other components and subsystems for facilitating input / output operations.

[0054] like Figure 6As shown, data storage device 100 may be incorporated into or form part of one or more other components of computing device 600. For example, data storage device 100 may be embodied in main memory 614 or otherwise included in main memory 614. Additionally or alternatively, data storage device 100 may be embodied in or otherwise included in solid-state drive 618 of computing device 600. Furthermore, in some embodiments, data storage device 100 may be embodied in or otherwise included in hard disk drive 616 of computing device 600. Of course, in other embodiments, data storage device 100 may be incorporated into or form part of other components of computing device 600.

[0055] References to memory devices can be applied to different memory types, and in particular, to any memory with a bank architecture. Memory devices generally refer to volatile memory technology. Volatile memory is memory whose state (and therefore the data stored in it) is indeterminate if power to the device is interrupted. Non-volatile memory is memory whose state is deterministic even if power to the device is interrupted. Dynamically volatile memory requires the data stored in the device to be refreshed to maintain its state. An example of dynamically volatile memory includes DRAM (Dynamic Random Access Memory), or certain variants such as Synchronous DRAM (SDRAM). The memory subsystem described herein is compatible with many memory technologies, such as DDR4 (DDR version 4, initial specification published by JEDEC in September 2012), DDR4E (under development by JEDEC), LPDDR4 (Low Power Double Data Rate (LPDDR) version 4, JESD209-4, initially published by JEDEC in August 2014), WIO2 (WideIO2, JESD229-2, initially published by JEDEC in August 2014), HBM (High Bandwidth DRAM, JESD235, initially published by JEDEC in October 2013), DDR5 (DDR version 5, currently under discussion by JEDEC), LPDDR5 (currently under discussion by JEDEC), HBM2 (HBM version 2, currently under discussion by JEDEC), and / or others, as well as technologies derived from and extended based on such specifications.

[0056] In one embodiment, in addition to or as an alternative to volatile memory, a reference to a memory device may refer to a non-volatile memory device whose state remains deterministic even when power to the device is interrupted.

[0057] Example

[0058] The following provides illustrative examples of the techniques disclosed herein. Embodiments of the techniques may include any one or more of the examples described below, and any combination thereof.

[0059] Example 1 includes an apparatus comprising a plurality of non-volatile, in-bit write, byte- or block-addressable memory devices, wherein the memory devices are arranged in one or more blocks and the memory devices in each block are connected to the same communication channel; and a data storage controller for selecting a subgroup of the plurality of memory devices in the block without modifying the identifier of each memory device, wherein there is more than one subgroup and fewer than all of the memory devices; and issuing commands to operate on the data of the selected subgroup.

[0060] Example 2 includes the subject of Example 1, and wherein issuing a command includes issuing a read command to read data from a selected subgroup of multiple memory devices in the block.

[0061] Example 3 includes the subject of either Example 1 or 2, and wherein issuing a command includes issuing a write command to write data to a selected subgroup of multiple memory devices in the block.

[0062] Example 4 includes the subject of any one of Examples 1-3, and wherein selecting a subgroup includes selecting a subgroup consisting of nine items in the memory device; and issuing a command includes issuing a read command.

[0063] Example 5 includes the subject of any one of Examples 1-4, and wherein selecting a subgroup includes selecting a subgroup consisting of ten memory devices; and issuing a command includes issuing a write command.

[0064] Example 6 includes the subject of any one of Examples 1-5, and wherein the data storage controller is further configured to select all of the memory devices in the block; and issue refresh commands to all of the memory devices in the block.

[0065] Example 7 includes the subject of any one of Examples 1-6, and wherein issuing a refresh command includes issuing a refresh read command to read all data from the memory device in the block.

[0066] Example 8 includes the subject of any one of Examples 1-7, and wherein issuing a refresh command includes issuing a refresh write command to write all data to the memory device in the block.

[0067] Example 9 includes the subject of any one of Examples 1-8, and wherein selecting a subgroup of multiple memory devices in a block includes setting the device state of one or more memory devices to a selected state.

[0068] Example 10 includes the subject of any one of Examples 1-9, and wherein selecting a subgroup of multiple memory devices in a block includes clearing the read command mask bits of one or more memory devices in the block.

[0069] Example 11 includes the subject of any one of Examples 1-10, and wherein selecting a subgroup of multiple memory devices in a block includes clearing the write command mask bits of one or more memory devices in the block.

[0070] Example 12 includes the subject of any one of Examples 1-11, and wherein the data storage controller is further configured to set the read command mask bit of one or more memory devices in the block to be blocked by one or more read commands from the memory devices.

[0071] Example 13 includes the subject of any one of Examples 1-12, and wherein the data storage controller is further configured to set the write command mask bit of one or more memory devices in the block to be blocked by one or more write commands from the memory devices.

[0072] Example 14 includes the subject of any one of Examples 1-13, and wherein selecting a subgroup includes selecting an initial memory device for the subgroup by sending the selection of an identifier of a memory device to the memory device; and issuing at least one command to add the identifier of one or more memory devices to the subgroup.

[0073] Example 15 includes the subject of any one of Examples 1-14, and wherein the data storage controller is further configured to issue a command to remove at least one memory device from the subgroup, wherein the command includes the identifier of one or more memory devices in the subgroup.

[0074] Example 16 includes the subject of any one of Examples 1-15, and wherein the data storage controller is further configured to issue a second command to the subgroup after one or more memory devices have been removed from the subgroup.

[0075] Example 17 includes the subject of any one of Examples 1-16, and wherein two identifiers are assigned to each memory device, and the selection of subgroups includes assigning additional identifiers to each memory device without modifying one or more current identifiers of each memory device.

[0076] Example 18 includes a method comprising selecting a subgroup of a plurality of memory devices in a block by a data storage controller without modifying the identifier of each memory device, wherein the plurality of memory devices are non-volatile, bit-write, byte- or block-addressable memory devices arranged in one or more blocks, the memory devices in each block being connected to the same communication channel, and the subgroup being more than one and less than all of the memory devices; and issuing a command by the data storage controller to operate on the data of the selected subgroup.

[0077] Example 19 includes the subject of Example 18, and wherein issuing a command includes issuing a read command by a data storage controller to read data from a selected subgroup of a plurality of storage devices in a block.

[0078] Example 20 includes the subject of any one of Examples 18 and 19, and wherein issuing a command includes issuing a write command by a data storage controller to write data to a selected subgroup of a plurality of storage devices in the block.

[0079] Example 21 includes the subject of any one of Examples 18-20, and wherein selecting a subgroup includes selecting a subgroup consisting of nine devices in the memory device by the data storage controller; and issuing a command includes issuing a read command by the data storage controller.

[0080] Example 22 includes the subject of any one of Examples 18-21, and wherein selecting a subgroup includes selecting a subgroup consisting of ten memory devices by the data storage controller; and issuing a command includes issuing a write command by the data storage controller.

[0081] Example 23 includes the subject of any one of Examples 18-22, and further includes the selection of all memory devices in the block by the data storage controller; and the issuance of refresh commands to all memory devices in the block by the data storage controller.

[0082] Example 24 includes the subject of any one of Examples 18-23, and wherein issuing a refresh command includes issuing a refresh read command by the data storage controller to read all data from the memory devices in the block.

[0083] Example 25 includes the subject of any one of Examples 18-24, and wherein issuing a refresh command includes issuing a refresh write command by the data storage controller to write all the data to the memory device in the block.

[0084] Example 26 includes the subject of any one of Examples 18-25, and wherein a subgroup of multiple memory devices in a selection block includes setting the device state of one or more memory devices to a selection state by a data storage controller.

[0085] Example 27 includes the subject of any one of Examples 18-26, and wherein selecting a subgroup of multiple memory devices in a block includes clearing the read command mask bits of one or more memory devices in the block by the data storage controller.

[0086] Example 28 includes the subject of any one of Examples 18-27, and wherein selecting a subgroup of multiple memory devices in a block includes clearing write command mask bits of one or more memory devices in the block by the data storage controller.

[0087] Example 29 includes the subject of any one of Examples 18-28, and further includes setting read command mask bits of one or more memory devices in the block by the data storage controller to block read commands from one or more memory devices.

[0088] Example 30 includes the subject of any one of Examples 18-29, and further includes setting write command mask bits of one or more memory devices in the block by the data storage controller to allow one or more blocking write commands from the memory devices.

[0089] Example 31 includes the subject of any one of Examples 18-30, and wherein selecting a subgroup includes selecting an initial memory device for the subgroup by the data storage controller sending the selection of an identifier of a memory device to the memory device; and the data storage controller issues at least one command to add one or more identifiers of the memory devices to the subgroup.

[0090] Example 32 includes the subject of any one of Examples 18-31, and further includes a command issued by a data storage controller to remove at least one memory device from a subgroup, wherein the command includes identifiers of one or more memory devices in the subgroup.

[0091] Example 33 includes the subject of any one of Examples 18-32, and further includes that, after one or more memory devices have been removed from the subgroup, a second command is issued by the data storage controller to the subgroup.

[0092] Example 34 includes the subject of any one of Examples 18-33, and wherein each memory device is assigned two identifiers, and the selection of subgroups includes assigning additional identifiers to each memory device by the data storage controller without modifying one or more current identifiers of each memory device.

[0093] Example 35 includes one or more machine-readable storage media including a plurality of instructions stored thereon, which, when executed, cause the device to perform the method of any one of Examples 18-34.

[0094] Example 36 includes an apparatus comprising a unit for selecting a subgroup of a plurality of memory devices in a block without modifying the identifier of each memory device, wherein the plurality of memory devices are non-volatile, in-bit write, byte or block addressable memory devices arranged in one or more blocks, the memory devices in each block being connected to the same communication channel, and the subgroup being more than one and less than all of the memory devices; and a unit for issuing commands to operate on data of the selected subgroup.

[0095] Example 37 includes the subject of Example 36, and wherein the unit for issuing commands includes a unit for issuing read commands to read data from a selected subgroup of a plurality of memory devices in the block.

[0096] Example 38 includes the subject of any one of Examples 36 and 37, and wherein the unit for issuing commands includes a unit for issuing write commands to write data to a selected subgroup of a plurality of memory devices in the block.

[0097] Example 39 includes the subject of any one of Examples 36-38, and wherein the unit for selecting a subgroup includes a unit for selecting a subgroup consisting of nine items in the memory device; and the unit for issuing a command includes a unit for issuing a read command.

[0098] Example 40 includes the subject of any one of Examples 36-39, and wherein the unit for selecting a subgroup includes a unit for selecting a subgroup consisting of ten items in the memory device; and the unit for issuing a command includes a unit for issuing a write command.

[0099] Example 41 includes the subject of any one of Examples 36-40, and further includes a unit for selecting all cells in the memory devices in the block; and a unit for issuing refresh commands to all cells in the memory devices in the block.

[0100] Example 42 includes the subject of any one of Examples 36-41, and wherein the unit for issuing a refresh command includes a unit for issuing a refresh read command to read data from all the memory devices in the block.

[0101] Example 43 includes the subject of any one of Examples 36-42, and wherein the unit for issuing a refresh command includes a unit for issuing a refresh write command to write data to all memory devices in the block.

[0102] Example 44 includes the subject of any one of Examples 36-43, and wherein the unit for selecting a subgroup of multiple memory devices in a block includes a unit for setting the device state of one or more memory devices to a selected state.

[0103] Example 45 includes the subject of any one of Examples 36-44, and wherein the unit for selecting a subgroup of multiple memory devices in a block includes a unit for clearing the read command mask bits of one or more memory devices in the block.

[0104] Example 46 includes the subject of any one of Examples 36-45, and wherein the unit for selecting a subgroup of multiple memory devices in a block includes a unit for clearing write command mask bits of one or more memory devices in the block.

[0105] Example 47 includes the subject matter of any one of Examples 36-46, and further includes a unit for setting a read command mask bit for one or more memory devices in the block to block read commands from one or more memory devices.

[0106] Example 48 includes the subject matter of any one of Examples 36-47, and further includes a unit for setting write command mask bits of one or more memory devices in the block to block write commands from one or more memory devices.

[0107] Example 49 includes the subject of any one of Examples 36-48, and wherein the unit for selecting a subgroup includes a unit for selecting an initial memory device of the subgroup by sending the selection of an identifier of a memory device to the memory device; and a unit for issuing at least one command to add an identifier of one or more memory devices to the subgroup.

[0108] Example 50 includes the subject matter of any one of Examples 36-49, and further includes a unit for issuing a command to remove at least one memory device from a subgroup, wherein the command includes identifiers of one or more memory devices in the subgroup.

[0109] Example 51 includes the subject of any one of Examples 36-50, and further includes a unit for issuing a second command to the subgroup after one or more memory devices have been removed from the subgroup.

[0110] Example 52 includes the subject of any one of Examples 36-51, and wherein each memory device is assigned two identifiers, and the unit for selecting a subgroup includes a unit for assigning an additional identifier to each memory device without modifying one or more current identifiers of each memory device.

Claims

1. An apparatus for accessing a memory device, comprising: Data storage controller, used for: At least a portion of the memory devices in a block is selected based on one of at least two identifiers, said at least two identifiers being assigned to all memory devices of the selected at least portion of the memory devices, wherein the memory devices in the block include non-volatile, byte- or block-addressable memories connected to the same communication channel, and wherein said at least two identifiers include a first identifier and a second identifier, the first identifier indicating that the selected at least portion of the memory devices will be accessed in response to a read command, and the second identifier indicating that the selected at least portion of the memory devices will be accessed in response to a write command, and wherein the selected at least portion of the memory devices includes a subgroup of memory devices in the block; and wherein said subgroup is selected based on either the first identifier or the second identifier; and Issue a command to access at least a selected portion of the memory device.

2. The apparatus of claim 1, wherein, The at least two identifiers also include: A third identifier indicates that, in response to a refresh command, at least a selected portion of the memory device will be accessed.

3. The apparatus of claim 2, wherein, The selected memory devices include at least a portion of all memory devices in the block.

4. The apparatus of claim 3, wherein, Commands for accessing all memory devices in the block include refresh commands, which include the third identifier.

5. The apparatus of claim 1, wherein, The subgroup is more than one but less than all the memory devices in the block.

6. The apparatus of claim 1, wherein, Commands for accessing a subgroup of memory devices in the block include write commands, the write commands including the second identifier.

7. The apparatus of claim 1, wherein, Commands for accessing a subgroup of memory devices in the block include refresh commands, which include the third identifier.

8. The apparatus of claim 1, wherein, Commands for accessing a subgroup of memory devices in the block include read commands, the read commands including the first identifier.

9. The apparatus of claim 1, wherein, The selection of memory devices includes at least a second subgroup of memory devices in the block, the second subgroup being selected based on the first identifier, and the second subgroup of memory devices being more than one and equal to N-2 memory devices in the block, where "N" represents the total number of memory devices in the block.

10. The apparatus of claim 9, wherein, The command for accessing the second subgroup of the memory devices in the block includes a read command, which includes the first identifier.

11. The apparatus of claim 1, wherein, After the memory devices in the block are initialized, the at least two identifiers are assigned to the memory devices in the block.

12. The apparatus of claim 1, wherein, Non-volatile, byte- or block-addressable memories include phase change memories using chalcogenide phase change materials, ferroelectric polymer memories, ferroelectric random access memories (FeTRAM), nanowire-based memories, phase change memories incorporating memristors, magnetoresistive random access memories (MRAM), or spin-transfer torque (STT)-MRAM.

13. A method for accessing a memory device, comprising: A data storage controller selects at least a portion of memory devices in a block based on one of at least two identifiers, said at least two identifiers being assigned to all memory devices in the selected at least portion of the memory devices, wherein the memory devices in the block comprise non-volatile, byte- or block-addressable memories connected to the same communication channel, and wherein said at least two identifiers include a first identifier and a second identifier, the first identifier indicating that the selected at least portion of the memory devices will be accessed in response to a read command, and the second identifier indicating that the selected at least portion of the memory devices will be accessed in response to a write command, and wherein the selected at least portion of the memory devices comprises a subgroup of memory devices in the block; and wherein said subgroup is selected based on either the first identifier or the second identifier; and Issue a command to access at least a selected portion of the memory device.

14. The method of claim 13, wherein, The at least two identifiers also include: A third identifier indicates that, in response to a refresh command, at least a selected portion of the memory device will be accessed.

15. The method of claim 14, wherein, The selected memory devices include at least a portion of all memory devices in the block.

16. The method of claim 13, wherein, The subgroup is more than one but less than all the memory devices in the block.

17. The method of claim 13, wherein, The selection of memory devices includes at least a second subgroup of memory devices in the block, the second subgroup being selected based on the first identifier, and the second subgroup of memory devices being more than one and equal to N-2 memory devices in the block, where "N" represents the total number of memory devices in the block.

18. The method of claim 13, comprising: After initializing the memory devices in the block, the at least two identifiers are assigned to the memory devices in the block.

19. At least one machine-readable medium comprising a plurality of instructions, said plurality of instructions causing the system to perform the method according to any one of claims 13 to 18 in response to execution by the system.

20. An apparatus for accessing a memory device, comprising a unit for performing the method according to any one of claims 13 to 18.

Citation Information

Patent Citations

  • Memory Signal Buffers and Modules Supporting Variable Access Granularity

    US20130036273A1

  • Systems and methods for refreshing a memory module

    US8264903B1