summaryrefslogtreecommitdiffstats
path: root/fs/nfs
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2008-10-06 20:08:56 -0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2008-10-07 18:19:05 -0400
commitd7fb120774f062ce7db439863ab5d4190d6f989c (patch)
tree621ce0a776c3bc4b66d0cea87e06f6ea7ed79398 /fs/nfs
parent8491945f11c227400ef294d560f6d7aace76bc33 (diff)
downloadop-kernel-dev-d7fb120774f062ce7db439863ab5d4190d6f989c.zip
op-kernel-dev-d7fb120774f062ce7db439863ab5d4190d6f989c.tar.gz
NFS: Don't use range_cyclic for data integrity syncs
It is more efficient to write linearly starting from the beginning of the file. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/nfs')
-rw-r--r--fs/nfs/write.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/nfs/write.c b/fs/nfs/write.c
index 3229e21..9f98458 100644
--- a/fs/nfs/write.c
+++ b/fs/nfs/write.c
@@ -1427,8 +1427,9 @@ static int nfs_write_mapping(struct address_space *mapping, int how)
.bdi = mapping->backing_dev_info,
.sync_mode = WB_SYNC_NONE,
.nr_to_write = LONG_MAX,
+ .range_start = 0,
+ .range_end = LLONG_MAX,
.for_writepages = 1,
- .range_cyclic = 1,
};
int ret;
OpenPOWER on IntegriCloud