readv.2: Wording fix: readv() and writev() are system calls, not functions

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2010-11-16 07:12:27 +01:00
parent 99149d6ee0
commit e7d8245112
1 changed files with 7 additions and 7 deletions

View File

@ -55,7 +55,7 @@ _BSD_SOURCE
.SH DESCRIPTION
The
.BR readv ()
function reads
system call reads
.I iovcnt
buffers from the file associated with the file descriptor
.I fd
@ -65,7 +65,7 @@ into the buffers described by
.PP
The
.BR writev ()
function writes
system call writes
.I iovcnt
buffers of data described by
.I iov
@ -94,13 +94,13 @@ struct iovec {
.PP
The
.BR readv ()
function works just like
system call works just like
.BR read (2)
except that multiple buffers are filled.
.PP
The
.BR writev ()
function works just like
system call works just like
.BR write (2)
except that multiple buffers are written out.
.PP
@ -211,9 +211,9 @@ first appeared in Linux 2.6.30; library support was added in glibc 2.10.
.SH "CONFORMING TO"
.BR readv (),
.BR writev ():
4.4BSD (these functions first appeared in 4.2BSD), POSIX.1-2001.
4.4BSD (these system calls first appeared in 4.2BSD), POSIX.1-2001.
Linux libc5 used \fIsize_t\fP as the type of the \fIiovcnt\fP argument,
and \fIint\fP as return type for these functions.
and \fIint\fP as the return type.
.\" The readv/writev system calls were buggy before Linux 1.3.40.
.\" (Says release.libc.)
@ -253,7 +253,7 @@ The wrapper function for
performs the analogous task using a temporary buffer and a call to
.BR write (2).
.SH BUGS
It is not advisable to mix calls to functions like
It is not advisable to mix calls to
.BR readv ()
or
.BR writev (),