Abstract: A computing system detects an input/output (I/O) device configuration error. The computing system includes at least one I/O device installed with firmware configured to control an I/O function, and a plurality of I/O ports installed on the at least one I/O device. At least one I/O port outputs a request to perform a current I/O configuration initialization and generates current I/O configuration data corresponding to the current I/O configuration initialization. A memory unit is configured to store the current I/O configuration data and previously generated I/O configuration data. The I/O device compares the current I/O configuration data to the previously generated I/O configuration data, and detects the I/O device configuration error in response to determining a mismatch between the current I/O configuration data and the previously generated I/O configuration data.

Abstract: In one aspect of buffer credit management in accordance with the present description, buffer over-commit logic determines a buffer over-commit value as, in one embodiment, proportional to a determined difference value between the average duration of an I/O operation over data transmission channels connected to a target control unit, and an average of cumulative lifespans that a set of buffers of the target control unit is committed to an I/O operation. In another aspect, buffer over-commit logic determines a buffer over-commit value as, in one embodiment, inversely proportional to buffer lifespan. In another aspect, buffer over-commit logic determines a buffer over-commit value as, in one embodiment, proportional to the determined difference value and inversely proportional to buffer lifespan. Other features and aspects may be realized, depending upon the particular application.

Abstract: In one aspect of buffer credit management in accordance with the present description, buffer over-commit logic determines a buffer over-commit value as, in one embodiment, proportional to a determined difference value between the average duration of an I/O operation over data transmission channels connected to a target control unit, and an average of cumulative lifespans that a set of buffers of the target control unit is committed to an I/O operation. In another aspect, buffer over-commit logic determines a buffer over-commit value as, in one embodiment, inversely proportional to buffer lifespan. In another aspect, buffer over-commit logic determines a buffer over-commit value as, in one embodiment, proportional to the determined difference value and inversely proportional to buffer lifespan. Other features and aspects may be realized, depending upon the particular application.

Abstract: A computing system detects an input/output (I/O) device configuration error. The computing system includes at least one I/O device installed with firmware configured to control an I/O function, and a plurality of I/O ports installed on the at least one I/O device. At least one I/O port outputs a request to perform a current I/O configuration initialization and generates current I/O configuration data corresponding to the current I/O configuration initialization. A memory unit is configured to store the current I/O configuration data and previously generated I/O configuration data. The I/O device compares the current I/O configuration data to the previously generated I/O configuration data, and detects the I/O device configuration error in response to determining a mismatch between the current I/O configuration data and the previously generated I/O configuration data.

Abstract: A computer-implemented method for lock-free use of a non-preemptive system resource by a preemptive thread, which may be interrupted. The method comprises registering a non-preemptive system resource and a first level reclaim handler for the non-preemptive system resource with the kernel of an operating system, registering a second level reclaim handler with the kernel, wherein the second level reclaim handler is included in an application program, and running the application program as a preemptive thread using the non-preemptive system resource. The first level reclaim handler is code that is a part of the implementation of the non-preemptive system resource in the kernel. The second level reclaim handler is code that is part of the application and is registered with the kernel before the application uses the non-preemptive system resource. The method enables a preemptive thread using a non-preemptive system resource to be preempted without crashing.

Abstract: A computer-implemented method for lock-free use of a non-preemptive system resource by a preemptive thread, which may be interrupted. The method comprises registering a non-preemptive system resource and a first level reclaim handler for the non-preemptive system resource with the kernel of an operating system, registering a second level reclaim handler with the kernel, wherein the second level reclaim handler is included in an application program, and running the application program as a preemptive thread using the non-preemptive system resource. The first level reclaim handler is code that is a part of the implementation of the non-preemptive system resource in the kernel. The second level reclaim handler is code that is part of the application and is registered with the kernel before the application uses the non-preemptive system resource. The method enables a preemptive thread using a non-preemptive system resource to be preempted without crashing.