Abstract: A method for transmitting a source file includes receiving at least one input relating to the transmission of the data; selecting a transmission strategy using the at least one input; processing the data using the selected transmission strategy; transmitting the processed data; transmitting metadata defining the selected transmission strategy; and processing the transmitted data using the transmitted metadata. A related system may include a transmission system and receiving station configured to perform such a method.

Abstract: An edge processing system includes first and second information handling systems. The first information handling system orchestrates the edge processing system, and creates a first key pair including a first private key and a first public key. The second information handling system receives fabric agent code that includes the first public key, a second key pair including a second private key and a second public key, and an address of the first information handling system. The second information handling system executes the fabric agent code to provide an access request to the address. The access request is encoded with the first public key. The first information handling system authenticates the access request with the first private key, and provides external compute fabric code to the second information handling system in response to authenticating the access request. The second information handling system instantiates the external compute fabric code to manage end points of the edge processing system.

Abstract: Disclosed herein are techniques for use in managing data storage. For example, in one embodiment, the techniques comprise determining a size of the write request. The size of the write request equating to half or more non-parity data portions in a full stripe of data but less than all non-parity data portions in the full stripe.

Abstract: Techniques are disclosed for determining ownership of a data segment. The techniques include providing a data segment in a data storage appliance that facilitates multiple references of the data segment by one or more storage entities. The techniques also include maintaining a plurality of counts in connection with the data segment, the plurality of counts comprising (i) a first count representing a sum of first values that identify the respective storage entities associated with each reference of the data segment, (ii) a second count representing a sum of second values that derive from key values of the respective storage entities associated with each reference of the data segment, and (iii) a third count representing a number of references of the data segment by the respective storage entities. The techniques also include determining whether the said storage entity exclusively owns the data segment based on the plurality of counts and a key value of one of the respective storage entities.

Abstract: Systems and methods are described for the coaching of users through successful calibration of a myoelectric prosthetic controller. The systems and methods are comprised of, and/or utilize, hardware and software components to input and analyze electromyography (EMG) based signals in association with movements, and to calibrate and output feedback about the signals. The hardware is further comprised of an apparatus for the detection of EMG signals, a prosthesis, an indicator, and a user interface. The software is further comprised of a user interface, a pattern recognition component, a calibration procedure, and a feedback mechanism. The systems and methods facilitate calibration of a myoelectric controller and provides the user with feedback about the calibration including information of the signal inputs and outputs, and messages about connected hardware and how to optimize signal data.

Abstract: Techniques are disclosed for determining ownership of a data segment. The techniques include providing a data segment in a data storage appliance that facilitates multiple references of the data segment by one or more storage entities. The techniques also include maintaining a plurality of counts in connection with the data segment, the plurality of counts comprising (i) a first count representing a sum of first values that identify the respective storage entities associated with each reference of the data segment, (ii) a second count representing a sum of second values that derive from key values of the respective storage entities associated with each reference of the data segment, and (iii) a third count representing a number of references of the data segment by the respective storage entities. The techniques also include determining whether the said storage entity exclusively owns the data segment based on the plurality of counts and a key value of one of the respective storage entities.

Abstract: There is disclosed herein techniques for managing data storage. In one exemplary embodiment, the techniques comprise generating one or more sets of storage devices. Each set is configured to be mutually exclusive with respect to other sets of the one or more sets such that storage devices within the same set provide the basis for the formation of a RAID (Redundant Arrays of Independent Disks) stripe. The techniques further comprise forming a RAID stripe from respective storage extents associated with different storage devices of the same set. The techniques further comprise mapping a storage object to the RAID stripe. The techniques further comprise servicing host I/O (Input/Output) operations directed to the storage object by using the RAID stripe mapped thereto.

Abstract: Disclosed herein are techniques for use in managing data storage. For example, in one embodiment, the techniques comprise determining a size of the write request. The size of the write request equating to half or more non-parity data portions in a full stripe of data but less than all non-parity data portions in the full stripe.

