On Thu, 5 Jul 2007, Jakob Goldbach wrote:
anyone else know for sure whether locking and client-side
caching can be disabled on a per file basis?
What do *you* mean by locking and caching?
Lustre is a POSIX compliant filesystem. This requires locking during
systemcalls. These locks are cached on the client until revoked by a
server.
You could probably set the number of locks keept on the client to zero
but this will kill performance. This setting is pr. filesystem not
filelevel.
fcntl locking is advisory locking of single files across systemcalls
and is completely orthogonal to intra-systemcall locking.
/Jakob
I am interested in disabling locking and client-side caching so that
the application itself can provide its own enforcement of file consistency
semantics and provide its own caching. I understand that Lustre is a
POSIX-compliant system; what I am unsure of is whether the locking and
caching system that provides such compliance can be disabled on a
per file basis.
--pmd
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
