Date: Tue, 05 Sep 2000 21:48:59 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Boris Popov <bp@butya.kz> 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: <39B4EBBB.9C7A5CAB@newsguy.com> References: <Pine.BSF.4.10.10009051705530.79991-100000@lion.butya.kz>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39B4EBBB.9C7A5CAB>