Don't hold on to the afs_xvcache lock while creating a symlink
authorRainer Toebbicke <rtb@pclella.cern.ch>
Mon, 21 Jun 2010 10:02:46 +0000 (12:02 +0200)
committerDerrick Brashear <shadow@dementia.org>
Wed, 23 Jun 2010 22:04:52 +0000 (15:04 -0700)
commitc39aee89c0649561041e7d955dd3db40629f2570
treeabdc3634e32dfed7ff8cdf6b5afa0cf568d4cb13
parentbd3f8adfe02aa09eedeec3cff824745eb749e473
Don't hold on to the afs_xvcache lock while creating a symlink

Holding the afs_xvcache lock over the RPC while creating a symlink is a
severe blow to performance as look-ups from other tasks likely
require the lock. Drop the lock and rely solely on the fileserver
to detect a clash with a same entry created simultaneously.

Change-Id: Ia6de353bd9dc003addf5f3be7a8f3e769247a513
Reviewed-on: http://gerrit.openafs.org/2233
Tested-by: Derrick Brashear <shadow@dementia.org>
Reviewed-by: Derrick Brashear <shadow@dementia.org>
src/afs/VNOPS/afs_vnop_symlink.c