From owner-freebsd-current Sun Mar 1 14:44:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17239 for freebsd-current-outgoing; Sun, 1 Mar 1998 14:44:15 -0800 (PST) (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 OAA17212 for ; Sun, 1 Mar 1998 14:44:07 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA03448; Sun, 1 Mar 1998 17:43:35 -0500 (EST) (envelope-from toor) Message-Id: <199803012243.RAA03448@dyson.iquest.net> Subject: Re: VM: Process hangs sleeping on vmpfw In-Reply-To: <199803012130.NAA09796@dingo.cdrom.com> from Mike Smith at "Mar 1, 98 01:30:46 pm" To: mike@smith.net.au (Mike Smith) Date: Sun, 1 Mar 1998 17:43:35 -0500 (EST) Cc: dima@tejblum.dnttm.rssi.ru, tlambert@primenet.com, FreeBSD-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 Mike Smith said: > > Unless I'm mistaken here the contention is between Terry's point of > view where all filesystems should be stackable, and Dima's where > filesystems may optionally make themselves stackable. > Yes. > > If I'm right, do we have a decision one way or the other? And if so, a > *comprehensive* set of patches that cover the conversion> > No, if we go with the approach of all filesystems stackable in a *traditional* way, we will likely have coherency problems. I don't have time to do all of the research, but it seems that others are starting to do so (and that is a VERY GOOD thing.) So, for those filesystems that it doesn't make sense to use the traditional approaches, and minor mistakes made, then we'll have to teach the code some exceptions. > > I'm happy to fight the style-nit and getting-it-done wars, but I gotta > have the ammunition first. 8) > Get it done. I don't like style-nit wars. (Other's on -core might disagree, but we'll discuss that privately if need be.) We can ALWAYS work the style nit issues. I don't like to see stuff that is a-priori known to be "messy" committed to the tree though. IF we have to choose between form and substance, let's go with substance. It is best to try to balance both though. Never commit code that you know to be incorrect. Remember, we are also considering stabilizing the system soon, and that means things like VM and VFS MUST be working well so that the upper level functionality has a chance to be debugged and made to be working well!!! I am "on the mend" right now, at least doing some commits that have been languishing in my queue for a week or so. (However, they broke some read/write, mmap coherency -- to be fixed in an hour or so.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message