Abstract: A method for charging a battery comprises: measuring a battery voltage with a voltage sensor and a battery current with a current sensor; applying, with a charging circuit, a first charging current to the battery until the measured battery voltage exceeds a predetermined voltage threshold, a magnitude of the first charging current being held at a first constant value; applying, with the charging circuit, in response to the measured battery voltage exceeding the predetermined voltage threshold, a second charging current to the battery until a cutoff criterion is satisfied, a magnitude of the second charging current being such that the battery voltage exceeds a steady state voltage limit for the battery; after the cutoff criterion is satisfied, determining a rest voltage of the battery; and updating the cutoff criterion based on a difference between the determined rest voltage and a target rest voltage.

Abstract: A handheld power tool battery pack included a housing in which at least one battery cell and an electronic system including a circuit board are situated, at least one light emitting element being situated on the circuit board. An elastic and transparent protection element is situated between the at least one light emitting element and the housing.

Abstract: A battery pack for a handheld power tool has a battery pack housing, at least one cell holder having at least one battery cell, and a battery pack electronics unit that includes at least one flexible, in particular bendable, circuit board.

Abstract: The approaches described herein implement synchronous execution of a user space operation from a kernel context. A thread, executing on a computing device, initializes a second kernel stack based on a first kernel stack. The computing device executes an operating system having a user space and a kernel space. The thread, executing in kernel space, performs a non-blocking call (e.g., an upcall) to execute an upcall function in user space. The upcall function may further call other user space functions or system calls. The system calls are performed using the second kernel stack. Upon termination of the upcall function, the thread continues execution on the first kernel stack.

Abstract: Techniques for enabling filter-level access to a virtual disk (VMDK) are provided. In one set of embodiments, an application can invoke a first application programming interface (API) for opening the VMDK, the invoking of the first API causing an ordered group of filters associated with the VMDK to be instantiated. The application can further coordinate with a target filter in the ordered group of filters to establish a communication channel with the target filter and can receive, from the target filter, a handle to the target filter via the communication channel. The application can then issue an I/O request to the VMDK via the target filter using the handle, the issuing causing data associated with the I/O request to be filtered by other filters that are downstream from the target filter in the ordered group.

Abstract: A method for charging a battery comprises: measuring a battery voltage with a voltage sensor and a battery current with a current sensor; applying, with a charging circuit, a first charging current to the battery until the measured battery voltage exceeds a predetermined voltage threshold, a magnitude of the first charging current being held at a first constant value; applying, with the charging circuit, in response to the measured battery voltage exceeding the predetermined voltage threshold, a second charging current to the battery until a cutoff criterion is satisfied, a magnitude of the second charging current being such that the battery voltage exceeds a steady state voltage limit for the battery; after the cutoff criterion is satisfied, determining a rest voltage of the battery; and updating the cutoff criterion based on a difference between the determined rest voltage and a target rest voltage.

Abstract: A method for charging a battery comprises: measuring a battery voltage with a voltage sensor and a battery current with a current sensor; applying, with a charging circuit, a first charging current to the battery until the measured battery voltage exceeds a predetermined voltage threshold, a magnitude of the first charging current being held at a first constant value; applying, with the charging circuit, in response to the measured battery voltage exceeding the predetermined voltage threshold, a second charging current to the battery until a cutoff criterion is satisfied, a magnitude of the second charging current being such that the battery voltage exceeds a steady state voltage limit for the battery; after the cutoff criterion is satisfied, determining a rest voltage of the battery; and updating the cutoff criterion based on a difference between the determined rest voltage and a target rest voltage.

Abstract: An angle grinder includes a housing, a drive unit configured to drive a usage tool, a sensor device configured to provide a rotation parameter, and a control unit configured to evaluate the rotation parameter to detect a clamped state of the usage tool. The sensor device has a yaw rate sensor configured to provide the rotation parameter in accordance with a rotational movement of the housing. The control unit triggers a safety mode in accordance with the rotation parameter or throttles the rotational speed and/or torque of the drive unit.

Abstract: The approaches described herein implement synchronous execution of a user space operation from a kernel context. A thread, executing on a computing device, initializes a second kernel stack based on a first kernel stack. The computing device executes an operating system having a user space and a kernel space. The thread, executing in kernel space, performs a non-blocking call (e.g., an upcall) to execute an upcall function in user space. The upcall function may further call other user space functions or system calls. The system calls are performed using the second kernel stack. Upon termination of the upcall function, the thread continues execution on the first kernel stack.

Abstract: A battery pack for a handheld power tool, having a cell holder that accommodates at least one battery cell, the battery cell having a cladding surface that runs parallel to a longitudinal axis, the cladding surface being limited by two end faces that run perpendicular to the longitudinal axis, and the cladding surface and the end faces forming an outer shell of the battery cell, and a battery pack electronics. The battery pack electronics includes at least one circuit board having contact elements for producing an electrical connection between the battery pack and the handheld power tool, in addition at least one contact arrangement corresponding to the battery cell is provided, the contact arrangement electrically contacting the corresponding battery cell at the cladding surface.

