Systems and methods for virtual computational storage devices

TWI945208BActive Publication Date: 2026-11-11SAMSUNG ELECTRONICS CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
TW111117387
Authority / Receiving Office
TW · TW
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-06-17
Filing Date
2022-05-10
Publication Date
2026-11-11
Estimated Expiration
2042-05-09

AI Technical Summary

Technical Problem

Computing systems with storage devices that do not support computing functions face challenges in efficiently utilizing both storage and computational capabilities, as they lack the ability to offload computations to storage devices that do not provide computing functionalities.

Method used

A virtual computing storage emulation module is implemented to provide a virtual computing storage device, which includes a storage element and a computing element, capable of translating computing and storage requests between the client and the respective elements, thereby emulating the functions of physical computing storage devices.

Benefits of technology

This solution enables efficient utilization of storage devices with computational capabilities, allowing for seamless translation and execution of computing and storage requests, enhancing the functionality of storage devices that do not inherently support computing tasks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure TWG2TB001919953_001
    Figure TWG2TB001919953_001
  • Figure TWG2TB001919953_002
    Figure TWG2TB001919953_002
  • Figure TWG2TB001919953_003
    Figure TWG2TB001919953_003
Patent Text Reader

Abstract

This invention provides a system comprising a virtual computing storage emulation module configured to provide a virtual computing storage device. The system further includes a storage element, wherein the virtual computing storage emulation module is configured to store data associated with the virtual computing storage device at the storage element. The system further includes a computing element. The virtual computing storage emulation module is configured to send computing requests associated with the virtual computing storage device to the computing element.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure is generally directed to systems and methods for virtual computational storage devices. Cross - reference to related applications

[0002] This application claims the priority and benefit of U.S. Provisional Application No. 63 / 196,081, filed on June 2, 2021, entitled "Virtual Computational Storage Devices", the entire content of which is incorporated herein by reference.

Background Art

[0003] Computational storage devices provide computational capabilities and data storage. Thus, a host device can store data at a computational storage device and offload computations to the computational storage device. However, a computing system can include storage devices that do not support computational capabilities.

[0004] The above information disclosed in this background art section is only for enhancing the understanding of the background of this disclosure, and thus it may contain information that does not constitute prior art.

Summary of the Invention

[0005] In various embodiments, systems, methods, and devices related to virtual computational storage devices are described herein.

[0006] A system includes a virtual computational storage emulation module configured to provide a virtual computational storage device. The system further includes a storage component, wherein the virtual computational storage emulation module is configured to store data associated with the virtual computational storage device at the storage component. The system further includes a computational component. The virtual computational storage emulation module is configured to send a computational request associated with the virtual computational storage device to the computational component.

[0007] A method includes providing a virtual computational storage device at a virtual computational storage device emulation module. Data associated with the virtual computational storage device is stored at a storage component. The method further includes receiving, at the virtual computational storage device emulation module, a computational request for the virtual storage device. The method further includes sending a translation of the computational request to a computational component.

[0008] A system includes a computing element of a first device and a storage element of a second device. The system further includes a compute storage client and a processor. The processor is configured to receive a compute request from the compute storage client. The processor is further configured to send a translation of the compute request to the computing element of the first device. The processor is further configured to receive a storage request from the compute storage client. The processor is further configured to send a translation of the storage request to the storage element of the second device.

Embodiments

[0010] Details of one or more embodiments of the subject matter described herein are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

[0011] Reference will now be made to the accompanying drawings, in which various embodiments of the present disclosure will be described more fully hereinafter. Some, but not all, embodiments are illustrated in the accompanying drawings. In fact, the present disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Unless otherwise indicated, the term "or" is used herein in both an alternative and a conjunctive sense. The terms "exemplary" and "example" are used for examples that do not indicate a level of quality. The same numbers refer to the same elements throughout the specification. Arrows in each of the figures depict bidirectional data flow and / or bidirectional data flow capabilities. The terms "path", "pathway", and "route" are used interchangeably herein.

[0012] Embodiments of the present disclosure may be implemented in various ways, including as a computer program product including a product. The computer program product may include a non-transitory computer-readable storage medium storing an application program, a program, a program component, a script, source code, code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, and / or the like (also referred to herein as executable instructions, instructions for execution, computer program products, code, and / or similar terms used interchangeably herein). Such non-transitory computer-readable storage media include all computer-readable media (including volatile and non-volatile media).

[0013] In one embodiment, the non-volatile computer-readable storage medium may include a floppy disk, a flexible disk, a hard disk, a solid-state storage (SSS) (e.g., a solid-state drive (SSD)), a solid state card (SSC), a solid state component (SSM), an enterprise flash drive, a magnetic tape, or any other non-transitory magnetic medium and / or the like. The non-volatile computer-readable storage medium may also include punched cards, paper tapes, optical mark sheets (or any other physical medium having a pattern of holes or other optically recognizable marks), a compact disc read only memory (CD-ROM), a compact disc-rewritable (CD-RW); a digital versatile disc (DVD), a Blu-ray disc (BD), any other non-transitory optical medium and / or the like. This non-volatile computer-readable storage medium may also include a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), flash memory (e.g., Serial, NAND, NOR, and / or the like), multimedia memory cards (MMC), secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF) cards, memory sticks, and / or the like.In addition, the non-volatile computer-readable storage medium may also include conductive-bridging random access memory (CBRAM), phase-change random access memory (PRAM), ferroelectric random-access memory (FeRAM), non-volatile random-access memory (NVRAM), magnetoresistive random-access memory (MRAM), resistive random-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon (SONOS), floating junction gate random access memory (FJG RAM), Millipede memory, track memory, and / or the like.

