aboutsummaryrefslogtreecommitdiff
path: root/fs/jfs/jfs_umount.c
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2006-03-20 13:44:36 -0500
committerTrond Myklebust <Trond.Myklebust@netapp.com>2006-03-20 13:44:36 -0500
commitfad61490419b3e494f300e9b2579810ef3bcda31 (patch)
tree1bca68921a83d4dc0219aa8d46c3c8e8313965c2 /fs/jfs/jfs_umount.c
parente17b1fc4b35399935f00a635206e183d9292fe4f (diff)
nfs: Use UNSTABLE + COMMIT for NFS O_DIRECT writes
Currently NFS O_DIRECT writes use FILE_SYNC so that a COMMIT is not necessary. This simplifies the internal logic, but this could be a difficult workload for some servers. Instead, let's send UNSTABLE writes, and after they all complete, send a COMMIT for the dirty range. After the COMMIT returns successfully, then do the wake_up or fire off aio_complete(). Test plan: Async direct I/O tests against Solaris (or any server that requires committed unstable writes). Reboot server during test. Based on an earlier patch by Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/jfs/jfs_umount.c')
0 files changed, 0 insertions, 0 deletions