Abstract: A method for processing a read request comprises intercepting a read request that includes a logical block address (LBA) of the storage device by an IO filter driver and retrieving a disk identifier (ID) associated with the LBA from a metadata file associated with the storage device. The method further comprises sending the LBA and the disk ID to a daemon configured to read and write to a cache. If the daemon returns cached data associated with the LBA and the disk ID, the method returns the cached data in response to the read request. If the daemon does not return cached data associated with the LBA and the disk ID, the method transmits the read request to the storage device.

Abstract: A rechargeable battery pack including at least one interface for establishing a mechanical and/or electrical connection of the rechargeable battery pack to a hand-held power tool and/or a charging device. The interface includes contact elements for the electrical and/or mechanical contacting of corresponding contact elements on the hand-held power tool and/or corresponding contact elements on the charging device, at least one contact element being a signal contact element electrically connected to a coding element. The rechargeable battery pack also includes a rechargeable battery pack electronics system configured for providing information regarding the rechargeable battery pack via the signal contact element, and storing at least in part in the coding element, and a microcontroller connected to the rechargeable battery pack electronics system in such a way that the microcontroller detects when information is called up at the signal contact element by a hand-held power tool and/or by a charging device.

Abstract: A circuit board, which includes at least one contact surface for electrical contacting with a contact partner, so that an electric current may be transferred between the circuit board and the contact partner, the circuit board including structures in at least one contact area, which are designed to pierce through contaminant layers and/or oxide layers present on the contact partner, the contact area including the contact surface.

Abstract: A dynamic content disk for a virtual computing instance is created as a thinly-provisioned virtual disk having a file system that is synthesized in accordance with a set of applications that are provisioned for a virtual machine (VM). To limit the allocated size of the dynamic content disk, a filter is attached to the dynamic content disk to intercept input-output operations (IOs) directed to the dynamic content disk and convert them to IOs directed to an application virtual disk that stores the actual files of the applications that are provisioned for the VM. The application virtual disk may be stored on different back-ends, such as storage area network (SAN), network file system, virtual SAN, cloud storage, or local storage.

Abstract: Exemplary methods, apparatuses, and systems include a first input/output (I/O) filter receiving, from a first filter module within a virtualization stack of a host computer, an input/output (I/O) request originated by a virtual machine and directed to a first virtual disk. The first I/O filter determines to redirect the I/O request to a second virtual disk and, in response, forwards the I/O request to a second I/O filter associated with the second virtual disk. The first I/O filter is a part of a first instance of a filter framework within the host computer and the second I/O filter is part of a second, separate instance of the filter framework.

Abstract: A dynamic content disk for a virtual computing instance is created as a thinly-provisioned virtual disk having a file system that is synthesized in accordance with a set of applications that are provisioned for a virtual machine (VM). To limit the allocated size of the dynamic content disk, a filter is attached to the dynamic content disk to intercept input-output operations (IOs) directed to the dynamic content disk and convert them to IOs directed to an application virtual disk that stores the actual files of the applications that are provisioned for the VM. The application virtual disk may be stored on different back-ends, such as storage area network (SAN), network file system, virtual SAN, cloud storage, or local storage.

Abstract: A method for opening a virtual disk comprises reading information from a metadata file that identifies the current owner of the virtual disk. The method further includes sending a release request to the current owner of the virtual disk to release the virtual disk, writing information to the metadata file identifying the new owner, and then opening the virtual disk.

Abstract: The approaches described herein implement execution of a user space operation from a kernel context. A thread, executing on a computing device, initializes a second kernel stack based on a first kernel stack. The computing device executes an operating system having a user space and a kernel space. The thread, executing in kernel space, performs a non-blocking call (e.g., an upcall) to execute an upcall function in user space, such as filtering input/output (I/O) requests. The upcall function may further call other user space functions or system calls. The system calls are performed using the second kernel stack. Upon termination of the upcall function, the thread continues execution on the first kernel stack in kernel space. For example, the thread handles the filtered I/O commands.

Abstract: Techniques for enabling secure cross-process memory sharing are provided. In one set of embodiments, a first user process executing on a computer system can create a memory handle representing a memory space of the first user process. The first user process can further define one or more access restrictions with respect to the memory handle. The first user process can then transmit the memory handle to a second user process executing on the computer system, the memory handle enabling the second user process to access at least a portion of the first process' memory space, subject to the one or more access restrictions.

Abstract: Techniques for enabling filter-level access to a virtual disk (VMDK) are provided. In one set of embodiments, an application can invoke a first application programming interface (API) for opening the VMDK, the invoking of the first API causing an ordered group of filters associated with the VMDK to be instantiated. The application can further coordinate with a target filter in the ordered group of filters to establish a communication channel with the target filter and can receive, from the target filter, a handle to the target filter via the communication channel. The application can then issue an I/O request to the VMDK via the target filter using the handle, the issuing causing data associated with the I/O request to be filtered by other filters that are downstream from the target filter in the ordered group.