Sha256: 7d45e428b136cbacd9fc7dc497fa21edc235b742346802d0856f0b4bd45f84e2
Contents?: true
Size: 1.55 KB
Versions: 8
Compression:
Stored size: 1.55 KB
Contents
.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com> .\" .\" SPDX-License-Identifier: LGPL-2.0-or-later .\" .TH io_uring_prep_writev 3 "November 15, 2021" "liburing-2.1" "liburing Manual" .SH NAME io_uring_prep_writev - prepare vector I/O write request .SH SYNOPSIS .nf .BR "#include <liburing.h>" .PP .BI "void io_uring_prep_writev(struct io_uring_sqe *sqe," .BI " int fd," .BI " const struct iovec *iovecs," .BI " unsigned nr_vecs," .BI " __u64 offset)" .PP .SH DESCRIPTION .PP The io_uring_prep_writev() prepares a vectored IO write request. The submission queue entry .I sqe is setup to use the file descriptor .I fd to start writing .I nr_vecs from the .I iovecs array at the specified .I offset. On files that support seeking, if the offset is set to .B -1, the write operation commences at the file offset, and the file offset is incremented by the number of bytes written. See .BR write (2) for more details. Note that for an async API, reading and updating the current file offset may result in unpredictable behavior, unless access to the file is serialized. It is not encouraged to use this feature, if it's possible to provide the desired IO offset from the application or library. On files that are not capable of seeking, the offset is ignored. After the write has been prepared it can be submitted with one of the submit functions. .SH RETURN VALUE None .SH SEE ALSO .BR io_uring_get_sqe (3), io_uring_prep_write (3), io_uring_prep_writev2 (3), io_uring_submit (3)
Version data entries
8 entries across 8 versions & 1 rubygems