On 23 March 2013 20:11, Eric van Gyzen wrote:
> At work, we discovered that our application's IPMI thread would often use a
> lot of CPU time. The KCS thread uses DELAY to wait for the BMC, so it can
> run without sleeping for a "long" time with a slow BMC. It also holds the
> ipmi_softc.ipmi_lo
On Saturday, March 23, 2013 11:11:20 pm Eric van Gyzen wrote:
> At work, we discovered that our application's IPMI thread would often
> use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC,
> so it can run without sleeping for a "long" time with a slow BMC. It
> also holds the
On 25.03.2013 02:38, Alexander V. Chernikov wrote:
> On 24.03.2013 07:11, Eric van Gyzen wrote:
>> At work, we discovered that our application's IPMI thread would often
>> use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC, so
>> it can run without sleeping for a "long" time with
On 24.03.2013 07:11, Eric van Gyzen wrote:
At work, we discovered that our application's IPMI thread would often
use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC, so
it can run without sleeping for a "long" time with a slow BMC. It also
holds the ipmi_softc.ipmi_lock during th
At work, we discovered that our application's IPMI thread would often
use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC,
so it can run without sleeping for a "long" time with a slow BMC. It
also holds the ipmi_softc.ipmi_lock during this time. When using
adaptive mutexes,