Abstract: A plurality of mapping modes may be shifted between in real time while maintaining continuous memory mapped access to an application. Data may be migrated between different types storage devices and/or interconnects. The shift between the plurality of mapping modes may be based on a change to the type storage device and/or type of interconnect for the data migration.

Abstract: A storage system includes a distributed file system. An attribute of a particular entity in the file system relates to a snapshot. In response to an operation in the storage system, it is determined whether the snapshot attribute is to be propagated to another entity of the file system.

Abstract: Example implementations relate to a storage memory direct access (SMDA) provider. The SMDA provider may pin a storage memory region to a memory address of a consumer machine, the storage memory region corresponding to a storage range of a storage device requested by the consumer machine. The SMDA provider may atomically commit data in the storage memory region accessed by the consumer machine via the memory address.

Abstract: According to some examples, a tenant-aware distributed file system is provided that permits a tenant to be recorded and associate the tenant with a set of file system entities in a name space in the tenant-aware distributed file system. In particular, a tenant file system entity may be defined and recorded in a tenant-aware distributed file system, and the tenant file system entity may be associated with a set of file system entities in the name space of the tenant-aware distributed file system. The tenant file system entity may be associated with a set of attributes that are to be applied by tenant-aware distributed file system to the set of file system entities associated with the tenant file system entity. The set of attributes included by a tenant file system entity can include a statically inherited attribute, a dynamically inheritable attribute, or both.

Abstract: According to an example, PM controller based atomicity assurance may include receiving data that is related to an application for storage in a PM. PM controller based atomicity assurance may further include receiving an indication of an atomic transaction that is related to the data, and receiving an indication to generate a CP that is related to the atomic transaction. The CP may be generated in a PM staging area. A determination may be made as to whether the CP in the PM staging area is closed or open. In response to a determination that the CP in the PM staging area is closed, content related to the CP may be propagated to the PM.

Abstract: A unifying memory controller (UMC) to send and receive data to and from a local host. The UMC also may manage data placement and retrieval by using an address mapper. The UMC may also selectively provide power to a plurality of memory locations. The UMC may also manage data placement based on a policy that can make use of a property stored in the metadata storage location. The property may be a property describing the data that is being managed. The UMC also may use its own local cache that may store copies of data managed by the circuit.

Abstract: Example implementations relate to a storage memory direct access (SMDA) provider. The SMDA provider may pin a storage memory region to a memory address of a consumer machine, the storage memory region corresponding to a storage range of a storage device requested by the consumer machine. The SMDA provider may atomically commit data in the storage memory region accessed by the consumer machine via the memory address.

Abstract: Example implementations may relate to a software defined networking (SDN) controller. A method may include receiving, at a SDN controller, a tagged initialization packet from a software defined network enabled switch. The method may include identifying, at the SDN controller, a tenant corresponding to or based on the tagged initialization packet. The method may include implementing a policy specific to the identified tenant.

Abstract: A plurality of segment sets of one or more storage segments of a distributed file system may be created and/or updated. The storage segments may be independently controlled. A placement policy may be assigned to each of the plurality of segment sets. The placement policy may control an initial placement and/or relocation of an object to the one or more storage segments for the assigned storage set.

Abstract: According to an example, PM controller based atomicity assurance may include receiving data that is related to an application for storage in a PM. PM controller based atomicity assurance may further include receiving an indication of an atomic transaction that is related to the data, and receiving an indication to generate a CP that is related to the atomic transaction. The CP may be generated in a PM staging area. A determination may be made as to whether the CP in the PM staging area is closed or open. In response to a determination that the CP in the PM staging area is closed, content related to the CP may be propagated to the PM.

Abstract: A unifying memory controller (UMC) to send and receive data to and from a local host. The UMC also may manage data placement and retrieval by using an address mapper. The UMC may also selectively provide power to a plurality of memory locations. The UMC may also manage data placement based on a policy that can make use of a property stored in the metadata storage location. The property may be a property describing the data that is being managed. The UMC also may use its own local cache that may store copies of data managed by the circuit.

Abstract: A plurality of mapping modes may be shifted between in real time while maintaining continuous memory mapped access to an application. Data may be migrated between different types storage devices and/or interconnects. The shift between the plurality of mapping modes may be based on a change to the type storage device and/or type of interconnect for the data migration.

Abstract: A technique includes receiving a query to a directory in a file system. In response to the query, both information targeted by the query and additional information are retrieved in anticipation of another query for the additional information.

Abstract: A technique includes receiving a request to restore a state of a file system. The request defines a rollback period, which extends from a restoration time that is specified by the request to a time at which the request was made. The technique includes reconstructing a state of the file system in response to a query using a preserved snapshot of the file system. The reconstruction including reconstructing the state at an arbitrary query time based at least in part on a dynamically inheritable attribute of an entity stored on the file system and the rollback period.

Abstract: A storage system includes a distributed file system. An attribute of a particular entity in the file system relates to a snapshot. In response to an operation in the storage system, it is determined whether the snapshot attribute is to be propagated to another entity of the file system.

Abstract: A storage system includes a distributed file system. An attribute of a particular entity in the file system relates to a snapshot. In response to an operation in the storage system, it is determined whether the snapshot attribute is to be propagated to another entity of the file system.

Abstract: Deduplication in a distributed file system is described. Key classes are determined from a set of potential keys, the potential keys used to represent file content stored by the file system. Control of the key classes is apportioned among index nodes of the file system. Nodes in the file system, during deduplication of data chunks of the file content, generate keys calculated from the data chunks. The keys are distributed among the index nodes based on relations between the keys and the key classes controlled by the index nodes.

Abstract: A first file server for use with a distributed-file system includes a processor configured to determine that an incoming file system communication is associated with a first portion of the distributed-file system associated with a second file server, send a first authorization request to the second file server to request authorization to directly access the first portion of the distributed-file system, analyze a first authorization response from the second file server to determine at least one storage location associated with the first portion of the distributed-file system, determine that an incoming second authorization request received from a third file server is associated with a second portion of the distributed-file system associated with the first file server, obtain data indicative of the second portion of the distributed-file system, and send a second authorization response that includes the data.

Abstract: A technique includes receiving a request to restore a state of a file system. The request defines a rollback period, which extends from a restoration time that is specified by the request to a time at which the request was made. The technique includes reconstructing a state of the file system in response to a query using a preserved snapshot of the file system. The reconstruction including reconstructing the state at an arbitrary query time based at least in part on a dynamically inheritable attribute of an entity stored on the file system and the rollback period.

Abstract: A technique includes receiving a query to a directory in a file system. In response to the query, both information targeted by the query and additional information are retrieved in anticipation of another query for the additional information.