diff options
author | 2011-07-12 13:42:01 -0400 | |
---|---|---|
committer | 2011-07-12 13:42:01 -0400 | |
commit | 87ed5eb44ad9338b1617a0e78dea81d681325298 (patch) | |
tree | 17570d0d4cab601d13efad77d5aaaa02a8433dab /tools/perf/scripts/python | |
parent | NFSv4.1: do not use deviceids after MDS clientid invalidation (diff) | |
download | linux-dev-87ed5eb44ad9338b1617a0e78dea81d681325298.tar.xz linux-dev-87ed5eb44ad9338b1617a0e78dea81d681325298.zip |
NFS: Don't use DATA_SYNC writes
If we're writing back data, and the FLUSH_STABLE flag is set, then we
always want to use NFS_FILE_SYNC, since we're always in a situation where
we're doing page reclaim, and so we want to free up the page as quickly
as possible.
If we're in the FLUSH_COND_STABLE case, then we either want to use another
unstable write (if we have to do a commit anyway) or again, we want to
use NFS_FILE_SYNC because we know that we have no more pages to write
out.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions