summaryrefslogtreecommitdiffstats
path: root/fs/namespace.c
diff options
context:
space:
mode:
authorDave Chinner <dchinner@redhat.com>2013-11-22 00:41:16 +0100
committerBen Myers <bpm@sgi.com>2013-12-11 22:23:04 +0100
commitf9b395a8ef8f34d19cae2cde361e19c96e097fad (patch)
tree647d39c42d63704ae5b142edf76981d8dfd92256 /fs/namespace.c
parentxfs: fix calculation of freed inode cluster blocks (diff)
downloadlinux-f9b395a8ef8f34d19cae2cde361e19c96e097fad.tar.xz
linux-f9b395a8ef8f34d19cae2cde361e19c96e097fad.zip
xfs: align initial file allocations correctly
The function xfs_bmap_isaeof() is used to indicate that an allocation is occurring at or past the end of file, and as such should be aligned to the underlying storage geometry if possible. Commit 27a3f8f ("xfs: introduce xfs_bmap_last_extent") changed the behaviour of this function for empty files - it turned off allocation alignment for this case accidentally. Hence large initial allocations from direct IO are not getting correctly aligned to the underlying geometry, and that is cause write performance to drop in alignment sensitive configurations. Fix it by considering allocation into empty files as requiring aligned allocation again. Signed-off-by: Dave Chinner <dchinner@redhat.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Ben Myers <bpm@sgi.com>
Diffstat (limited to 'fs/namespace.c')
0 files changed, 0 insertions, 0 deletions