Date: Tue, 5 Sep 2000 21:11:11 +0700 (ALMST) From: Boris Popov <bp@butya.kz> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: freebsd-fs@FreeBSD.ORG, dillon@FreeBSD.ORG, semenu@FreeBSD.ORG, tegge@FreeBSD.ORG Subject: Re: CFR: nullfs, vm_objects and locks... (patch) Message-ID: <Pine.BSF.4.10.10009052108550.81844-100000@lion.butya.kz> In-Reply-To: <39B4EBBB.9C7A5CAB@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Sep 2000, Daniel C. Sobral 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? Just like in the stacking case: access to vnode on the underlying filesystem should be serialized which is done by proper(shared) locking. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10009052108550.81844-100000>