READV(3P)
π READV(3P) β POSIX Programmer's Manual π
okay bestie, so this one's from the POSIX Programmer's Manual β the readv(3P) page specifically. Come sit with me, we're gonna read a vector together and it's gonna be iconic. π
π¨ PROLOG π¨
Heads up before we even start: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ β so if you're on Linux, go peek at the corresponding Linux manual page for the tea on Linux behavior. Orβ¦ the interface might not even be implemented on Linux at all. π Like, no cap, check first.
β¨ NAME β¨
readv β read a vector π
πΈ SYNOPSIS πΈ
#include <sys/uio.h>
ssize_t readv(int fildes, const struct iovec *iov, int iovcnt);
π DESCRIPTION π
So readv() is basically read()'s cooler sibling β it shall be equivalent to read(), except for the stuff we're about to spill below. π«Ά
What it does: it takes the input data and places it into the iovcnt buffers specified by the members of the iov array. That's iov[0], iov[1], β¦, iov[iovcnt-1]. A whole lil lineup. π
The iovcnt argument is valid if it's greater than 0 and less than or equal to {IOV_MAX}. That's the vibe check. β
Every single iovec entry specifies the base address and length of an area in memory where data should be placed. And here's the important bit, bestie: readv() shall always fill an area completely before proceeding to the next. No half-filled buffers, no skipping ahead. It's giving main character energy with commitment. π
And upon successful completion? readv() shall mark for update the last data access timestamp of the file. Timestamps updated, slay. β¨
π₯ RETURN VALUE π₯
Refer to read(). (Yeah that's it, go read that one, it's the source of truth fr fr.)
π ERRORS π
Refer to read().
In addition, the readv() function shall fail if:
EINVALβ the sum of theiov_lenvalues in theiovarray overflowed anssize_t. π Yeah, that's an overflow, we do not love that.
The readv() function may fail if:
EINVALβ theiovcntargument was less than or equal to 0, or greater than{IOV_MAX}. π
The following sections are informative. (Read: the required bits are done, everything from here is bonus lore. π¦)
π EXAMPLES π
π Reading Data into an Array
okay so the following example reads data from the file associated with the file descriptor fd into the buffers specified by members of the iov array. Watch and learn:
#include <sys/types.h>
#include <sys/uio.h>
#include <unistd.h>
...
ssize_t bytes_read;
int fd;
char buf0[20];
char buf1[30];
char buf2[40];
int iovcnt;
struct iovec iov[3];
iov[0].iov_base = buf0;
iov[0].iov_len = sizeof(buf0);
iov[1].iov_base = buf1;
iov[1].iov_len = sizeof(buf1);
iov[2].iov_base = buf2;
iov[2].iov_len = sizeof(buf2);
...
iovcnt = sizeof(iov) / sizeof(struct iovec);
bytes_read = readv(fd, iov, iovcnt);
...
Three buffers, one syscall. It's giving efficiency, it's giving organized. π
π§ APPLICATION USAGE π§
None. (Nothing to add, bestie, the example said it all. π )
π RATIONALE π
Refer to read().
β FUTURE DIRECTIONS β
None.
π SEE ALSO π
read()writev()
The Base Definitions volume of POSIX.1β2017, <sys_uio.h>
π COPYRIGHT π
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .
and that's the whole page, bestie!! π this one was brought to you by IEEE/The Open Group, dated 2017, and the manual name was READV(3P). go read some vectors, ily, bye!! πβ¨ππ¦
π¦ where this page comes from
- alpine 3.22: man-pages-posix 2017a-r0 Β· custom
- alpine 3.23: man-pages-posix 2017a-r0 Β· custom
- alpine 3.24: man-pages-posix 2017a-r0 Β· custom
- arch rolling: man-pages 6.19-1
- arch rolling: man-pages 6.20-1 Β· BSD-2-Clause AND BSD-3-Clause AND BSD-4.3TAHOE AND BSD-4-Clause-UC AND GPL-1.0-or-later AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND LGPL-3.0-linking-exception AND LGPL-3.0-or-later AND LicenseRef-Public-Domain AND LicenseRef-UltraPermissive AND Linux-man-pages-1-para AND Linux-man-pages-copyleft AND Linux-man-pages-copyleft-2-para AND Linux-man-pages-copyleft-var AND MIT AND Spencer-94
- nixpkgs unstable: man-pages-posix 2017a
- opensuse-leap 16.0: man-pages-posix 2017a-160000.4.1 Β· SUSE-IEEE
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms