If a cache invalidation is triggered, and we happen to have a lot of
writebacks cached at the time, then the call to invalidate_inode_pages2()
will end up calling ->launder_page() on each and every dirty page in order
to sync its contents to disk, thus defeating write coalescing.
The following patch ensures that we try to sync the inode to disk before
calling invalidate_inode_pages2() so that we do the writeback as efficiently
as possible.
Reported-by: William Dauchy <william@xxxxxxxxx>
Reported-by: Pascal Bouchareine <pascal@xxxxxxxxx>
Signed-off-by: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
Tested-by: William Dauchy <william@xxxxxxxxx>
---
v2: Add check for regular file as per Jeff Layton's suggestion.
fs/nfs/inode.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
index af6e806..46ac6a6 100644
--- a/fs/nfs/inode.c
+++ b/fs/nfs/inode.c
@@ -965,7 +965,14 @@ static int nfs_invalidate_mapping(struct inode *inode, struct address_space *map
struct nfs_inode *nfsi = NFS_I(inode);
if (mapping->nrpages != 0) {
- int ret = invalidate_inode_pages2(mapping);
+ int ret;
+
+ if (S_ISREG(inode->i_mode)) {
+ ret = nfs_sync_mapping(mapping);
+ if (ret < 0)
+ return ret;
+ }
+ ret = invalidate_inode_pages2(mapping);
if (ret < 0)
return ret;
}
--
1.8.3.1
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
