s3: Avoid oplock break by storing timestamps with gpfs_set_times
authorChristof Schmitt <cs@samba.org>
Tue, 7 Jan 2014 18:55:46 +0000 (11:55 -0700)
committerChristof Schmitt <cs@samba.org>
Wed, 8 Jan 2014 23:04:47 +0000 (00:04 +0100)
commitd1dacd62bbff93351763ff339cca13ba8180dd89
tree39e9dd8b8f75f1d92c22605366a30b44e002da5c
parentca931e460460ffe46735f98b31db47220772d566
s3: Avoid oplock break by storing timestamps with gpfs_set_times

The gpfs_set_times API call allows setting timestamps directly in GPFS
without going through the utime() call. Using this API call fixes an
unecessary oplock break when a client sends a SET_FILE_ALLOCATION_INFO
request and no other client has opened the file. The call to utime()
triggers the oplock break through the Linux kernel. Using the
gpfs_set_times call for updating the timestamp avoids the call to
utime() and the oplock break.

Signed-off-by: Christof Schmitt <cs@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
Autobuild-User(master): Christof Schmitt <cs@samba.org>
Autobuild-Date(master): Thu Jan  9 00:04:48 CET 2014 on sn-devel-104
docs-xml/manpages/vfs_gpfs.8.xml
source3/modules/gpfs.c
source3/modules/vfs_gpfs.c
source3/modules/vfs_gpfs.h