From owner-freebsd-current  Tue Jul  2 19:57:35 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EE9DD37B400
	for <freebsd-current@freebsd.org>; Tue,  2 Jul 2002 19:57:29 -0700 (PDT)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4377E43E3B
	for <freebsd-current@freebsd.org>; Tue,  2 Jul 2002 19:57:29 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA18939;
	Tue, 2 Jul 2002 22:57:28 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g632uwB24486;
	Tue, 2 Jul 2002 22:56:58 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15650.26618.523781.562050@grasshopper.cs.duke.edu>
Date: Tue, 2 Jul 2002 22:56:58 -0400 (EDT)
To: Julian Elischer <julian@elischer.org>
Cc: freebsd-current@freebsd.org
Subject: Re: KSE signal problems still
In-Reply-To: <Pine.BSF.4.21.0207021927590.97650-100000@InterJet.elischer.org>
References: <15650.23048.273299.232384@grasshopper.cs.duke.edu>
	<Pine.BSF.4.21.0207021927590.97650-100000@InterJet.elischer.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


Julian Elischer writes:
 > > 
 > > However, it does seem a bit silly, as we end up dropping
 > > and-reaquiring the sched lock quite a few times:
 > 
 > That's why I just asked you to test the concept..
 > If I know that just aquiring it here is ok, 
 > (I presume you tried doing some work like this)
 > that tells me that this code isn't called from some odd place,
 > with the sched lock already set.
 > 
 > (that and code inspection of course..)
 > 
 > Now we know it works we can try optimise it..
 > 
 > I'm going home now for dinner, 
 > so if you feel like checking this or something mor optimal in,
 > be my guest :-)

OK, I've checked in the unoptimized fix.   Please do optimize it when
you get a chance.

Thanks,

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message