Suparna Bhattacharya 20acaa18d0 [PATCH] ext3 sequential read regression fix ... ext3-get-blocks support caused ~20% degrade in Sequential read performance (tiobench). Problem is with marking the buffer boundary so IO can be submitted right away. Here is the patch to fix it. 2.6.18-rc6: ----------- # ./iotest 1048576+0 records in 1048576+0 records out 4294967296 bytes (4.3 GB) copied, 75.2726 seconds, 57.1 MB/s real 1m15.285s user 0m0.276s sys 0m3.884s 2.6.18-rc6 + fix: ----------------- [root@elm3a241 ~]# ./iotest 1048576+0 records in 1048576+0 records out 4294967296 bytes (4.3 GB) copied, 62.9356 seconds, 68.2 MB/s The boundary block check in ext3_get_blocks_handle needs to be adjusted against the count of blocks mapped in this call, now that it can map more than one block. Signed-off-by: Suparna Bhattacharya <suparna@in.ibm.com> Tested-by: Badari Pulavarty <pbadari@us.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>		2006-09-16 12:54:32 -07:00
..
acl.c
acl.h
balloc.c	[PATCH] ext3 filesystem bogus ENOSPC with reservation fix	2006-08-27 11:01:30 -07:00
bitmap.c
dir.c
file.c
fsync.c
hash.c
ialloc.c
inode.c	[PATCH] ext3 sequential read regression fix	2006-09-16 12:54:32 -07:00
ioctl.c
Makefile
namei.c	[PATCH] ext3: avoid triggering ext3_error on bad NFS file handle	2006-07-31 13:28:36 -07:00
namei.h
resize.c
super.c	[PATCH] knfsd: Make ext3 reject filehandles referring to invalid inode number	2006-09-16 12:54:31 -07:00
symlink.c
xattr_security.c
xattr_trusted.c
xattr_user.c
xattr.c
xattr.h