Date: Wed, 15 May 2002 08:51:01 -0700 From: Alfred Perlstein <bright@mu.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Richard Sharpe <rsharpe@ns.aus.com>, freebsd-hackers@freebsd.org Subject: Re: File locking, closes and performance in a distributed filesystemenv Message-ID: <20020515155101.GF1585@elvis.mu.org> In-Reply-To: <3CE21DE4.441F6B36@mindspring.com> References: <Pine.LNX.4.33.0205151117270.5078-100000@ns.aus.com> <3CE1F8E2.868B2965@mindspring.com> <20020515062425.GD1585@elvis.mu.org> <3CE21DE4.441F6B36@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Terry Lambert <tlambert2@mindspring.com> [020515 01:36] wrote: > Alfred Perlstein wrote: > > As Terry stated you can't do that, however you could cache that the > > VNODE has a lock, that would reduce the requirement for calling the > > ADVLOCK VOP. > You'd really have to know when the lock list went to NULL, to get > any benefit out of it, since locking would still end up being per-file > sticky. You could post-check after every successful unlock... but to > cache the remote state would mean another RPC to ask for locks, which > would just be front-loading the expense, instead of back-loading it. [snip] He could also maintain a local cache of this per vnode, basically maintain a mirror of the lock list locally in order to see if a remote op must be done. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020515155101.GF1585>