From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 7 17:35:18 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9121616A4CE; Mon, 7 Jun 2004 17:35:18 +0000 (GMT) Received: from relay.transip.nl (relay.transip.nl [80.69.66.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3205B43D39; Mon, 7 Jun 2004 17:35:18 +0000 (GMT) (envelope-from ali@transip.nl) Received: from redguy (peris.demon.nl [212.238.139.202]) by relay.transip.nl (Postfix) with SMTP id 0D9ED34A33A; Mon, 7 Jun 2004 19:35:16 +0200 (CEST) Message-ID: <00bd01c44cb5$ccf5f840$0400a8c0@redguy> From: "Ali Niknam" To: "John Baldwin" , References: <00da01c44b3f$74d3d8c0$0400a8c0@redguy> <200406070827.21333.jhb@FreeBSD.org> Date: Mon, 7 Jun 2004 19:35:07 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailman-Approved-At: Tue, 08 Jun 2004 12:27:51 +0000 cc: Robert Watson Subject: Re: FreeBSD 5.2.1: Mutex/Spinlock starvation? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 17:35:18 -0000 > 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 | tel 0182-504424 | fax 0182-504460 Transip B.V. | http://www.transip.nl/ | Mensen met verstand van zaken.