FreeBSD 5.2.1: Mutex/Spinlock starvation?

[Ali Niknam]

> There isn't a timeout.  Rather, the lock spins so long as the current
> owning thread is executing on another CPU.

Interesting. Is there a way to 'lock' CPU's so that they always run on
'another' CPU ?

Unfortunately as we speak the server is down again :( This all makes me
wonder wether I should simply go back to 4.10.
I decreased the maximum number of apache children to 1400 and the server
seems to be barely holding on:
last pid:  2483;  load averages: 75.77, 28.63, 11.40    up 0+00:04:32
19:35:07
1438 processes:2 running, 294 sleeping, 1142 lock
CPU states:  6.2% user,  0.0% nice, 62.6% system,  7.5% interrupt, 23.8%
idle
Mem: 698M Active, 27M Inact, 209M Wired, 440K Cache, 96M Buf, 1068M Free
Swap: 512M Total, 512M Free


Are there anymore quite stable things to do ? That is except for upping to
current, which I frankly feel is too dangerous...

-- 
 Ali Niknam <ali at transip.nl> | tel 0182-504424 | fax 0182-504460
 Transip B.V. | http://www.transip.nl/ | Mensen met verstand van zaken.