new methods: ->read_iter() and ->write_iter() sandbox/pawelo/kdbus-next-wip
authorAl Viro <viro@zeniv.linux.org.uk>
Tue, 11 Feb 2014 23:37:41 +0000 (18:37 -0500)
committerPaul Osmialowski <p.osmialowsk@samsung.com>
Wed, 15 Apr 2015 15:45:09 +0000 (17:45 +0200)
commit778a43408f732464f684f06af742eacdb9748eb8
tree87eb906dd43462d30129a0451ea514e5bbfaf840
parent8d4f4bf0cc146699097ba8417b03e0bef8b0f976
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]

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