From owner-freebsd-current Mon Aug 26 17:42:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA27972 for current-outgoing; Mon, 26 Aug 1996 17:42:10 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA27966; Mon, 26 Aug 1996 17:42:07 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id AAA16894; Tue, 27 Aug 1996 00:41:37 GMT Date: Tue, 27 Aug 1996 09:41:37 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Terry Lambert cc: eric@ms.uky.edu, freebsd-fs@FreeBSD.ORG, current@FreeBSD.ORG Subject: vclean (was The VIVA file system) In-Reply-To: <199608262155.OAA23328@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 26 Aug 1996, Terry Lambert wrote: > The address space compression is interesting for vnode-based buffering; > FreeBSD currently uses this method, but... well, I've railed often > enough against vclean that I think everyone knows how I feel. > Some subsystems now depend on the ability to disassociate buffers from vnodes. For example, kill the session leader and the session terminal is revoked from all children and the deadfs is associated with the vnode. The only call that doesn't return an error is close() and the children eventually exit. I think what needs to be looked at is having more synchronized buffer cache/vnode recycling policies. Regards, Mike Hancock