diff options
author | Christoph Hellwig <hch@infradead.org> | 2010-02-09 11:43:49 +1100 |
---|---|---|
committer | Dave Chinner <david@fromorbit.com> | 2010-02-09 11:43:49 +1100 |
commit | 07fec73625dc0db6f9aed68019918208a2ca53f5 (patch) | |
tree | 04f4ad3f829c3d64d6b2a3c0bddf11a4374eb93d /Makefile | |
parent | e8b217e7530c6a073ac69f1c85b922d93fdf5647 (diff) | |
download | linux-stable-07fec73625dc0db6f9aed68019918208a2ca53f5.tar.gz linux-stable-07fec73625dc0db6f9aed68019918208a2ca53f5.tar.bz2 linux-stable-07fec73625dc0db6f9aed68019918208a2ca53f5.zip |
xfs: log changed inodes instead of writing them synchronously
When an inode has already be flushed delayed write,
xfs_inode_clean() returns true and hence xfs_fs_write_inode() can
return on a synchronous inode write without having written the
inode. Currently these sycnhronous writes only come sync(1),
unmount, a sycnhronous NFS export and cachefiles so should be
relatively rare and out of common performance paths.
Realistically, a synchronous inode write is not necessary here; we
can avoid writing the inode by logging any non-transactional changes
that are pending. This needs to be done with synchronous
transactions, but it avoids seeking between the log and inode
clusters as we do now. We don't force the log if the inode is
pinned, though, so this differs from the fsync case. For normal
sys_sync and unmount behaviour this is fine because we do a
synchronous log force in xfs_sync_data which is called from the
->sync_fs code.
It does however break the NFS synchronous export guarantees for now,
but work is under way to fix this at a higher level or for the
higher level to provide an additional flag in the writeback control
to tell us that a log force is needed.
Portions of this patch are based on work from Dave Chinner.
Signed-off-by: Christoph Hellwig <hch@infradead.org>
Reviewed-by: Dave Chinner <david@fromorbit.com>
Reviewed-by: Alex Elder <aelder@sgi.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions