Data storage device and method for hiding adjustment generation latency
By processing adjustment value generation and data reading in parallel in the controller of the data storage device, the problem of large wait time overhead during the AES-XTS decryption process is solved, the decryption efficiency of the data storage device is improved, and the waiting time is significantly reduced. .
Patent Information
- Application Number
- CN202410014025.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-07-19
- Filing Date
- 2024-01-04
- Publication Date
- 2024-11-05
AI Technical Summary
Existing data storage devices have high waiting time when decrypting encrypted data, which affects data reading efficiency. Especially when using the AES-XTS decryption algorithm, there is a large waiting time overhead in the generation of adjustment values and data decryption.
By in the controller of the data storage device, the adjustment value generation process and the data reading process are carried out in parallel, and the waiting time generated by the adjustment value is hidden in the data reading waiting time, thereby sending the encrypted data and adjustment values to the decryption engine at the same time. Reduce decryption waiting time.
Effectively reduce the waiting time during the AES-XTS decryption process, reduce the overall read waiting time, and improve the decryption efficiency of data storage devices. Specifically, it reduces the decryption waiting time by half, accounting for 28% of the total waiting time. 56% lower.
Smart Images

Figure CN118898089A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 461,953, filed on April 26, 2023, which is hereby incorporated by reference into this application. Background Art
[0003] The data storage device may have a security engine to perform encryption and decryption of data. An example of a cryptographic algorithm that may be used by the security engine is AES-XTS, which refers to the Advanced Encryption Standard (AES) cipher using an XOR-encrypted XOR (XEX) tunable block cipher (XTS) with ciphertext stealing. In AES-XTS, two keys are used, one key for performing the AES block encryption and the other key for encrypting the "tuning value". BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Figure 1A is a block diagram of a data storage device according to an embodiment.
[0005] Figure 1B is a block diagram illustrating a storage module according to one embodiment.
[0006] Figure 1C is a block diagram illustrating a hierarchical storage system according to one embodiment.
[0007] Figure 2A It is shown that according to one embodiment Figure 1A A block diagram of components of a controller of a data storage device is shown.
[0008] Figure 2B It is shown that according to one embodiment Figure 1A A block diagram of components of a memory data storage device is shown.
[0009] Figure 3 is a block diagram of a host and a data storage device according to an embodiment.
[0010] Figure 4 is a flow chart of a method of one embodiment for decrypting data using an AES-XTS decryption algorithm.
[0011] Figure 5 is a block diagram of a data storage device according to an embodiment.
[0012] Figure 6 is a graph comparing decryption latency to the total read latency budget.
[0013] Figure 7 is a block diagram of a data storage device according to an embodiment.
[0014] Figure 8 is a graph comparing decryption latency to the total read latency budget.
[0015] Fig. 9 is a diagram of a media interface of a media controller according to one embodiment.
[0016] Fig.10 is a diagram of a media interface of a media controller, wherein the media interface includes a first-in-first-out buffer, according to one embodiment.
[0017] Fig.11 is a diagram of a media interface of a media controller according to an embodiment, wherein the media interface includes a data bus occupancy recorder.
[0018] Fig.12 is a diagram of a data bus occupancy recorder according to one embodiment.
[0019] Fig.13 is a flow chart of a method of one embodiment for issuing an adjustment generation request when updating a data bus occupancy register in response to an issued read command.
[0020] Fig.14 is a flow chart of a method of one embodiment for setting an adjustment vector when updating a data bus occupancy register based on an issued read command.
[0021] Fig.15 is a diagram of a data occupancy recorder according to one embodiment.
[0022] Fig.16 is a flow diagram of a method of one embodiment for returning encrypted data read from memory. DETAILED DESCRIPTION
[0023] The following embodiments generally relate to a data storage device and method for hiding an adjusted generation latency. In one embodiment, a data storage device is provided, the data storage device comprising: a memory; a decryption engine; and a controller coupled to the memory and the decryption engine, wherein the controller is configured to: receive a read request including an address; read encrypted data from the memory, wherein the encrypted data is read from a location in the memory associated with the address; while the encrypted data is being read from the memory, generate a value required to decrypt the encrypted data, wherein the value is generated at least in part from the address; and send the encrypted data and the generated value to the decryption engine to decrypt the data.
[0024] In another embodiment, a method is provided, the method being performed in a memory controller in a data storage device including a memory and an AES-XTS decryption engine. The method includes: generating an adjustment value from a read address during a time when encrypted data is being read from a location associated with the read address in the memory; and sending the adjustment value and the encrypted data to the AES-XTS decryption engine.
[0025] In another embodiment, a data storage device is provided that includes a memory and means for reducing latency when decrypting encrypted data read from the memory by hiding latency for calculating a value used to decrypt the encrypted data within latency for reading the encrypted data from the memory.
[0026] Other embodiments are possible, and each of the embodiments may be used alone or in combination.Therefore, various embodiments will now be described with reference to the drawings.
[0027] Implementation
[0028] The following embodiments relate to a data storage device (DSD). As used herein, a "data storage device" refers to a device that stores data. Examples of DSDs include, but are not limited to, hard disk drives (HDDs), solid-state drives (SSDs), tape drives, hybrid drives, and the like. Details of an example DSD are provided below.
[0029] exist Figures 1A to 1C A data storage device suitable for implementing aspects of these embodiments is shown in FIG. Figure 1A is a block diagram illustrating a data storage device 100 according to one embodiment of the subject matter described herein. Figure 1A , the data storage device 100 includes a controller 102 and a non-volatile memory that may be composed of one or more non-volatile memory dies 104. As described herein, the term die refers to a collection of non-volatile memory cells formed on a single semiconductor substrate, and associated circuits for managing the physical operations of those non-volatile memory cells. The controller 102 interacts with a host system and transmits command sequences for read operations, program operations, and erase operations to the non-volatile memory dies 104.
[0030] The controller 102 (which may be a non-volatile memory controller (e.g., a flash memory, a resistive random access memory (ReRAM), a phase change memory (PCM), or a magnetoresistive random access memory (MRAM) controller)) may take the form of, for example, a processing circuit, a microprocessor or processor, and a computer-readable medium storing computer-readable program code (e.g., firmware) executable by a (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. The controller 102 may be configured with hardware and / or firmware to perform the various functions described below and shown in the flow charts. In addition, some components shown as being internal to the controller may also be stored external to the controller, and other components may be used. Furthermore, the phrase "operably communicating with" may mean communicating directly or indirectly (wired or wirelessly) with, communicating through, one or more components, which may or may not be shown herein.
[0031] As used herein, a nonvolatile memory controller is a device that manages data stored on a nonvolatile memory and communicates with a host such as a computer or electronic device. In addition to the specific functions described herein, a nonvolatile memory controller can have various functions. For example, a nonvolatile memory controller can format a nonvolatile memory to ensure that the memory is operating correctly, mark bad nonvolatile memory cells, and allocate spare cells to replace future faulty cells. Some parts in the spare cells can be used to accommodate firmware to operate the nonvolatile memory controller and implement other features. In operation, when the host needs to read data from the nonvolatile memory or write data to the nonvolatile memory, it can communicate with the nonvolatile memory controller. If the host provides a logical address to read / write data, the nonvolatile memory controller can convert the logical address received from the host into a physical address in the nonvolatile memory. (Alternatively, the host can provide the physical address.) The nonvolatile memory controller may also perform various memory management functions such as, but not limited to, wear leveling (distributing writes to avoid wearing out specific memory blocks that would otherwise be written repeatedly) and garbage collection (moving only valid data pages to new blocks after a block is full so the complete block can be erased and reused).
[0032] The non-volatile memory die 104 may include any suitable non-volatile storage medium, including resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), phase change memory (PCM), NAND flash memory cells, and / or NOR flash memory cells. The memory cells may be in the form of solid-state (e.g., flash) memory cells, and may be programmable once, programmable a few times, or programmable multiple times. The memory cells may also be single-level cells (SLC), multi-level cells (MLC) (e.g., dual-level cells, triple-level cells (TLC), quad-level cells (QLC), etc.), or use other memory cell level technologies now known or later developed. In addition, the memory cells may be manufactured in two dimensions or in three dimensions.
[0033] The interface between the controller 102 and the non-volatile memory die 104 may be any suitable flash memory interface, such as switch mode 200, 400, or 800. In one embodiment, the data storage device 100 may be a card-based system, such as a secure digital card (SD) or a micro secure digital (micro SD) card. In an alternative embodiment, the data storage device 100 may be part of an embedded data storage device.
[0034] Although in Figure 1A In the example shown, data storage device 100 (sometimes referred to herein as a memory module) includes a single channel between controller 102 and non-volatile memory die 104, but the subject matter described herein is not limited to having a single memory channel. For example, in some memory system architectures (such as Figure 1B and Figure 1C In the architecture shown in ), there may be 2, 4, 8 or more memory channels between the controller and the memory device depending on the capabilities of the controller. In any of the embodiments described herein, even if a single channel is shown in the drawings, there may be more than one single channel between the controller and the memory die.
[0035] Figure 1B A storage module 200 including a plurality of non-volatile data storage devices 100 is shown. Thus, the storage module 200 may include a storage controller 202 that interacts with a host and a data storage device 204 including a plurality of data storage devices 100. The interface between the storage controller 202 and the data storage device 100 may be a bus interface such as a Serial Advanced Technology Attachment (SATA), a Peripheral Component Interconnect Express (PCIe) interface, or a Double Data Rate (DDR) interface. In one embodiment, the storage module 200 may be a solid state drive (SSD) or a non-volatile dual in-line memory module (NVDIMM) such as found in a server PC or a portable computing device such as a laptop computer and a tablet computer.
[0036] Figure 1C 2 is a block diagram illustrating a hierarchical storage system. Hierarchical storage system 250 includes a plurality of storage controllers 202, each of which controls a corresponding data storage device 204. A host system 252 can access memory within storage system 250 via a bus interface. In one embodiment, the bus interface can be a non-volatile memory express (NVMe) or Fibre Channel over Ethernet (FCoE) interface. In one embodiment, Figure 1C The system shown may be a rack-mountable mass storage system that can be accessed by multiple host computers, such as might be found in a data center or in other locations where mass storage is needed.
[0037] Figure 2A 1 is a block diagram illustrating exemplary components of the controller 102 in greater detail. The controller 102 includes a front-end module 108 that interacts with a host, a back-end module 110 that interacts with one or more non-volatile memory dies 104, and various other modules that perform functions that will now be described in detail. A module may take the form of, for example, a packaged functional hardware unit designed for use with other components, a portion of a program code (e.g., software or firmware) that can be executed by a (micro)processor or processing circuit that typically performs a specific one of the related functions, or an independent hardware or software component that interacts with a larger system. In addition, a "means" for performing a function may be implemented with at least any structure for a controller described herein, and may be pure hardware or a combination of hardware and computer-readable program code.
[0038] Referring again to the modules of controller 102, buffer management / bus controller 114 manages buffers in random access memory (RAM) 116 and controls internal bus arbitration of controller 102. Read only memory (ROM) 118 stores system boot code. Figure 2A Shown as being located separately from the controller 102, but in other embodiments, one or both of the RAM 116 and ROM 118 may be located within the controller. In still other embodiments, portions of the RAM and ROM may be located within the controller 102 and external to the controller.
[0039] The front-end module 108 includes a host interface 120 and a physical layer interface (PHY) 122 that provide an electrical interface with a host or a next-level storage controller. The type of host interface 120 can be selected depending on the type of memory used. Examples of host interface 120 include, but are not limited to, SATA, SATA Express, Serial Attached Small Computer System Interface (SAS), Fibre Channel, Universal Serial Bus (USB), PCIe, and NVMe. The host interface 120 is generally useful for transmitting data, control signals, and timing signals.
[0040] The back-end module 110 includes an error correction code (ECC) engine 124 that encodes data bytes received from the host and decodes and error corrects data bytes read from the non-volatile memory. A command sequencer 126 generates command sequences, such as a program command sequence and an erase command sequence, for transmission to the non-volatile memory die 104. A RAID (Redundant Array of Independent Drives) module 128 manages the generation of RAID parity and the recovery of failed data. RAID parity can be used as an additional level of integrity protection for data written to the memory device 104. In some cases, the RAID module 128 can be part of the ECC engine 124. The memory interface 130 provides command sequences to the non-volatile memory die 104 and receives status information from the non-volatile memory die 104. In one embodiment, the memory interface 130 can be a double data rate (DDR) interface, such as a switching mode 200, 400 or 800 interface. The flash control layer 132 controls the overall operation of the back-end module 110.
[0041] The data storage device 100 also includes other discrete components 140, such as external electrical interfaces, external RAM, resistors, capacitors, or other components that can interact with the controller 102. In alternative embodiments, one or more of the physical layer interface 122, the RAID module 128, the media management layer 138, and the buffer management / bus controller 114 are optional components that are not required in the controller 102.
[0042] Figure 2B1 is a block diagram showing components of the nonvolatile memory die 104 in more detail. The nonvolatile memory die 104 includes peripheral circuits 141 and a nonvolatile memory array 142. The nonvolatile memory array 142 includes nonvolatile memory cells for storing data. The nonvolatile memory cells may be any suitable nonvolatile memory cells, including ReRAM, MRAM, PCM, NAND flash memory cells, and / or NOR flash memory cells in a two-dimensional configuration and / or a three-dimensional configuration. The nonvolatile memory die 104 also includes a data cache 156 for caching data. The peripheral circuits 141 include a state machine 152 that provides status information to the controller 102.
[0043] Return again Figure 2A , the flash control layer 132 (which will be referred to herein as the flash translation layer (FTL), or more generally as the "media management layer" since the memory may not be flash) handles flash errors and interacts with the host. Specifically, the FTL (which may be an algorithm in firmware) is responsible for the internals of memory management and converts writes from the host to writes to the memory 104. The FTL may be needed because the memory 104 may have limited endurance, may only write to multiple pages, and / or may not be written to (unless it is erased as a block). The FTL understands these potential limitations of the memory 104, which may not be visible to the host. Therefore, the FTL attempts to convert writes from the host to writes into the memory 104.
[0044] The FTL may include a logical to physical address (L2P) mapping (sometimes referred to herein as a table or data structure) and an allocated cache memory. Thus, the FTL converts a logical block address ("LBA") from the host to a physical address in memory 104. The FTL may include other features such as, but not limited to, power failure recovery (so that the FTL's data structures can be recovered in the event of a sudden power loss) and wear leveling (so that wear across memory blocks is even to prevent certain blocks from being overly worn, which would result in a greater chance of failure).
[0045] Returning to the attached figure, Figure 3300 and data storage device 100 of one embodiment. Host 300 can take any suitable form, including but not limited to a computer, a mobile phone, a tablet computer, a wearable device, a digital video recorder, a monitoring system, etc. In this embodiment, host 300 (here, a computing device) includes a processor 330 and a memory 340. In one embodiment, the computer readable program code stored in the host memory 340 configures the host processor 330 to perform the actions described herein. Therefore, the actions performed by the host 300 are sometimes referred to as being performed by an application (computer readable program code) running on the host 300 in this article. For example, the host 300 can be configured to send data (e.g., initially stored in the host's memory 340) to the data storage device 100 for storage in the memory 104 of the data storage device.
[0046] In one embodiment, the data storage device 100 includes a security engine that is separate from the controller 102 (but can be controlled by the controller) and is configured to perform encryption and / or decryption of data stored in the memory 104 of the data storage device 100. The security engine will sometimes be referred to as a decryption engine in this article, but it should be understood that the security engine can also perform encryption (alternatively, a separate encryption engine can be used). The security engine can be implemented in any suitable manner. In one embodiment, the security engine includes an arithmetic logic unit (ALU) configured to perform cryptographic processing according to one or more cryptographic algorithms. Any suitable cryptographic algorithm can be used.
[0047] In one embodiment, the security engine includes an ALU configured to perform encryption and decryption according to the Advanced Encryption Standard (AES) established by the National Institute of Standards and Technology (NIST). The AES ALU may include a control circuit and an AES cryptographic core. The AES core may be configured to cryptographically process data blocks of a set block size (such as 128 bits). In order to encrypt data larger than the set block size, AES may use a block cipher mode, such as XTS. XTS stands for "XEX tunable block cipher with ciphertext misappropriation", where XEX stands for "XOR encrypted XOR". Generally speaking, AES is a block cipher, and XTS is a block cipher mode using two AES keys, one key is used to perform AES block encryption, and the other key is used to encrypt an "adjustment value", which can be used to update the encryption mechanism for each data block encrypted in a block sequence. In the AES-XTS standard, the adjustment value is a 128-bit element in a Galois field (GF).
[0048] Data encrypted using AES-XTS is effectively double-encrypted using two independent keys, and the security engine performs the reverse process of decrypting the data. Figure 4As shown in flowchart 400 in FIG. 1 , the reverse process may include an adjustment generation phase 410 and a data decryption phase 420. In the adjustment generation phase 410, the adjustment generator generates an adjustment value from an adjustment key and a logical block address and / or tag of data retrieved from memory 104. In the data decryption phase 420, the encrypted data, the data key for the data, and the adjustment value are provided to a decryption engine that outputs decrypted data. It is desirable to perform these two phases sequentially because the second phase requires an adjustment value that is a result of the first phase. As shown in FIG. Figure 4 As indicated in , each of these phases 410, 420 is associated with the same latency (e.g., 14-16 cycles with a 2Ghz frequency, totaling 7ns-8ns). In addition to these latencies, there is latency when reading encrypted data from memory 104 ("memory" is sometimes referred to as "medium" hereinafter).
[0049] Figure 5 is a block diagram of some exemplary components of a data storage device according to an embodiment. Figure 5 As shown, these components include media / memory 510 and a media controller 502 including sorting logic 502. In this example, the media 510 includes MRAM, but any suitable type of memory may be used. Since MRAM can be a relatively unreliable form of memory (e.g., compared to NAND), it can benefit from the robustness provided by AES-XTS. Figure 5 The media controller 500 is also shown in communication with an AES-XTS security engine 520, which includes a data decryptor 522, an adjustment generator 524, and triggers 526, 528. Additional / different components may be used. For example, the security engine 520 may also have a data encryptor (or a separate encryption engine may be used). In addition, although the security engine 520 is configured to use AES-XTS in this embodiment, different algorithms are used in other embodiments.
[0050] like Figure 5As shown, the media controller 500 receives a read request from the host 300 having a read address (e.g., a logical address or a corresponding physical address) and (optionally) a tag identifying the process in the host 300 that is requesting data. The sequencing logic 502 in the media controller 500 determines the order of the request relative to other received requests and reads the encrypted data from the media 510 at the appropriate time. The media controller 500 then provides the tag, the read request, and the encrypted data to the security engine 520. The adjustment generator 524 uses the read request to generate an adjustment value, which is provided as input along with the encrypted data to the data decryptor 522, which decrypts and outputs the decrypted data. In this example, the tag is simply passed through the security engine 520 (using triggers 526, 528 to synchronize the delivery of the tag to the host with the decrypted data). In other examples, the tag is provided as an input to the adjustment generator 524 in addition to or in lieu of the read address. As shown in FIG. Figure 5 The bottom and Figure 6 As shown in the graph of , the adjustment calculation and data decryption take the same amount of time in hardware implementation (in this example, 14-16 cycles with 2Ghz frequency, totaling 7ns-8ns), and incur a relatively high latency overhead.
[0051] The following embodiments can be used to reduce this latency overhead by effectively hiding the latency of calculating the adjustment value in the latency of reading the encrypted data from the medium 510. Assuming that the AES-XTS decryption latency represents the majority of the read round trip latency within the MRAM channel controller (MCC), these embodiments can significantly reduce the read round trip latency of the MCC. In one embodiment (see Figure 7), the adjustment generator 704 moves from the security engine 720 to the media controller 700. In operation, the media controller 700 receives a read request from the host 300 with a read address (e.g., LBA) and (optionally) a tag identifying the process in the host 300 that is requesting data. The sequencing logic 702 in the media controller 700 determines the order of the request relative to other received requests and reads the encrypted data from the medium 710 at the appropriate time. In this embodiment, the adjustment generator 704 generates the adjustment value during the waiting time associated with reading the encrypted data from the medium 710. In this way, the adjustment value is generated when the media controller 700 is ready to send the encrypted data to the security engine 720. This allows both the encrypted data and the adjustment value to be sent to the security engine 720 at the same time, so the data decryptor 722 can start decrypting the encrypted data when the adjustment value is received without having to wait for the adjustment value to be generated. That is, preparing the adjustment value from the medium 510 during the sensing time hides the adjustment generation in the read pipeline. Therefore, when the data is received from the medium 510, the AES decryption process can start immediately without additional delay.
[0052] like Figure 7 The bottom and Figure 8 As shown in the graph of , media read latency, adjustment generation latency, and data decryption latency are reduced compared to the above-described embodiments. In addition, due to the reduction in latency, only a single set of flip-flops 726 is used in this embodiment. More specifically, moving the adjustment generator to the media controller allows adjustment value generation to be performed in parallel with media reads, which allows adjustment generation latency to be hidden within media read latency. In one example, by doing so, the total AES-XTS decryption latency can be halved, resulting in AES-XTS decryption latency accounting for 28%-56% of the overall MCC budget.
[0053] When the media controller is "out of order" (i.e., the order in which the data is returned is different from the order in which the read requests were made), a challenge may be raised. The following embodiments may be used to match the generated adjustment values to the correct read data. In some embodiments, a conventional memory protocol is used, where the read data is returned in order with the issued requests. In another embodiment, a hybrid read memory protocol is used, where the read data is returned out of order with the issued requests. These embodiments are discussed below.
[0054] Returning to the attached figure, Fig. 9 An example media interface 900 is shown that can be used in a media controller using a conventional memory protocol (e.g., DDR5), where the media interface 900 returns read data in the same order as the read requests were issued to the media. Fig. 9As shown, in this example, the media interface 900 may include an adjustment generator 704 and two ongoing first-in, first-out (FIFO) buffers 902, 904, one buffer for adjustment values and the other buffer for tags. The FIFOs 902, 904 may be configured to output adjustment values and tags when reading their corresponding encrypted data from the media 710, so all three may be delivered together. More specifically, when a read request is issued, its read address is fed to the adjustment generator 704, and the generated adjustment is then pushed into the ongoing adjustment FIFO 902. When the encrypted read data is returned from the media 710, the media interface 900 dequeues the heads of both the ongoing request tag FIFO 904 and the ongoing adjustment FIFO 902. Thus, the read encrypted data is returned along with its corresponding read address and adjustment.
[0055] Fig.10 Another example media interface 1000 that can support hybrid reads is shown. In this example, instead of including a FIFO, the media interface 1000 includes a data bus occupancy recorder 1010 and a trigger 1020. The data bus occupancy recorder 1010 can send a read address and an index to the adjustment generator 704, and the adjustment generator 704 can return the generated adjustment value and the corresponding index. When the media 710 returns the encrypted data read, the data bus occupancy recorder 1010 can also return the corresponding tag and adjustment value. Fig.11 10 is a diagram of the contents of data occupation buffer 1010 in an example use case. Fig.11 As shown, the data occupancy buffer 1010 in this example stores an occupancy vector pointing to a current loop pointer, an address vector, and an adjustment vector.
[0056] Fig.12 is a diagram of the contents of data occupation buffer 1010, which will be combined with Fig.13 and Fig.14 Flowcharts 1300 and 1400 in are discussed. Fig.13 The flowchart in FIG. 1 is directed to a method for issuing an embodiment of an adjustment generation request when updating a data bus occupancy register based on an issued read command. Fig.13 As shown, the method includes setting a cyclic continuous read bit in the occupancy vector (action 1310), setting an entry in the request tag vector (action 1320), and sending an adjustment generation request to the adjustment generator (action 1330). Therefore, in this step, when a read request is issued, after processing the occupancy vector and the request tag vector update, the data bus occupancy recorder 1010 sends an adjustment generation request to the adjustment generator 704, wherein Data_Cycle_Start is used as the outbound index and the read address of the issued read command is used as the outbound read address. Fig.14 Flowchart 1400 in FIG. 1 is directed to a method for setting an adjustment vector when updating a data bus occupancy register based on an issued read command. Fig.14 As shown, the method includes setting an adjustment vector entry in an adjustment vector (act 1410). Thus, when the adjustment generator 704 returns an inbound adjustment with an inbound index, the adjustment vector / inbound index entry is set as the inbound adjustment.
[0057] Fig.15 is a diagram of the contents of the data occupancy buffer 1010 in another example use case related to read data processing, and will be combined with Fig.16 1600 in the discussion of a method for returning encrypted data read from a memory. Fig.16 As shown, the method includes obtaining a corresponding tag from the request tag vector and a corresponding adjustment vector entry in the adjustment vector (act 1610) and returning the encrypted read data (act 1620). Therefore, in the method, when returning the read encrypted data from the media, the media controller also looks up the adjustment value in the adjustment vector instead of just looking up the corresponding request tag.
[0058] Finally, as described above, any suitable type of memory may be used. Semiconductor memory devices include volatile memory devices, such as dynamic random access memory ("DRAM") or static random access memory ("SRAM") devices, non-volatile memory devices, such as resistive random access memory ("ReRAM"), electrically erasable programmable read-only memory ("EEPROM"), flash memory (which may also be considered a subset of EEPROM), ferroelectric random access memory ("FRAM"), and magnetoresistive random access memory ("MRAM"), as well as other semiconductor elements capable of storing information. Each type of memory device may have a different configuration. For example, a flash memory device may be configured in a NAND configuration or a NOR configuration.
[0059] The memory device may be formed of passive elements and / or active elements in any combination. By way of non-limiting example, passive semiconductor memory elements include ReRAM device elements, which in some embodiments include resistivity switching memory elements such as antifuses, phase change materials, etc., and optionally include steering elements such as diodes, etc. Further by way of non-limiting example, active semiconductor memory elements include EEPROM and flash memory device elements, which in some embodiments include elements having charge storage regions, such as floating gates, conductive nanoparticles, or charge storage dielectric materials.
[0060] A plurality of memory elements may be configured so that they are connected in series or so that each element may be accessed individually. By way of non-limiting example, a flash memory device (NAND memory) in a NAND configuration typically comprises memory elements connected in series. A NAND memory array may be configured so that the array is composed of a plurality of strings of memory, wherein the string is composed of a plurality of memory elements that share a single bit line and are accessed as a group. Alternatively, the memory elements may be configured so that each element may be accessed individually, such as a NOR memory array. NAND memory configurations and NOR memory configurations are examples, and memory elements may be configured in other ways.
[0061] Semiconductor memory elements located in and / or above a substrate may be arranged in two or three dimensions, such as a two-dimensional memory structure or a three-dimensional memory structure.
[0062] In a two-dimensional memory structure, semiconductor memory elements are arranged in a single plane or a single memory device level. Typically, in a two-dimensional memory structure, the memory elements are arranged in a plane (e.g., in an xz-direction plane) that extends substantially parallel to the major surface of a substrate supporting the memory elements. The substrate may be a wafer on or in which the layers of the memory elements are formed, or it may be a carrier substrate to which the memory elements are attached after they are formed. As a non-limiting example, the substrate may include a semiconductor, such as silicon.
[0063] The memory elements may be arranged in a single memory device level in an ordered array, such as in multiple rows and / or columns. However, the memory elements may be arranged in an unconventional configuration or a non-orthogonal configuration. The memory elements may each have two or more electrodes or contact lines, such as a bit line and a word line.
[0064] The three-dimensional memory array is arranged so that the memory elements occupy multiple planes or multiple memory device levels, thereby forming a structure in three dimensions (i.e., in the x-direction, y-direction and z-direction, wherein the y-direction is substantially perpendicular to the major surface of the substrate, and the x-direction and the z-direction are substantially parallel to the major surface of the substrate).
[0065] As a non-limiting example, a three-dimensional memory structure may be arranged vertically as a stack of multiple two-dimensional memory device levels. As another non-limiting example, a three-dimensional memory array may be arranged as a plurality of vertical columns (e.g., columns extending substantially perpendicular to the major surface of the substrate, i.e., in the y-direction), wherein each column has a plurality of memory elements. The columns may be arranged in a two-dimensional configuration, such as in the xz plane, resulting in a three-dimensional arrangement of memory elements, wherein the elements are located on multiple vertically stacked memory planes. Other configurations of three-dimensional memory elements may also constitute a three-dimensional memory array.
[0066] By way of non-limiting example, in a three-dimensional NAND memory array, memory elements may be coupled together to form NAND strings within a single horizontal (e.g., xz) memory device level. Alternatively, memory elements may be coupled together to form vertical NAND strings that span multiple horizontal memory device levels. Other three-dimensional configurations are contemplated in which some NAND strings contain memory elements in a single memory level, while other strings contain memory elements that span multiple memory levels. Three-dimensional memory arrays may also be designed in NOR configurations as well as ReRAM configurations.
[0067] Typically, in a monolithic three-dimensional memory array, one or more memory device levels are formed over a single substrate. Optionally, a monolithic three-dimensional memory array may also have one or more memory layers at least partially within a single substrate. As a non-limiting example, the substrate may include a semiconductor, such as silicon. In a monolithic three-dimensional array, the layers of each memory device level that make up the array are typically formed on the layers of the underlying memory device level of the array. However, the layers of adjacent memory device levels of a monolithic three-dimensional memory array may be shared or have intervening layers between the memory device levels.
[0068] The two-dimensional arrays may then be formed separately and then packaged together to form a non-monolithic memory device having multiple memory layers. For example, a non-monolithic stacked memory may be constructed by forming memory levels on separate substrates and then stacking the memory levels on top of each other. The substrate may be thinned or removed from the memory device levels before stacking, but since the memory device levels are initially formed on separate substrates, the resulting memory array is not a monolithic three-dimensional memory array. In addition, multiple two-dimensional memory arrays or three-dimensional memory arrays (monolithic or non-monolithic) may be formed on separate chips and then packaged together to form a stacked chip memory device.
[0069] Typically, associated circuitry is required to operate and communicate with the memory element. As a non-limiting example, a memory device may have circuitry for controlling and driving the memory element to implement functions such as programming and reading. The associated circuitry may be located on the same substrate as the memory element and / or on a separate substrate. For example, a controller for memory read-write operations may be located on a separate controller chip and / or on the same substrate as the memory element.
[0070] Those skilled in the art will recognize that the present invention is not limited to the two-dimensional and three-dimensional structures described, but encompasses all related memory structures within the spirit and scope of the invention as described herein and as understood by those skilled in the art.
[0071] It is intended that the foregoing detailed description be understood as an illustration of selected forms that the invention may take, rather than as a definition of the invention. It is intended that only the following claims (including all equivalents) define the scope of the invention as claimed. Finally, it should be noted that any aspect of any embodiment described herein may be used alone or in combination with each other.
Claims
1. A data storage device, comprising: Memory; Decryption engine; and a controller coupled to the memory and the decryption engine, wherein the controller is configured to: receiving a read request including an address; reading encrypted data from the memory, wherein the encrypted data is read from a location in the memory associated with the address; generating a value required to decrypt the encrypted data while the encrypted data is being read from memory, wherein the value is generated at least in part from the address; as well as The encrypted data and the generated value are sent to the decryption engine to decrypt the data.
2. The data storage device according to claim 1, wherein the controller is further configured to: receiving a tag associated with a process in a host requesting the encrypted data; and The tag is sent to the decryption engine along with the encrypted data and the generated value. 3 . The data storage device of claim 1 , wherein the decryption engine is configured to decrypt the encrypted data using two keys, and wherein one of the two keys comprises the generated value. The data storage device of claim 1 , wherein the generated value comprises an adjustment value. 5 . The data storage device of claim 1 , wherein the decryption engine is configured to decrypt the encrypted data using an AES-XTS algorithm.
6. The data storage device of claim 1, wherein the encrypted data is received out of order relative to sending a command to the memory to read the address, and wherein the controller is further configured to match the encrypted data with the generated value.
7. The data storage device of claim 1, wherein the controller includes a data bus occupancy recorder. 8 . The data storage device of claim 7 , wherein the controller is further configured to issue an adjustment generation request when updating the data bus occupancy register according to the issued read command.
9. The data storage device of claim 7, wherein the controller is further configured to set the adjustment vector when updating the data bus occupancy register according to the issued read command.
10. The data storage device of claim 1, wherein the memory comprises a magnetoresistive random access memory (MRAM).
11. The data storage device of claim 1, wherein the memory comprises a three-dimensional memory.
12. In a memory controller in a data storage device including a memory and an AES-XTS decryption engine, a method comprising: generating an adjustment value from a read address during a time when encrypted data is being read from a location in the memory associated with the read address; as well as The adjustment value and the encrypted data are sent to the AES-XTS decryption engine.
13. The method according to claim 12, further comprising: receiving a tag associated with a process in a host requesting the encrypted data; as well as The tag is sent to the AES-XTS decryption engine along with the encrypted data and the adjustment value.
14. The method of claim 12, wherein the encrypted data is received out of order relative to sending a command to the memory to read the address, and wherein the method further comprises matching the encrypted data with the generated value.
15. The method of claim 12, wherein the memory controller includes a data bus occupancy recorder.
16. The method of claim 15, further comprising issuing an adjustment generation request when updating a data bus occupancy register in accordance with an issued read command.
17. The method of claim 15, further comprising setting an adjustment vector when updating a data bus occupancy register according to an issued read command.
18. The method of claim 12, wherein the memory comprises a magnetoresistive random access memory (MRAM).
19. The method of claim 10, wherein the memory comprises a three-dimensional memory.
20. A data storage device, the data storage device comprising: Memory; and Means for reducing latency in decrypting encrypted data read from the memory by hiding latency in calculating an adjustment value for decrypting the encrypted data within latency in reading the encrypted data from the memory.