[0014] In one embodiment, the volatile computer-readable storage medium may include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), fast page mode dynamic random access memory (FPM DRAM), extended data-out dynamic random access memory (EDO DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), double data rate type two synchronous dynamic random access memory (DDR2 SDRAM), double data rate type three synchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamic random access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM (T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory component (RIMM), dual in-line memory component (DIMM), single in-line memory component (SIMM), video random access memory (VRAM), cache memory (including various levels), flash memory, register memory, and / or the like. It should be understood that in cases where an embodiment is described as using a computer-readable storage medium, other types of computer-readable storage media may be substituted for or used in addition to the computer-readable storage media described above.

[0015] As should be understood, various embodiments of the present disclosure may also be implemented as a method, apparatus, system, computing device, computing entity, and / or the like. Thus, embodiments of the present disclosure may take the form of an apparatus, system, computing device, computing entity, and / or the like that executes instructions stored on a computer-readable storage medium to perform certain steps or operations. Therefore, embodiments of the present disclosure may also take the form of a complete hardware embodiment, a complete computer program product embodiment, and / or an embodiment that includes a combination of a computer program product and hardware for performing certain steps or operations.

[0016] Embodiments of the present disclosure are described below with reference to block diagrams and flowchart illustrations. Therefore, it should be understood that each block in the block diagrams and flowchart illustrations can be implemented in the form of a computer program product, a complete hardware embodiment, a combination of hardware and a computer program product, and / or an apparatus, system, computing device, computing entity, and / or the like that can interchangeably use instructions, operations, steps, and similar terms (e.g., executable instructions, instructions for execution, code, and / or the like) for execution on a computer-readable storage medium. For example, program code can be sequentially fetched, loaded, and executed such that one instruction is fetched, loaded, and executed at a time. In some example embodiments, fetching, loading, and / or execution can be performed in parallel such that multiple instructions are fetched, loaded, and / or executed together. Thus, such embodiments can produce a machine configured to perform the steps or operations specified in the block diagrams and flowchart illustrations. Therefore, the block diagrams and flowchart illustrations support various combinations of embodiments for performing the specified instructions, operations, or steps. As used herein, a compute storage device refers to a storage device that supports compute tasks. For example, a compute storage device may include storage components (e.g., non-volatile memory such as flash memory) and compute components (e.g., a central processor unit (CPU), a graphics processor unit (GPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) such as a tensor processing unit, a processor core, etc.), and is configured to support storing data at the compute component and executing compute tasks at the compute component. Thus, a compute storage device may provide storage capabilities to a compute storage client (e.g., a compute device) and may support offloading compute tasks from the compute storage client to the compute storage device. Referring to FIG. 1A, a block diagram depicting a system 100 for providing a virtual compute storage device is shown.

[0018] System 100 includes a virtual compute storage emulation module 102, a compute component 106, a storage component 108, and a compute storage client 104. The virtual compute storage emulation module 102 may correspond to software (e.g., a hypervisor) that may be executed by a processing device (not shown) of a compute device (e.g., a server device) to provide access to a virtual compute storage device 110. The virtual compute storage device 110 may be a logical construct rather than a physical compute storage device. The virtual compute storage emulation module 102 provides the virtual compute storage device 110 by emulating (e.g., reproducing) the functionality of a physical compute storage device. The functionality of the virtual compute storage device 110 is implemented by the compute component 106 and the storage component 108. The virtual compute storage emulation module 102 is configured to emulate a physical compute storage device to provide storage request translation and to provide compute request translation, as further described herein. The compute component 106 and the storage component 108 may be components of a physical compute storage device or one or more other types of devices.

[0019] The computing element 106 may correspond to a CPU, GPU, FPGA, ASIC, processor core, another type of processor element, or a combination thereof. The storage element 108 may correspond to a solid state drive, a hard disk drive, another type of non-volatile memory, or a combination thereof. The computing element 106 and the storage element 108 may correspond to different devices or to a single device. For example, the computing element 106 and the storage element 108 may correspond to a physical computing storage device. In some embodiments, the computing element 106 and the storage element 108 are within the device executing the virtual computing storage emulation module 102. In some embodiments, the computing element 106 and the storage element 108 are external to the device executing the virtual computing storage emulation module 102. Although a single computing element and a single storage element are illustrated, the system 100 may include additional computing elements and additional storage elements. Further, although the virtual computing storage device 110 is illustrated as being supported by a single computing element and a single storage element, the virtual computing storage device 110 may be supported by more than one computing element and / or more than one storage element. Additionally, the virtual computing storage emulation module 102 may provide more than one virtual computing storage device. Communication between the virtual computing storage emulation module 102 and the computing element 106 and the storage element 108 may be carried via: a peripheral component interconnect (PCI) link, a PCI express (PCIe) link, a serial advanced technology attachment (SATA) link, a serial attached small computer system interface (SASCSI) link, a fiber channel, an Ethernet link, an Institute of Electrical and Electronics Engineers (IEEE) 802.11 link, another type of link, or a combination thereof. Communication between the virtual computing storage emulation module 102 and the computing element 106 and the storage element 108 may include non-volatile memory express (NVMe) communication.

[0020] Configure the computing storage client 104 to publish computing requests and storage requests to the virtual computing storage emulation module 102 for a computing device or software. In an implementation where the computing storage client 104 corresponds to software, the computing storage client 104 can correspond to a virtual computing device provided by a hypervisor that executes instructions at a computing element (such as computing element 106) to emulate a computing device. Communication between the computing storage client 104 and the virtual computing storage emulation module 102 can be carried via: a Peripheral Component Interconnect (PCI) link, a Peripheral Component Interconnect Express (PCIe) link, a Serial Advanced Technology Attachment (SATA) link, a Serial Attached Small Computer System Interface (SASCSI) link, Fibre Channel, an Ethernet link, an Institute of Electrical and Electronics Engineers (IEEE) 802.11 link, another type of link, or a combination thereof. Communication between the virtual computing storage emulation module 102 and the computing element 106 and the storage element 108 can include Non-Volatile Memory Express (NVMe) communication.

[0021] In operation, the storage element 108 stores data 112 associated with the virtual computing storage device 110, and the computing element 106 executes computing requests associated with the virtual computing storage device 110. The data 112 can be written to the storage element 108 by the virtual computing storage emulation module 102 in response to a request from the computing storage client 104. As depicted in FIG. 1A, the virtual computing storage emulation module 102 provides computing request translation.

[0022] In the illustrated example, the compute storage client 104 sends a compute request 114 to the virtual compute storage emulation module 102. The compute request 114 may be addressed to the virtual compute storage device 110. The virtual compute storage emulation module 102 may maintain a mapping of the virtual compute storage device 110 to the compute element 106 and thus translate the compute request 114 into a request for the compute element 106. Accordingly, the virtual compute storage emulation module 102 may forward the compute request 114 to the compute element 106. It should be noted that although the above example describes forwarding the compute request 114 to the compute element 106, in practice, a message different from the message received by the virtual compute storage emulation module 102 from the compute storage client 104 may be sent to the compute element 106. For example, the compute request 114 may correspond to an NVMe request, such as an NVMe command (or other type of request) to load and / or execute a program, but the compute element 106 may not support NVMe (or another type of protocol). Thus, the virtual compute storage emulation module 102 may translate the compute request 114 into a translated message in a protocol supported by the compute element 106. The virtual compute storage emulation module 102 may forward the translated message rather than the compute request 114 to the compute element 106. As indicated above, the virtual compute storage emulation module 102 may support emulation of a physical compute storage device. The translation of the compute request may include an aspect of this emulation.

[0023] In some embodiments, the virtual compute storage device 110 may correspond to more than one compute element. In such cases, the virtual compute storage emulation module 102 may select which compute element to forward the compute request 114 based on a load balancing algorithm. Additionally or alternatively, the virtual compute storage emulation module 102 may select the compute element to forward the compute request 114 based on the address of the data targeted by the compute request 114. For example, the virtual compute storage emulation module 102 may forward the compute request 114 to a particular compute storage device in response to determining that the compute request 114 targets data stored on the particular compute storage device.

[0024] The computing element 106 can directly or via the virtual computing storage emulation module 102 return the result (not shown) of the computing request 114 to the computing storage client 104. Similarly, the computing element 106 can communicate with the storage element 108 directly or via the virtual computing storage emulation module 102. For example, the computing request 114 can target the data 112. The computing element 106 can directly retrieve the data 112 from the storage element 108, or the virtual computing storage emulation module 102 can retrieve the data 112 from the storage element 108 and transfer the data 112 together with the computing request 114 to the computing element 106. In an embodiment where the computing element 106 returns the result via the virtual computing storage emulation module 102, the virtual computing storage emulation module can translate the result into a protocol supported by the computing storage client 104 (e.g., a protocol configured to support communication between the computing storage client and the computing storage device). As indicated above, the virtual computing storage emulation module 102 can support the emulation of a physical computing storage device. The translation of the computing request result can include an aspect of this emulation.

[0025] FIG. 1B shows an example where the virtual computing storage emulation module 102 of the system 100 provides storage request translation. In the example shown, the computing storage client 104 sends a storage request 116 to the virtual computing storage emulation module 102. The storage request 116 can correspond to a read request or a write request. In some embodiments, the storage request 116 corresponds to an NVMe request. The storage request 116 is directed to the virtual computing storage device 110. The virtual computing storage emulation module 102 maintains a mapping between the virtual computing storage device and the storage element. Based on the mapping, the virtual computing storage emulation module 102 can transfer the storage request 116 to the storage element 108. It should be noted that although the above example describes transferring the storage request 116 to the storage element 108, in practice, a message different from the message received by the virtual computing storage emulation module 102 from the computing storage client 104 can be sent to the storage element 108. For example, the storage request 116 can correspond to an NVMe request (or other type of request), but the storage element 108 may not support NVMe (or another type of protocol). Therefore, the virtual computing storage emulation module 102 can translate the storage request 116 into a translated message of a protocol supported by the storage element 108. The virtual computing storage emulation module 102 can transfer the translated message instead of the storage request 116 to the storage element 108. As indicated above, the virtual computing storage emulation module 102 can support the emulation of a physical computing storage device. The translation of the storage request can include an aspect of this emulation.

[0026] In some embodiments, the virtual computing storage device 110 may correspond to more than one storage element. In such cases, the virtual computing storage emulation module 102 may select a storage element for forwarding the storage request 116 based on the address targeted by the storage request 116 (e.g., a logical block address (LBA)). For example, for each virtual computing storage device, the virtual computing storage emulation module 102 may maintain a mapping of storage elements to ranges of addresses (e.g., LBAs). In an instance where the storage request 116 corresponds to a write request, the virtual computing storage emulation module 102 may select which storage element to forward the storage request 116 based on a load balancing algorithm. The virtual computing storage emulation module 102 may update the mapping of addresses to storage elements to reflect to which storage element the write request was sent. For example, in response to sending a write to LBA A to a first storage element, the virtual computing storage emulation module 102 may update the mapping to indicate that LBA A is associated with the first storage element.

[0027] The computing element 106 may directly or via the virtual computing storage emulation module 102 return the result (not shown) of the storage request 116 to the compute storage client 104. For example, the storage element 108 may send the data 112 to the compute storage client 104 in response to a read request. As another example, the storage element 108 may send a read request to the compute storage client 104 in response to a write request (alternatively, the virtual computing storage emulation module 102 may send the read request to the compute storage client 104). In an instance where the result is returned via the virtual computing storage emulation module 102, the virtual computing storage emulation module 102 may translate the result into a protocol used by the compute storage client 104. As indicated above, the virtual computing storage emulation module 102 may support emulation of a physical compute storage device. The translation of the storage request result may include an aspect of this emulation. Emulation is further described with respect to FIG. 1C.

[0028] In some instances, the storage request 116 corresponds to a request to write the data 112 to the storage element 108. The virtual computing storage emulation module 102 may translate the storage request 116 and forward it to the storage element 108 as described above.

[0029] FIG. 1C depicts an example of the system 100 that provides emulation of a compute storage device. In the illustrated example, the compute storage client 104 and the virtual computing storage emulation module 102 communicate according to a protocol supported by the compute storage device (e.g., NVMe). The virtual computing storage emulation module 102 is configured to translate between these compute storage messages and messages according to one or more protocols supported by the computing element 106 and the storage element 108.

[0030] In the illustrated example, the compute storage client 104 sends a computational storage (CSD) command 118 (e.g., a compute command, a storage command, or another type of command) to the virtual compute storage emulation module 102. The CSD command 118 conforms to a CSD protocol (e.g., NVMe) supported by the compute storage client 104 and the virtual compute storage emulation module 102. The virtual compute storage emulation module 102 translates the CSD command 118 into a hardware command 120 that conforms to the protocol utilized by the compute element 106, and sends the hardware command 120 to the compute element 106. The translation portion may include translating an address identified in the CSD command 118 to an address associated with the storage element 108. For example, LBA A of the virtual compute storage device 110 may be mapped to LBA B at the storage element 108. In some embodiments, the virtual compute storage emulation module 102 may extract data from the storage element 108 based on the translated address, and include the extracted data in the hardware command 120. Although the previous example describes both a virtual compute storage device and a storage element 108 that support LBAs, the virtual compute storage device 110 and the storage element 108 may support different types of addressing schemes (e.g., key-value). The virtual compute storage emulation module 102 may translate between the addressing scheme presented by the virtual compute storage device 110 and the addressing scheme supported by the storage element 108. In response to the hardware command 120, the compute element 106 generates a hardware result 122 and sends the hardware result 122 to the virtual compute storage emulation module 102. The virtual compute storage emulation module 102 translates the hardware result 122 into a CSD result 124 that conforms to the CSD protocol utilized by the compute storage client 104, and transmits the CSD result 124 to the compute storage client 104.

[0031] Although FIG. 1C depicts an example where the CSD command 118 corresponds to a compute command, it should be noted that the virtual compute storage emulation module 102 can provide a similar translation of storage commands. For example, the CSD command 118 can correspond to a storage request. Thus, the virtual compute storage emulation module 102 can translate the CSD command 118 into a hardware command 120 and send the hardware command 120 to the storage element 108. As described above, the CSD command 118 and the hardware command 120 can have different protocols and / or utilize different addressing schemes. In this case, the storage element 108 can send back a hardware result 122 (e.g., containing data 112) to the virtual compute storage emulation module 102, and the virtual compute storage emulation module 102 can translate the hardware result 122 into a CSD result 124 and send the CSD result 124 to the compute storage client 104. Thus, the virtual compute storage emulation module 102 can provide translation of both compute and storage commands addressed to the virtual compute storage device.

[0032] In addition to providing translation of compute storage device messages, the virtual compute storage emulation module 102 can also emulate other functions of the compute storage device. For example, the virtual compute storage emulation module 102 can maintain one or more submission queues (or other data structures) associated with the compute storage device in the memory (not shown) of the compute device on which the virtual compute storage emulation module is executing. As another example, the virtual compute storage emulation module 102 can announce the availability of the compute storage device to the compute storage client 104 according to the CSD protocol. It should be noted that the announced capabilities can correspond to the emulated capabilities. That is, the virtual compute storage emulation module 102 can announce hardware capabilities and can implement the announced hardware capabilities in software.

[0033] Thus, FIGS. 1A - 1C illustrate a system for providing a virtual compute storage device. The system supports storage device translation and forwarding, compute device translation and forwarding, and emulation of other functions of the compute storage device. As further described below, the underlying hardware used by the virtual compute storage emulation module 102 to provide the virtual compute storage device can take many forms. Thus, the system 100 of FIGS. 1A - 1C can provide the functionality of the compute storage device to the compute storage client in a wide variety of hardware configurations.

[0034] As briefly described above, the virtual compute storage device provided by the virtual compute storage emulation module 102 can be supported by more than one storage element and / or more than one compute element. FIGS. 2A - 2B illustrate several examples where the virtual compute storage device is supported by additional physical components.

[0035] FIG. 2A shows an example of system 100 where virtual computing storage device 110 corresponds to first storage element 202 and second storage element 204 rather than storage element 108. First storage element 202 stores first data 206 associated with virtual computing storage device 110, and second storage element 204 stores second data 208 associated with virtual computing storage device 110.

[0036] Computing storage client 104 may send a first storage request 210 to virtual computing storage emulation module 102. First storage request 210 may identify a first address 212 (e.g., a first LBA). Virtual computing storage emulation module 102 may forward first storage request 210 to first storage element 202 based on first address 212. For example, virtual computing storage emulation module 102 may store a mapping of the addresses of virtual computing storage device 110 to the addresses of first storage element 202 and second storage element 204. In some embodiments, first storage request 210 may correspond to a write request, and virtual computing storage emulation module 102 may send first storage request 210 to first storage element 202 based on a load balancing algorithm. For example, virtual computing storage emulation module 102 may distribute write requests among the storage elements in a round-robin fashion (or according to some other algorithm). In response to writing data for a particular virtual storage device address to a particular address of a storage element, virtual computing storage emulation module 102 may update the mapping of virtual computing storage device addresses to storage element addresses to indicate that a particular virtual storage device address is mapped to a particular address of a storage element.

[0037] In the example shown, computing storage client 104 issues a second storage request 214 that identifies a second address 216 and forwards second storage request 214 to second storage element 204. Virtual computing storage emulation module 102 may identify second storage element 204 to receive second storage request 214 using the techniques described above with respect to first storage request 210. It should be noted that, like storage request 116 described above, first storage request 210 and second storage request 214 may be translated by virtual computing storage emulation module 102 into messages that conform to one or more protocols utilized by first storage element 202 and second storage element 204. First storage element 202 and second storage element 204 may support different protocols.

[0038] FIG. 2B shows an example of system 100 where virtual computing storage device 110 corresponds to first computing element 218 and second computing element 220 rather than computing element 106. In the example shown, computing storage client 104 sends first computing request 224 and second computing request 228 to virtual computing storage emulation module 102. Both first computing request 224 and second computing request 228 are directed to virtual computing storage device 110. First computing request 224 identifies first address 226 and second computing request 228 identifies second address 230. Virtual computing storage emulation module 102 forwards first computing request 224 to first computing element 218 and forwards second computing request 228 to second computing element 220. Virtual computing storage emulation module 102 may forward first computing request 224 to first computing element 218 based on first address 226. For example, virtual computing storage emulation module 102 may manage the mapping of virtual computing storage device addresses to computing elements. In another example, virtual computing storage emulation module 102 may forward computing requests according to a load balancing algorithm. As described above, virtual computing storage emulation module 102 may translate computing request 224, computing request 228 into different protocols and then forward them to computing element 218, computing element 220. In some embodiments, virtual computing storage emulation module 102 retrieves data associated with first address 226 from storage element 108 and forwards this data together with first computing request 224 to first computing element 218. Similarly, virtual computing storage emulation module 102 may retrieve data associated with second address 230 from storage element 108 and forwards this data together with second computing request 228 to second computing element 220.

[0039] Note that the virtual computing storage device may correspond to more than one computing element and more than one storage element. Additionally, although FIGS. 2A - 2B illustrate examples with 2 storage elements and 2 computing elements respectively, other numbers of storage elements and / or computing elements may be utilized by virtual computing storage emulation module 102 to provide the virtual computing storage device. Further, virtual computing storage emulation module 102 may support more than one virtual computing storage device. Examples where virtual computing storage emulation module 102 supports more than one virtual computing storage device are illustrated in FIGS. 3A - 3C.

[0040] In FIG. 3A, the virtual computing storage emulation module 102 provides a first virtual computing storage device 302 and a second virtual computing storage device 304 instead of the virtual computing storage device 110. The first virtual computing storage device 302 is supported by a first computing element 306 and a first storage element 308. The first storage element 308 stores first data 310 associated with the first virtual computing storage device 302. The second virtual computing storage device 304 is supported by a second computing element 312 and a second storage element 314. The second storage element 314 stores second data 316 associated with the second virtual computing storage device 304.

[0041] The virtual computing storage emulation module 102 is configured to provide compute request translation, storage request translation, and virtual computing storage device emulation for the first virtual computing storage device and the second virtual computing storage device, as described above with reference to the virtual computing storage device 110. The virtual computing storage emulation module 102 may direct storage commands for the first virtual computing storage device 302 to the storage element (e.g., the first storage element 308) that supports the first virtual computing storage device 302 (and translate the storage commands). The virtual computing storage emulation module 102 may direct compute commands for the first virtual computing storage device 302 to the computing element (e.g., the first computing element 306) that supports the first virtual computing storage device 302 (and translate the compute commands). Similarly, the virtual computing storage emulation module 102 may direct compute and storage commands for the second virtual computing storage device 304 to the devices that support the second virtual computing storage device 304 (e.g., the second computing element 312 and the second storage element 314) (and translate the compute and storage commands). In addition, the virtual computing storage emulation module 102 may emulate other functions of the first virtual computing storage device 302 and the second virtual computing storage device 304, as described above. For example, the virtual computing storage emulation module 102 may maintain submission queues associated with the virtual computing storage device 302, the virtual computing storage device 304, announce the availability of the virtual computing storage device 302, the virtual computing storage device 304, etc.

[0042] Although FIG. 3A shows virtual computing storage devices supported by a single underlying physical device, it should be noted that physical devices may be shared among the virtual computing storage devices. FIG. 3B shows an example where the first virtual computing storage device 302 and the second virtual computing storage device 304 share a storage element 330. Accordingly, the virtual computing storage emulation module 102 may forward a first storage request 332 for the first virtual computing storage device 302 and a second storage request 334 for the second virtual computing storage device 304 to the storage element 330 (and / or translate the first storage request 332 and the second storage request 334).

[0043] FIG. 3C shows an example where the first virtual computing storage device 302 and the second virtual computing storage device 304 share the computing element 350. Thus, the virtual computing storage emulation module 102 can forward the first computing request 352 for the first virtual computing storage device 302 and the second computing request 354 for the second virtual computing storage device 304 to the computing element 350 (and / or translate the first computing request 352 and the second computing request 354). Thus, FIGS. 3A to 3C show different examples where the virtual computing storage emulation module 102 supports more than one virtual computing storage device. As depicted, different virtual computing storage devices can be supported by different underlying physical devices or can share the underlying physical devices.

[0044] It should be noted that although the examples described herein include a single host, the virtual computing storage emulation module 102 can support more than one host. In some examples, the virtual computing storage device is exclusive to a host. In other examples, the virtual computing storage device is shared among hosts. It should further be noted that the virtual computing storage emulation module 102 can support virtual computing storage devices with different functions. For example, the virtual computing storage emulation module 102 can provide a first virtual computing storage device that provides compression / decompression and a second virtual computing storage device that provides encryption / decryption. The virtual computing storage emulation module 102 can perform compression / decompression of data for requests associated with the first virtual computing storage device as part of emulating the first virtual computing storage device. In addition, the virtual computing storage emulation module 102 can perform encryption / decryption of data for requests associated with the second virtual computing storage device as part of emulating the second virtual computing storage device.

[0045] As described above, system 100 can use computing and storage components from various sources to provide virtual computing storage devices. Referring to FIG. 4, which is a system 400 for providing virtual computing storage devices. System 400 includes a computing device 402. Computing device 402 includes a computing component 404 and a storage component 406. Computing component 404 can include a processing device and can correspond to computing component 106, first computing component 218, second computing component 220, first computing component 306, or second computing component 312 described above. Storage component 406 can include a non-volatile storage device and can correspond to storage component 108, first storage component 202, second storage component 204, first storage component 308, or second storage component 314. Computing device 402 is configured to execute a hypervisor 408 that includes a virtual computing storage emulation module 410. Hypervisor 408 can execute at computing component 404 or at another processor of computing device 402. Virtual computing storage emulation module 410 can correspond to virtual computing storage emulation module 102 described above.

[0046] Hypervisor 408 is configured to provide a first virtual machine 412 and a second virtual machine 416. In some embodiments, first virtual machine 412 or second virtual machine 416 corresponds to computing storage client 104. Virtual computing storage emulation module 410 is configured to present a first virtual computing storage device 414 to first virtual machine 412 and a second virtual computing storage device 418 to second virtual machine 416. First virtual computing storage device 414 can correspond to virtual computing storage device 110, first virtual computing storage device 302, or second virtual computing storage device 304. Second virtual computing storage device 418 can correspond to virtual computing storage device 110, first virtual computing storage device 302, or second virtual computing storage device 304.

[0047] Virtual computing storage emulation module 410 is configured to use the components of computing device 402 to provide the functionality of virtual computing storage devices 414, 418. Thus, virtual computing storage emulation module 410 can translate computing requests for virtual computing storage devices 414, 418 into computing requests for computing component 404 and translate storage requests for virtual computing storage devices 414, 418 into storage requests for storage component 406, as described above. Thus, FIG. 4A shows that a computing device (e.g., a server) can use the components of the computing device to provide virtual computing storage device functionality.

[0048] Referring to FIG. 4B, an alternative implementation of system 400 is shown, where computing device 402 communicates with a first computing storage device 430 and a second computing storage device 432 (e.g., via PCIe or some other connection). The first computing storage device 430 includes a first computing element 434 and a first storage element 436. The second computing storage device 432 includes a second computing element 438 and a second storage element 440. The first computing element 434 may include a processing device and may correspond to computing element 106, the first computing element 218, the second computing element 220, the first computing element 306, or the second computing element 312 described above. Similarly, the second computing element 438 may include a processing device and may correspond to computing element 106, the first computing element 218, the second computing element 220, the first computing element 306, or the second computing element 312 described above. The first storage element 436 may include a non-volatile storage device and may correspond to storage element 108, the first storage element 202, the second storage element 204, the first storage element 308, or the second storage element 314 described above. Similarly, the second storage element 440 may include a non-volatile storage device and may correspond to storage element 108, the first storage element 202, the second storage element 204, the first storage element 308, or the second storage element 314 described above.

[0049] The virtual computing storage emulation module 410 is configured to use the components of the computing storage device 430 and the computing storage device 432 to provide the functionality of the virtual computing storage device 414 and the virtual computing storage device 418. Thus, the virtual computing storage emulation module 410 may translate computing requests for the virtual computing storage device 414 and the virtual computing storage device 418 into computing requests for the components of the first computing storage device 430 and / or the components of the second computing storage device 432, as described above. Thus, FIG. 4B shows that the components of the physical computing storage device may be virtualized by the disclosed system.

[0050] Referring to FIG. 4C, an alternative implementation of system 400 is shown, where computing device 402 communicates with a computing element 450 and a storage element 452 (e.g., via PCIe or some other connection). The computing element 450 may include a processing device (e.g., an FPGA) and may correspond to computing element 106, the first computing element 218, the second computing element 220, the first computing element 306, or the second computing element 312 described above. The storage element 452 may include a non-volatile storage device (e.g., a non-computing storage device) and may correspond to storage element 108, the first storage element 202, the second storage element 204, the first storage element 308, or the second storage element 314 described above.

[0051] The virtual computing storage emulation module 410 is configured to use the external computing element 450 and the storage element 452 to provide the functionality of the virtual computing storage devices 414 and 418. Thus, the virtual computing storage emulation module 410 can translate the computing requests for the virtual computing storage devices 414 and 418 into computing requests for the computing element 450, and translate the storage requests for the virtual computing storage devices 414 and 418 into storage requests for the storage element 452, as described above. Thus, FIG. 4C shows that a computing device (e.g., a server) can use external components to provide virtual computing storage device functionality.

[0052] FIG. 4D shows that the virtual computing storage emulation module 410 can use any combination of the devices described with reference to FIGS. 4A-4C to provide a virtual computing storage device. Thus, the virtual computing storage emulation module 410 can provide a virtual computing device that corresponds to an internal (corresponding to the device executing the virtual computing storage emulation module) processing element, an internal storage device, an external (corresponding to the device executing the virtual computing storage emulation module) processing element, an external storage device, a physical computing storage device, or any combination thereof.

[0053] FIG. 5 is a flowchart of a method 500 for providing a virtual computing storage device. The method 500 can be performed by a virtual computing storage emulation module (e.g., by one or more processors executing this module), such as the virtual computing storage emulation module 102 or the virtual computing storage emulation module 410. The method 500 includes providing a virtual computing storage device at a virtual computing storage device emulation module at 502, where the data associated with the virtual computing storage device is stored at a storage element. For example, the virtual computing storage emulation module 102 can provide the virtual computing storage device 110. The data 112 of the virtual computing storage device 110 can be stored at the storage element 108. In another example, the first data 206 of the virtual computing storage device can be stored at the first storage element 202, and the second data 208 can be stored at the second storage element 204. In another example, the virtual computing storage emulation module 102 can provide a first virtual computing storage device 302 and a second virtual computing storage device 304. The first data 310 of the first virtual computing storage device 302 can be stored at the first storage element 308, and the second data 316 of the second virtual computing storage device 304 can be stored at the second storage element 314. In another example, the first data 310 of the first virtual computing storage device 302 and the second data 316 of the second virtual computing storage device 304 can be stored at the storage element 330.

[0054] Method 500 further includes receiving, at 504, a compute request for a virtual storage device at a virtual compute storage device emulation module. For example, virtual compute storage emulation module 102 may receive compute request 114, CSD command 118, first compute request 224, second compute request 228, first compute request 352, or second compute request 354 from compute storage client 104.

[0055] Method 500 further includes sending, at 506, a translation of the compute request to a compute element. For example, virtual compute storage emulation module 102 may send a translation of compute request 114, first compute request 224, second compute request 228, first compute request 352, or second compute request 354 (e.g., hardware command 120) to compute element 106, first compute element 218, second compute element 220, first compute element 306, or second compute element 312. Generating the translation may include mapping a request in a first protocol (e.g., NVMe) to a request in a second protocol (e.g., a protocol supported by the processing element).

[0056] Thus, method 500 may provide techniques for virtualization of compute storage devices. Accordingly, a compute storage client may enjoy the benefits of a compute storage device in a system with a wide variety of underlying physical components.

[0057] In some instances, method 500 further includes initializing a virtual compute storage device. For example, virtual compute storage emulation module 102 or virtual compute storage emulation module 410 may generate one or more mapping tables of the virtual compute storage device to physical components. The mapping table may map addresses of the virtual compute storage device to addresses of physical storage devices. The mapping table may further map the virtual compute storage device to compute elements. Physical components may be assigned to the virtual compute storage device, and the mapping table may be set based on commands from the compute storage client, based on a load balancing algorithm, or a combination thereof.

[0058] FIG. 5B is a flowchart of a method 510 for providing a virtual computing storage device that supports storage requests. The method 510 may be performed by a virtual computing storage emulation module (e.g., by one or more processors executing this module), such as virtual computing storage emulation module 102 or virtual computing storage emulation module 410. The method 510 includes providing, at 512, a virtual computing storage device at a virtual computing storage device emulation module, where data associated with the virtual computing storage device is stored at a storage element. For example, the virtual computing storage emulation module 102 may provide the virtual computing storage device 110. The data 112 of the virtual computing storage device 110 may be stored at the storage element 108. In another example, the first data 206 of the virtual computing storage device may be stored at the first storage element 202, and the second data 208 may be stored at the second storage element 204. In another example, the virtual computing storage emulation module 102 may provide a first virtual computing storage device 302 and a second virtual computing storage device 304. The first data 310 of the first virtual computing storage device 302 may be stored at the first storage element 308, and the second data 316 of the second virtual computing storage device 304 may be stored at the second storage element 314. In another example, the first data 310 of the first virtual computing storage device 302 and the second data 316 of the second virtual computing storage device 304 may be stored at the storage element 330.

[0059] The method 510 further includes receiving, at 514, a storage request for the virtual storage device at the virtual computing storage device emulation module. For example, the virtual computing storage emulation module 102 may receive a storage request 116, a CSD command 118, a first storage request 210, a second storage request 214, a first storage request 332, or a second storage request 334 from the computing storage client 104.

[0060] The method 510 further includes sending, at 516, a translation of the storage request to the storage element. For example, the virtual computing storage emulation module 102 may send a translation of the storage request 116, the CSD command 118, the first storage request 210, the second storage request 214, the first storage request 332, or the second storage request 334 (e.g., the hardware command 120) to the storage element 108, the first storage element 202, the second storage element 204, the first storage element 308, or the second storage element 314. Generating the translation may include mapping a request in a first protocol (e.g., NVMe) to a request in a second protocol (e.g., a protocol supported by the storage element).

[0061] Thus, method 510 may provide techniques for supporting the virtualization of compute storage devices for storage commands. Accordingly, a compute storage client may enjoy the benefits of compute storage devices in a system with a wide variety of underlying physical components.

[0062] FIG. 5C is a flowchart of method 520 for a virtual compute storage device that provides command results in a compute storage format. Method 520 may be performed by a virtual compute storage emulation module (e.g., by one or more processors executing this module), such as virtual compute storage emulation module 102 or virtual compute storage emulation module 410. The method includes receiving, at 524, a command result at the virtual compute storage device emulation module from a hardware device. For example, virtual compute storage emulation module 102 may receive hardware result 122 from compute element 106 (or storage element 108). Hardware result 122 may correspond to a message generated in response to a compute or storage command. For example, hardware result 122 may include the result of a computation from compute element 106 or data retrieved from storage element 108.

[0063] Method 520 further includes sending, at 526, a translation of the hardware result to a compute storage client. For example, virtual compute storage emulation module 102 may send CSD result 124 to compute storage client 104. CSD result 124 may correspond to a translated version of hardware result 122. In some embodiments, CSD result 124 is a message compliant with the NVMe protocol, but hardware result 122 may comply with a different protocol.

[0064] Thus, method 520 may provide techniques for the virtualization of compute storage devices for returning the results of commands to a compute storage client. Accordingly, a compute storage client may enjoy the benefits of compute storage devices in a system with a wide variety of underlying physical components. It should be noted that one or more of method 500, method 510, method 520 (or aspects thereof) may be combined and / or performed by the same device.

[0065] FIG. 6 is a block diagram of a computing system 600 that may provide a virtual compute storage device. Computing system 600 includes a computing device 602. Computing device 602 may correspond to computing device 402 described above. Computing device 602 includes a processor device 606 and a memory device 608. Processor device 606 may include a CPU, CPU cores, another type of processor device, or a combination thereof.

[0066] The memory device 608 may include non-volatile memory, volatile memory, or a combination thereof. As used herein, the memory device 608 is a manufactured article. The memory device 608 stores virtual compute storage device (CSD) instructions 610 that can be executed by the processor device 606 to provide a virtual compute storage device. The virtual CSD instructions may correspond to the virtual compute storage emulation module 102, the hypervisor 408, the virtual compute storage emulation module 410, or a combination thereof. The virtual CSD instructions 610 can be executed by the processor device 606 to perform one or more of the methods 500, 510, 520.

[0067] The computing system 600 further includes a storage device 612. The storage device 612 may correspond to a non-volatile storage device, such as a solid state drive or another storage device.

[0068] The computing device further includes a communication interface 614 configured to communicate with external components. The communication interface 614 may correspond to an Ethernet interface, an IEEE 802.11 interface, a PCIe interface, a SATA interface, a SAS interface, another type of interface, or a combination thereof. In some embodiments, the communication interface 614 may be configured to send messages to and / or receive messages from a compute storage client (such as the compute storage client 104).

[0069] The communication interface 614 is connected to a compute storage device 616, a storage device 618, and a processor device 620. The virtual CSD instructions 610 can be executed by the processor device 606 to provide a virtual compute storage device that utilizes one or more compute elements and one or more storage elements. The one or more compute elements may include the processor device 606, the compute storage device 616, the processor device 620, or a combination thereof. The one or more storage elements may include the storage device 612, the compute storage device 616, the storage device 618, or a combination thereof. The processor device 606 may correspond to the compute element 106, the first compute element 218, the second compute element 220, the first compute element 306, the second compute element 312, the compute element 404, the first compute element 434, the second compute element 438, the compute element 450, or a combination thereof. The compute storage device 616 may correspond to the compute element 106, the first compute element 218, the second compute element 220, the first compute element 306, the second compute element 312, the first compute storage device 430, the second compute storage device 432, or a combination thereof. The processor device 620 may correspond to the compute element 106, the first compute element 218, the second compute element 220, the first compute element 306, the second compute element 312, the compute element 450, or a combination thereof.

[0070] In some embodiments, the memory device 608 further includes instructions executable by the processor device 606 to provide a compute storage client, such as the compute storage client 104, the first virtual machine 412, the second virtual machine 416, or a combination thereof.

[0071] The storage device 612 may correspond to the storage element 108, the first storage element 202, the second storage element 204, the first storage element 308, the second storage element 314, the storage element 330, the first storage element 308, the second storage element 314, the storage element 406, or a combination thereof. The compute storage device 616 may correspond to the storage element 108, the first storage element 202, the second storage element 204, the first storage element 308, the second storage element 314, the storage element 330, the first storage element 308, the first compute storage device 430, the second compute storage device 432, or a combination thereof. The storage device 618 may correspond to the storage element 108, the first storage element 202, the second storage element 204, the first storage element 308, the second storage element 314, the storage element 330, the first storage element 308, the storage element 452, or a combination thereof.

[0072] Thus, the computing system 600 may provide virtualization of compute storage devices, as described herein. The computing system 600 may include more or fewer components than shown. For illustration, some examples may not include the compute storage device 616, the storage device 618, the processor device 620, or any combination thereof.

[0073] Certain embodiments may be implemented in one or a combination of hardware, firmware, and software, or hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device that can be read and executed by at least one processor to perform the operations described herein. The computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine, e.g., a computer. For example, the computer-readable storage device may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and other storage devices and media.

[0074] The term "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any embodiment described herein as "exemplary" should not be construed as being preferred or advantageous over other embodiments. As used herein, the terms "computing device", "user device", "communication station", "station", "handheld device", "mobile device", "wireless device", and "user equipment" (UE) refer to a wireless communication device, such as a cellular phone, smartphone, tablet computer, laptop computer, wireless terminal, notebook computer, femtocell, high data rate (HDR) subscriber station, access point, printer, point-of-sale device, access terminal, or another personal communication system (PCS) device. The device may be mobile or stationary.

[0075] As used in this document, the term "communicate" is intended to include transmitting or receiving or both transmitting and receiving. This may be particularly applicable in the claims when describing the organization of data transmitted by one device and received by another device, provided that only the functionality of one of those devices violates the claims. Similarly, when only the functionality of one of those devices is claimed, a two-way exchange of data between the two devices (both devices transmitting and receiving during the exchange) may be described as "communicating". As used herein with respect to wireless communication signals, the term "communicate" includes transmitting wireless communication signals and / or receiving wireless communication signals. For example, a wireless communication unit capable of conveying wireless communication signals may include a wireless transmitter for transmitting wireless communication signals to at least one other wireless communication unit, and / or a wireless communication receiver for receiving wireless communication signals from at least one other wireless communication unit.

[0076] Some embodiments can be used in conjunction with various devices and systems such as the following: personal computer (PC), desktop computer, mobile computer, laptop computer, notebook computer, tablet computer, server computer, handheld computer, handheld device, personal digital assistant (PDA) device, handheld PDA device, on-board device, off-board device, hybrid device, vehicle device, non-vehicle device, mobile or portable device, consumer device, non-mobile or non-portable device, wireless communication station, wireless communication device, wireless access point (AP), wired or wireless router, wired or wireless modem, video device, audio device, audio-video (A / V) device, wired or wireless network, wireless local area network, wireless video area network (WVAN), local area network (LAN), wireless LAN (WLAN), personal area network (PAN), wireless PAN (WPAN), and the like.

[0077] Some embodiments can be used in conjunction with the following: unidirectional and / or bidirectional wireless communication systems, cellular radiotelephone communication systems, mobile phone, cellular phone, radiotelephone, personal communication system (PCS) device, PDA device incorporating a wireless communication device, mobile or portable global positioning system (GPS) device, device incorporating a GPS receiver or transceiver or chip, device incorporating an RFID element or chip, multiple input multiple output (MIMO) transceiver or device, single input multiple output (SIMO) transceiver or device, multiple input single output (MISO) transceiver or device, device having one or more internal antennas and / or external antennas, digital video broadcast (DVB) device or system, multi-standard wireless device or system, wired or wireless handheld device (e.g., smart phone), wireless application protocol (WAP) device, or the like.

[0078] Some embodiments may be used in connection with one or more types of wireless communication signals and / or systems that follow one or more wireless communication protocols, such as Radio Frequency (RF), Infrared (IR), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), Extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, Single-Carrier CDMA, Multi-Carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth™, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra-Wideband (UWB), Global System for Mobile communication (GSM), 2G, 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE Advanced, Enhanced Data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in a variety of other devices, systems, and / or networks.

