Abstract: Provided are systems, methods, and apparatuses for transferring programs from a host to a computational storage device is described. The method can include: determining a program to transfer from a host to a computational storage device, determining that a size of the program exceeds a predetermined threshold, and transferring, based on the size, at least a portion of the program to the computational storage device.

Abstract: A topology is disclosed. The topology may include at least one Non-Volatile Memory Express (NVMe) Solid State Drive (SSD), a Field Programmable Gate Array (FPGA) to implement one or more functions supporting the NVMe SSD, such as data acceleration, data deduplication, data integrity, data encryption, and data compression, and a Peripheral Component Interconnect Express (PCIe) switch. The PCIe switch may communicate with both the FPGA and the NVMe SSD.

Abstract: A storage device may include a storage medium, a storage device controller coupled to the storage medium, a host interface coupled to the storage device controller, and an attachable module interface configured to connect an attachable compute module to the storage device controller. The attachable module interface may include a data interface, a side-band interface, and/or a power interface. The attachable module interface may include a connector configured to connect the attachable compute module to the storage device controller. The storage device may include an enclosure having an opening configured to enable the attachable compute module to be connected to the attachable module interface through the opening. The storage device controller may be configured to utilize one or more resources of the attachable compute module. The storage device controller may be configured to communicate with the attachable compute module through one or more command extensions of a storage protocol.

Abstract: Embodiments of the present invention include a drive-to-drive storage system comprising a host server having a host CPU and a host storage drive, one or more remote storage drives, and a peer-to-peer link connecting the host storage drive to the one or more remote storage drives. The host storage drive includes a processor and a memory, wherein the memory has stored thereon instructions that, when executed by the processor, causes the processor to transfer data from the host storage drive via the peer-to-peer link to the one or more remote storage drives when the host CPU issues a write command.

Abstract: A topology is disclosed. The topology may include at least one Non-Volatile Memory Express (NVMe) Solid State Drive (SSD), a Field Programmable Gate Array (FPGA) to implement one or more functions supporting the NVMe SSD, such as data acceleration, data deduplication, data integrity, data encryption, and data compression, and a Peripheral Component Interconnect Express (PCIe) switch. The PCIe switch may communicate with both the FPGA and the NVMe SSD.

Abstract: Provided are systems, methods, and apparatuses for providing storage-efficient sensors. A method can include: using a discovery service to determine one or more parameters associated with a storage device via a network over a medium; transmitting data from at least one sensor to a storage device via the network over the medium; processing the data and storing at least a portion of the data at the storage device; and transmitting at least a second portion of the data via the network to at least one host.

Abstract: A device may include a device memory, and a device functionality circuit, wherein at least a portion of the device functionality circuit may be capable of accessing at least a portion of the device memory, and a control circuit configured to provide information, wherein the information may indicate that the at least a portion of the device functionality circuit may be capable of accessing the at least a portion of the device memory. Additionally, or alternatively, the control circuit may be configured to receive at least one request, and perform, based on the at least one request, a configuration operation, wherein the configuration operation may include configuring at least a portion of the device memory to be accessed by the at least a portion of the device functionality circuit.

Abstract: A Lightweight Bridge (LWB) is disclosed. The LWB may be a circuit. An endpoint of the LWB that may expose a plurality of Physical Functions (PFs) to a host. A root port of the LWB may connect to a device and determine the PFs and Virtual Functions (VFs) exposed by the device. An Application Layer-Endpoint (APP-EP) and an Application Layer-Root Port (APP-RP) may translate between the PFs exposed by the endpoint and the PFs/VFs exposed by the device. The APP-EP and the APP-RP may implement a mapping between the PFs exposed by the endpoint and the PFs/VFs exposed by the device.

Abstract: An apparatus may include a device including at least one computational resource configured to perform a computational device function, and a circuit configured to access, based on an identifier, the computational device function, wherein the identifier may include protocol information for the computational device function. The protocol information may include information to pass a parameter. The information to pass the parameter may include information to pass a parameter to the computational device function. The information to pass the parameter may indicate a parameter passing technique. The parameter passing technique may include passing the parameter with a command. The parameter passing technique may include passing the parameter using a reference to the parameter. The identifier may include a first portion including at least a portion of the protocol information. The identifier may include a second portion including information to identify a functionality of the computational device function.

Abstract: Embodiments of the present invention include a drive-to-drive storage system comprising a host server having a host CPU and a host storage drive, one or more remote storage drives, and a peer-to-peer link connecting the host storage drive to the one or more remote storage drives. The host storage drive includes a processor and a memory, wherein the memory has stored thereon instructions that, when executed by the processor, causes the processor to transfer data from the host storage drive via the peer-to-peer link to the one or more remote storage drives when the host CPU issues a write command.

