Abstract: A method for determining a utilization-based fee for storing data includes determining a number of write operations for writing a quantity of data to a solid state drive (SSD) and determining an amount of a fee based on the number of write operations for writing the quantity of data to the SSD. A lifetime of the SSD can be determined based on, for example, the number of blocks in the SSD and the maximum number of write operations per block. A utilization factor for a particular workload can be determined by dividing the number of write operations in the workload by the lifetime. The value of the utilization factor can then be used to determine the amount of the fee. A bill based on the amount of the fee can be generated and transmitted.

Abstract: A method for determining a utilization-based fee for storing data includes determining a number of write operations for writing a quantity of data to a solid state drive (SSD) and determining an amount of a fee based on the number of write operations for writing the quantity of data to the SSD. A lifetime of the SSD can be determined based on, for example, the number of blocks in the SSD and the maximum number of write operations per block. A utilization factor for a particular workload can be determined by dividing the number of write operations in the workload by the lifetime. The value of the utilization factor can then be used to determine the amount of the fee. A bill based on the amount of the fee can be generated and transmitted.

Abstract: A data storage device includes a number of blocks in multiple dies and a controller configured to perform operations. A method of controlling the data storage device includes: translating logical addresses to physical addresses; activating one or more dies; writing data to one or more blocks; determining the number of write operations performed on the storage device; facilitating determination of a lifetime of the storage device based on a number of blocks, a particular number of write operations, and a maximum number of write operations per block; providing the number of write operations that have been performed to a host to facilitate determination of an amount of a fee, where providing the number of write operations facilitates tracking a percentage of the lifetime of the storage device.

Abstract: A method for determining a utilization-based fee for storing data includes determining a number of write operations for writing a quantity of data to a solid state drive (SSD) and determining an amount of a fee based on the number of write operations for writing the quantity of data to the SSD. A lifetime of the SSD can be determined based on, for example, the number of blocks in the SSD and the maximum number of write operations per block. A utilization factor for a particular workload can be determined by dividing the number of write operations in the workload by the lifetime. The value of the utilization factor can then be used to determine the amount of the fee. A bill based on the amount of the fee can be generated and transmitted.

Abstract: A method, processor, and computer system for handling interrupts within a hierarchical register structure. The method includes receiving at a root-level register an indication of an interrupt occurring at a lower level register in the register structure, using a system interrupt handler to invoke an error handler assigned to a set of registers of the structure that includes the lower level register, and using the invoked error handler to handle the interrupt and return to the system interrupt handler.

Abstract: A distributed network switch includes multiple switch modules connected by one or more physical cables. One switch module may determine which connector port of a remote switch module is connected by physical cable based on information received from the remote switch module, including link identifiers, and further based on a physical topology predetermined about the type of remote switch module.

Abstract: A method, processor, and computer system for handling interrupts within a hierarchical register structure. The method includes receiving at a root-level register an indication of an interrupt occurring at a lower level register in the register structure, using a system interrupt handler to invoke an error handler assigned to a set of registers of the structure that includes the lower level register, and using the invoked error handler to handle the interrupt and return to the system interrupt handler.

Abstract: A distributed network switch includes multiple switch modules connected by one or more physical cables. One switch module may determine which connector port of a remote switch module is connected by physical cable based on information received from the remote switch module, including link identifiers, and further based on a physical topology predetermined about the type of remote switch module.

Abstract: When testing or validating a hardware system, a script file representing a portion of the firmware may be used to test the system instead of using the firmware code itself. For example, the script file may be plurality of register commands that perform the same initialization sequence as the firmware. Before connecting the hardware system to firmware drivers, the script file may be used to debug the initialization sequence. Instead of generating this script file manually, a firmware testing tool may be used. While executing the firmware, the tool may record the different register access commands performed during the initialization process. The script file is then generated programmatically using these recorded commands without requiring input from the system designer. The generated script file may then be tested on the hardware system to determine whether the command sequence in the script file forces the hardware system into the desired state.

Abstract: A distributed network switch includes multiple switch modules connected by one or more physical cables. One switch module may determine which connector port of a remote switch module is connected by physical cable based on information received from the remote switch module, including link identifiers, and further based on a physical topology predetermined about the type of remote switch module.

Abstract: A distributed network switch includes multiple switch modules connected by one or more physical cables. One switch module may determine which connector port of a remote switch module is connected by physical cable based on information received from the remote switch module, including link identifiers, and further based on a physical topology predetermined about the type of remote switch module.

Abstract: A method, processor, and computer system for handling interrupts within a hierarchical register structure. The method includes receiving at a root-level register an indication of an interrupt occurring at a lower level register in the register structure, using a system interrupt handler to invoke an error handler assigned to a set of registers of the structure that includes the lower level register, and using the invoked error handler to handle the interrupt and return to the system interrupt handler.

Abstract: A method, processor, and computer system for handling interrupts within a hierarchical register structure. The method includes receiving at a root-level register an indication of an interrupt occurring at a lower level register in the register structure, using a system interrupt handler to invoke an error handler assigned to a set of registers of the structure that includes the lower level register, and using the invoked error handler to handle the interrupt and return to the system interrupt handler.

Abstract: When testing or validating a hardware system, a script file representing a portion of the firmware may be used to test the system instead of using the firmware code itself. For example, the script file may be plurality of register commands that perform the same initialization sequence as the firmware. Before connecting the hardware system to firmware drivers, the script file may be used to debug the initialization sequence. Instead of generating this script file manually, a firmware testing tool may be used. While executing the firmware, the tool may record the different register access commands performed during the initialization process. The script file is then generated programmatically using these recorded commands without requiring input from the system designer. The generated script file may then be tested on the hardware system to determine whether the command sequence in the script file forces the hardware system into the desired state.

Abstract: When testing or validating a hardware system, a script file representing a portion of the firmware may be used to test the system instead of using the firmware code itself. For example, the script file may be plurality of register commands that perform the same initialization sequence as the firmware. Before connecting the hardware system to firmware drivers, the script file may be used to debug the initialization sequence. Instead of generating this script file manually, a firmware testing tool may be used. While executing the firmware, the tool may record the different register access commands performed during the initialization process. The script file is then generated programmatically using these recorded commands without requiring input from the system designer. The generated script file may then be tested on the hardware system to determine whether the command sequence in the script file forces the hardware system into the desired state.

Abstract: When testing or validating a hardware system, a script file representing a portion of the firmware may be used to test the system instead of using the firmware code itself. For example, the script file may be plurality of register commands that perform the same initialization sequence as the firmware. Before connecting the hardware system to firmware drivers, the script file may be used to debug the initialization sequence. Instead of generating this script file manually, a firmware testing tool may be used. While executing the firmware, the tool may record the different register access commands performed during the initialization process. The script file is then generated programmatically using these recorded commands without requiring input from the system designer. The generated script file may then be tested on the hardware system to determine whether the command sequence in the script file forces the hardware system into the desired state.