[0079] Although example processing systems have been described above, embodiments of the subject matter and functional operations described herein may be implemented in other types of digital electronic circuitry or in computer software, firmware, or hardware (including the structures disclosed in this specification and their structural equivalents) or in a combination of one or more of them.

[0080] Examples of the subject matter and operations described in this disclosure may be implemented in digital electronic circuitry, or in computer software, firmware, or hardware (including the structures disclosed in this specification and their structural equivalents), or in combinations of one or more of them. Embodiments of the subject matter described in this disclosure may be implemented as one or more computer programs encoded on a computer storage medium (i.e., one or more components of computer program instructions) for execution by, or to control the operation of, an information / data processing apparatus. Alternatively or additionally, the program instructions may be encoded on an artificially-generated propagated signal (e.g., a machine-generated electrical, optical, or electromagnetic signal) that has been generated to encode information / data for transmission to a suitable receiver apparatus for execution by the information / data processing apparatus. The computer storage medium may be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Further, when the computer storage medium is not a propagated signal, the computer storage medium may be a source or destination of computer program instructions encoded in an artificially-generated propagated signal. The computer storage medium may also be one or more individual physical components or media (e.g., multiple CDs, disks, or other storage devices) or be included in one or more individual physical components or media.

[0081] The operations described in this disclosure may be implemented as operations performed by an information / data processing apparatus on information / data stored on one or more computer-readable storage devices or received from other sources.

