AIO_WRITE(3P)

✨ AIO_WRITE(3P) ✨

okay bestie, welcome to the POSIX Programmer's Manual 💖 this page is literally part of it. quick heads up tho — the Linux implementation of this interface may differ (so go consult the corresponding Linux manual page for the deets on Linux behavior), or honestly the interface may not be implemented on Linux at all. vibe check passed either way, let's go 🦋

---

🌸 NAME 🌸

aio_write — asynchronous write to a file. yes, the asynchronous one. she does not wait. she queues and dips 💅

---

✨ SYNOPSIS ✨

#include <aio.h>

int aio_write(struct aiocb *aiocbp);

---

💜 DESCRIPTION 💜

So the aio_write() function shall write aiocbp->aio_nbytes to the file associated with aiocbp->aio_fildes, from the buffer pointed to by aiocbp->aio_buf. And she shall return when the write request has been initiated or, at a minimum, queued to the file or device. queued and out, no waiting around 😌

If prioritized I/O is supported for this file, then the asynchronous operation shall be submitted at a priority equal to a base scheduling priority minus aiocbp->aio_reqprio. And if Thread Execution Scheduling is not supported, then that base scheduling priority is the one of the calling process; otherwise, the base scheduling priority is the one of the calling thread. iykyk 🧚

The aiocbp argument may be used as an argument to aio_error() and aio_return() to figure out the error status and return status, respectively, of the asynchronous operation while it's still proceeding. main character energy, checking in on your own op ✨

The aiocbp argument points to an aiocb structure. And here's the scary part, so listen up: if the buffer pointed to by aiocbp->aio_buf or the control block pointed to by aiocbp becomes an illegal address prior to asynchronous I/O completion, then the behavior is undefined. 💀 not a drill.

If O_APPEND is not set for the file descriptor aio_fildes, then the requested operation shall take place at the absolute position in the file as given by aio_offset, as if lseek() were called immediately prior to the operation with an offset equal to aio_offset and a whence equal to SEEK_SET. If O_APPEND is set for the file descriptor, or if aio_fildes is associated with a device that is incapable of seeking, then write operations append to the file in the same order as the calls were made — except under circumstances described in Section 2.8.2, Asynchronous I/O. And after a successful call to enqueue an asynchronous I/O operation, the value of the file offset for the file is unspecified. yeah. unspecified. we don't know her 🙈

The aio_sigevent member specifies the notification which occurs when the request is completed. cute little ping when she's done 🎀

The aiocbp->aio_lio_opcode field shall be ignored by aio_write(). ignored. not read. not considered. moving on 💅

Simultaneous asynchronous operations using the same aiocbp produce undefined results. so like… don't do that bestie 😭

If synchronized I/O is enabled on the file associated with aiocbp->aio_fildes, the behavior of this function shall be according to the definitions of synchronized I/O data integrity completion, and synchronized I/O file integrity completion.

For any system action that changes the process memory space while an asynchronous I/O is outstanding to the address range being changed, the result of that action is undefined. UNDEFINED. don't touch the memory while she's working 💀

For regular files, no data transfer shall occur past the offset maximum established in the open file description associated with aiocbp->aio_fildes. she knows her limits, periodt.

---

🔥 RETURN VALUE 🔥

The aio_write() function shall return the value zero if the I/O operation is successfully queued; otherwise, the function shall return the value -1 and set errno to indicate the error. zero = slay, -1 = something went wrong, check errno 💖

---

👑 ERRORS 👑

The aio_write() function shall fail if:

• EAGAIN — The requested asynchronous I/O operation was not queued due to system resource limitations. system said no room bestie 😭

Each of the following conditions may be detected synchronously at the time of the call to aio_write(), or asynchronously. If any of the conditions below are detected synchronously, the aio_write() function shall return -1 and set errno to the corresponding value. If any of the conditions below are detected asynchronously, the return status of the asynchronous operation shall be set to -1, and the error status of the asynchronous operation is set to the corresponding value. two paths, same drama ✨

• EBADF — The aiocbp->aio_fildes argument is not a valid file descriptor open for writing.
• EINVAL — The file offset value implied by aiocbp->aio_offset would be invalid, aiocbp->aio_reqprio is not a valid value, or aiocbp->aio_nbytes is an invalid value.

In the case that the aio_write() successfully queues the I/O operation, the return status of the asynchronous operation shall be one of the values normally returned by the write() function call. And if the operation is successfully queued but is subsequently canceled or encounters an error, the error status for the asynchronous operation contains one of the values normally set by the write() function call, or one of the following:

• EBADF — The aiocbp->aio_fildes argument is not a valid file descriptor open for writing.
• EINVAL — The file offset value implied by aiocbp->aio_offset would be invalid.
• ECANCELED — The requested I/O was canceled before the I/O completed due to an explicit aio_cancel() request.

The following condition may be detected synchronously or asynchronously:

• EFBIG — The file is a regular file, aiobcp->aio_nbytes is greater than 0, and the starting offset in aiobcp->aio_offset is at or beyond the offset maximum in the open file description associated with aiocbp->aio_fildes.

The following sections are informative. (translation: cute but not binding 🫶)

---

🌈 EXAMPLES 🌈

None.

---

🍓 APPLICATION USAGE 🍓

None.

---

🦋 RATIONALE 🦋

None.

---

⭐ FUTURE DIRECTIONS ⭐

None.

---

💖 SEE ALSO 💖

• Section 2.8.2, Asynchronous I/O
• aio_cancel()
• aio_error()
• aio_read()
• aio_return()
• close()
• exec
• exit()
• fork()
• lio_listio()
• lseek()
• write()

The Base Definitions volume of POSIX.1‐2017, <aio.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 lil masterpiece was brought to you by IEEE/The Open Group, dated 2017 — thanks for coming to my TED talk, now go queue some async writes and stay hydrated 🫶🌸