Abstract: Provided are systems, methods, and apparatuses for providing storage-efficient sensors. A method can include: using a discovery service to determine one or more parameters associated with a storage device via a network over a medium; transmitting data from at least one sensor to a storage device via the network over the medium; processing the data and storing at least a portion of the data at the storage device; and transmitting at least a second portion of the data via the network to at least one host.

Abstract: A storage device is disclosed. The storage device may include storage for data and at least one Input/Output (I/O) queue for requests from at least one virtual machine (VM) on a host device. The storage device may support an I/O queue creation command to request the allocation of an I/O queue for a VM. The I/O queue creation command may include an LBA range attribute for a range of Logical Block Addresses (LBAs) to be associated with the I/O queue. The storage device may map the range of LBAs to a range of Physical Block Addresses (PBAs) in the storage.

Abstract: A method may include allocating, using a programming interface, to an application, a resource of a computational device, tracking, using a resource manager, the resource, and determining, using the resource manager, an operation of the application. The method may further include modifying, by the resource manager, based on the determining the operation of the application, a status of at least a portion of the resource. The operation of the application may include a modification of an execution of the application. The modification may be based on an execution state of the application, for example, a valid execution state. The method may further include transferring, based on the determining the operation of the application, an execution of the application to a mechanism to control the application. The method may further include executing, based on the determining the operation of the application, a mechanism to monitor the operation of the application.

Abstract: A Lightweight Bridge (LWB) is disclosed. The LWB may be a circuit. An endpoint of the LWB that may expose a plurality of Physical Functions (PFs) to a host. A root port of the LWB may connect to a device and determine the PFs and Virtual Functions (VFs) exposed by the device. An Application Layer-Endpoint (APP-EP) and an Application Layer-Root Port (APP-RP) may translate between the PFs exposed by the endpoint and the PFs/VFs exposed by the device. The APP-EP and the APP-RP may implement a mapping between the PFs exposed by the endpoint and the PFs/VFs exposed by the device.

Abstract: A method may include creating an association identifier based on an association between a computational device function and a compute engine of a computational device, and invoking an execute command to perform an execution of the computational device function using the compute engine, wherein the execute command uses the association identifier. The compute engine may be a first compute engine, and the association may be further between the computational device function and a second compute engine of the computational device. The execute command may perform an execution of the computational device function using the second compute engine. The execution of the computational device function using the first compute engine and the execution of the computational device function using the second compute engine may overlap. The execute command may include the association identifier. The creating the association identifier may include invoking a create association command.

Abstract: Provided are systems, methods, and apparatuses for managing storage device memory. A method can include receiving, from a host, a command for managing the memory; performing, by the storage device, the command on first data stored on the memory via at least one processing element in the storage device to generate second data; and transmitting, by the storage device, third data based on the second data to the host.

Abstract: A method may include interacting with an interface for one or more computational devices, wherein the interacting is based on an identifier, and wherein the identifier comprises information that identifies a functionality of a computational device functions. The information may include a functionality identifier. The identifier may further include information that identifies a group of the computational device function. The group of the computational device function may be based on a source of the computational device function. The information that identifies the functionality of a computational device function may include a functionality identifier, and the information that identifies the group of the computational device function may include a group identifier. The functionality identifier may include a unique function identifier, and the group identifier may include an organizationally unique identifier.

Abstract: A storage device is disclosed. The storage device may include first storage for a data. A controller may manage access to the data in the storage. A second storage may store a first identifier and a second identifier, the first identifier for an event and the second identifier for a program. A processor may receive the event and execute the program based at least in part on the event table.

Abstract: A system is disclosed. The system may include a processor, a storage device, and aa computational device. A plugin may be associated with a service on the computational device. A framework may be implemented in software and configured to be executed on the processor. The framework may include a receiver to receive a service request from an application configured to be executed on the processor and a service response from the plugin. The service request may identify a service requested by the application. The framework may also include a plugin selector to select the plugin based at least in part on the service. The framework may also include a transmitter to deliver the service request to the plugin and the service response to the application. The application may be agnostic to the plugin and the computational device.

Abstract: Provided are systems, methods, and apparatuses for managing functions for storage devices. The method can include: determining one or more functions associated with a first device and determining one or more corresponding function types for the functions; grouping the functions based on the function types using a group name; and providing the group name to a second device for use in connection with an associated application, wherein the storage device comprises a computational storage (CS) device.