[0082] The term “data processing apparatus” encompasses all kinds of devices, apparatuses, and machines for processing data, including (by way of example) programmable processors, computers, system-on-a-chip, or multiple or combinations of the foregoing. The apparatus may include dedicated logic circuitry, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). In addition to hardware, the apparatus may also include code that creates an execution environment for the computer programs being discussed, such as code that constitutes processor firmware, protocol stack, database management system, operating system, cross-platform runtime environment, virtual machine, or a combination of one or more of them. The apparatus and the execution environment may implement various different computing model infrastructures, such as web services, distributed computing, and grid computing infrastructures.

[0083] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language (including compiled or interpreted languages), and it can be deployed in any form (including as a standalone program or as a component, module, subroutine, object, or other unit suitable for a computing environment). A computer program may or may not correspond to a file in a file system. The program can be stored as part of a file that holds other programs or information / data (e.g., one or more scripts stored in a markup language document), stored in a single file dedicated to the program in question, or stored in multiple coordinated files (e.g., files that store one or more components, subroutines, or portions of code). A computer program can be deployed to execute on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0084] The processes and logical flows described herein can be performed by one or more programmable processors that execute one or more computer programs to perform actions by operating on input information / data and generating output. Processors suitable for executing computer programs include, by way of example, both general and special purpose microprocessors, as well as any one or more processors of any kind of digital computer. In general, a processor will receive instructions and information / data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for performing actions in accordance with the instructions and one or more memory devices for storing the instructions and data. In general, a computer will also include one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, or be operatively coupled to one or more mass storage devices to receive information / data therefrom, or to transfer information / data thereto, or both. However, a computer need not have such devices. Devices suitable for storing computer program instructions and information / data include all forms of non-volatile memory, media, and memory devices, including, by way of example: semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM disks and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0085] To provide for interaction with a user, embodiments of the subject matter described herein may be implemented on a computer having a display device (e.g., a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor) for displaying information / data to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user may provide input to the computer. Other kinds of devices may also be used to provide for interaction with the user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input. Additionally, the computer may interact with the user by performing operations such as sending a document to and receiving a document from a device used by the user; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.

