summaryrefslogtreecommitdiffstats
path: root/fs/nfs/write.c
diff options
context:
space:
mode:
authorTrond Myklebust <trond.myklebust@primarydata.com>2015-12-28 13:30:42 -0500
committerTrond Myklebust <trond.myklebust@primarydata.com>2015-12-28 13:30:42 -0500
commitb0ac1bd2bbfd5e500432714e55a791c4d394047f (patch)
tree47d3df28fd2355a110891df0b6139f73796e8fa0 /fs/nfs/write.c
parent1a093ceb053832c25b92f3cf26b957543c7baf9b (diff)
downloadop-kernel-dev-b0ac1bd2bbfd5e500432714e55a791c4d394047f.zip
op-kernel-dev-b0ac1bd2bbfd5e500432714e55a791c4d394047f.tar.gz
NFS: Background flush should not be low priority
Background flush is needed in order to satisfy the global page limits. Don't subvert by reducing the priority. This should also address a write starvation issue that was reported by Neil Brown. Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'fs/nfs/write.c')
-rw-r--r--fs/nfs/write.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/nfs/write.c b/fs/nfs/write.c
index 7b93164..7a4fe7d 100644
--- a/fs/nfs/write.c
+++ b/fs/nfs/write.c
@@ -247,8 +247,6 @@ static int wb_priority(struct writeback_control *wbc)
return FLUSH_HIGHPRI | FLUSH_STABLE;
if (wbc->sync_mode == WB_SYNC_ALL)
ret = FLUSH_COND_STABLE;
- if (wbc->for_kupdate || wbc->for_background)
- ret |= FLUSH_LOWPRI;
return ret;
}
OpenPOWER on IntegriCloud