xtc_aio.h

/*-
 * Copyright (c) 2026, The XTC Project
 * @stability stable
 * Use of this source code is governed by the ISC License.
 *
 * src/inc/xtc_aio.h
 *      Async file I/O for fibers.  A read/write/fsync that suspends the
 *      calling fiber and resumes it on completion, keeping the loop live
 *      for other work meanwhile.
 *
 *      This is a SINGLE, PORTABLE async-file-I/O API: write storage code
 *      once as though true AIO is always available, and it runs unchanged
 *      everywhere libxtc builds.  Where the host has a native completion
 *      engine (io_uring on Linux, IOCP on Windows) the call uses it; where
 *      it does not, the call transparently offloads to the blocking thread
 *      pool -- the SAME API and the same observable behavior (the fiber
 *      parks, the loop keeps running, the call returns the byte count or a
 *      negative errno).  The caller never branches on the platform.
 *
 *      Must be called from a fiber running on a loop; off a loop the op
 *      runs synchronously.  Returns the byte count transferred (>= 0) or
 *      a negative errno; xtc_aio_fsync returns 0 or a negative errno.
 *      See xtc_aio(3).
 */
 
#ifndef XTC_AIO_H
#define XTC_AIO_H
 
#include "xtc_export.h"
 
#include <stdint.h>
#if !defined(_WIN32)
#include <sys/uio.h>     /* struct iovec (POSIX scatter/gather) */
#endif
 
/*
 * PUBLIC: int xtc_aio_pread __P((int, void *, uint32_t, int64_t));
 * PUBLIC: int xtc_aio_pwrite __P((int, const void *, uint32_t, int64_t));
 * PUBLIC: int xtc_aio_fsync __P((int));
 * PUBLIC: int xtc_aio_fdatasync __P((int));
 */
 
XTC_API int xtc_aio_pread(int fd, void *buf, uint32_t len, int64_t off);
XTC_API int xtc_aio_pwrite(int fd, const void *buf, uint32_t len, int64_t off);
 
#if !defined(_WIN32)
/*
 * PUBLIC: int xtc_aio_preadv __P((int, const struct iovec *, int, int64_t));
 * PUBLIC: int xtc_aio_pwritev __P((int, const struct iovec *, int, int64_t));
 *
 * Vectored (scatter/gather) variants: read into / write from the
 * iovcnt buffers described by iov, at file offset off, as one atomic
 * positioned op -- the async-fiber analog of preadv(2)/pwritev(2).
 * They exist so code that already builds struct iovec arrays (a WAL
 * writer, PostgreSQL's smgr/md layer, any readv/writev consumer) can
 * move to libxtc without flattening or looping.  Same semantics as the
 * scalar calls: the fiber parks and the loop stays live; returns the
 * total byte count transferred (>= 0) or a negative errno.
 *
 * Where the host has io_uring the op is submitted natively
 * (IORING_OP_READV/WRITEV); elsewhere it transparently offloads to the
 * blocking pool (preadv/pwritev on a worker thread) -- identical
 * observable behavior, as with the scalar API.  iovcnt must be in
 * [1, IOV_MAX]; out of range returns -EINVAL (the AIO surface's
 * negative-errno convention), so a caller cannot force an unbounded
 * submission.  Direct-I/O builds validate each iovec base and the
 * total length against the device alignment.
 *
 * POSIX only: Windows lacks preadv/pwritev and struct iovec; a
 * WSABUF/OVERLAPPED-scatter port is future work, so these are not
 * declared there.  The scalar xtc_aio_pread/pwrite remain available on
 * every platform.
 */
XTC_API int xtc_aio_preadv(int fd, const struct iovec *iov, int iovcnt, int64_t off);
XTC_API int xtc_aio_pwritev(int fd, const struct iovec *iov, int iovcnt, int64_t off);
#endif /* !_WIN32 */
 
XTC_API int xtc_aio_fsync(int fd);       /* full sync: data + metadata */
XTC_API int xtc_aio_fdatasync(int fd);   /* data only (the page/WAL flush hot path) */
 
/*
 * The internal / test hook __xtc_aio_force_offload (force the
 * blocking-pool offload path even on a host with a native completion
 * engine) is library-internal (the __ prefix) and not part of the
 * stable API; it lives in "aio_int.h", not in this installed public
 * header.
 */
 
#endif /* XTC_AIO_H */