lustre: get rid of messing with iovecs
* switch to ->read_iter/->write_iter
* keep a pointer to iov_iter instead of iov/nr_segs
* do not modify iovecs; use iov_iter_truncate()/iov_iter_advance() and
a new primitive - iov_iter_reexpand() (expand previously truncated
iterator) istead.
* (racy) check for lustre VMAs intersecting with iovecs kept for now as
for_each_iov() loop.
Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk>
Showing
- drivers/staging/lustre/lustre/include/lclient.h 1 addition, 10 deletionsdrivers/staging/lustre/lustre/include/lclient.h
- drivers/staging/lustre/lustre/lclient/lcommon_cl.c 3 additions, 45 deletionsdrivers/staging/lustre/lustre/lclient/lcommon_cl.c
- drivers/staging/lustre/lustre/llite/file.c 19 additions, 87 deletionsdrivers/staging/lustre/lustre/llite/file.c
- drivers/staging/lustre/lustre/llite/llite_internal.h 1 addition, 2 deletionsdrivers/staging/lustre/lustre/llite/llite_internal.h
- drivers/staging/lustre/lustre/llite/rw.c 1 addition, 2 deletionsdrivers/staging/lustre/lustre/llite/rw.c
- drivers/staging/lustre/lustre/llite/vvp_io.c 12 additions, 17 deletionsdrivers/staging/lustre/lustre/llite/vvp_io.c
- include/linux/uio.h 9 additions, 0 deletionsinclude/linux/uio.h
Please register or sign in to comment