From owner-freebsd-smp Fri Nov 17 16:28:18 2000 Delivered-To: freebsd-smp@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 4D72C37B479 for ; Fri, 17 Nov 2000 16:28:17 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAI0S3B09680 for ; Fri, 17 Nov 2000 16:28:03 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200011180021.QAA61821@freefall.freebsd.org> Date: Fri, 17 Nov 2000 16:28:45 -0800 (PST) From: John Baldwin To: smp@FreeBSD.org Subject: RE: cvs commit: src/sys/kern kern_timeout.c Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 18-Nov-00 John Baldwin wrote: > jhb 2000/11/17 16:21:01 PST > > Modified files: > sys/kern kern_timeout.c > Log: > Release sched_lock very briefly to give interrupts a chance to fire if we > are in softclock() for a long time. The old code already did an > splx()/slphigh() pair here, I just missed adding in the equivalent mutex > operations on sched_lock earlier. Before this I could get processes to hang (the box was still up, but one process was stuck, tying up its pty) though the box was still fine (I could login and do stuff) if I ran a buildworld -j X where X > 1. With this I built a kernel with -j 8 and am currently chugging through a -j 64 world. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message