Abstract: In accordance with some embodiments, raw data in a first data format may be generated or received. Then, the raw data may be transformed to cloud data in a second data format. Finally, the cloud data may be transformed into device data in a third data format.

Abstract: In accordance with some embodiments, identification of transport streams facilitates the classification of those streams. Classification of those streams in turn enables a classification to be matched to a quality of service policy. Thus, quality of service policies may be enforced so that different streams can be afforded appropriate quality of service.

Abstract: In accordance with some embodiments, classification of input/output requests from a database to a storage system may be performed. Each input/output request may be associated with a database class, and each database class may be mapped to a quality of service policy. Thus, quality of service may be enforced such that different data blocks within the storage system of the database may be afforded appropriate quality of service.

Abstract: Storage class memory may be used in an architecture to achieve high performance, high reliability, high compatibility. In some embodiments, reads may be handled in a conventional way used in a memory based model. However writes do not use a memory based model but instead correspond to a storage based model. The hybrid nature can be achieved by setting the storage class memory to be write protected so that all writes must go through a software based block device interface. In some embodiments, the software based block device interface prevents erroneous writes to the storage class memory.

Abstract: A storage unit may have an associated processor and storage controller. The storage controller associated with the storage unit may store a mapping of objects (i.e., data) to blocks in the storage unit. This mapping may be received from another source, such as a file system, database, or software application, among other possibilities. The processor associated with the storage unit may execute operation s on the objects stored in the storage unit.

Abstract: A device, system, and method are disclosed. In one embodiment, a device includes caching logic that is capable of receiving an I/O storage request from an operating system. The I/O storage request includes an input/output (I/O) data type tag that specifies a type of I/O data to be stored or loaded with the I/O storage request. The caching logic is also capable of determining, based at least in part on a priority level associated with the I/O data type, whether to allocate cache to the I/O storage request.

Abstract: A storage device includes encryption policies that may be applied to data stored thereon. Different encryption policies may be applied to different data on the storage device. Input/output (I/O) requests may identify the appropriate encryption policy to be applied using a data tag of the I/O request. The data tag may be applied by the file system when the I/O request is issued, or may be added by a filter driver before the I/O request is delivered to the storage device.