From owner-freebsd-current Thu May 21 22:41:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08838 for freebsd-current-outgoing; Thu, 21 May 1998 22:41:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08822 for ; Thu, 21 May 1998 22:41:45 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id AAA02910; Fri, 22 May 1998 00:41:31 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805220541.AAA02910@dyson.iquest.net> Subject: Re: Explosion update on Softupdates - it is NOT CCD related In-Reply-To: from Michael Hancock at "May 22, 98 01:39:52 pm" To: michaelh@cet.co.jp (Michael Hancock) Date: Fri, 22 May 1998 00:41:31 -0500 (EST) Cc: karl@mcs.net, julian@whistle.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 21 May 1998, Karl Denninger wrote: > > > Diablo uses mmap to read, and write to do writes to the spool files. > > It also does a hell of a lot of flock()ing. > > It would seem that a lot of flocking would defeat the purpose of > softupdates. Or is it that softupdates defeats the purpose of flocking? > There appear to be some wierd, unforseen interactions between the softupdates and our VFS/VM code. I don't see it as a bug in anything as much as an oversight. I haven't really studied the issue very carefully yet, but the (or some kind of) problem exists. The ball should NOT be in Kirk's court, I think that it should be in mine right now. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message