From owner-cvs-src@FreeBSD.ORG Tue Jul 13 21:37:48 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C917416A4CE; Tue, 13 Jul 2004 21:37:48 +0000 (GMT) Received: from av5-1-sn3.vrr.skanova.net (av5-1-sn3.vrr.skanova.net [81.228.9.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 568B543D1D; Tue, 13 Jul 2004 21:37:48 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av5-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 83DFF37EDC; Tue, 13 Jul 2004 23:37:47 +0200 (CEST) Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net [81.228.9.178]) by av5-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 75E2B37E68; Tue, 13 Jul 2004 23:37:47 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 3D42938009; Tue, 13 Jul 2004 23:37:47 +0200 (CEST) From: "Daniel Eriksson" To: "'John Baldwin'" , Date: Tue, 13 Jul 2004 23:36:17 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <200407132049.i6DKnDMv076454@repoman.freebsd.org> Importance: Normal Subject: RE: cvs commit: src/sys/kern sched_4bsd.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2004 21:37:48 -0000 John Baldwin wrote: > Set TDF_NEEDRESCHED when a higher priority thread is scheduled in > sched_add() rather than just doing it in sched_wakeup(). The old > ithread preemption code used to set NEEDRESCHED=20 > unconditionally if it > didn't preempt which masked this bug in SCHED_4BSD. Does this mean it should be safe to turn preemption back on in param.h = (for a kernel using SHED_4BSD)? Or is this not related to the hard hangs = reported over the last week? /Daniel