From owner-freebsd-arch Tue Feb 6 8:32:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 8948D37B4EC; Tue, 6 Feb 2001 08:32:03 -0800 (PST) Received: from fwd07.sul.t-online.com by mailout02.sul.t-online.com with smtp id 14QB27-00052q-00; Tue, 06 Feb 2001 17:31:59 +0100 Received: from frolic.no-support.loc (520094253176-0001@[217.80.111.106]) by fmrl07.sul.t-online.com with esmtp id 14QB1l-2Kk35mC; Tue, 6 Feb 2001 17:31:37 +0100 Received: (from bjoern@localhost) by frolic.no-support.loc (8.11.1/8.9.3) id f16GLp600648; Tue, 6 Feb 2001 17:21:51 +0100 (CET) (envelope-from bjoern) From: Bjoern Fischer Date: Tue, 6 Feb 2001 17:21:50 +0100 To: Boris Popov Cc: freebsd-arch@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: vnode interlock API Message-ID: <20010206172150.A528@frolic.no-support.loc> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bp@butya.kz on Tue, Feb 06, 2001 at 05:00:03PM +0600 X-Sender: 520094253176-0001@t-dialin.net Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, > Few months ago simple locks used for vnode interlock were replaced > by mutexes. It causes additional pain for externally maintained > filesystems and lowers portability of the code between -stable and > -current. > > So, I suggest to introduce two macro definitions which will hide > implementation details for interlocks: > > #define VI_LOCK(vp) mtx_enter(&(vp)->v_interlock, MTX_DEF) > #define VI_UNLOCK(vp) mtx_exit(&(vp)->v_interlock, MTX_DEF) BTW, does this mean that -current vnode locking works sufficiently enough to support stacked file systems a la Eric Zadok's FiST software? Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message