Abstract: Systems, apparatuses and methods may provide for technology that identifies a first namespace descriptor, a device memory descriptor, and a first request to execute a program on a logical volume that spans a plurality of physical drives, selects a first target drive from the plurality of physical drives based on the first namespace descriptor, and configures the first target drive to execute the program on first input data associated with the first namespace descriptor and write a first output of the program to a first memory region in an internal memory of the first target drive. In one example, the technology maps the device memory descriptor to the first memory region.

Abstract: A semiconductor chip is described. The semiconductor chip includes memory address decoder logic circuitry comprising different memory address bit manipulation paths to respectively impose different memory interleaving schemes for memory accesses directed to artificial intelligence information in a memory and non artificial intelligence information in the memory. The artificial intelligence information is to be processed with artificial intelligence logic circuitry disposed locally to the memory.

Abstract: A semiconductor chip is described. The semiconductor chip includes memory address decoder logic circuitry comprising different memory address bit manipulation paths to respectively impose different memory interleaving schemes for memory accesses directed to artificial intelligence information in a memory and non artificial intelligence information in the memory. The artificial intelligence information is to be processed with artificial intelligence logic circuitry disposed locally to the memory.

Abstract: A high availability (HA) failover manager maintains data availability of one or more input/output (I/O) resources in a cluster by ensuring that each I/O resource is available (e.g., mounted) on a hosting node of the cluster and that each I/O resource may be available on one or more partner nodes of the cluster if a node (i.e., a local node) were to fail. The HA failover manager (HA manager) processes inputs from various sources of the cluster to determine whether failover is enabled for a local node and each partner node in an HA group, and for triggering failover of the I/O resources to the partner node as necessary. For each I/O resource, the HA manager may track state information including (i) a state of the I/O resource (e.g., mounted or un-mounted); (ii) the partner node(s) ability to service the I/O resource; and (iii) whether a non-volatile log recording I/O requests is synchronized to the partner node(s).

Abstract: The turn signal riding gloves is a pair of gloves with lights integrated into an exterior surface that form turn signals or a braking signal light. Each of the pair of gloves operates independent of one another. Each of the pair of gloves includes a powering member that is wired in between a plurality of buttons and the plurality of lights. The plurality of buttons may be linearly aligned along a side surface of an index finger of the respective glove. In use, the motorcyclist simply raises an applicable hand and corresponding glove into the air, and pressing one of the plurality of buttons in order to generate a brake light signal, left turn signal, or right turn signal.

Abstract: Examples include techniques for performing read-optimized lazy erasure encoding of data streams. An embodiment includes receiving a request to write a stream of data, separating the stream into a first plurality of extents, storing a primary replica and one or more additional replicas of each extent of the separated stream to a plurality of data storage nodes, and updating a list of extents to be erasure encoded. The embodiment further includes when an erasure encoded stripe can be created, getting the data for each of the extents of the erasure encoded stripe, calculating parity extents for unencoded extents of the erasure encoded stripe, writing the parity extents to a second plurality of data storage nodes, and deleting the one or more additional replicas of the extents of the erasure encoded stripe from the first plurality of data storage nodes.

Abstract: A high availability (HA) failover manager maintains data availability of one or more input/output (I/O) resources in a cluster by ensuring that each I/O resource is available (e.g., mounted) on a hosting node of the cluster and that each I/O resource may be available on one or more partner nodes of the cluster if a node (i.e., a local node) were to fail. The HA failover manager (HA manager) processes inputs from various sources of the cluster to determine whether failover is enabled for a local node and each partner node in an HA group, and for triggering failover of the I/O resources to the partner node as necessary. For each I/O resource, the HA manager may track state information including (i) a state of the I/O resource (e.g., mounted or un-mounted); (ii) the partner node(s) ability to service the I/O resource; and (iii) whether a non-volatile log recording I/O requests is synchronized to the partner node(s).

Abstract: A high availability (HA) failover manager maintains data availability of one or more input/output (I/O) resources in a cluster by ensuring that each I/O resource is available (e.g., mounted) on a hosting node of the cluster and that each I/O resource may be available on one or more partner nodes of the cluster if a node (i.e., a local node) were to fail. The HA failover manager (HA manager) processes inputs from various sources of the cluster to determine whether failover is enabled for a local node and each partner node in an HA group, and for triggering failover of the I/O resources to the partner node as necessary. For each I/O resource, the HA manager may track state information including (i) a state of the I/O resource (e.g., mounted or un-mounted); (ii) the partner node(s) ability to service the I/O resource; and (iii) whether a non-volatile log recording I/O requests is synchronized to the partner node(s).

Abstract: A high availability (HA) failover manager maintains data availability of one or more input/output (I/O) resources in a cluster by ensuring that each I/O resource is available (e.g., mounted) on a hosting node of the cluster and that each I/O resource may be available on one or more partner nodes of the cluster if a node (i.e., a local node) were to fail. The HA failover manager (HA manager) processes inputs from various sources of the cluster to determine whether failover is enabled for a local node and each partner node in an HA group, and for triggering failover of the I/O resources to the partner node as necessary. For each I/O resource, the HA manager may track state information including (i) a state of the I/O resource (e.g., mounted or un-mounted); (ii) the partner node(s) ability to service the I/O resource; and (iii) whether a non-volatile log recording I/O requests is synchronized to the partner node(s).