From owner-freebsd-fs Tue Sep 5 5:49:42 2000 Delivered-To: freebsd-fs@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0552D37B422; Tue, 5 Sep 2000 05:49:39 -0700 (PDT) Received: from newsguy.com (p17-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.82]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id VAA26709; Tue, 5 Sep 2000 21:49:27 +0900 (JST) Message-ID: <39B4EBBB.9C7A5CAB@newsguy.com> Date: Tue, 05 Sep 2000 21:48:59 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Boris Popov Cc: freebsd-fs@FreeBSD.ORG, dillon@FreeBSD.ORG, semenu@FreeBSD.ORG, tegge@FreeBSD.ORG Subject: Re: CFR: nullfs, vm_objects and locks... (patch) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Boris Popov wrote: > > The simple solution for it is to integrate lock structure into > vnode and making vnode.v_vnlock initially point to it. Any filesystem > above can pickup the pointer and assign it to v_vnlock field in its own > vnode structure. If underlying filesystem doesn't provide any lock > structure then bad times are coming and each layer can maintain its own > lock state. How can it handle fs multiplexing? Ie, a single underlying layer with multiple non-stacked layers above? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@white.bunnies.bsdconspiracy.net OK, so the solar flares are my fault.. I am sorry, ok?!?! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message