summaryrefslogtreecommitdiff
path: root/fs/cifs/file.c
diff options
context:
space:
mode:
authorSteve French <sfrench@us.ibm.com>2009-02-23 15:21:59 +0000
committerSteve French <sfrench@us.ibm.com>2009-03-12 01:36:20 +0000
commitbe652445fdccb8e5d4391928c3b45324ea37f9e1 (patch)
tree9912b7022b06d3ad08ff73d71505f018fe96922b /fs/cifs/file.c
parent10e70afa75c90702b2326abaaa757d6b7835636f (diff)
downloadlwn-be652445fdccb8e5d4391928c3b45324ea37f9e1.tar.gz
lwn-be652445fdccb8e5d4391928c3b45324ea37f9e1.zip
[CIFS] Add new nostrictsync cifs mount option to avoid slow SMB flush
If this mount option is set, when an application does an fsync call then the cifs client does not send an SMB Flush to the server (to force the server to write all dirty data for this file immediately to disk), although cifs still sends all dirty (cached) file data to the server and waits for the server to respond to the write write. Since SMB Flush can be very slow, and some servers may be reliable enough (to risk delaying slightly flushing the data to disk on the server), turning on this option may be useful to improve performance for applications that fsync too much, at a small risk of server crash. If this mount option is not set, by default cifs will send an SMB flush request (and wait for a response) on every fsync call. Signed-off-by: Steve French <sfrench@us.ibm.com>
Diffstat (limited to 'fs/cifs/file.c')
-rw-r--r--fs/cifs/file.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/cifs/file.c b/fs/cifs/file.c
index 83b4741b6ad0..6411f5f65d72 100644
--- a/fs/cifs/file.c
+++ b/fs/cifs/file.c
@@ -1538,7 +1538,8 @@ int cifs_fsync(struct file *file, struct dentry *dentry, int datasync)
rc = CIFS_I(inode)->write_behind_rc;
CIFS_I(inode)->write_behind_rc = 0;
tcon = CIFS_SB(inode->i_sb)->tcon;
- if (!rc && tcon && smbfile)
+ if (!rc && tcon && smbfile &&
+ !(cifs_sb->mnt_cifs_flags & CIFS_MOUNT_NO_SSYNC))
rc = CIFSSMBFlush(xid, tcon, smbfile->netfid);
}