new methods: ->read_iter() and ->write_iter()
authorAl Viro <viro@zeniv.linux.org.uk>
Tue, 11 Feb 2014 23:37:41 +0000 (18:37 -0500)
committerAl Viro <viro@zeniv.linux.org.uk>
Tue, 6 May 2014 21:36:00 +0000 (17:36 -0400)
commit293bc9822fa9b3c9d4b7893bcb241e085580771a
tree89aae8e9d832199906d413dcffd5b885bcee14fe
parent7f7f25e82d54870df24d415a7007fbd327da027b
new methods: ->read_iter() and ->write_iter()

Beginning to introduce those.  Just the callers for now, and it's
clumsier than it'll eventually become; once we finish converting
aio_read and aio_write instances, the things will get nicer.

For now, these guys are in parallel to ->aio_read() and ->aio_write();
they take iocb and iov_iter, with everything in iov_iter already
validated.  File offset is passed in iocb->ki_pos, iov/nr_segs -
in iov_iter.

Main concerns in that series are stack footprint and ability to
split the damn thing cleanly.

[fix from Peter Ujfalusi <peter.ujfalusi@ti.com> folded]

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Documentation/filesystems/Locking
Documentation/filesystems/vfs.txt
fs/aio.c
fs/file_table.c
fs/open.c
fs/read_write.c
include/linux/fs.h