Date: Thu, 15 Feb 2007 15:08:12 -0500 From: Garrett Wollman <wollman@csail.mit.edu> To: Tomas Olsson <tol@it.su.se> Cc: freebsd-fs@freebsd.org, arla-drinkers@stacken.kth.se Subject: Re: Arla on FreeBSD Message-ID: <17876.48556.909232.678959@khavrinen.csail.mit.edu> In-Reply-To: <lsrhctn6393.fsf@kashyyyk.ite.kth.se> References: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB6@ms05.mailstreet2003.net> <45D1F30A.6080403@freebsd.org> <eqsut3$6a3$1@sea.gmane.org> <20070213192906.U726@chrishome.localnet> <20070214162938.GA96725@keira.kiwi-computer.com> <20070214173211.L1054@chrishome.localnet> <20070214170808.GC96725@keira.kiwi-computer.com> <lsrvei45pq1.fsf@kashyyyk.ite.kth.se> <20070215044707.GA39168@deviant.kiev.zoral.com.ua> <lsrmz3f680v.fsf_-_@kashyyyk.ite.kth.se> <20070215104537.GC39168@deviant.kiev.zoral.com.ua> <lsrhctn6393.fsf@kashyyyk.ite.kth.se>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On 15 Feb 2007 12:59:04 +0100, Tomas Olsson <tol@it.su.se> said: > We currently open the cache files from nnpfs' VOPs, are there any risks > (deadlock?) involved if one passes an absolute path to vn_open() in such a > context? A possible compromise (although I don't think vn_open() can handle it) is to skip the naming layer altogether and just have nnpfs and arlad pass around file handles (of the getfh()/VFS_FHTOVP() variety). Then you don't have to worry about naming since you're just accessing the cache files by inode, and the kernel takes care of managing the vnodes for you. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17876.48556.909232.678959>