summaryrefslogtreecommitdiff
path: root/fs/proc
diff options
context:
space:
mode:
authorJeff Moyer <jmoyer@redhat.com>2007-10-16 23:27:20 -0700
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-10-17 08:42:53 -0700
commit41d10da3717409de33d5441f2f6d8f072ab3fbb6 (patch)
tree4822afef881132248a7c91ba6eb33065f3209f2b /fs/proc
parentc17ac85504efec5f3a9b0c5b05bffd6f30e5b655 (diff)
downloadlinux-3.10-41d10da3717409de33d5441f2f6d8f072ab3fbb6.tar.gz
linux-3.10-41d10da3717409de33d5441f2f6d8f072ab3fbb6.tar.bz2
linux-3.10-41d10da3717409de33d5441f2f6d8f072ab3fbb6.zip
aio: account I/O wait time properly
Some months back I proposed changing the schedule() call in read_events to an io_schedule(): http://osdir.com/ml/linux.kernel.aio.general/2006-10/msg00024.html This was rejected as there are AIO operations that do not initiate disk I/O. I've had another look at the problem, and the only AIO operation that will not initiate disk I/O is IOCB_CMD_NOOP. However, this command isn't even wired up! Given that it doesn't work, and hasn't for *years*, I'm going to suggest again that we do proper I/O accounting when using AIO. Signed-off-by: Jeff Moyer <jmoyer@redhat.com> Acked-by: Zach Brown <zach.brown@oracle.com> Cc: Benjamin LaHaise <bcrl@kvack.org> Cc: Suparna Bhattacharya <suparna@in.ibm.com> Cc: Badari Pulavarty <pbadari@us.ibm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/proc')
0 files changed, 0 insertions, 0 deletions