Abstract: Techniques for preserving locality of storage accesses to copies of storage objects in a cluster of appliances. Mapping metadata is created indicating regions in a copy of a storage object that are mapped to local storage allocated from a target appliance. Read and write operations to regions of the copy that are mapped to storage in the target appliance are processed within the target appliance. Write operations to regions that are not mapped to storage in the target appliance cause storage to be allocated to the copy in the target appliance, mapped to the regions indicated by the write operations, and used to store the write data. Read operations to regions that are not mapped to storage in the target appliance are performed on an original storage object located on a source appliance, from which the copy of the storage object was made.

Abstract: An improved technique involves processing a workflow in stages, and processing all requests in a queue for a given stage before moving onto the next stage. Along these lines, each request received by a storage processor is assigned to a core and placed in a first queue for that core. Within that core, a single system thread executes first instructions for a task, e.g., checking the storage cache for the requested data from a request, and then transfers the request to a second queue. Rather than perform additional tasks to completely satisfy the request, however, the thread executes the first instructions for a prespecified number of requests in the first queue. Only when the thread has executed instructions for the prespecified number of requests, the thread begins execution of second instructions for requests in the second queue, and work on the next task begins.

Abstract: A technique for managing spare disk drives in a data storage system includes transferring segments of data from disk drives of an operating RAID group to spare regions on a set of spare disk drives to create unused space in the disk drives of the RAID group, thus using the spare regions to overprovision storage in the RAID group. Upon a failure of one of the disk drives in the RAID group, data of the failing disk drive are rebuilt based on the segments of data as well as on data from still-functioning disk drives in the RAID group. Thus, the spare disk drives act not only to overprovision storage for the RAID group prior to disk drive failure, but also to fulfill their role as spares in the event of a disk drive failure.

Abstract: A technique for operating a Hyper-Converged Infrastructure (HCI) system includes running an IO stack on a physical computing server of the HCI system. The IO stack exposes multiple protocol endpoints for providing host applications with access to data objects. Protocol endpoints are exposed both to host applications running within the HCI system and to host applications running on external computing devices, thus enabling the HCI system to double as a data storage system with respect to external computing devices.

Abstract: A method of writing data to persistent storage includes (a) for each data block of a set of data blocks, storing data of that data block at an offset within a log segment of the persistent storage in conjunction with a logical block address (LBA) of that data block on the persistent storage, a size of the log segment being larger than a size of each data block, (b) identifying a particular log segment of the persistent storage that has become filled with data blocks, and (c) upon identifying the particular log segment as having become filled, inserting pointers to respective data blocks stored within the particular log segment into respective locations defined by the respective LBA of each respective data block within a map tree.

Abstract: A hyper-converged infrastructure (HCI) provides one or more HCI units, each HCI unit including a pair of physical computing servers coupled to shared, nonvolatile storage. The shared, nonvolatile storage of each HCI unit is dedicated to that pair of physical computing servers and provides redundant storage of application data. Each of the pair of physical computing servers runs a set of application instances and an IO (Input/Output) stack. The application instances receive client requests over a network and generate IO requests specifying reads and writes of application data. The IO stack processes the IO requests to effect the specified reads and writes in the shared non-volatile storage.

Abstract: A laparoscopic retractor (11) comprises a shaft (8) having a proximal and distal end, the distal end of the shaft being configured for adjustment from a substantially straight orientation to a curved orientation having a substantially U-shaped hook suitable for laparoscopic retraction. The proximal end of the shaft comprises a handle (1) operably connected to the distal end of the shaft for adjustment of the distal end from the substantially straight orientation to the curved orientation. The distal end of the shaft is enclosed within a flexible sheath (4) that is adapted to be inflated, and wherein a portion of the sheath covering the distal end of the shaft comprises inflatable balloon means such as one or more inflatable balloons (5) which cover the substantially U-shaped hook.

Abstract: A laparoscopic retractor (11) comprises a shaft (8) having a proximal and distal end, the distal end of the shaft being configured for adjustment from a substantially straight orientation to a curved orientation having a substantially U-shaped hook suitable for laparoscopic retraction. The proximal end of the shaft comprises a handle (1) operably connected to the distal end of the shaft for adjustment of the distal end from the substantially straight orientation to the curved orientation. The distal end of the shaft is enclosed within a flexible sheath (4) that is adapted to be inflated, and wherein a portion of the sheath covering the distal end of the shaft comprises inflatable balloon means such as one or more inflatable balloons (5) which cover the substantially U-shaped hook.