From owner-freebsd-current Fri Feb 27 01:58:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28266 for freebsd-current-outgoing; Fri, 27 Feb 1998 01:58:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28254 for ; Fri, 27 Feb 1998 01:58:18 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id JAA05443; Fri, 27 Feb 1998 09:57:34 GMT Date: Fri, 27 Feb 1998 18:57:34 +0900 (JST) From: Michael Hancock To: Eivind Eklund cc: freebsd-current@FreeBSD.ORG Subject: Re: VFS_VRELE - WILLRELE must die In-Reply-To: <19980227103412.52813@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Feb 1998, Eivind Eklund wrote: > Uhm - what might 'RELE' stand for? My _guess_ is that it is a > shortened form of 'RELEASE', but that's not certain - there are lots > of other possibilities. > > If it is 'release', I'd like VFS_VRELE to be renamed to VFS_VRELEASE. Have a look at vrele() and vput() in vfs_subr.c, calls to these are scattered all over the fs code. VFS_VRELE would be more familiar than VFS_VRELEASE to people working on the fs code. Most of the implementations do the same thing so I'll probably add a vfsop section with vfs_vrele(mp,vp) to phk's vfs_default.c which I stumbled onto today. This can be done anytime later though. If these are accepted then we can start working horizontally across the offending VOPs starting with vop_create. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message