summaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorWeston Andros Adamson <dros@primarydata.com>2014-11-12 20:08:00 +0300
committerTrond Myklebust <trond.myklebust@primarydata.com>2014-11-25 01:00:42 +0300
commitcb1410c71e0b6b2eba8c1890645a76ff86169d24 (patch)
tree22fb6770fed66df7d51676e25e5a525bdd352abe /crypto
parent6a74c0c9402b85647793da70edc9d6b097d54472 (diff)
downloadlinux-cb1410c71e0b6b2eba8c1890645a76ff86169d24.tar.xz
NFS: fix subtle change in COMMIT behavior
Recent work in the pgio layer made it possible for there to be more than one request per page. This caused a subtle change in commit behavior, because write.c:nfs_commit_unstable_pages compares the number of *pages* waiting for writeback against the number of requests on a commit list to choose when to send a COMMIT in a non-blocking flush. This is probably hard to hit in normal operation - you have to be using rsize/wsize < PAGE_SIZE, or pnfs with lots of boundaries that are not page aligned to have a noticeable change in behavior. Signed-off-by: Weston Andros Adamson <dros@primarydata.com> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions