Whamcloud - gitweb
status: on ./mcreate I believe the client lock on the file and the mds
authorbraam <braam>
Mon, 24 Jun 2002 17:22:36 +0000 (17:22 +0000)
committerbraam <braam>
Mon, 24 Jun 2002 17:22:36 +0000 (17:22 +0000)
commit62de5fe80defed4774be0570fe9c9e75761e5aa3
treec98f2e4eb8e1686d362a0a0346ac001152efb582
parent7407323847ce2fdf665b915f5b465056302a998f
status: on ./mcreate I believe the client lock on the file and the mds
lock on the directory are both correctly enqueued.

- updated documentation regarding lock / resource refcounting
- removed unnecessary resource_getref before policy (thanks phil)
- local locks to addref, server locks don't
- variety of small fixes
- print lock/type names
- add one reference on lock for creation, put it away once for destroy
  [otherwise 0 ref locks can "live" and that causes the resources grief]
- small fix to change_resource
lustre/include/linux/lustre_dlm.h
lustre/ldlm/ldlm_lock.c
lustre/ldlm/ldlm_lockd.c
lustre/ldlm/ldlm_request.c
lustre/ldlm/ldlm_resource.c