* John Baldwin <[EMAIL PROTECTED]> [011008 11:46] wrote: > > On 08-Oct-01 [EMAIL PROTECTED] wrote: > > In doing some kernel profiling analysis it seems that splx is taking up big > > chunks of time. > > That's becaause splx() can result in interrupts blocked during an spl() getting > a chance to run, including soft interrrupts such as softclock and the network > software interrupts. Note that splx itself is quick, it is the releasing of > interrupts which is expensive, which will only happen on the "outside" splx() > if you have nested spl's.
It's not the releasing that's expensive, it's _running_ them in the context of the party that does the splx() that makes them look expensive. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message