Filesystem: Add readv/writev handlers

The readv() and writev() support was implemented in terms of multiple
calls to the read and write handlers.  This imposes a problem on device
files which use an IO vector as single request entity.  For example a
low-level network device (e.g. BPF(4)) may use an IO vector to create
one frame from multiple protocol layers each with its own IO vector
entry.

1 files changed, 1 insertions, 20 deletions

diff --git a/cpukit/libcsupport/src/readv.c b/cpukit/libcsupport/src/readv.c
index e47f22850a..6a4e0579f3 100644
--- a/cpukit/libcsupport/src/readv.c
+++ b/cpukit/libcsupport/src/readv.c
@@ -36,31 +36,12 @@ ssize_t readv(
 )
 {
   ssize_t        total;
-  int            v;
   rtems_libio_t *iop;
 
   total = rtems_libio_iovec_eval( fd, iov, iovcnt, LIBIO_FLAGS_READ, &iop );
 
   if ( total > 0 ) {
-    /*
-     *  Now process the readv().
-     */
-    total = 0;
-    for ( v = 0 ; v < iovcnt ; v++ ) {
-      ssize_t bytes = ( *iop->pathinfo.handlers->read_h )(
-        iop,
-        iov[ v ].iov_base,
-        iov[ v ].iov_len
-      );
-
-      if ( bytes < 0 )
-        return -1;
-
-      total += bytes;
-
-      if ( bytes != iov[ v ].iov_len )
-        break;
-    }
+    total = ( *iop->pathinfo.handlers->readv_h )( iop, iov, iovcnt, total );
   }
 
   return total;