From owner-freebsd-current Tue Apr 2 06:45:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA29083 for current-outgoing; Tue, 2 Apr 1996 06:45:49 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA29076 for ; Tue, 2 Apr 1996 06:45:46 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id JAA00446; Tue, 2 Apr 1996 09:45:11 -0500 (EST) From: "John S. Dyson" Message-Id: <199604021445.JAA00446@dyson.iquest.net> Subject: Re: calcru: negative time: To: bde@zeta.org.au (Bruce Evans) Date: Tue, 2 Apr 1996 09:45:11 -0500 (EST) Cc: bde@zeta.org.au, phk@critter.tfs.com, freebsd-current@freefall.freebsd.org, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199604021118.VAA10642@godzilla.zeta.org.au> from "Bruce Evans" at Apr 2, 96 09:18:01 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It (actually failing of a more complete test in mi_switch()) seems > to be connected with doing a bunch of disk accesses after the system > has been idle for some time. I suspect vm. I didn't like changing > splimp() in vm to splhigh(). > If there are some times where splhigh() is on for too long, that needs to be changed (we aren't using another interlock mechanism when we should be.) Splhigh is correct for it's intended purpose -- lock out ANY other access to the VM data structures. Splimp is just a hack in it's own right implying that the networking code is the ONLY code in the system that needs potentially concurrent access -- and that is potentially NOT true. John