mm/writeback: discard NR_UNSTABLE_NFS, use NR_WRITEBACK instead

[linux-block.git] / fs / nfs / internal.h

diff --git a/fs/nfs/internal.h b/fs/nfs/internal.h
index 1f32a9fbfdafbb21c57db8d60097bc1593837499..6673a77884d9daeeee1f11f565ef541779e28fa7 100644 (file)
--- a/fs/nfs/internal.h
+++ b/fs/nfs/internal.h
@@ -668,7 +668,8 @@ void nfs_super_set_maxbytes(struct super_block *sb, __u64 maxfilesize)
 }
 
 /*
- * Record the page as unstable and mark its inode as dirty.
+ * Record the page as unstable (an extra writeback period) and mark its
+ * inode as dirty.
  */
 static inline
 void nfs_mark_page_unstable(struct page *page, struct nfs_commit_info *cinfo)
@@ -676,8 +677,11 @@ void nfs_mark_page_unstable(struct page *page, struct nfs_commit_info *cinfo)
        if (!cinfo->dreq) {
                struct inode *inode = page_file_mapping(page)->host;
 
-               inc_node_page_state(page, NR_UNSTABLE_NFS);
-               inc_wb_stat(&inode_to_bdi(inode)->wb, WB_RECLAIMABLE);
+               /* This page is really still in write-back - just that the
+                * writeback is happening on the server now.
+                */
+               inc_node_page_state(page, NR_WRITEBACK);
+               inc_wb_stat(&inode_to_bdi(inode)->wb, WB_WRITEBACK);
                __mark_inode_dirty(inode, I_DIRTY_DATASYNC);
        }
 }