[0086] Embodiments of the subject matter described herein may be implemented in a computing system that includes backend components, such as a data server; or includes middleware components, such as an application server; or includes frontend components, such as a client computer having a graphical user interface or a web browser through which a user may interact with embodiments of the subject matter described herein; or any combination of one or more such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks (“LANs”) and wide area networks (“WANs”), the Internetwork (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

[0087] A computing system may include a client and a server. The client and the server are generally remote from each other and typically interact via a communication network. The relationship of the client to the server is generated by computer programs running on respective computers and having a client-server relationship to each other. In some embodiments, the server transmits information / data (e.g., an HTML page) to the client device (e.g., for the purpose of displaying the information / data to a user interacting with the client device and receiving user input from the user). Information / data generated at the client device (e.g., the result of user interaction) may be received at the server from the client device.

[0088] Although this specification contains many details of specific embodiments, these details should not be construed as limiting the scope of any embodiment or of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features described herein in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. Moreover, although the features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be deleted from the combination, and the claimed combination may be directed to a sub-combination or variant of a sub-combination.

[0089] Similarly, although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed to achieve a desirable result. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

[0090] Accordingly, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the acts recited in the claims may be performed in a different order and still achieve a desirable result. Additionally, the processes depicted in the accompanying figures do not necessarily require the particular order shown or sequential order to achieve a desirable result. In certain embodiments, multitasking and parallel processing may be advantageous.

[0091] Benefiting from the foregoing description and the teachings presented in the associated drawings, those of ordinary skill in the art to which these embodiments pertain will appreciate many modifications and other embodiments of the disclosure set forth herein. Accordingly, it is to be understood that the embodiments are not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Brief Description of the Drawings

Claims

1. A system for a virtual computing storage device, comprising: A virtual computing storage simulation module, configured to provide a virtual computing storage device; A storage element, wherein the virtual computing storage simulation module is configured to store data associated with the virtual computing storage device at the storage element; and computing elements, wherein the virtual computing storage emulation module is configured to send computing requests associated with the virtual computing storage device to the computing elements, wherein the virtual computing storage emulation module is implemented by software executed by a processing device, and wherein the virtual computing storage emulation module is further configured to send data retrieved from the storage element to the computing elements in response to the computing requests.

2. The system of claim 1, wherein the storage element includes a solid-state drive, and wherein the storage element and the computing element correspond to components of a computing storage device.

3. The system as claimed in claim 1, wherein the storage element and the computing element correspond to components of a server device.

4. The system as claimed in claim 1, wherein the storage element corresponds to a component of a storage device, and wherein the computing element corresponds to a component of a device other than the storage device.

5. The system as described in claim 1, wherein the virtual computing storage emulation module is further configured to announce the availability of the virtual computing storage device.

6. The system as claimed in claim 1, wherein the system further includes a second storage element, wherein the virtual computing storage emulation module is configured to store second data associated with the virtual computing storage device at the second storage element.

7. The system of claim 6, wherein a first address range of the virtual computing storage device is associated with the storage element, a second address range of the virtual computing storage device is associated with the second storage element, and wherein the virtual computing storage emulation module is configured to: store the data at the storage element in response to a first request to store the data indicating the first address range; and store the second data at the second storage element in response to a second request to store the second data indicating the second address range.

8. The system as claimed in claim 6, wherein the virtual computing storage simulation module is configured to select the second storage element for storing the second data based on a load balancing algorithm.

9. The system as claimed in claim 1, wherein the system further includes a second computing element, wherein the virtual computing storage emulation module is configured to send a second computing request associated with the virtual computing storage device to the second computing element.

10. The system of claim 9, wherein the virtual computing storage simulation module is configured to select the second computing element for the second computing request based on the address of data associated with the second computing request.

11. The system of claim 9, wherein the virtual computing storage simulation module is configured to select the second computing element for the second computing request based on a load balancing algorithm.

12. The system as claimed in claim 1, wherein the virtual computing storage emulation module is further configured to provide a second virtual computing storage device.

13. The system of claim 12, wherein the virtual computing storage emulation module is further configured to store second data associated with the second virtual computing storage device at the storage element.

14. The system of claim 12, wherein the virtual computing storage emulation module is configured to send a second computing request associated with the second virtual computing storage device to the computing element.

15. A method for a virtual computing storage device, comprising: A virtual computing storage device is provided at the virtual computing storage device simulation module, wherein data associated with the virtual computing storage device is stored at the storage element; The virtual computing storage device emulation module receives a computing request for a virtual storage device; translates and sends the computing request to a computing element; and responds to the computing request by sending data extracted from the storage element to the computing element, wherein the virtual computing storage device emulation module is implemented by software executed by a processing device.

16. The method of claim 15, wherein the translation of sending the computation request includes translating the address of the virtual computing storage device identified by the computation request into the translated address of the storage element.

17. The method of claim 15, wherein the translation of sending the computation request comprises translating the computation request from a first protocol to a second protocol.

18. The method of claim 15, further comprising: Receive a storage request that identifies the first address of the virtual computing storage device; And send a translated storage request to the storage element, the translated storage request identifying the translated address of the storage element.

19. A system for a virtual computing storage device, comprising: The computing element of the first device; Storage element of the second device; Compute storage on the user end; And a processor, configured to: receive computing requests from the computing storage user terminal; Translate and send the computation request to the computing element of the first device; receive a storage request from the computing storage user terminal; and translate and send the storage request to the storage element of the second device; And in response to the computing request, data retrieved from the storage element of the second device is sent to the computing element of the first device.

20. The system as claimed in claim 19, wherein the computing element corresponds to a field programmable gate array (FPGA).

Citation Information

Patent Citations

  • Hardware-based virtualization of input / output (I / O) memory management unit

    CN111133425A

  • Virtual bands concentration for self encrypting drives

    TW201521413A

  • Cache management method for storage device

    US20040193803A1

  • Unified address translation for virtualization of input / output devices

    WO2019132976A1