From owner-freebsd-hackers Tue Sep 4 10:10:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 751F137B405; Tue, 4 Sep 2001 10:10:35 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id A665628E08; Wed, 5 Sep 2001 00:10:31 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 9BA1C28C76; Wed, 5 Sep 2001 00:10:31 +0700 (ALMST) Date: Wed, 5 Sep 2001 00:10:31 +0700 (ALMST) From: Boris Popov To: Maxim Sobolev Cc: Poul-Henning Kamp , Brent Verner , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Junior Kernel Hacker task: improve vnode->v_tag In-Reply-To: <200109041343.f84DhO097646@vega.vega.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 4 Sep 2001, Maxim Sobolev wrote: > > The places which inspect v_tag will have to be changed to use > > strcmp() then... > > I think that we can add a new vnode flag, say VCANLOCK, so that each > particular VFS can set it if it supports locking, which should allow > to remove pre-defined VFS list from the IS_LOCKING_VFS macro. I can > produce a patch if it sounds reasonably. I'm not sure if this a right thing to do. Under SMPng each filesystem is ought to implement correct vnode locking, i.e. vop_nolock() and friends shouldn't exist. -- Boris Popov http://rbp.euro.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message